From cc25393425517b15a17cd0c279505c715e780e48 Mon Sep 17 00:00:00 2001 From: Martin Trigaux Date: Tue, 3 Nov 2015 11:44:14 +0100 Subject: [PATCH] [ADD] .pot files make gettext --- locale/sources/accounting.pot | 7324 ++++++++++++++++++++++++++++++ locale/sources/applications.pot | 22 + locale/sources/crm.pot | 1163 +++++ locale/sources/expenses.pot | 22 + locale/sources/index.pot | 22 + locale/sources/inventory.pot | 2873 ++++++++++++ locale/sources/point_of_sale.pot | 638 +++ locale/sources/purchase.pot | 469 ++ locale/sources/recruitment.pot | 22 + 9 files changed, 12555 insertions(+) create mode 100644 locale/sources/accounting.pot create mode 100644 locale/sources/applications.pot create mode 100644 locale/sources/crm.pot create mode 100644 locale/sources/expenses.pot create mode 100644 locale/sources/index.pot create mode 100644 locale/sources/inventory.pot create mode 100644 locale/sources/point_of_sale.pot create mode 100644 locale/sources/purchase.pot create mode 100644 locale/sources/recruitment.pot diff --git a/locale/sources/accounting.pot b/locale/sources/accounting.pot new file mode 100644 index 000000000..b68f92f16 --- /dev/null +++ b/locale/sources/accounting.pot @@ -0,0 +1,7324 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2015-11-03 11:43+0100\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" + +#: ../../accounting.rst:5 +msgid "Accounting" +msgstr "" + +#: ../../accounting/bank.rst:3 +msgid "Bank & Cash" +msgstr "" + +#: ../../accounting/bank/feeds.rst:3 +msgid "Bank Feeds" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:3 +msgid "Import Coda statement files (Belgium only)" +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." +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." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:14 +msgid "Test now the feature `with this sample CODA file `__" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:17 +#: ../../accounting/bank/feeds/manual.rst:12 +#: ../../accounting/bank/feeds/ofx.rst:18 +#: ../../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:20 +#: ../../accounting/bank/setup/foreign_currency.rst:22 +#: ../../accounting/bank/setup/manage_cash_register.rst:9 +#: ../../accounting/others/adviser/assets.rst:24 +#: ../../accounting/others/adviser/budget.rst:18 +#: ../../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/application.rst:32 +#: ../../accounting/others/taxes/retention.rst:23 +#: ../../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_discounts.rst:15 +#: ../../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/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 +#: ../../accounting/receivables/customer_payments/paypal.rst:23 +#: ../../accounting/receivables/getting_paid/automated_followups.rst:31 +msgid "Configuration" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:20 +msgid "Install the CODA feature" +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 `_" +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." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:33 +msgid "Import your first CODA file" +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." +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." +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." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:55 +msgid "Importing CODA files" +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**." +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." +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." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:78 +#: ../../accounting/bank/feeds/qif.rst:65 +msgid ":doc:`ofx`" +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 +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.rst:3 +#: ../../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" +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." +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." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:24 +msgid "Create your Bank Statements" +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." +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." +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." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:44 +msgid "When you are done, click on **SAVE**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:47 +msgid "Reconcile your Bank Statements" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:49 +msgid "You can choose to directly reconcile the statement by clicking on the button |manual04|" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:54 +msgid "You can also start the reconciliation process from the dashboard by clicking on **Reconcile # Items**." +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**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:68 +msgid "Hit CTRL-Enter to reconcile all the balanced items on the sheets." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:71 +msgid "Close Bank Statements from the reconciliation" +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|." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:78 +msgid "Otherwise, click on |manual08| to open the statement and correct the issue." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:84 +msgid "Close Bank Statements" +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." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:92 +msgid "To close the bank statement, just click on **Validate**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:99 +msgid ":doc:`../reconciliation/use_cases`" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:100 +#: ../../accounting/bank/reconciliation/use_cases.rst:115 +msgid ":doc:`../feeds/synchronize`" +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:3 +msgid "Import OFX statement files" +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." +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." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:15 +msgid "Test now the feature `with this sample OFX file `__" +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." +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." +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." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:46 +msgid "Importing OFX files" +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**." +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." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:65 +#: ../../accounting/bank/feeds/qif.rst:66 +msgid ":doc:`coda`" +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:3 +msgid "Import QIF statement files" +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." +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." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:16 +msgid "Test now the feature `with this sample QIF file `__" +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." +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." +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." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:47 +msgid "Importing QIF files" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:3 +msgid "How to synchronize Odoo with your bank?" +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 `__" +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." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:19 +msgid "In order to connect with the banks, Odoo uses two web-services:" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:21 +msgid "Plaid: for the main banks in the U.S." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:23 +msgid "Yodlee: for all other banks" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:29 +msgid "Odoo Online Users" +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**." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:36 +msgid "Odoo Enterprise Users" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:38 +msgid "If you plan to use a bank interface with your Odoo Enterprise subscription, contact `Odoo Support `__ in order to get the credentials to sync Yodlee or Plaid with your bank accounts." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:43 +msgid "Once you get your credentials, you can register them from the :menuselection:`Configuration --> Settings` menu of the Accounting application." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:47 +msgid "Sync your bank feeds" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:49 +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." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:57 +msgid "In the bank form, from the Bank Account tab, set the bank feeds option to **Bank Synchronization**." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:63 +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." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:67 +msgid "Once you filled in your credentials, your bank feeds will be synchronized every 4 hours." +msgstr "" + +#: ../../accounting/bank/misc.rst:3 +msgid "MISC" +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 record checks received, record them on the bank account on which you plan to deposit them. Once you select the bank account (or check journal is 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 deposit 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 fills all the checks contained in this deposit for the matching. (2 checks were in this batch deposit the example below)" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:124 +#: ../../accounting/payables/pay/sepa.rst:113 +#: ../../accounting/receivables/customer_payments/paypal.rst:132 +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 "Inter Bank Tranfers" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:5 +msgid "A company might have several bank accounts or cash registers. Within odoo it is possible to handle internal transfers of money with only a couple of clicks." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:9 +msgid "We will take the following example to illustrate. My company has two bank accounts and I want to transfer 50.000 euros from one of our bank accounts to the another one." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:17 +msgid "Check your Chart of Accounts and default transfer account" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:19 +msgid "To handle internal transfers you need a transfer account in your charts of account. Odoo will generate an account automatically based on the country of your chart of account. To parameter your chart of account and check the default transfer account go into your the accounting module, select :menuselection:`Configuration --> Settings`." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:25 +msgid "Your chart of accounts will be pre-installed depending on the country specified during your registration, it cannot be changed." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:31 +msgid "The default transfer account will automatically be generated as well depending on your country's legislation. If necessary it can be modified from the same page." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:39 +msgid "Create a second bank account / Journal" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:41 +msgid "Before we can register an internal transfer we need to add a new bank to our accounting dashboard. To do so enter the accounting module, click on :menuselection:`Configuration --> Bank Accounts`. Create a new bank account. You should fill in the **Account Number**. You can also create and edit your bank to specify your bank's details." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:50 +msgid "By saving the changes you now have 2 bank accounts." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:56 +msgid "Register an internal transfer from one bank to another." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:58 +msgid "We will now transfer 50.000 euros from our **Bank** to our **Bank BE57 0633 9533 1498** account." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:62 +msgid "Log an internal transfer" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:64 +msgid "The first step is to register the internal paiement. To do so, go into your accounting dashboard. click on the **more** button of one of your banks and select :menuselection:`New --> Internal transfer`." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:71 +msgid "Create a new payment. The payment type will automatically be set to internal transfer. Select the **Bank** you want to transfer to, specify the **Amount** and add a **Memo** if you wish." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:76 +msgid "The memo is important if you wish to automatically reconcile (`see `_)." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:81 +msgid "Save and confirm the changes to register the payment." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:83 +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 +msgid "Import bank statements and reconcile" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:92 +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 +msgid "That is because we did not import the bank statement confirming the departure and arrival 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 +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 +msgid "The following window will open:" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:120 +msgid "You need to choose counterparts for the paiement. Select the correct bank statement line corresponding to the paiement and click on the **reconcile** button. Close the statement to finish the transaction" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:127 +msgid "The same steps will need to be repeated once you receive your second bank statement. Note that if you specify the correct amount, and the same memo in both bank statement and payment transaction 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/overview/terminologies.rst:19 +msgid "Bank Reconciliation" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:3 +msgid "Configure model of entries" +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." +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." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:16 +msgid "Create 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`." +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." +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." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:36 +msgid "Save your changes when you are done." +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." +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`" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:49 +msgid "Register your payments based on a reconciliation model" +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." +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." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:61 +msgid "Finally, click on **Reconcile** to finish the process." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:65 +#: ../../accounting/bank/reconciliation/use_cases.rst:116 +msgid ":doc:`../feeds/manual`" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:66 +#: ../../accounting/bank/reconciliation/use_cases.rst:114 +msgid ":doc:`../feeds/ofx`" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:67 +msgid ":doc:`use_cases`" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:3 +msgid "Use cases in the bank reconciliation process?" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:8 +msgid "Linking your bank statements with your accounting can be a lot of work. You need to find invoices back, relate payments and that amount of administration can cast a lot of time. Luckily, with Odoo you can very easily link your invoices or any other payment with your bank statements." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:14 +msgid "Two reconciliation processes exist in Odoo." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:16 +msgid "We can directly register a payment on the invoices" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:17 +msgid "We can reconcile open invoices with bank statements" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:22 +msgid "No special configuration is necessary to register invoices. All we need to do is install the accounting app." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:29 +msgid "User cases" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:32 +msgid "Case 1: Payments registration" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:34 +msgid "We received the payment proof for our invoice of 2100 euros issued to Smith & Co." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:37 +msgid "We start at our issued Invoice of 2100 euros for Smith & Co. Because the sold product is a service we demand an immediate payment. Our accountant only handles the bank statements at the end of week, so we have to mark the invoice as paid so we can remember we can start the service with our customer." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:43 +msgid "Our customer send us a payment confirmation. We can thus register a payment and mark the invoice as paid." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:49 +msgid "By clicking on **register payment,** we are telling Odoo that our customer paid the Invoice. We thus have to specify the amount and the payment method" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:56 +msgid "We can always find the payment back from the Invoice by clicking on the :menuselection:`Info --> Open Payment`." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:62 +msgid "The invoice has been paid and **the reconciliation has been done automatically.**" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:66 +msgid "Case 2: Bank statements reconciliations" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:68 +msgid "We start at our issued Invoice of 3000 euros for Smith & Co. Let's also assume that other Invoices are open for different customers." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:74 +msgid "We receive our bank statement and not only the invoice of Smith & Co has been paid, the one of Buzz of 92 euros as well." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:77 +msgid "**Import** or **Create** the bank statements. Please refer to the documents from the Bank Feeds section." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:83 +msgid "On the dashboard, click on **Reconcile # Items**" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:88 +msgid "If everything was right (correct partner name, right amount) odoo will do the reconciliations **automatically**." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:94 +msgid "If some issues are found, you will need to take **manual actions**." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:96 +msgid "For example, if the partner is missing from your bank statement, just fill it in :" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:102 +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:110 +msgid "Hit CTRL-Enter to reconcile all the balanced items in the sheet." +msgstr "" + +#: ../../accounting/bank/setup.rst:3 +msgid "Setup" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:2 +msgid "Set up your new bank account" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:4 +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." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:9 +msgid "Go to the list of your bank accounts" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:11 +msgid "Go to :menuselection:`Configuration --> Settings --> Configure your company bank accounts` > The bank accounts are configured on the company information. You have to be in the edit mode to be able to do your changes." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:21 +msgid "If you are working in a multi-company environnement, you have to switch company to add, edit or delete bank accounts on another company." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:24 +msgid "Add or edit a bank account" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:26 +msgid "Click on **Add an item** to add a new bank account. If you want to edit one, simply click on the line." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:33 +msgid "If the bank account type is IBAN, Odoo will check if the number is valid" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:39 +msgid "View *Bank Account* in our Online Demonstration" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:50 +msgid "The initial balance of a bank statement will be set to the closing balance of the previous one within the same journal automatically." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:52 +msgid "As you may notice in the journal form, a dedicated account has been generated automatically at the bank account creation." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:55 +msgid "Delete a bank account or credit card account" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:57 +msgid "Click on the trashcan icon |image5| in the list of your bank accounts to remove one bank account." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:3 +msgid "How to manage a bank in a foreign currency?" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:5 +msgid "In Odoo, every transaction is recorded in the default currency of the company. Reports are all based on the currency of the company. But for transactions occurring in another currency, Odoo stores both the value in the currency of the company and the value in the currency of the transaction." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:11 +msgid "When you have a bank account in a foreign currencies, for every transaction, Odoo stores two values:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:14 +msgid "The debit/credit in the currency of the company" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:16 +msgid "The debit/credit in the currency of the bank account" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:18 +msgid "Currency rates are updated automatically using yahoo.com, or the European Central bank web-services." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:25 +msgid "Activate the multi-currency feature" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:27 +msgid "In order to allow your company to work with multiple currencies, you should activate the multi-currency mode. In the accounting application, go into :menuselection:`Configuration --> Settings --> Accounting & Finance Features` make sure the **Allow Multi-currencies** box is ticked. Provide a **Currency Exchange Gain / Loss** account, then click on **Apply**." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:34 +msgid "Configure currencies" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:36 +msgid "Once the Odoo is configured to support multiple currencies, you should activate the currencies you plan to work with. To do that, go the menu :menuselection:`Configuration --> Currencies`. All the currencies are created by default, but you should activate the ones you plan to support. (to activate a currency, check his active field)" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:42 +msgid "After having activated the currencies, you can configure the parameters to automate the currency rate update. These options are also in the settings of the Accounting application, in the bottom of the page:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:49 +msgid "Click on the **Update Now** link to update the currency rates now." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:52 +msgid "Create a new bank account" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:54 +msgid "In the accounting application, we first go to :menuselection:`Configuration --> Accounting / Bank account`, and we create a new one." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:60 +msgid "Once you save this bank account, Odoo will create all the documents for you:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:63 +msgid "An account in the trial balance" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:65 +msgid "A journal in your dashboard" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:67 +msgid "Information about the bank account in the footer of your invoices if checked the box **Show in Invoices Footer**" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:71 +msgid "Example: A vendor bill in a foreign currency" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:73 +msgid "Based on the above example, let's assume we receive the following bill from a supplier in China." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:76 +msgid "In the :menuselection:`Purchase --> Vendor Bills` , this is what you could see:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:81 +msgid "Once you are ready to pay this bill, click on register payment on the bill to record a payment." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:87 +msgid "That's all you have to do. Odoo will automatically post the foreign exchange gain or loss at the reconciliation of the payment with the invoice, depending if the currency rate increased or decreased between the invoice and the payment date." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:92 +msgid "Note that you can pay a foreign bill with another currency. In such a case, Odoo will automatically convert between the two currencies." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:96 +msgid "Customers Statements" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:98 +msgid "Customers and vendor statements are managed in the currency of the invoice. So, the amount due by your customer (to your vendor) is always expressed in the currency of the invoice." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:102 +msgid "If you have several invoices with different currencies for the same customer, Odoo will split the customer statement by currency, as shown in the report below." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:109 +msgid "In the above report, the account receivable associated to Camptocamp is not managed in a secondary currency, which means that it keeps every transaction in his own currency. If you prefer, you can set the account receivable of this customer with a secondary currency and all his debts will automatically be converted in this currency." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:115 +msgid "In such a case, the customer statement always has only one currency. In general, this is not what the customer expect as he prefers to see the amounts in the currency of the invoices he received;" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:3 +msgid "How to manage a cash register?" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:5 +msgid "The cash register is a journal to register receivings and payments transactions. It calculates the total money in and out, computing the total balance." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:14 +msgid "Configure the Cash journal in :menuselection:`Accounting --> Configuration --> Journals`." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:17 +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:25 +msgid "Usage" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:28 +msgid "How to register cash payments?" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:30 +msgid "To register a cash payment specific to another customer, you should follow these steps:" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:33 +msgid "Go to :menuselection:`Accounting --> Dashboard --> Cash --> Register Transactions`" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:36 +msgid "Fill in the start and ending balance" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:38 +msgid "Register the transactions, specifying the customers linked to the transaction" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:41 +msgid "Put money in" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:43 +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 +msgid "Take money out" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:53 +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 +msgid "The transactions will be added to the current cash payment registration." +msgstr "" + +#: ../../accounting/others.rst:3 +#: ../../accounting/receivables/customer_invoices/overview.rst:108 +msgid "Others" +msgstr "" + +#: ../../accounting/others/adviser.rst:3 +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:66 +msgid "View *Asset Types* in our Online Demonstration" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:69 +msgid "Create assets manually" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:71 +msgid "To register an asset manually, go to the menu :menuselection:`Adviser --> Assets`." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:77 +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:83 +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:88 +msgid "Explanation of the fields:" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:94 +msgid "Try creating an *Asset* in our online demonstration" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:97 +msgid "Create assets automatically from a supplier bill" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:99 +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:106 +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:113 +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:117 +msgid "How to deprecate an asset?" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:119 +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:124 +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:131 +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:136 +msgid "How to modify an existing asset?" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:138 +msgid "Click on :guilabel:`Modify Depreciation`" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:139 +msgid "Change the number of depreciation" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:141 +msgid "Odoo will automatically recompute a new depreciation board." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:144 +msgid "How to record the sale or disposal of an asset?" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:146 +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 financial budget?" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:8 +msgid "Managing budgets is an essential part of running a business. It allows you to measure your actual financial performance against the planned one. Odoo manages its budgets using both General and Analytic Accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:12 +msgid "We will use the following example to illustrate. We just started a project with Smith&Co and we would like to budget the incomes and expenses of that project. We plan to have a revenue of 1000 and we don't want to spend more than 700." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:20 +msgid "First we need to install the relevant apps to use budgeting. The main module is the accounting app. Go in the app module and install the **Accounting and Finance** app." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:27 +msgid "Further configuration is as well necessary. Go to :menuselection:`Accounting module --> Configuration --> Settings` and enable the **Budget management** feature" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:34 +msgid "If we want to be precise and point specific invoices and vendors bills to our budget, you should enable the Analytic accounting as well. If we don't we will only be able to budget the total amount of general accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:40 +msgid "Budgetary Positions" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:42 +msgid "Budgetary positions are the general accounts for which you want to keep budgets (typically expense or income accounts). They need to be defined so Odoo can know it which accounts he needs to go get the budget information. Some might be already installed with your chart of accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:48 +msgid "To define the positions enter the :menuselection:`Accounting module --> Configuration --> Budgetary Positions`." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:51 +msgid "For our example we need to define what accounts relates to our project's expenses. Create a position and add items to select the accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:57 +msgid "In this case we select the three relevant accounts used wherein we will book our expenses." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:63 +msgid "Click on *Select*." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:68 +msgid "Save the changes to confirm your Budgetary position." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:70 +msgid "Repeat this steps to create a revenue budgetary position. Only in this case select the relevant income accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:74 +msgid "Analytical account" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:76 +msgid "If you wish to point specific invoices or vendor bills to your budget you need to use analytical accounting. Odoo needs to know which costs or expenses are relevant to a specified budget. To do so we need to link our invoices and expenses to a defined analytical account. Create an analytical account by entering the Accounting module and clicking :menuselection:`Advisers --> Analytic Accounts --> Open Charts`. Create a new Account called Smith&Co project and select the related partner." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:88 +msgid "Set a budget" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:90 +msgid "Let's now set our targets for our budget. We specified that we expect to gain 1000 with this project and we would like not to spend more than 700." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:94 +msgid "To set those targets, enter the accounting app, select :menuselection:`Advisers --> Budgets` and create a new Budget." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:97 +msgid "We have to give a name to the budget. In this case we'll call it \"Smith Project\". Select the period wherein the budget will be applicable. Next add an item to specify your targets in the Budget Line." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:104 +msgid "Select the Budgetary Position related to the Budget Line. In other words, select the position that points to the accounts you want to budget. In this case we will start with our 700 maximum charge target. Select the \"Cost\" Budgetary Position and specify the Planned Amount. As we are recording a cost, we need to specify a **negative amount**. Finally, select the corresponding analytic account." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:114 +msgid "Click on **Save & new** to input the revenue budget. The Budgetary Position is Revenue and the Planned Amount is 1000. Save and close" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:117 +msgid "You'll need to **Confirm** and **Approve** the budget." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:120 +msgid "Check your budget" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:122 +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:127 +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:131 +msgid "for more information about booking invoices and purchase orders see:" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:133 +msgid ":doc:`../../receivables/customer_invoices/overview`" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:134 +msgid ":doc:`../../../purchase/overview/from_po_to_invoice`" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:136 +msgid "Go back in the budget list and find the Smith Project." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:138 +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:147 +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/analytic.rst:3 +msgid "Analytic" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:3 +msgid "How to track costs of purchases, expenses, subcontracting?" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:8 +msgid "Thanks to analytical accounting we can track costs of purchases, expenses and subcontracting in the accounting module." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:11 +msgid "We'll take the following example. We sold a consulting package for a customer. The package is all inclusive meaning no extra cost can be added. We would however like to follow which cost were attached to this transaction as we need to pay for purchases, expenses, and subcontracting costs related to the project." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:20 +msgid "The following modules needs to be installed to track cost. Enter the app module and install the following apps:" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:28 +msgid "Please note that the applications provided by these apps only allows us to **track** the costs. We won't be able to automatically re invoice those costs to our customers. To track and **re invoice costs** you should install the Sales management app as well." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:36 +msgid "You can refer to the following docs about reinvoicing costs through analytical accounts: :doc:`../../../purchase/purchases/rfq/subcontracting`" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:40 +msgid "Enable Analytical accounting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:42 +msgid "Next step is to activate the analytical accounting. In the accounting app, select :menuselection:`Configuration --> Settings` and thick the Analytic accounting box." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:49 +msgid "Moreover, scroll down and thick the **Analytic accounting for purchases** box." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:55 +msgid "Don't forget to save our changes." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:58 +msgid "Create an Analytical account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:60 +msgid "First of all you should create an Analytical account on which you can point all your expenses. Enter the accounting app, select :menuselection:`Configuration --> Analytic Accounts`. Create a new one. In this case we will call it \"consulting pack\" for our customer Smith&Co." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:68 +msgid "We will point all our costs to this account to keep track of them." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:71 +msgid "Record an expense" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:73 +msgid "We start by booking an expense. Our IT technician had to take a train to go see our customer. He paid for his ticket himself." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:78 +msgid "Create an expense product" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:80 +msgid "We first need to create an expense product. Enter the **Expense** module, Click on :menuselection:`Configuration --> Expense Products`. Create a new product called Train ticket and set the cost price to 15.50 euros. Make sure the **Can be expensed** box is ticked." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:89 +msgid "Book the expense" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:91 +msgid "Enter the Expense module, click on :menuselection:`My expenses --> Create`. Select the Train ticket product and link it to the analytical account discussed above." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:98 +msgid "Submit to manager and wait for the manager to approve and post the journal entries." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:102 +msgid "Create a Purchase Order linked to the analytical account" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:105 +msgid "Purchase Product" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:107 +msgid "We also need to buy a software for our customers. In the purchase app create a purchase order for the software product. (please refer to the following document: :doc:`../../../purchase/overview/from_po_to_invoice`). Within the line we can link the product's cost with the analytical account. Specify the order line and select the correct analytical account. Confirm the sale." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:117 +msgid "Accept the delivery and enter the invoice. Once the invoice is entered the cost price (**Vendor Price** field) will be booked in the analytical account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:121 +msgid "Subcontracting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:123 +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:129 +msgid "For more information about subcontracting please refer to the following document: :doc:`../../../purchase/purchases/rfq/subcontracting`" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:134 +msgid "You can also track cost with timesheets, see: :doc:`timesheets`" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:137 +msgid "Track costs in accounting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:139 +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:142 +msgid "Enter the accounting module, click on :menuselection:`Advisers --> Analytic Accounts --> Open Charts`." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:145 +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:153 +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 ?" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:5 +msgid "Human resource of course has a cost. It is interesting to see how much a particular contract costs the company in term of human power in relation to the invoiced amounts." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:9 +msgid "We will take the following example: Our two employees **Harry Potter** and **Cedric Digory** both work on a **Consultancy pack** for our customer **Smith&Co**. Harry is paid 18€ p.h. and Cedric's salary is 12€ p.h. We would like to track their timesheet costs within the accounting app, and compare them with the revenue of the consultancy service." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:18 +msgid "First, install the three applications necessary to use this functionality, namely **Accounting**, **Sales** and **Timesheet**. Enter the apps module name and install them." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:31 +msgid "Next you will need to enable analytical accounting. To do so enter the **Accounting app**. Select :menuselection:`Configuration --> Settings` and tick the **Analytic accounting** option (see picture below)" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:38 +msgid "Apply your changes." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:41 +msgid "Create an employee" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:43 +msgid "In order to check the revenue of an employee you need to have one. To create an employee enter the **Employee** app. Select **Employees** and create a new employee, fill in the name and the basic information." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:47 +msgid "On the employee sheet enter the **HR settings** tab. Here you are able to specify the **Timesheet Cost** of your employee. In this case Harry has a cost of 18 euros / hours. We will thus fill in 18 in this field." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:55 +msgid "If you want the employee to be able to enter timesheets he needs to be related to a User." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:58 +msgid "Repeat the operation to create the Cedric Digory employee. Don't forget to specify its related user and **Timesheet Costs**." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:62 +msgid "Issue a Sales Order" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:64 +msgid "We created two employees called Harry Potter and Cedric Diggory in the **Employee** app. Both of them will work on a consultancy contract for our customer Smith&Co where they will point their hours on a timesheet." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:68 +msgid "We thus need to create a **sales order** with a **service** product invoiced **based on time and material** and tracked by timesheets with **hours** as unit of measures." +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)." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:82 +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 +msgid "Fill in timesheet" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:94 +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 +msgid "Harry worked three hours on a SWOT analysis for Smith&Co." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:104 +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 +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 +msgid "Analytic accounting" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:117 +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 +msgid "We can use two methods to analyze this situation." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:124 +msgid "Without filters" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:126 +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 +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 +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 +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 +msgid "With filters" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:150 +msgid "We can thus filter this information from the **Analytic Entries**." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:152 +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 +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 +msgid "In the results we see timesheets activities and invoiced lines with the corresponding costs and revenues." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:168 +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 "" + +#: ../../accounting/others/analytic/usage.rst:3 +msgid "Analytic account usage" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:5 +msgid "The analytic accounting can be used for several purposes:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:7 +msgid "analyse costs of a company" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:9 +msgid "reinvoice time to a customer" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:11 +msgid "analyse performance of a service or a project" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:13 +msgid "To manage analytic accounting, you have to activate it in :menuselection:`Configuration --> Settings`:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:19 +msgid "To illustrate analytic accounts clearly, you will follow three use cases, each in one of three different types of company:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:22 +msgid "Industrial company: Costs Analyse" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:24 +msgid "Law Firm: reinvoice spent hours" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:26 +msgid "IT/Services Company: performance analysis" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:29 +msgid "Case 1: Industrial company: Costs Analyse" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:31 +msgid "In industry, you will often find analytic charts of accounts structured into departments and products the company itself is built on." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:34 +msgid "The objective is to examine the costs, sales and margins by department/resources and by product. The first level of the structure comprises the different departments, and the lower levels represent the product ranges the company makes and sells." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:39 +msgid "**Analytic Chart of Accounts for an Industrial Manufacturing Company**:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:41 +msgid "Marketing Department" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:43 +msgid "Commercial Department" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:45 +msgid "Administration Department" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:47 +#: ../../accounting/others/analytic/usage.rst:66 +#: ../../accounting/others/analytic/usage.rst:70 +#: ../../accounting/others/analytic/usage.rst:72 +#: ../../accounting/others/analytic/usage.rst:80 +msgid "Production Range 1" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:49 +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:82 +msgid "Production Range 2" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:51 +msgid "In daily use, it is useful to mark the analytic account on each purchase invoice. When the invoice is approved, it will automatically generate the entries for both the general and the corresponding analytic accounts. For each entry on the general accounts, there is at least one analytic entry that allocates costs to the department which incurred them." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:58 +msgid "Here is a possible breakdown of some general accounting entries for the example above, allocated to various analytic accounts:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:62 +msgid "**General accounts**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:62 +msgid "**Analytic accounts**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +msgid "**Title**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../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 +#: ../../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/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/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 "" + +#: ../../accounting/others/analytic/usage.rst:66 +msgid "Purchase of Raw Material" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:70 +#: ../../accounting/others/analytic/usage.rst:72 +#: ../../accounting/others/analytic/usage.rst:84 +msgid "2122" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +msgid "1500" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +msgid "-1 500" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:68 +msgid "Subcontractors" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:72 +#: ../../accounting/others/analytic/usage.rst:84 +msgid "450" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:72 +msgid "-450" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:70 +msgid "Credit Note for defective materials" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:70 +#: ../../accounting/others/analytic/usage.rst:70 +msgid "200" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:72 +msgid "Transport charges" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +msgid "Staff costs" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +msgid "2121" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +msgid "10000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +#: ../../accounting/others/analytic/usage.rst:84 +msgid "Marketing" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +#: ../../accounting/others/analytic/usage.rst:80 +#: ../../accounting/others/analytic/usage.rst:82 +msgid "-2 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:76 +msgid "Commercial" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:76 +msgid "-3 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:78 +#: ../../accounting/others/analytic/usage.rst:167 +msgid "Administrative" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:78 +msgid "-1 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:84 +msgid "PR" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:84 +msgid "-400" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:87 +msgid "The analytic representation by department enables you to investigate the costs allocated to each department in the company. The analytic chart of accounts shows the distribution of the company's costs using the example above:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:94 +msgid "In this example of a hierarchical structure in Odoo, you can analyse not only the costs of each product range, but also the costs of the whole production. A report that relates both general accounts and analytic accounts enables you to get a breakdown of costs within a given department." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:103 +msgid "The examples above are based on a breakdown of the costs of the company. Analytic allocations can be just as effective for sales. That gives you the profitability (sales - costs) of different departments." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:107 +msgid "This analytic representation by department is generally used by trading companies and industries." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:110 +msgid "A variantion of this, is not to break it down by sales and marketing departments, but to assign each cost to its corresponding product range. This will give you an analysis of the profitability of each product range." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:115 +msgid "Choosing one over the other depends on how you look at your marketing effort. Is it a global cost allocated in some general way, or is each product range responsible for its own marketing costs?" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:120 +msgid "Case 2: Law Firm: costs of human resources?" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:122 +msgid "Law firms generally adopt management by case, where each case represents a current client file. All of the expenses and products are then attached to a given file/analytic account." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:126 +msgid "A principal preoccupation of law firms is the invoicing of hours worked, and the profitability by case and by employee." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:129 +msgid "Mechanisms used for encoding the hours worked will be covered in detail in timesheet documentation. Like most system processes, hours worked are integrated into the analytic accounting. In the employee form, specify the cost of the employee. The hourly charge is a function of the employee's cost." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:135 +msgid "So a law firm will opt for an analytic representation which reflects the management of the time that employees work on the different customer cases." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:139 +msgid "Billing for the different cases is a bit unusual. The cases do not match any entry in the general account nor do they come from purchase or sales invoices. They are represented by the various analytic operations and do not have exact counterparts in the general accounts. They are calculated on the basis of the hourly cost per employee." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:145 +msgid "At the end of the month when you pay salaries and benefits, you integrate them into the general accounts but not in the analytic accounts, because they have already been accounted for in billing each account. A report that relates data from the analytic and general accounts then lets you compare the totals, so you can readjust your estimates of hourly cost per employee depending on the time actually worked." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:153 +msgid "The following table shows an example of different analytic entries that you can find for your analytic account:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:157 +msgid "**Amount**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:157 +msgid "**General Account**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:159 +msgid "Study the file (1 h)" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:159 +#: ../../accounting/others/analytic/usage.rst:161 +#: ../../accounting/others/analytic/usage.rst:165 +#: ../../accounting/others/analytic/usage.rst:169 +msgid "Case 1.1" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:159 +msgid "-15" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:161 +msgid "Search for information (3 h)" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:161 +msgid "-45" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:163 +msgid "Consultation (4 h)" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:163 +msgid "Case 2.1" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:163 +msgid "-60" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:165 +msgid "Service charges" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:165 +#: ../../accounting/others/analytic/usage.rst:165 +msgid "280" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:165 +msgid "705 – Billing services" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "Stationery purchase" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "-42" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "601 – Furniture purchase" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "42" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "Fuel Cost -Client trip" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "-35" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "613 – Transports" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "35" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:171 +msgid "Staff salaries" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:171 +msgid "6201 – Salaries" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:171 +msgid "3 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:174 +msgid "Such a structure allows you to make a detailed study of the profitability of various transactions." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:177 +msgid "For more details about profitablity, please read the following document: :doc:`timesheets`" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:180 +msgid "But analytical accounting is not limited to a simple analysis of the profitability of different customer. The same data can be used for automatic recharging of the services to the customer at the end of the month. To invoice customers, just link the analytic account to a sale order and sell products that manage timesheet or expenses ." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:187 +msgid "Case 3: IT Services Company: perfomance analysis" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:189 +msgid "Most IT service companies face the following problems:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:191 +msgid "project planning," +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:193 +msgid "invoicing, profitability and financial follow-up of projects," +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:195 +msgid "managing support contracts." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:197 +msgid "To deal with these problems, you would use an analytic chart of accounts structured by project and by sale order." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:200 +msgid "The management of services, expenditures and sales is similar to that presented above for lawyers. Invoicing and the study of profitability are also similar." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:204 +msgid "But now look at support contracts. These contracts are usually limited to a prepaid number of hours. Each service posted in the analytic accounts shows the remaining hours of support. To manage support contracts, you would create a product configured to invoice on order and link the sale order to an analytic account" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:210 +msgid "In Odoo, each analytic line lists the number of units sold or used, as well as what you would usually find there – the amount in currency units (USD or GBP, or whatever other choice you make). So you can sum the quantities sold and used on each sale order to determine whether any hours of the support contract remain." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:217 +msgid "Conclusion" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:219 +msgid "Analytic accounting helps you to analyse costs and revenues whatever the use case. You can sell or purchase services, track time or analyse the production performance." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:223 +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 +#: ../../accounting/overview/terminologies.rst:72 +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:86 +msgid "View *Create Account* in our Online Demonstration" +msgstr "" + +#: ../../accounting/others/inventory.rst:3 +msgid "Inventory" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:3 +msgid "Impact on the average price valuation when returning goods" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:5 +msgid "As stated in the `*inventory valuation page* `__, one of the possible costing method you can use in perpetual stock valuation, is the average cost." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:10 +msgid "This document answers to one recurrent question for companies using that method to make their stock valuation: how does a shipping returned to its supplier impact the average cost and the accounting entries? This document is **only** for the specific use case of a perpetual valuation (as opposed to the periodic one) and in average price costing method (as opposed to standard of FIFO)." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:18 +msgid "Definition of average cost" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:20 +msgid "The average cost method calculates the cost of ending inventory and cost of goods sold on the basis of weighted average cost per unit of inventory." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:24 +msgid "The weighted average cost per unit is calculated using the following formula:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:27 +msgid "When new products arrive in a warehouse, the new average cost is recomputed as:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:33 +msgid "When products leave the warehouse: the average cost **does not** change" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:36 +msgid "Defining the purchase price" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:38 +msgid "The purchase price is estimated at the reception of the products (you might not have received the vendor bill yet) and reevaluated at the reception of the vendor bill. The purchase price includes the cost you pay for the products, but it may also includes additional costs, like landed costs." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:45 +msgid "Average cost example" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Operation" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +msgid "Delta Value" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Inventory Value" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Qty On Hand" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Avg Cost" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:50 +#: ../../accounting/others/inventory/avg_price_valuation.rst:50 +#: ../../accounting/others/inventory/avg_price_valuation.rst:146 +#: ../../accounting/others/inventory/avg_price_valuation.rst:146 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "$0" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:50 +#: ../../accounting/others/inventory/avg_price_valuation.rst:146 +msgid "0" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +msgid "Receive 8 Products at $10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +msgid "+8\\*$10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "$80" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "8" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "$10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +msgid "Receive 4 Products at $16" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +msgid "+4\\*$16" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +msgid "$144" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +msgid "12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:84 +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:103 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:119 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "$12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +msgid "Deliver 10 Products" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +msgid "-10\\*$12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:84 +#: ../../accounting/others/inventory/avg_price_valuation.rst:103 +#: ../../accounting/others/inventory/avg_price_valuation.rst:119 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +msgid "$24" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:84 +#: ../../accounting/others/inventory/avg_price_valuation.rst:103 +#: ../../accounting/others/inventory/avg_price_valuation.rst:119 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +msgid "2" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:60 +msgid "At the beginning, the Avg Cost is set to 0 set as there is no product in the inventory. When the first reception is made, the average cost becomes logically the purchase price." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:64 +msgid "At the second reception, the average cost is updated because the total inventory value is now ``$80 + 4*$16 = $144``. As we have 12 units on hand, the average price per unit is ``$144 / 12 = $12``." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:68 +msgid "By definition, the delivery of 10 products does not change the average cost. Indeed, the inventory value is now $24 as we have only 2 units remaining of each ``$24 / 2 = $12``." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:73 +msgid "Purchase return use case" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:75 +msgid "In case of a product returned to its supplier after reception, the inventory value is reduced using the average cost formulae (not at the initial price of these products!)." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:79 +msgid "Which means that the above table will be updated as follow:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "Return of 1 Product initially bought at $10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +msgid "-1\\*$12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "1" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:90 +msgid "Explanation: counter example" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:92 +msgid "Remember the definition of **Average Cost**, saying that we do not update the average cost of a product leaving the inventory. If you break this rule, you may lead to inconsistencies in your inventory." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:96 +msgid "As an example, here is the scenario when you deliver one piece to the customer and return the other one to your supplier (at the cost you purchased it). Here is the operation:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +msgid "Customer Shipping 1 product" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +msgid "-1\\*$10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "**$2**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +msgid "**0**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:110 +msgid "As you can see in this example, this is not correct: an inventory valuation of $2 for 0 pieces in the warehouse." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:113 +msgid "The correct scenario should be to return the goods at the current average cost:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +msgid "**$0**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:126 +msgid "On the other hand, using the average cost to value the return ensure a correct inventory value at all times." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:130 +msgid "Further thoughts on anglo saxon mode" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:132 +msgid "For people in using the **anglo saxon accounting** principles, there is another concept to take into account: the stock input account of the product, which is intended to hold at any time the value of vendor bills to receive. So the stock input account will increase on reception of incoming shipments and will decrease when receiving the related vendor bills." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:139 +msgid "Back to our example, we see that when the return is valued at the average price, the amount booked in the stock input account is the original purchase price:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "stock input" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "price diff" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +msgid "($80)" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "Receive vendor bill $80" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +msgid "($64)" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +msgid "Receive vendor bill $64" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "**$10**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "**$12**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "Receive vendor refund $10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "$2" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:163 +msgid "This is because the vendor refund will be made using the original purchase price, so to zero out the effect of the return in the stock input in last operation, we need to reuse the original price. The price difference account located on the product category is used to book the difference between the average cost and the original purchase price." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:3 +msgid "Record exchange rates at payments" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:8 +msgid "Any company doing international trade faces the case where the payments are in a different currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:11 +msgid "After receiving their payments, you have the option to convert the amount into your company currency. Multi currency payment implies rates fluctuations. The rate differences are automatically recorded by Odoo." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:19 +msgid "Enable multi-currencies" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:21 +msgid "In the accounting module, Go to :menuselection:`Configuration --> Settings` and flag **Allow multi currencies**, then click on **apply**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:27 +msgid "Configure the currency rates in :menuselection:`Configuration --> Currencies`. Write down the rate and make sure the currency is active." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:33 +msgid "In this document, the base currency is **Euro** and we will record payments in **Dollars**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:40 +msgid "You can automatically fetch the currency rates from the **European Central Bank** or from **Yahoo**. Please read the document : :doc:`how_it_works`." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:45 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:31 +msgid "Configure your journal" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:47 +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/exchange.rst:54 +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/exchange.rst:62 +msgid "Record a payment in a different currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:64 +msgid "In the **Accounting** application, go to :menuselection:`Sales --> Payments`. Register the payment and indicate that it was done in the foreign currency. Then click on **confirm**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:71 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:83 +msgid "The journal entry has been posted but not allocated." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:73 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:85 +msgid "Go back to your invoice (:menuselection:`Sales --> Customer Invoices`) and click on **Add** to allocate the payment." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:80 +msgid "Record a bank statement in a different currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:82 +msgid "Create or import the bank statement of your payment. The **Amount** is in the company currency. There are two complementary fields, the **Amount currency**, which is the amount that was actually paid and the **Currency** in which it was paid." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:89 +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/exchange.rst:97 +msgid "Check the exchange rate differences" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:99 +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/exchange.rst:106 +msgid "The Exchange difference journal can be changed in your accounting settings." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:109 +#: ../../accounting/payables/pay/multiple.rst:153 +msgid ":doc:`../../bank/reconciliation/configure`" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:110 +#: ../../accounting/payables/pay/multiple.rst:103 +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?" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:8 +msgid "Choosing to use the multi-currency option in Odoo will allow you to send sales invoices, quotes and purchase orders or receive bills and payments in currencies other than your own. With multi-currency, you can also set up bank accounts in other currencies and run reports on your foreign currency activities." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:18 +msgid "Turn on multi-currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:20 +msgid "In the accounting module, Go to :menuselection:`Configuration --> Settings` and flag **Allow multi currencies**, then click on **Apply**." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:27 +#: ../../accounting/others/multicurrencies/how_it_works.rst:160 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:109 +msgid "Exchange Rate Journal" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:29 +msgid "The **Rate Difference Journal** records the differences between the payment registration and the expected amount. For example, if a payment is paid 1 month after the invoice was issued, the exchange rate has probably changed. The fluctuation implies some loss or profit that are recorded by Odoo." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:35 +msgid "You can change it in the settings:" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:41 +msgid "View or edit rate being used" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:43 +msgid "You can manually configure the currency rates in :menuselection:`Configuration --> Currencies`. Open the currencies you want to use in Odoo and edit it. Make sure the currency is active." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:50 +msgid "Click on **View Rates** to edit it and to see the history :" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:55 +msgid "Click on **Create** to add the rate. Fill in the date and the rate. Click on **Save** when you are done." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:62 +msgid "Live Currency Rate" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:64 +msgid "By default, the currencies need to be updated manually. But you can synchronize it with `Yahoo `__ or the `European Central Bank `__. In :menuselection:`Configuration --> Settings`, go to the **Live Currency Rate** section." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:69 +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 +msgid "Only the **active** currencies are updated" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:81 +msgid "Configure your charts of account" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:83 +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 +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 +msgid "Configure your journals" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:96 +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/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/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 +msgid "Sales Orders and Invoices" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:119 +#: ../../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 +msgid "Purchases orders and Vendor Bills" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:129 +#: ../../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 +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." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:146 +msgid "Bank Statements" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:148 +#: ../../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 +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 +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 +msgid ":doc:`invoices_payments`" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:171 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:120 +msgid ":doc:`exchange`" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:3 +msgid "How to manage invoices & payment in multiple currencies" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:8 +msgid "Odoo provides multi-currency support with automatic currency gross or loss entry adjustment. There are a few things Odoo has been to ease the user's life." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:12 +msgid "All the account transactions will be done using the company currency. However you can see two extra fields with the journal entry where secondary currency and amount will visible. You can create multi-currency journals of force a specific currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:17 +msgid "When creating an invoice, the currency can be changed very easily; however Odoo takes the company currency as a default assignment. It will convert all the amounts automatically using that currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:25 +msgid "Enable Multi-Currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:27 +msgid "For information about enabling Multi-Currency, please read the document: :doc:`how_it_works`" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:33 +msgid "In order to register payments in other currencies, you have to remove the currency constraint on the journal. Go to the accounting application, on the journal, click on :menuselection:`More --> Settings`." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:48 +msgid "Multi-currency invoices & Vendor Bills" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:54 +msgid "Invoices" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:64 +msgid "Vendor Bills" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:74 +msgid "Multi-currency Payments" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:76 +msgid "In the accounting application, go to :menuselection:`Sales --> Payments`. Register the payment and indicate that it was done in the foreign currency. Then click on **Confirm**." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:92 +msgid "Multi- Currency Bank Statements" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:101 +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/invoices_payments.rst:111 +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 +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 get a customized reports with your own formulas ?" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:8 +msgid "Odoo 9 comes with a powerful and easy-to-use reporting framework. Creating new reports (such as a tax report or a balance sheet for a specific country) to suit your needs is now easier than ever." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:13 +msgid "Activate the developer mode" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:15 +msgid "In order to have access to the financial report creation interface, the **developer mode** needs to be activated. To do that, first click the **?** at the top right, then **About**." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:22 +msgid "Click on : **Activate the developer mode**." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:28 +msgid "Create your financial report" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:30 +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:36 +msgid "Once the name is filled, there are two other parameters that need to be configured:" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:39 +msgid "**Show Credit and Debit Columns**" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:41 +msgid "**Analysis Period** :" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:43 +msgid "Based on date ranges (eg Profit and Loss)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:45 +msgid "Based on a single date (eg Balance Sheet)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:47 +msgid "Based on date ranges with 'older' and 'total' columns and last 3 months (eg. Aged Partner Balances)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:50 +msgid "Bases on date ranges and cash basis method (eg Cash Flow Statement)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:54 +msgid "Add lines in your custom reports" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:56 +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:63 +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:67 +msgid "You have several objects available in the formula :" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:69 +msgid "``Ndays`` : The number of days in the selected period (for reports with a date range)." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:72 +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:76 +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:83 +msgid "Other useful fields :" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:85 +msgid "**Type** : Type of the result of the formula." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:87 +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:90 +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:93 +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:98 +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:30 +msgid "Balance Sheet" +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/application.rst:3 +msgid "How to apply specific taxes by country, state or city ?" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:5 +msgid "In Odoo, the default tax to apply on a product/service is set on the **product form**. But, some customers may have specific tax rates because of their status (in some countries, construction companies are VAT exempts) or their location (customers in a different country, state and/or city may be subjected to another tax rate)." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:11 +msgid "In order to select the right tax to apply according to the customer or product, Odoo uses the concept of **fiscal positions**. If a customer has a specific fiscal position, the default tax may be replaced by another one. (as an example, construction companies have 0% instead of 21% in Belgium for construction related work)." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:17 +msgid "As an example, in Belgium, for the VAT tax, there are 3 fiscal positions that depend on on the country of the customer and some companies (like construction companies) benefit from a specific fiscal treatments:" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:21 +msgid "**Belgian companies:** with 21% VAT (default, on product form)" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:23 +msgid "**European companies:** with 0% VAT (intra-EU)" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:25 +msgid "**Other countries:** 0% (but a different tax since it uses different accounts)" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:28 +msgid "**Construction companies:** with 0% VAT, only for construction companies in Belgium" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:35 +msgid "Set the right taxes on your products" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:37 +msgid "The main taxes are automatically configured according to the chart of accounts of your country." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:40 +msgid "But if you want to set a specific tax on a specific product, you can set the **sales and purchases taxes** on the **product form**, under the **Accounting tab**. These taxes are the default one (used when you sell to companies that are in the same country/state than you)" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:49 +msgid "If you work in a multi-company 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/application.rst:55 +msgid "Defining Fiscal Positions" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:57 +msgid "The main fiscal positions are automatically created according to the chart of accounts of your country. But you may have to create fiscal positions manually for specific use cases." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:61 +msgid "To define fiscal positions, from the **Accounting** application, go to :menuselection:`Configuration --> Fiscal Positions`." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:64 +msgid "Fiscal position is just a set of rules that maps default taxes (as defined on product form) into other taxes. In the screenshot below, european customers have a VAT of 0% instead of the default 15%, for both sales and purchases." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:73 +msgid "You can also map the **income / expense account** according to the fiscal position. For example, in Belgium, revenues from sales are not posted in the same account than revenues from sales in foreign countries." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:78 +msgid "Apply fiscal positions automatically" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:80 +msgid "If you check the box **Detect Automatically**, the fiscal position will be applied automatically if the **Country**, **State**, **City** or even the **Country Group** matches. You can also apply the fiscal position only to companies having a valid **VAT number**." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:85 +msgid "You can also set a target **Country/State/City**. The fiscal position will be applied if the destination address of the customer matches these criteria." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:93 +msgid "Specific use cases" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:95 +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:101 +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**. You can also create one that is a grouping of two other taxes, depending on how you want to make them appear on the invoice." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:107 +msgid "Using fiscal positions" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:109 +msgid "If you keep the field **Fiscal Position** empty on customers :menuselection:`Accounting --> Sales --> Customers`, the fiscal position is applied automatically on sales order, purchase orders, web orders and invoices." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:116 +msgid "But, if you set the fiscal position, Odoo will use this specific fiscal position for this customer on orders (example: construction companies). In such a case, it's recommended to set the fiscal position on the customer form. Odoo will automatically reuse this value for orders and invoices, without trying to auto-detect the fiscal position." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:122 +msgid "If you set the fiscal position at the sale order or invoice level, it will only apply to this document only and not to future orders/invoices of the same customer." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:126 +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:132 +#: ../../accounting/others/taxes/retention.rst:70 +msgid ":doc:`create`" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:3 +msgid "How to define 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 taxes, retention, withholding taxes, etc. For most countries, the chart of account you setup is automatically pre-configured with the main taxes of the country." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:11 +msgid "This section details how you can define new taxes for specific use cases." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:15 +msgid "Managing Taxes" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:18 +msgid "Defining new taxes" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:20 +msgid "In order to create new taxes, use the menu :menuselection:`Configuration --> Taxes` in the accounting application. From this menu, you will get all the taxes you can use: sales taxes and purchase taxes." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:27 +msgid "When you create a new tax, you can set the following information:" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:29 +msgid "**Scope**: Sales, Purchases or None (e.g. deprecated tax)" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:31 +msgid "**Tax Account**: is the account 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:35 +msgid "**Label on Invoices**: a short text on how you want this tax to be printed on invoice line. For example, a tax named \"21% on Services\" can have the following label on invoice \"21%\"." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:39 +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:43 +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:47 +msgid "**Tags**: are used for custom reports. (usually, you can keep this field empty)" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:50 +msgid "Taxes allow different computation mechanism:" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:52 +msgid "**Fixed**, example: an eco-tax of $1.34 per battery" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:54 +msgid "**Percentage**, example: 15% sales tax" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:56 +msgid "**Percentage of price**, tax included: example in brazil" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:58 +msgid "**Group of taxes**: allows to have a compound tax" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:65 +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:69 +msgid "If a tax is included in price, it means that the price set on the product form includes this tax. As an example, let's say you have a product with a sale tax of 10%. The sale price on the product form is $100." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:74 +msgid "If the tax is not included in the price, you will get:" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:76 +msgid "Price without tax: $100" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:78 +msgid "Taxes: $10" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:80 +msgid "Total to pay: $110" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:82 +msgid "If the tax is included in the price" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:84 +msgid "Price without tax: 90.91" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:86 +msgid "Taxes: $9.09" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:88 +msgid "Total to pay: $100" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:94 +msgid "Stop using a tax" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:96 +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:101 +msgid "Setting your default taxes" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:103 +msgid "Once you have created your taxes, you can define which tax is the default one when creating new products (for sales and purchase taxes). To set the default taxes, in the accounting application, go in the menu :menuselection:`Configuration --> Settings`." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:111 +msgid "Once taxes are set by default, when you create a new product, Odoo will propose you the right taxes by default on the product form." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:116 +msgid "Setting the default taxes impact the creation of product, but not sales order or invoices. The tax used on sales order or invoices is defined by the product on the sale order line." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:122 +msgid ":doc:`application`" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:123 +msgid ":doc:`retention`" +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:3 +msgid "How to manage retention 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/overview/getting_started.rst:3 +msgid "Getting Started" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:3 +msgid "How to setup Odoo Accounting?" +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." +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." +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" +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" +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" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:28 +msgid "Importing your starting balances" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:29 +msgid "Define the users for accounting" +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." +msgstr "" + +#: ../../accounting/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:3 +msgid "The Accounting behind Odoo" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:5 +msgid "This page summarises the way Odoo deals with typical accounts and transactions." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:9 +msgid "Double-entry bookkeeping" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:11 +msgid "Odoo automatically creates all the behind-the-scenes journal entries for each of your accounting transactions: customer invoices, point of sale order, expenses, inventory moves, etc." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:15 +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 `__" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:23 +msgid "Accrual and Cash Basis Methods" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:25 +msgid "Odoo support both accrual and cash basis reporting. This allows you to report income / expense at the time transactions occur, or when payment is made or received." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:30 +msgid "Multi-companies" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:32 +msgid "Odoo allows to manage several companies within the same database. Each company has its own chart of accounts an rules. You can get consolidation reports following your consolidation rules." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:36 +msgid "Users can access several companies but always work in one company at a time." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:40 +msgid "Multi-currencies" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:42 +msgid "Every transaction is recorded in the default currency of the company. For transactions occurring in another currency, Odoo stores both the value in the currency of the company and the value in the currency of the transaction. Odoo can generate currencies gains and losses after the reconciliation of the journal items." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:48 +msgid "Currency rates are updated once a day using a yahoo.com online web-service." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:52 +msgid "International Standards" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:54 +msgid "Odoo accounting support more than 50 countries. The Odoo core accounting implement accounting standards that is common to all countries and specific modules exists per country for the specificities of the country like the chart of accounts, taxes, or bank interfaces." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:60 +msgid "In particular, Odoo's core accounting engine support:" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:62 +msgid "Anglo-Saxon Accounting (U.S., U.K.,, and other English-speaking countries including Ireland, Canada, Australia, and New Zealand) where cost of good sold are reported when products are sold/delivered." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:66 +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 +msgid "Odoo also have modules to comply with IFRS rules." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:74 +msgid "Accounts Receivable & Payable" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:76 +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 +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 +msgid "Wide range of financial reports" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:88 +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 +msgid "Performance reports (such as Profit and Loss, Budget Variance)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:93 +msgid "Position reports (such as Balance Sheet, Aged Payables, Aged Receivables)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:95 +msgid "Cash reports (such as Bank Summary)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:96 +msgid "Detail reports (such as Trial Balance and General Ledger)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:97 +msgid "Management reports (such as Budgets, Executive Summary)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:99 +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 +msgid "Import bank feeds automatically" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:105 +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 +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 +msgid "Calculates the tax you owe your tax authority" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:121 +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 +msgid "Inventory Valuation" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:128 +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 `__" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:137 +msgid "Easy retained earnings" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:139 +msgid "Retained earnings is 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/memento.rst:5 +msgid "Accounting Memento For Entrepreneurs (US GAAP)" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:11 +msgid "The **Profit and Loss** (P&L) report shows the performance of the company over a specific period (usually the current year)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:16 +msgid "The **Gross Profit** equals the revenues from sales minus the cost of goods sold." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:21 +msgid "**Operating Expenses** (OPEX) include administration, sales and R&D salaries as well as rent and utilities, miscellaneous costs, insurances, … anything beyond the costs of products sold." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:27 +msgid "The **Balance Sheet** is a snapshot of the company's finances at a specific date (as opposed to the Profit and Loss which is an analysis over a period)" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:32 +msgid "**Assets** represent the company's wealth, things it owns. Fixed assets includes building and offices, current assets include bank accounts and cash. A client owing money is an asset. An employee is not an asset." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:38 +msgid "**Liabilities** are obligations from past events that the company will have to pay in the future (utility bills, debts, unpaid suppliers)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:43 +msgid "**Equity** is the amount of the funds contributed by the owners (founders or shareholders) plus previously retained earnings (or losses)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:48 +msgid "Each year, net profits (or losses) are reported to retained earnings." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:54 +msgid "What is owned (an asset) has been financed through debts to reimburse (liabilities) or equity (profits, capital)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:57 +msgid "A difference is made between buying an assets (e.g. a building) and expenses (e.g. fuel). Assets have an intrinsic value over time, versus expenses having value in them being consumed for the company to \"work\"." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:64 +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 "" + +#: ../../accounting/overview/main_concepts/memento.rst:76 +msgid "Balance = Debit - Credit" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:84 +msgid "Journal Entries" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:86 +msgid "Every financial document of the company (e.g. an invoice, a bank statement, a pay slip, a capital increase contract) is recorded as a journal entry, impacting several accounts." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:90 +msgid "For a journal entry to be *balanced*, the sum of all its debits must be equal to the sum of all its credits." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:95 +msgid "examples of accounting entries for various transactions. Example:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:97 +msgid "Example 1: Customer Invoice:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:99 +#: ../../accounting/overview/main_concepts/memento.rst:117 +msgid "Explanation:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:101 +msgid "You generate a revenue of $1,000" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:102 +msgid "You have a tax to pay of $90" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:103 +msgid "The customer owes $1,090" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:105 +#: ../../accounting/overview/main_concepts/memento.rst:122 +msgid "Configuration:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:107 +msgid "Income: defined on the product, or the product category" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:108 +#: ../../accounting/overview/main_concepts/memento.rst:125 +msgid "Account Receivable: defined on the customer" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:109 +msgid "Tax: defined on the tax set on the invoice line" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:111 +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 "" + +#: ../../accounting/overview/main_concepts/memento.rst:115 +msgid "Example 2: Customer Payment:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:119 +msgid "Your customer owes $1,090 less" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:120 +msgid "Your receive $1,090 on your bank account" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:124 +msgid "Bank Account: defined on the related bank journal" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:130 +#: ../../accounting/overview/main_concepts/memento.rst:216 +#: ../../accounting/overview/main_concepts/memento.rst:226 +#: ../../accounting/overview/main_concepts/memento.rst:242 +#: ../../accounting/overview/terminologies.rst:25 +msgid "Reconciliation" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:132 +msgid "Reconciliation is the process of linking journal items of a specific account, matching credits and debits." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:135 +msgid "Its primary purpose is to link payments to their related invoices in order to mark invoices that are paid and clear the customer statement. This is done by doing a reconciliation on the *Accounts Receivable* account." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:139 +msgid "An invoice is marked as paid when its Accounts Receivable journal items are reconciled with the related payment journal items." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:142 +msgid "Reconciliation is performed automatically by the system when:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:144 +msgid "the payment is registered directly on the invoice" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:145 +msgid "the links between the payments and the invoices are detected at the bank matching process" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:0 +msgid "Customer Statement Example" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:156 +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +#: ../../accounting/overview/process_overview/customer_invoice.rst:132 +msgid "Accounts Receivable" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:156 +#: ../../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_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 "" + +#: ../../accounting/overview/main_concepts/memento.rst:156 +#: ../../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_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 "" + +#: ../../accounting/overview/main_concepts/memento.rst:158 +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 "" + +#: ../../accounting/overview/main_concepts/memento.rst:160 +msgid "70" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:162 +msgid "Invoice 2" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:162 +#: ../../accounting/overview/main_concepts/memento.rst:166 +msgid "65" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:164 +msgid "Payment 1.2" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:164 +msgid "30" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:166 +msgid "Payment 2" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:168 +msgid "Invoice 3" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:168 +#: ../../accounting/overview/main_concepts/memento.rst:172 +msgid "50" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:172 +msgid "Total To Pay" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:179 +msgid "Bank reconciliation is the matching of bank statement lines (provided by your bank) with transactions recorded internally (payments to suppliers or from customers). For each line in a bank statement, it can be:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:184 +msgid "matched with a previously recorded payment:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:184 +msgid "a payment is registered when a check is received from a customer, then matched when checking the bank statement" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:188 +msgid "recorded as a new payment:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:187 +msgid "the payment's journal entry is created and :ref:`reconciled ` with the related invoice when processing the bank statement" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:191 +msgid "recorded as another transaction:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:191 +msgid "bank transfer, direct charge, etc." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:193 +msgid "Odoo should automatically reconcile most transactions, only a few of them should need manual review. When the bank reconciliation process is finished, the balance on the bank account in Odoo should match the bank statement's balance." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:201 +msgid "Checks Handling" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:203 +msgid "There are two approaches to manage checks and internal wire transfer:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:205 +msgid "Two journal entries and a reconciliation" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:206 +msgid "One journal entry and a bank reconciliation" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:210 +msgid "The first journal entry is created by registering the payment on the invoice. The second one is created when registering the bank statement." +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_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_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 "" + +#: ../../accounting/overview/main_concepts/memento.rst:218 +#: ../../accounting/overview/main_concepts/memento.rst:244 +msgid "Invoice ABC" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:220 +#: ../../accounting/overview/main_concepts/memento.rst:228 +msgid "Undeposited funds" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:220 +#: ../../accounting/overview/main_concepts/memento.rst:228 +msgid "Check 0123" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:230 +#: ../../accounting/overview/main_concepts/memento.rst:246 +#: ../../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 "" + +#: ../../accounting/overview/main_concepts/memento.rst:235 +msgid "A journal entry is created by registering the payment on the invoice. When reconciling the bank statement, the statement line is linked to the existing journal entry." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:242 +msgid "Bank Statement" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:246 +msgid "Statement XYZ" +msgstr "" + +#: ../../accounting/overview/process_overview.rst:3 +msgid "Process overview" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:3 +msgid "From Invoice to Payment Collection" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:5 +msgid "Odoo supports multiple invoicing and payment workflows, so you can choose and use the ones that match your business needs. Whether you want to accept a single payment for a single invoice, or process a payment spanning multiple invoices and taking discounts for early payments, you can do so efficiently and accurately." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:12 +msgid "From Draft Invoice to Profit and Loss" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:14 +msgid "If we pick up at the end of a typical 'order to cash' scenario, after the goods have been shipped, you will: issue an invoice; receive payment; deposit that payment at the bank; make sure the Customer Invoice is closed; follow up if Customers are late; and finally present your Income on the Profit and Loss report and show the decrease in Assets on the Balance Sheet report." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:21 +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 "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:36 +msgid "An invoice must be provided to the customer with the necessary information in order for them to pay for the goods and services ordered and delivered. It must also include other information needed to pay the invoice in a timely and precise manner." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:42 +msgid "Draft invoices" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:44 +msgid "The system generates invoice which are initially set to the Draft state. While these invoices" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:47 +msgid "remain unvalidated, they have no accounting impact within the system. There is nothing to stop users from creating their own draft invoices." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:50 +msgid "Let's create a customer invoice with following information:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:52 +msgid "Customer: Agrolait" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:53 +msgid "Product: iMac" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:54 +msgid "Quantity: 1" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:55 +msgid "Unit Price: 100" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:56 +msgid "Taxes: Tax 15%" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:64 +msgid "The document is composed of three parts:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:66 +msgid "the top of the invoice, with customer information," +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:67 +msgid "the main body of the invoice, with detailed invoice lines," +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:68 +msgid "the bottom of the page, with detail about the taxes, and the totals." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:71 +msgid "Open or Pro-forma invoices" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:73 +msgid "An invoice will usually include the quantity and price the of goods and/or services, the date, any parties involved, the unique invoice number, and any tax information." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:77 +msgid "\"Validate\" the invoice when you are ready to approve it. The invoice then moves from the Draft state to the Open state." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:80 +msgid "When you have validated an invoice, Odoo gives it a unique number from a defined, and modifiable, sequence." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:86 +msgid "Accounting entries corresponding to this invoice are automatically generated when you validate the invoice. You can see the details by clicking on the entry in the Journal Entry field in the \"Other Info\" tab." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:95 +msgid "Send the invoice to customer" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:97 +msgid "After validating the customer invoice, you can directly send it to the customer via the 'Send by email' functionality." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:103 +msgid "A typical journal entry generated from a validated invoice will look like as follows:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Partner**" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Due date**" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +#: ../../accounting/overview/process_overview/customer_invoice.rst:111 +#: ../../accounting/overview/process_overview/customer_invoice.rst:130 +#: ../../accounting/overview/process_overview/customer_invoice.rst:132 +msgid "Agrolait" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +msgid "01/07/2015" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +#: ../../accounting/overview/process_overview/customer_invoice.rst:130 +#: ../../accounting/overview/process_overview/customer_invoice.rst:132 +msgid "115" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:111 +msgid "15" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:113 +#: ../../accounting/receivables/customer_invoices/overview.rst:16 +msgid "Sales" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:117 +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:89 +msgid "Payment" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:119 +msgid "In Odoo, an invoice is considered to be paid when the associated accounting entry has been reconciled with the payment entries. If there has not been a reconciliation, the invoice will remain in the Open state until you have entered the payment." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:124 +msgid "A typical journal entry generated from a payment will look like as follows:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:136 +msgid "Receive a partial payment through the bank statement" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:138 +msgid "You can manually enter your bank statements in Odoo, or you can import them in from a csv file or from several other predefined formats according to your accounting localisation." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:142 +msgid "Create a bank statement from the accounting dashboard with the related journal and enter an amount of $100 ." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:149 +msgid "Reconcile" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:151 +msgid "Now let's reconcile!" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:156 +msgid "You can now go through every transaction and reconcile them or you can mass reconcile with instructions at the bottom." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:158 +msgid "After reconciling the items in the sheet, the related invoice will now display \"You have outstanding payments for this customer. You can reconcile them to pay this invoice. \"" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:168 +msgid "Apply the payment. Below, you can see that the payment has been added to the invoice." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:175 +msgid "Payment Followup" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:177 +msgid "There's a growing trend of customers paying bills later and later. Therefore, collectors must make every effort to collect money and collect it faster." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:181 +msgid "Odoo will help you define your follow-up strategy. To remind customers to pay their outstanding invoices, you can define different actions depending on how severely overdue the customer is. These actions are bundled into follow-up levels that are triggered when the due date of an invoice has passed a certain number of days. If there are other overdue invoices for the same customer, the actions of the most overdue invoice will be executed." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:189 +msgid "By going to the customer record and diving into the \"Overdue Payments\" you will see the follow-up message and all overdue invoices." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:199 +msgid "Customer aging report:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:201 +msgid "The customer aging report will be an additional key tool for the collector to understand the customer credit issues, and to prioritize their work." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:205 +msgid "Use the aging report to determine which customers are overdue and begin your collection efforts." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:212 +msgid "Profit and loss" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:214 +msgid "The Profit and Loss statement displays your revenue and expense details. Ultimately, this gives you a clear image of your Net Profit and Loss. It is sometimes referred to as the \"Income Statement\" or \"Statement of Revenues and Expenses.\"" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:223 +msgid "Balance sheet" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:225 +msgid "The balance sheet summarizes the your company's liabilities, assets and equity at a specific moment in time." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:234 +msgid "For example, if you manage your inventory using the perpetual accounting method, you should expect a decrease in account \"Current Assets\" once the material has been shipped to the customer." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:3 +msgid "From Vendor Bills to Payments" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:5 +msgid "Once vendor bills are registered in Odoo, you can easily pay vendors for the correct amount and at the right time (not too late, not too early; depending on your vendor policy). Odoo also offers reports to track your aged payable balances." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:10 +msgid "If you want to control vendor bills received from your vendors, you can use the Odoo Purchase application that allows you to control and pre-complete them automatically based on past purchase orders." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:15 +msgid "From Vendor Bill to Payment" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:18 +msgid "Record a new vendor bill" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:20 +msgid "When a vendor bill is received, you can record it from :menuselection:`Purchases --> Vendor Bills` in the Accounting application. As a shortcut, you can also use the **New Bill** feature on the accounting dashboard." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:27 +msgid "To register a new vendor bill, start by selecting a vendor and inputting their invoice as the **Vendor Reference**, then add and confirm the product lines, making sure to have the right product quantities, taxes and prices." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:35 +msgid "Save the invoice to update the pre tax and tax amounts at the bottom of the screen. You will most likely need to configure the prices of your products without taxes as Odoo will compute the tax for you." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:40 +msgid "On the bottom left corner, Odoo shows a summary table of all taxes on the vendor bill. In several countries, different methods are accepted to round the totals (round per line, or round globally). The default rounding method in Odoo is to round the final prices per line (as you may have different taxes per product. E.g. Alcohol and cigarettes). However if your vendor has a different tax amount on their bill, you can change the amount in the bottom left table to adjust and match." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:48 +msgid "Validate The Vendor Bill" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:50 +msgid "Once the vendor bill is validated, a journal entry will be generated based on the configuration on the invoice. This journal entry may differ depending on the the accounting package you choose to use." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:54 +msgid "For most European countries, the journal entry will use the following accounts:" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:57 +#: ../../accounting/overview/process_overview/supplier_bill.rst:66 +msgid "**Accounts Payable:** defined on the vendor form" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:59 +#: ../../accounting/overview/process_overview/supplier_bill.rst:68 +msgid "**Taxes:** defined on the products and per line" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:61 +msgid "**Expenses:** defined on the line item product used" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:63 +msgid "For Anglo-Saxon (US) accounting, the journal entry will use the following accounts:" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:70 +msgid "**Goods Received:** defined on the product form" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:72 +msgid "You can check your Profit & Loss or the Balance Sheet reports after having validated a couple of vendor bills to see the impact on your general ledger." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:77 +msgid "Pay a bill" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:79 +msgid "To create a payment for an open vendor bill directly, you can click on **Register a Payment** at the top of the form." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:82 +msgid "From there, you select the payment method (i.e. Checking account, credit card, check, etc…) and the amount you wish to pay. By default, Odoo will propose the entire remaining balance on the bill for payment. In the memo field, we recommend you set the vendor invoice number as a reference (Odoo will auto fill this field from the from the vendor bill if set it correctly)." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:94 +msgid "You can also register a payment to a vendor directly without applying it to a vendor bill. To do that, :menuselection:`Purchases --> Payments`. Then, from the vendor bill you will be able to reconcile this payment with directly." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:99 +msgid "Printing vendor Checks" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:101 +msgid "If you choose to pay your vendor bills by check, Odoo offers a method to do so directly from your vendor payments within Odoo. Whether you do so on a daily basis or prefer to do so at the end of the week, you can print in checks in batches." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:106 +msgid "If you have checks to print, Odoo's accounting dashboard acts as a to do list and reminds you of how many checks you have left to be printed." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:112 +msgid "By selecting the amount of checks to be printed, you can dive right into a list of all payments that are ready to be processed." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:115 +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:127 +msgid "Aged payable balance" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:129 +msgid "In order to get a list of open vendor bills and their related due dates, you can use the **Aged Payable** report, under the reporting menu, (in :menuselection:`Reporting --> Business Statement --> Aged payable`) to get a visual of all of your outstanding bills." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:137 +msgid "From here, you can click directly on a vendors name to open up the details of all outstanding bills and the amounts due, or you can annotate any line for managements information. At any point in time while you're looking through the report, you can print directly to Excel or PDF and get exactly what you see on the screen." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:144 +msgid ":doc:`customer_invoice`" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:3 +msgid "Accounting Terminologies" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:6 +msgid "Journal" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:9 +msgid "A journal is like a folder in which you record all transactions of the same type: all the statements of a bank account, all customer invoices, all supplier bills. It's used to organize similar transactions together." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:13 +msgid "Payment Terms" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:16 +msgid "Payment terms describe how and when a customer invoice (or supplier bill) should be pay over the time. Example: 30% direct payment, balance in two months." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:22 +msgid "Bank reconciliation is the process of matching your payment lines with existing journal items or creating new journal items on the fly." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:28 +msgid "Journal items reconciliation is the process of linking several journal items together like an invoice and a payment. This allows to mark invoices as paid." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:31 +msgid "Deposit Ticket" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:34 +msgid "Deposit tickets group several payment orders (usually checks) that are deposited together at the bank. This allows an easy reconciliation with the bank statement line if the line has one line per deposit." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:38 +msgid "Journal Entry" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:41 +msgid "A journal entry is an accounting transaction, usually related to a financial document: invoice, payment, receipt, etc. A journal entry always consists of at least two lines. The sum of the credits of all journal items of a journal entry is equal to the sum of their debits." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:46 +msgid "Journal Item" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:49 +msgid "A line of a journal entry, with a debit or credit associated to an account." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:51 +msgid "Analytic Accounts" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:54 +msgid "Sometimes called **Cost Accounts**, are accounts that are not part of the chart of account and that allows to track costs and revenues. Analytic account are usually structured by projects, departments, etc. Every journal item is posted in a regular account in the chart of account and can be posted to an analytic accounting for reporting purposes." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:60 +msgid "Analytic Entries" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:63 +msgid "Cost or revenues posted to analytic accounts, usually related to journal entries." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:65 +msgid "Sales Receipt" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:68 +msgid "A receipt or other slip of paper issued by a store or other vendor showing where a purchase was made and also the amount, date, department, etc. Sales receipt are usually used instead of invoices if the sale is paid in cash in the store." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:75 +msgid "Property owned by the company. Odoo Asset management is used to manage the depreciation / amortization of the asset over the time." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:77 +msgid "Deferred Revenues" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:80 +msgid "Are used to recognize revenues of sales of services that are provided over a long period of time. If you sell a 3 years maintenance contract, you can use the deferred revenue mechanism to recognize 1/36 of the revenue every month." +msgstr "" + +#: ../../accounting/overview/terminologies.rst:84 +msgid "Fiscal Position" +msgstr "" + +#: ../../accounting/overview/terminologies.rst:87 +msgid "Define the taxes that should be applied for a specific customer/vendor or invoice. Example: If some customers benefit for specific taxes (government, construction companies, EU companies that are VAT subjected,…), you can assign a fiscal position to them and the right tax will be selected according to the products they buy." +msgstr "" + +#: ../../accounting/payables.rst:3 +msgid "Account Payables" +msgstr "" + +#: ../../accounting/payables/misc.rst:3 +msgid "Misc" +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:187 +msgid "Miscellaneous" +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?" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:5 +msgid "When you get hundreds of vendor bills per month with each of them having different payment terms, it could be complex to follow what you have to pay and when. Paying your vendors too early can decrease your cash availabilities and paying too late can lead to extra charges." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:10 +msgid "Fortunately, Odoo provides you the right tools to manage payment orders to vendors efficiently." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:14 +msgid "Configuration: payment terms" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:16 +msgid "In order to track the vendor conditions, we use payment terms in Odoo. Payment terms allow to keep track of the conditions to compute the due date on an invoice. As an example, a payment term can be:" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:20 +msgid "50% within 30 days" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:22 +msgid "50% within 45 days" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:24 +msgid "To create your most common payment terms, use the menu: :menuselection:`Configuration --> Management --> Payment Terms` in the **Accounting** application. The following example show a payment term of 30% directly and the balance after 30 days." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:32 +msgid "Once payment terms are defined, you can assign them to your vendor by default. Set the Vendor Payment Term field on the Accounting tab of a vendor form. That way, every time you will purchase to this vendor, Odoo will propose you automatically the right payment term." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:42 +msgid "If you do not set a specific payment term on a vendor, you will still be able to set a specific payment term on the vendor bill." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:46 +msgid "Forecast bills to pay with the Aged Payables report" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:48 +msgid "In order to track amounts to be paid to the vendors, use the Aged Payable report. You can get it from the Reports menu of the Accounting application. This report gives you a summary per vendor of the amounts to pay, compared to their due date (the due date being computed on each bill using the payment term)." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:57 +msgid "This reports tells you how much you will have to pay within the next months." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:61 +msgid "Select bills to pay" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:63 +msgid "Using the menu :menuselection:`Purchases --> Vendor Bills`, you can get a list of vendor bills. Using the advanced filters, you can list all the bills that you should pay or the bills that are overdue (you are late on the payment)." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:70 +msgid "From this screen, you can also switch to the pivot table or the graph view to get statistics on the amount due over the next month, using the group by \"Due Date\" feature." +msgstr "" + +#: ../../accounting/payables/pay.rst:3 +msgid "Pay supplier bills" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:3 +msgid "Pay by Checks" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:5 +msgid "Once you decide to pay a supplier bill, you can select to pay by check. Then, at the end of the day, the manager can print all checks by batch. Finally, the bank reconciliation process will match the checks you sent to suppliers with actual bank statements." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:14 +#: ../../accounting/payables/pay/sepa.rst:29 +msgid "Install the required module" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:16 +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 +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 +msgid "Activate checks payment methods" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:31 +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 +msgid "Compatible check stationery for printing checks" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:44 +msgid "United States" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:46 +msgid "For the United States, Odoo supports by default the check formats of:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:48 +msgid "**Quickbooks & Quicken**: check on top, stubs in the middle and bottom" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:49 +msgid "**Peachtree**: check in the middle, stubs on top and bottom" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:50 +msgid "**ADP**: check in the bottom, and stubs on the top." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:52 +msgid "It is also possible to customize your own check format through customizations." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:55 +msgid "Pay a supplier bill with a check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:57 +msgid "Paying a supplier with a check is done in three steps:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:59 +msgid "registering a payment you'd like to do on the bill" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:60 +msgid "printing checks in batch for all registered payments" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:61 +msgid "reconcile bank statements" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:64 +msgid "Register a payment by check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:66 +msgid "To register a payment on a bill, open any supplier bill from the menu :menuselection:`Purchases --> Supplier 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: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 +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 +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 +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" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:109 +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." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:120 +msgid "Pay anything with a check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:122 +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 +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 +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 `_" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:138 +msgid "`Reconcile bank statements `_" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:3 +msgid "How to pay several bills at once?" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:5 +msgid "Odoo provides a simple and effective way to handle several bills at once, with various quick or complex options. With one single process, anyone is able to handle bills and payment in just a few clicks." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:10 +msgid "Pay multiple bills with one payment" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:13 +msgid "Record several payments" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:15 +msgid "In the following example, we will generate some bills. You can control the whole process from your accounting dashboard (first screen you get when you open the accounting application)." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:22 +msgid "To create a bill, open the Dashboard menu and click on **Vendor Bills**. In the Vendor Bills window, click on **Create**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:28 +msgid "Choose the vendor from which you wish to purchase the product, and click on Add an item to add one (or more) product(s). Click on **Save** and then **Validate**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:33 +msgid "Pay supplier bills, one after the other" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:38 +msgid "We will now record a payment for one bill only. Open the bill, then click on **Register Payment**. Insert the Payment Method, Date and Amount, and click on **Validate**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:45 +msgid "Once you have validated the payment, the system will automatically reconcile the payment with the bill, and set the bill as **Paid**. The system will also generate a move from the payment account and reconcile it with the expense transaction." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:51 +msgid "Pay several bills altogether" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:53 +msgid "In order to illustrate the process thoroughly, create at least 2 more bills following the above standing guide. **Make sure all bills come from the same vendor.**" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:60 +msgid "In the Vendors Bills, select the new bills you have just created by checking the box next to each of them. In the Action menu located in the middle of the page, click on **Register Payment**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:67 +msgid "Insert the details of the payment. The system calculated the total amount for both bills, but you can modify it freely. Click on **Validate**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:71 +msgid "Record the payment, reconcile afterwards" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:73 +msgid "You can also reconcile a payment with bills after the payment has been recorded." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:76 +msgid "First, we need to create a payment" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:78 +msgid "This will handle from :menuselection:`Dashboard --> Bank journal --> More Option --> Send Money`" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:84 +msgid "Creating payment order with check payment method. Selecting related Vendor and amount which remain to pay. After filling all details, we will confirm the payment order which will generate payment transaction with the system." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:92 +msgid "As you can see, bill payment status show what is posted and what is remaining to reconcile." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:95 +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 +msgid "Partial payments of several supplier bills" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:109 +msgid "How to pay several supplier bills having cash discounts at once?" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:111 +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 +msgid "We are creating multiple bills and partially pay them through bank statements." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:118 +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 +msgid "We are creating the following bills with the assignment of the above payment term." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:130 +msgid "We have created the following bills:" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:135 +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 +msgid "Before reconciling this bank statement, we need to create one statement model for cash discount." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:147 +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 +msgid "Pay with SEPA" +msgstr "" + +#: ../../accounting/payables/pay/sepa.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. SEPA allows you to send payment orders to your bank to automate bank wire transfer." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:10 +msgid "SEPA is supported by the banks of the 28 EU member states as well as Iceland, Norway, Switzerland, Andorra, Monaco and San Marino." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:13 +msgid "With Odoo, once you decide to pay a vendor, you can select to pay the bill with SEPA. Then, at the end of the day, the manager can generate the SEPA file containing all bank wire transfers and send it to the bank. The file follows the SEPA Credit Transfer 'PAIN.001.001.03' specifications. This is a well-defined standard that makes consensus among banks." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:20 +msgid "Once the payments are processed by your bank, you can directly import the account statement inside Odoo. The bank reconciliation process will seamlessly match the SEPA orders you sent to your bank with actual bank statements." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:31 +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 +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 +msgid "Activate SEPA payment methods on banks" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:43 +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 +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 +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 +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 +msgid "Register your payments" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:72 +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 +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 +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 +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 +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 +msgid "Generate SEPA files" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:98 +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 +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 +msgid "The bank refuses my SEPA file" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:118 +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 +msgid "There is no Bank Identifier Code recorded for bank account ..." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:125 +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/followup.rst:168 +#: ../../accounting/receivables/customer_payments/recording.rst:129 +msgid ":doc:`check`" +msgstr "" + +#: ../../accounting/payables/supplier_bills.rst:3 +msgid "Supplier Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:3 +msgid "When should I use supplier bills or purchase receipts?" +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 paiements. They are my day-to-day ticket receipts." +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." +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 taxe amount over the entire bill." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:20 +msgid "If my company's bank account is used to pay for goods were only a purchase receipt are issued I should use the purchase receipts function in Odoo to handle them in accounting." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:24 +msgid "Let's take the following example: we need to buy foreign 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." +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." +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." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:45 +msgid "Register a receipt" +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." +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`." +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." +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%." +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." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:3 +msgid "How to manage vendor Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:5 +msgid "The **Purchase** application allows you to manage your purchase orders, incoming products, and vendor bills all seamlessly in one place." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:8 +msgid "If you want to set up a vendor bill control process, the first thing you need to do is to have purchase data in Odoo. Knowing what has been purchased and received is the first step towards understanding your purchase management processes." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:13 +msgid "Here is the standard work flow in Odoo:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:15 +msgid "You begin with a **Request for Quotation (RFQ)** to send out to your vendor(s)." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:18 +msgid "Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase Order (PO)**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:21 +msgid "Confirming the PO generates an **Incoming Shipment** if you purchased any stockable products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:24 +msgid "Upon receiving a **Vendor Bill** from your Vendor, validate the bill with products received in the previous step to ensure accuracy." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:27 +msgid "This process may be done by three different people within the company, or only one." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:34 +msgid "Installing the Purchase and Inventory applications" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:36 +msgid "From the **Apps** application, search for the **Purchase** module and install it. Due to certain dependencies, Installing Purchase will automatically install the **Inventory** and **Accounting** applications." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:41 +msgid "Creating products" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:43 +msgid "Creating products in Odoo is essential for quick and efficient purchasing within Odoo. Simply navigate to the Products submenu under Purchase, and click create." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:50 +msgid "When creating the product, Pay attention to the **Product Type** field, as it is important:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:53 +msgid "Products that are set as **Stockable or Consumable** will allow you to keep track of their inventory levels. These options imply stock management and will allow for receiving these kinds of products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:58 +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 +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 recommend to set the product type to **Service**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:70 +msgid "Managing your Vendor Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:73 +msgid "Purchasing products or services" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:75 +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 +msgid "Validate the purchase order and receive the products from the Inventory application." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:89 +msgid "Receiving Products" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:91 +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 +msgid "Navigating this route will take you to a list of all orders awaiting to be received." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:106 +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 also have the capability to 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 +msgid "Purchasing service products does not trigger a delivery order." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:120 +msgid "Managing Vendor Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:122 +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 +msgid "The first thing you will need to do upon creating a Vendor Bill is to select the appropriate Vendor as this will also pull up any associated accounting or pricelist information. From there, you can choose to specify any 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 +msgid "While the invoice is in 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 +msgid "Your vendor may send you several bills for the same Purchase Order if:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:152 +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 +msgid "Your vendor is sending you a partial bill or asking for a deposit." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:155 +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 +msgid "Vendor Bill Matching" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:167 +msgid "What to do if your vendor bill does not match what you received" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:169 +msgid "If the bill you receive from the vendor has different quantities than what Odoo automatically populates as quantities, this could be due to several reasons:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:173 +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 +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 +msgid "or the vendor did not bill you for previously purchased products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:182 +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 +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 +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 +msgid "someone in the company forgot to record a purchase order for this vendor," +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:195 +msgid "or the vendor is charging you for something you did not order." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:200 +msgid "How product quantities are managed" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:202 +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 +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 +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 +msgid "Ordered quantities" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:220 +msgid "or Received quantities" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:223 +msgid "Batch Billing" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:225 +msgid "When creating a vendor bill and selecting the appropriate purchase order, you may continue to select additional purchase orders and Odoo will add the additional line items from that purchase order.. 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/receivables.rst:3 +msgid "Account Receivables" +msgstr "" + +#: ../../accounting/receivables/customer_invoices.rst:3 +msgid "Customer Invoices" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:3 +msgid "How to setup cash discounts?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:5 +msgid "Cash discounts are an incentive (usually a small percentage) that you offer to customers in return for paying a bill owed before the scheduled due date. If used properly, cash discounts improve the Days Sales Outstanding aspect of a business's cash conversion cycle." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:10 +msgid "For example, a typical cash discount would be: you offer a 2% discount on an invoice due in 30 days if the customer were to pay within the first 5 days of receiving the invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:18 +msgid "Payment terms" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:20 +msgid "In order to manage cash discounts, we will use the payment terms concept of Odoo (From the Accounting module, go to :menuselection:`Configuration --> Management --> Payment terms --> Create`)." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:24 +msgid "Let's start with the above example: a 2% discount on an invoice due in 30 days if the customer were to pay within the first 5 days." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:27 +msgid "A typical payment term of 30 days would have only one installment: balance in 30 days. But, in order to configure the cash discount, you can configure the payment term with two installments:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:31 +msgid "98% within 5 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:32 +msgid "balance within 30 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:37 +msgid "To make it clear that it's not a payment term but a cash discount, don't forget to set a clear description that will appear on the invoice: Invoice is due within 30 days, but you can benefit from a 2% cash discount if you pay within 5 days." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:43 +msgid "Bank reconciliation model" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:45 +msgid "In order to speed up the bank reconciliation process, we can create a model of entry for all cash discounts. To do that, from the Accounting application dashboard, click on the \"More\" link on the bank and choose the option \"Reconciliation Models\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:53 +msgid "Create a new model for cash discounts as follow:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:55 +msgid "**Button Label**: Cash Discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:56 +msgid "**Account**: Cash Discount (according to your country)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:57 +msgid "**Amount Type**: Percentage" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:58 +msgid "**Amount**: 100%" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:60 +msgid "**Taxes**: depending on your country, you may put a tax on the cash" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:60 +msgid "discount if taxes have to be deduced" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:67 +msgid "Even if it's a 2% cash discount, set a 100% amount on the reconciliation model as it means 100% of the remaining balance (the 2%). You can use the same reconciliation model for all your cash discount. No need to create a model per payment term." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:73 +msgid "Creating an invoice with a cash discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:75 +msgid "When you create a customer invoice, set the right payment term \"30 days, 2% cash discount\" right after having selected the customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:81 +msgid "Once the invoice is validated, Odoo will automatically split the account receivable part of the journal entry with two installments having a different due date: 98% within 5 days, 2% within 30 days." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:92 +msgid "Paying the invoice with a cash discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:94 +msgid "If the customer pays with a cash discount, when processing the bank statement, you will match the payment (98%) with the related line in the journal entry." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:101 +msgid "As you can see in the above screenshot, when selecting the customer, you also see the 2% remaining of 3$. If you want to accept the cash discount (if the customer paid within the 5 days), you can click on this line with 2%, click on \"Open Balance\", and select your \"Cash Discount\" reconciliation model. That way, the invoice is marked as fully paid." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:109 +msgid "from now on, matching the remaining 2% has to be done manually. In the future, we plan to automate the reconciliation of the 2% if the 98% are paid on time." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:113 +msgid "Paying the invoice in full" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:115 +msgid "If the customer pays the invoice fully, without benefiting from the cash discount, you will reconcile the payment (in full) with the two lines from the invoice (98% and 2%). Just click on the two lines to match them with the payment." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:125 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:116 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:86 +msgid ":doc:`overview`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:3 +msgid "Deferred revenues: how to automate them?" +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." +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." +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:27 +msgid "Module installation" +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." +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:41 +msgid "Define deferred revenue types" +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`." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:51 +msgid "Example: 12 months maintenance contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:53 +msgid "Some example of deferred revenues types:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:55 +msgid "1 year service contract" +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" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:59 +msgid "Set deferred revenues on products" +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:65 +msgid "Here are some examples of products and their related deferred revenue types:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:69 +msgid "Product" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:69 +msgid "Deferred Revenue Type" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:71 +msgid "Support Contract: 3 years" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:73 +msgid "Netflix subscription: 3 years" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:75 +msgid "Flowers every month" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:75 +msgid "1 year product contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:79 +msgid "Sell and invoice products" +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 +msgid "**Dr**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 +msgid "**Cr**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:89 +msgid "Accounts receivable" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:89 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:91 +msgid "24000" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:91 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:100 +msgid "Deferred revenue account" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:94 +msgid "Then, every month, Odoo will post a journal entry for the revenue recognition." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:100 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:102 +msgid "1000" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:102 +msgid "Service revenue account" +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:3 +msgid "How to define an installment plan for an invoice" +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:8 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:8 +msgid "Example, for a specific invoice:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:10 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:10 +msgid "Pay 50% within 10 days" +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" +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:22 +msgid "Configure your usual installment plans from the application :menuselection:`Accounting --> Configuration > Payment Terms`." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.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, 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%)" +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:39 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:38 +msgid "Payment terms for customers" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:41 +msgid "You can set payment terms on:" +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." +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" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:51 +msgid "**an invoice**: the payment term will apply on this invoice only" +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):" +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" +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:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 +msgid "Jan 03" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 +msgid "10" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 +msgid "Jan 30" +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`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:3 +msgid "How to modify a validated invoice?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:5 +msgid "In most accounting legislation over the word, it's not allowed to modify an invoice that is validated and sent to the customer. However, you sometimes need to change an invoice for different reasons: the sale has changed, the made a mistake while recording the invoice, etc." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:10 +msgid "Thus, the right way to modify an invoice is to:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:12 +msgid "Refund the original invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:13 +msgid "Create a new invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:15 +msgid "Odoo's refund mechanism helps you handle the whole process in just a few clicks." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:19 +msgid "Modify an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:21 +msgid "If your invoice is still in draft, you can modify it the way you want. However, if your invoice is validated, you can not change it anymore. If you need to modify it, the right operations to do are:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:25 +msgid "Refund the original invoice;" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:26 +msgid "Reconcile the original invoice with the refund to void them;" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:27 +msgid "Create a new draft invoice, a copy of the original;" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:28 +msgid "Validate the new invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:30 +msgid "All those steps are automated by Odoo. All you have to do is to click on the Refund button on an invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:36 +msgid "In the refund dialog, select the option \"Modify: create a refund, reconcile and create a draft invoice\". Once you click on the \"Create Refund\" button, Odoo will void your existing invoice and create a new draft invoice that is a duplicate of the original one." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:41 +msgid "Edit this new draft invoice and validate it when it's correct." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:45 +msgid "if you already sent the original invoice to your customer, you should send the new invoice and the refund to the customer so that he gets all the documents." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:50 +msgid ":doc:`refund`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:3 +msgid "Overview of the invoicing process" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:5 +msgid "Depending on your business and the application you use, there are different ways to automate the customer invoice creation in Odoo. Usually, draft invoices are created by the system (with information coming from other documents like sales order or contracts) and accountant just have to validate draft invoices and send the invoices in batch (by regular mail or email)." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:12 +msgid "Depending on your business, you may opt for one of the following way to create draft invoices:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:19 +msgid "Sales Order ‣ Invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:21 +msgid "In most companies, salespeople create quotations that become sales order once they are validated. Then, draft invoices are created based on the sales order. You have different options like:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:25 +msgid "Invoice manually: use a button on the sale order to trigger the draft invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:28 +msgid "Invoice before delivery: invoice the full order before triggering the delivery order" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:31 +msgid "Invoice based on delivery order: see next section" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:33 +msgid "Invoice before delivery is usually used by the eCommerce application when the customer pays at the order and we deliver afterwards. (pre-paid)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:37 +msgid "For most other use cases, it's recommended to invoice manually. It allows the salesperson to trigger the invoice on demand with options: invoice the whole order, invoice a percentage (advance), invoice some lines, invoice a fixed advance." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:42 +msgid "This process is good for both services and physical products." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:47 +msgid "Sales Order ‣ Delivery Order ‣ Invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:49 +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 +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" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:64 +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 +msgid "Contracts" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:73 +msgid "Regular Contracts ‣ Invoices" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:75 +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 +msgid "Activities can be:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:81 +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)" +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 +msgid "expenses like travel and accommodation that you re-invoice to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:89 +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:99 +msgid "Recurring Contracts ‣ Invoices" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:101 +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 +msgid "Creating an invoice manually" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:113 +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 +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 +msgid "if you need to create a refund" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:123 +msgid "If you need to give a discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:125 +msgid "if you need to change an invoice created from a sales order" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:127 +msgid "if you need to invoice something not related to your core business" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:130 +msgid "Specific modules" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:132 +msgid "Some specific modules are also able to generate draft invoices:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:134 +msgid "**membership**: invoice your members every year" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:136 +msgid "**repairs**: invoice your after-sale services" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:3 +msgid "Defining and using payment terms" +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:14 +msgid "Payment terms are different from invoicing in several times. If, for a specific order, you invoice the customer in two parts, that's not a payment term but invoice conditions." +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." +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%)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:35 +msgid "Using Payment Terms" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:40 +msgid "Payment terms can be set 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." +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" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:51 +msgid "**an invoice**: to apply the payment term on this invoice only" +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:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:79 +msgid "In the customer statement, you will see two lines with different due dates." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:83 +msgid "Payment terms for vendor bills" +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." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96 +msgid ":doc:`cash_discounts`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:3 +msgid "How to edit or refund an invoice?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:4 +msgid "In Odoo, it's not possible to modify an invoice that has been validated and sent to the customer. If a mistake was made on a validated invoice, the legal way to handle that is to refund the invoice, reconcile it with the original invoice to close them and create a new invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:10 +msgid "Modifying a validated invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:12 +msgid "If you need to modify an existing invoice, use the Refund Invoice button on the invoice. In the refund method field, select \"Modify: create a refund, reconcile, and create a new draft invoice\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:19 +#: ../../accounting/receivables/customer_invoices/refund.rst:37 +msgid "Odoo will automatically:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:21 +#: ../../accounting/receivables/customer_invoices/refund.rst:39 +msgid "Create a refund for your invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:22 +#: ../../accounting/receivables/customer_invoices/refund.rst:40 +msgid "Reconcile the refund invoice with the original invoice (marking both as Paid)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:23 +msgid "Create a new draft invoice you can modify" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:25 +msgid "Then, you can modify the draft invoice and validate it once it's correct." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:28 +msgid "Cancelling an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:30 +msgid "If you need to cancel an existing invoice, use the Refund Invoice button on the invoice. In the refund method field, select \"Cancel: create a refund and reconcile\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:42 +msgid "Nothing else needs to be done. You can send the refund by regular mail or email to your customer, if you already sent the original invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:46 +msgid "Refunding part of an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:48 +msgid "If you need to refund an existing invoice partially, use the Refund Invoice button on the invoice. In the refund method field, select \"Create a draft refund\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:55 +msgid "Odoo will automatically create a draft refund. You may modify the refund (example: remove the lines you do not want to refund) and validate it. Then, send the refund by regular mail or email to your customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:61 +msgid "Refunding an invoice is different from refunding a payment. Usually, a refund invoice is sent before the customer has done a payment. If the customer has already paid, they should be reimbursed by doing a customer payment refund." +msgstr "" + +#: ../../accounting/receivables/customer_payments.rst:3 +msgid "Customer Payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:3 +msgid "How to register customer payments by checks" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:5 +msgid "There are two ways to handle payments received by checks. Odoo support both approaches so that you can use the one that better fits your habits." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:9 +msgid "**Undeposited Funds:** once you receive the check, you record a payment by check on the invoice. (using a Check journal and posted on the Undeposited Fund account) Then, once the check arrives in your bank account, move money from Undeposited Funds to your bank account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:16 +msgid "**One journal entry only:** once your receive the check, you record a payment on your bank, paid by check, without going through the **Undeposited Funds**. Once you process your bank statement, you do the matching with your bank feed and the check payment, without creating a dedicated journal entry." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:23 +msgid "We recommend the first approach as it is more accurate (your bank account balance is accurate, taking into accounts checks that have not been cashed yet). Both approaches require the same effort." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:27 +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/check.rst:32 +msgid "You may have a look at the *Deposit Ticket feature* if you deposit several checks to your bank accounts in batch." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:36 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:37 +msgid "Option 1: Undeposited Funds" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:41 +msgid "Create a journal **Checks**" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:43 +msgid "Set **Undeposited Checks** as a defaut credit/debit account" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:45 +msgid "Set the bank account related to this journal as **Allow Reconciliation**" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:48 +#: ../../accounting/receivables/customer_payments/check.rst:109 +msgid "From check payments to bank statements" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:50 +msgid "The first way to handle checks is to create a check journal. Thus, checks become a payment method in itself and you will record two transactions." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:54 +#: ../../accounting/receivables/customer_payments/check.rst:111 +msgid "Once you receive a customer check, go to the related invoice and click on **Register Payment**. Fill in the information about the payment:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:57 +msgid "Payment method: Check Journal (that you configured with the debit and credit default accounts as **Undeposited Funds**)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:60 +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 "" + +#: ../../accounting/receivables/customer_payments/check.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:72 +#: ../../accounting/receivables/customer_payments/check.rst:83 +#: ../../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 "" + +#: ../../accounting/receivables/customer_payments/check.rst:72 +#: ../../accounting/receivables/customer_payments/check.rst:83 +msgid "Undeposited Funds" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:75 +#: ../../accounting/receivables/customer_payments/check.rst:121 +msgid "The invoice is marked as paid as soon as you record the check." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:77 +msgid "Then, once you get the bank statements, you will match this statement with the check that is in Undeposited Funds." +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 "" + +#: ../../accounting/receivables/customer_payments/check.rst:89 +msgid "If you use this approach to manage received checks, you get the list of checks that have not been cashed in the **Undeposit Funds** account (accessible, for example, from the general ledger)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:94 +msgid "Both methods will produce the same data in your accounting at the end of the process. But, if you have checks that have not been cashed, this one is cleaner because those checks have not been reported yet on your bank account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:100 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:110 +msgid "Option 2: One journal entry only" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:105 +msgid "These is nothing to configure if you plan to manage your checks using this method." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:114 +msgid "**Payment method:** the bank that will be used for the deposit" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:116 +msgid "Memo: write the check number" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:123 +msgid "Once you will 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/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 "" + +#: ../../accounting/receivables/customer_payments/check.rst:139 +msgid "You may also record the payment directly without going on the customer invoice, using the menu :menuselection:`Sales --> Payments`. This method may be more convenient if you have a lot of checks to record in a batch but you will have to reconcile entries afterwards (matching payments with invoices)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:145 +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 handle 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 "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 +#: ../../accounting/receivables/customer_payments/followup.rst:167 +msgid ":doc:`recording`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:167 +#: ../../accounting/receivables/customer_payments/recording.rst:128 +msgid ":doc:`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 "How to get paid and organize customer follow-ups?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:5 +msgid "Getting paid and organizing customer reminders is always a difficult task, however it is critical for the health of the company to stay diligent about outstanding receivables. Fortunately, Odoo provides the right tools to track receivables, automate customer statements, and measure your performance." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:12 +msgid "Customer follow-ups: A step by step guide" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:15 +msgid "Cleaning up outstanding payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:17 +msgid "If you have any unreconciled transactions in your bank account, you will need to process them first before you begin analyzing your customers statements. This ensures that you have recorded all of the latest customer payments before sending out reminders to any customers with outstanding balances." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:27 +msgid "Checking the Aged Receivables report" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:29 +msgid "After you have reconciled all of your bank accounts, you can then generate an accurate Aged Receivables Report from the Reports menu. This report will display all of the customers and their outstanding balances on open invoices." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:37 +msgid "The report displays this information in time increments to better paint a picture of the outstanding balances your customers hold and for how long they have held these outstanding balances. You can then appropriately focus your efforts on the appropriate customers." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:42 +msgid "You can then select any of the customers on this list and Odoo will open up their invoice details in the form of the Customer Follow-Up letter, also known as the **Customer Statement**." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:49 +msgid "From the customer statement, you can:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:51 +msgid "Change and customize the message that is sent to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:53 +msgid "Send a reminder email to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:55 +msgid "Send a printed reminder letter to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:57 +msgid "Send automated printed reminders by utilizing our Docsaway integration" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:60 +msgid "Zoom in on the different open invoices or payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:62 +msgid "Remove an invoice or payment from the report (in case of conflict)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:64 +msgid "Log any call notes made to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:66 +msgid "Schedule your next follow up task to stay on top of customer payments (e.g. call back in 15 days if not payments are made)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:69 +msgid "You can set reminders for when you would like to next contact the particular customer. Selecting **Manual** will open up the follow up scheduling tool, while selecting **Auto** will automatically recommend that you contact the customer 15 days from then if the customer has not yet paid for the invoice. Installing the **Follow-Up Plans** module will allow you to define automated actions and intervals to send reminders." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:79 +msgid "If you have already sent out a reminder to a customer a few days ago, a warning message will appear at the top of the screen, reminding you that you should not send another reminder so soon since one was already sent recently. Every time you log a note, Odoo will automatically set the next reminder date, unless you choose to manually set it by selecting the next reminder button at the top right of the screen." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:88 +msgid "You can also specify the expected payment date on an invoice line directly, therefore defining the next reminder in case the invoice has not been paid." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:92 +msgid "Sending customer statements" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:94 +msgid "Send your customers reminders in batches in the menu :menuselection:`Sales --> Customer Statements`." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:97 +msgid "Here Odoo will open all the statements awaiting to be processed, which is determined by the last reminder they received. You can choose to process them one by one, send multiple letters or emails in batches, or set a next action date for the next time they'll be contacted." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:104 +msgid "If an invoice has not yet been paid, Odoo will remind you to contact at particular customer based after their next action date." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:107 +msgid "You can access the customer statement report daily and Odoo will only display the customers you need to contact on any given day. This is based on:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:111 +msgid "Customers you have not yet received a payment from" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:113 +msgid "Customers that have not been reminded over the last X days (\"X\" being defined as the overdue date of the invoice after the first reminder, then the next action date set at every reminder)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:118 +msgid "Setting up your dunning process" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:120 +msgid "The **Payment Follow-up Management** module allows you to define reminder plans. After installing it from the **Apps** menu, go to the **Follow-up Levels** menu in the accounting configuration to set up your dunning process." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:125 +msgid "Some Examples are:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:127 +msgid "**Email**: 3 days before overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:129 +msgid "**Email+Letter**: at the overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:131 +msgid "**Email+Call**: 15 days after the overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:133 +msgid "**Email+Letter**: 60 days after the overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:138 +msgid "Thanks to this module, you can send every email and letters in batches for all your customers at once. The next reminder will automatically be computed based on your configured follow-up plan." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:142 +msgid "The module will also add a red/green dot on each customer, this will allow you to easily mark customer status's with the following options: \"Good Debtor, Normal Debtor, or bad debtors." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:150 +msgid "DSO: Measuring your performance" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:152 +msgid "The DSO (Days of Outstanding Sales) is a measure of the average number of days that a company takes to collect revenue after a sale has been made. DSO is calculated by dividing the amount of accounts receivable during a given period by the total value of credit sales during the same period, and multiplying the result by the number of days in the period measured." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:159 +msgid "You can get the DSO of your company from the Executive Summary report under Reporting (check the KPI average debtors days)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:3 +msgid "How to accept paypal payments on invoices?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:5 +msgid "The \"Paypal Payment Acquirer\" module allows you to accept payments via paypal, for your sales orders, invoices, or online orders. As paypal accepts payments through credit cards (VISA, Mastercard, …), you will be able to process most payment methods." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:10 +msgid "Paypal support two modes:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:12 +msgid "Paypal Merchant Account: the user is redirected to paypal to do the payment (either with a credit card or a paypal account)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:15 +msgid "PayPal PayFlow Pro (S2S, Server 2 Server): the user is not redirected to paypal and the payment can be done in the background. This method is mostly used for subscription businesses where you need to charge your customers periodically." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:20 +msgid "As of today, Odoo only support the normal Paypal Merchant Account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:26 +msgid "Install the \"PayPal Payment Acquirer\" module" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:28 +msgid "Start by installing the **PayPal Payment Acquirer** module." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:30 +msgid "Once the module is installed, you should see a new payment acquirer in the Setting application, menu \"Payment Acquirers\"." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:36 +msgid "By default, Paypal is configured to work in a test environment, out-of-the-box. It means you can already test the full order to payment flow with the paypal sandbox, without having to configure the next steps." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:42 +msgid "Creating and configuring a PayPal merchant account" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:45 +msgid "Create a basic Paypal account" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:47 +msgid "Existing or newly created Personal Paypal account can be used." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:49 +msgid "Or upgrade your account to Business account (merchant) if needed" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:55 +msgid "Paypal Account Summary page" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:58 +msgid "Paypal Configuration" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:60 +msgid "Access \"Seller preferences\" menu from `PayPal website `__" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:66 +msgid "Access \"Website preferences\" and configure Auto Return" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:68 +msgid "**Database name**: yourcompany" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:69 +#: ../../accounting/receivables/customer_payments/paypal.rst:87 +msgid "**Website URL**: https://yourcompany.odoo.com/" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:70 +msgid "**Return URL**: https://yourcompany.odoo.com/shop/confirmation" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:75 +msgid "These settings will redirect your buyer to your web confirmation page." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:79 +msgid "Access and edit Instant payment notifications settings - IPN" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:84 +msgid "Example" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:86 +msgid "**Database name**: \"yourcompany\"" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:88 +msgid "**Notification URL**: https://yourcompany.odoo.com/payment/paypal/ipn/" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:90 +msgid "verify that your Notify URL uses the correct protocol (HTTP / HTTPS)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:92 +msgid "Set the encoding to UTF-8 from the menu :menuselection:`Settings --> Language Encoding --> More Options --> More selling tools`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:101 +msgid "Record your Merchant Paypal ID (personal or business account both will have it) it will be entered in Odoo backend :menuselection:`Paypal Settings --> Account Options`." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:109 +msgid "If you want your customers to be able to pay through Paypal while not having a Paypal account- following setting \"Paypal Account Optional\" needs to be set to **ON**. All users will be able to choose Credit/debit card payment option - Paypal account not required." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:118 +msgid "Setup your Paypal Payment Acquirer account credentials in Odoo" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:120 +msgid ":menuselection:`Settings --> Payments --> Payment Acquirers --> Paypal`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:122 +msgid "**Paypal Email ID**: your paypal account email address" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:124 +msgid "**Paypal Merchant ID**: ID retrieved at previous step" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:134 +msgid "If your eCommerce customer gets this Error Message after completing Paypal payment instead of being redirected to your database:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:140 +msgid "Verify the Auto Return URL you have `configured in Paypal `_ is correct and pointing to your own domain name." +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:143 +msgid "You can either:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:145 +msgid "Enter the correct return URL and activate Auto Return" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:147 +msgid "or deactivate Auto Return and delete URL (this method will have an extra click through Paypal in order to return to your ecommerce page.)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/paypal.rst:153 +#: ../../accounting/receivables/customer_payments/recording.rst:127 +msgid ":doc:`credit_cards`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:3 +msgid "What are the different ways to record a payment?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:5 +msgid "In Odoo, a payment can either be linked directly to an invoice or be a stand alone record for use on a later date:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:8 +msgid "If a payment is linked to an invoice, it reduces the amount due of the invoice. You can have multiple payments linked to the same invoice." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:12 +msgid "If a payment is not linked to an invoice, the customer has an outstanding credit with your company, or your company as an outstanding balance with a vendor. You can use this outstanding credit/debit to pay future invoices or bills." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:18 +msgid "Paying an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:20 +msgid "If you register a payment on a customer invoice or a vendor bill, the payment is automatically reconciled with the invoice reducing the amount due." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:27 +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 +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 +msgid "Payments not tied to an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:42 +msgid "Registering a payment" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:44 +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 +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 +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 +msgid "Reconciling invoice payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:64 +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 +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 +msgid "Reconciling all your outstanding payments and invoices" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:78 +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 +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 +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 +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 +msgid "Transferring money from one bank account to another" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:103 +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 +msgid "This will take you to the same screen you have for receiving and making payments." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:118 +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/getting_paid.rst:3 +msgid "How to get paid?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:3 +msgid "How to automate customer follow-ups with plans?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:5 +msgid "With the Odoo Accounting application, you get a dynamic aged receivable report, customer statements and you can easily send them to customers." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:8 +msgid "If you want to go further in the automation of the credit collection process, you can use follow-up plans. They will help you automate all the steps to get paid, by triggering them at the right time: send customer statements by emails, send regular letter (through the Docsaway integration), create a task to manually call the customer, etc..." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:14 +msgid "Here is an example of a plan:" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:17 +msgid "When?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:17 +msgid "What?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:17 +msgid "Who?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:19 +msgid "3 days before due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:19 +msgid "Email" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:19 +#: ../../accounting/receivables/getting_paid/automated_followups.rst:21 +msgid "automated" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:21 +msgid "1 day after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:21 +msgid "Email + Regular Letter" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:23 +msgid "15 days after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:23 +msgid "Call the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:23 +#: ../../accounting/receivables/getting_paid/automated_followups.rst:25 +msgid "John Mac Gregor" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:25 +msgid "35 days after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:25 +msgid "Email + Letter + Call" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:27 +msgid "60 days after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:27 +msgid "Formal notice" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:27 +msgid "Bailiff" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:34 +msgid "Install Reminder Module" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:36 +msgid "You must start by activating the feature, using the menu :menuselection:`Configuration --> Settings` of the Accounting application. From the settings screen, activate the feature **Enable payment follow-up management**." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:44 +msgid "Define Payment Follow-ups Levels" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:46 +msgid "To automate customer follow ups, you must configure your follow–up levels using the menu :menuselection:`Accounting --> Configuration --> Payment Follow-ups`. You should define one and only one follow-up plan per company." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:50 +msgid "The levels of follow-up are relative to the due date; when no payment term is specified, the invoice date will be considered as the due date." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:53 +msgid "For each level, you should define the number of days and create a note which will automatically be added into the reminder letter." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:59 +msgid "Odoo defines several actions for every reminder:" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:61 +msgid "**Manual Action:** assign a responsible that will have to call the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:62 +msgid "**Send an Email:** send an email to customer using the provided text" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:63 +msgid "**Send a Letter:** send a letter by regular mail, using the provided note" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:69 +msgid "As you need to provide a number of days relative to the due date, you can use a negative number. As an example, if an invoice is issued the January 1st but the due date is January 30, if you set a reminder 3 days before the due date, the customer may receive an email in January 17." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:76 +msgid "Doing your weekly follow-ups" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:78 +msgid "Once everything is setup, Odoo will prepare follow-up letters and emails automatically for you. All you have to do is to the menu :menuselection:`Sales --> Customers Statement` in the accounting application." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:85 +msgid "Odoo will automatically propose you actions based on the follow-up plan you defined, invoices to pay and payment received." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:88 +msgid "You can use this menu every day, once a week or once a month. You do not risk to send two times the same reminder to your customer. Odoo only proposes you the action you have to do. If you do it every day, you will have a few calls to do per day. If you do it once a month, you will have much more work once you do it." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:94 +msgid "It's up to you to organize the way you want to work. But it's a good practice to reconcile your bank statements before launching the follow-ups. That way, all paid invoices will be reconciled and you will not send a follow-up letter to a customer that already paid his invoice." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:99 +msgid "From a customer follow-up proposition, you can:" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:101 +msgid "Get the customer information to contact him" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:103 +msgid "Drill down to the customer information form by clicking on its name" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:105 +msgid "Change the text (or the email or letter) and adapt to the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:107 +msgid "Change the colored dot to mark the customer as being a good, normal or bad debtor" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:110 +msgid "Log a note is you called the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:112 +msgid "Exclude some invoices from the statement table (litigation)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:114 +msgid "Send an email with the statement" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:116 +msgid "Print a letter, or send a regular mail (if you installed the Docsaway integration)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:119 +msgid "Plan the next reminder (but it's better to keep in automatic mode so that Odoo will stick to the follow-up plan of the company)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:122 +msgid "Drill down to an invoice" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:124 +msgid "Change the expected payment date of an invoice (thus, impacting the next time Odoo will propose you to send a reminder)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:128 +msgid "You can force a customer statement, even if Odoo do not proposes you to do it, because it's not the right date yet. To do this, you should go to the Aged Receivable report (in the report menu of the Accounting application). From this report, you can click on a customer to get to his customer statement." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:135 +msgid "How to exclude an invoice from auto follow up?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:137 +msgid "To see all **overdue invoices** or **on need of action**," +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:139 +msgid "Go to :menuselection:`Accounting --> Sales --> Customers Statement`" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:145 +msgid "Exclude a specific invoice for a specific date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:147 +msgid "Odoo can exclude an invoice from follow-ups actions for specific date by clicking on **Log a Note**, then choose one of the ready options (*one week*, *two weeks*, *one month*, *two months*), So Odoo will calculate the required date according to the current date." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:155 +msgid "Another way to achieve it is the following: click on the required invoice, then choose **Change expected payment date/note**, then enter a new payment date and note." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:162 +msgid "Exclude a specific invoice forever" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:164 +msgid "Odoo can exclude an invoice for a specific customer by clicking on the checkbox **Excluded**" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:168 +msgid "If you click on **History**, you can see all follow ups actions." +msgstr "" + diff --git a/locale/sources/applications.pot b/locale/sources/applications.pot new file mode 100644 index 000000000..72cfba6f1 --- /dev/null +++ b/locale/sources/applications.pot @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2015-11-03 11:43+0100\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" + +#: ../../applications.rst:3 +msgid "Applications" +msgstr "" + diff --git a/locale/sources/crm.pot b/locale/sources/crm.pot new file mode 100644 index 000000000..bdc71fccf --- /dev/null +++ b/locale/sources/crm.pot @@ -0,0 +1,1163 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2015-11-03 11:43+0100\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" + +#: ../../crm.rst:5 +msgid "CRM" +msgstr "" + +#: ../../crm/leads.rst:3 +msgid "Leads" +msgstr "" + +#: ../../crm/leads/generate.rst:3 +msgid "Generate leads" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:3 +msgid "How to generate leads from incoming emails?" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:5 +msgid "There are several ways for your company to :doc:`generate leads with Odoo CRM `. One of them is using your company's generic email address as a trigger to create a new lead in the system. In Odoo, each one of your sales teams is linked to its own email address from which prospects can reach them. For example, if the personal email address of your Direct team is **direct@mycompany.example.com**, every email sent will automatically create a new opportunity into the sales team." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:14 +#: ../../crm/leads/generate/website.rst:73 +#: ../../crm/leads/manage/automatic_assignation.rst:30 +#: ../../crm/leads/manage/lead_scoring.rst:19 +#: ../../crm/overview/started/setup.rst:10 +msgid "Configuration" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:16 +msgid "The first thing you need to do is to configure your **outgoing email servers** and **incoming email gateway** from the :menuselection:`Settings module --> General Settings`." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:19 +msgid "Then set up your alias domain from the field shown here below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:26 +msgid "Set up team alias" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:28 +msgid "Go on the Sales module and click on **Dashboard**. You will see that the activation of your domain alias has generated a default email alias for your existing sales teams." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:35 +msgid "You can easily personalize your sales teams aliases. Click on the More button from the sales team of your choice, then on **Settings** to access the sales team form. From the **Email Alias** field, enter your email alias and click on **Save**. Make sure to allow receiving emails from everyone." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:41 +msgid "From there, each email sent to this email address will generate a new lead into the related sales team." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:48 +msgid "Set up catch-all email domain" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:50 +msgid "Additionally to your sales team aliases, you can also create a generic email alias (e.g. *contact@* or *info@* ) that will also generate a new contact in Odoo CRM. Still from the Sales module, go to :menuselection:`Configuration --> Settings` and set up your catch-all email domain." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:57 +msgid "You can choose whether the contacts generated from your catch-all email become leads or opportunities using the radio buttons that you see on the screenshot here below. Note that, by default, the lead stage is not activated in Odoo CRM." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:67 +#: ../../crm/leads/generate/import.rst:89 +#: ../../crm/leads/generate/website.rst:194 +msgid ":doc:`manual`" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:68 +#: ../../crm/leads/generate/manual.rst:69 +#: ../../crm/leads/generate/website.rst:195 +msgid ":doc:`import`" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:69 +#: ../../crm/leads/generate/import.rst:91 +#: ../../crm/leads/generate/manual.rst:73 +msgid ":doc:`website`" +msgstr "" + +#: ../../crm/leads/generate/import.rst:3 +msgid "How to import contacts to the CRM?" +msgstr "" + +#: ../../crm/leads/generate/import.rst:5 +msgid "In Odoo CRM, you can import a database of potential customers, for instance for a cold emailing or cold calling campaign, through a CSV file. You may be wondering if the best option is to import your contacts as leads or opportunities. It depends on your business specificities and workflow:" +msgstr "" + +#: ../../crm/leads/generate/import.rst:11 +msgid "Some companies may decide to not use leads, but instead to keep all information directly in an opportunity. For some companies, leads are merely an extra step in the sales process. You could call this extended (start from lead) versus simplified (start from opportunity) customer relationship management." +msgstr "" + +#: ../../crm/leads/generate/import.rst:17 +msgid "Odoo perfectly allows for either one of these approaches to be chosen. If your company handles its sales from a pre qualification step, feel free to activate first the lead stage as described below in order to import your database as leads" +msgstr "" + +#: ../../crm/leads/generate/import.rst:23 +#: ../../crm/leads/generate/manual.rst:9 +#: ../../crm/leads/generate/website.rst:38 +#: ../../crm/salesteam/setup/organize_pipeline.rst:62 +msgid "Activate the lead stage" +msgstr "" + +#: ../../crm/leads/generate/import.rst:25 +msgid "By default, the lead stage is not activated in Odoo CRM. If you want to import your contacts as leads rather than opportunities, go to :menuselection:`Configuration --> Settings`, select the option **use leads if…** as shown below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/import.rst:33 +msgid "This activation will create a new submenu :menuselection:`Sales --> Leads` from which you will be able to import your contacts from the **Import** button (if you want to create a lead manually, :doc:`click here `)" +msgstr "" + +#: ../../crm/leads/generate/import.rst:41 +msgid "Import your CSV file" +msgstr "" + +#: ../../crm/leads/generate/import.rst:43 +msgid "On the new submenu :menuselection:`Sales --> Leads`, click on **Import** and select your Excel file to import from the **Choose File** button. Make sure its extension is **.csv** and don't forget to set up the correct File format options (**Encoding** and **Separator**) to match your local settings and display your columns properly." +msgstr "" + +#: ../../crm/leads/generate/import.rst:50 +msgid "If your prospects database is provided in another format than CSV, you can easily convert it to the CSV format using Microsoft Excel, OpenOffice / LibreOffice Calc, Google Docs, etc." +msgstr "" + +#: ../../crm/leads/generate/import.rst:58 +msgid "Select rows to import" +msgstr "" + +#: ../../crm/leads/generate/import.rst:60 +msgid "Odoo will automatically map the column headers from your CSV file to the corresponding fields if you tick *The first row of the file contains the label of the column* option. This makes imports easier especially when the file has many columns. Of course, you can remap the column headers to describe the property you are importing data into (First Name, Last Name, Email, etc.)." +msgstr "" + +#: ../../crm/leads/generate/import.rst:72 +msgid "If you want to import your contacts as opportunities rather than leads, make sure to add the *Type* column to your csv. This column is used to indicate whether your import will be flagged as a Lead (type = Lead) or as an opportunity (type = Opportunity)." +msgstr "" + +#: ../../crm/leads/generate/import.rst:77 +msgid "Click the **Validate** button if you want to let Odoo verify that everything seems okay before importing. Otherwise, you can directly click the Import button: the same validations will be done." +msgstr "" + +#: ../../crm/leads/generate/import.rst:83 +msgid "For additional technical information on how to import contacts into Odoo CRM, read the **Frequently Asked Questions** section located below the Import tool on the same window." +msgstr "" + +#: ../../crm/leads/generate/import.rst:90 +#: ../../crm/leads/generate/manual.rst:71 +#: ../../crm/leads/generate/website.rst:196 +msgid ":doc:`emails`" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:3 +msgid "How to create a contact into Odoo CRM?" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:5 +msgid "Odoo CRM allows you to manually add contacts into your pipeline. It can be either a lead or an opportunity." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:11 +msgid "By default, the lead stage is not activated in Odoo CRM. To activate it, go to :menuselection:`Configuration --> Settings`, select the option \"\"use leads if…** as shown below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:18 +msgid "This activation will create a new submenu **Leads** under **Sales** that gives you access to a list of all your leads from which you will be able to create a new contact." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:26 +msgid "Create a new lead" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:28 +msgid "Go to :menuselection:`Sales --> Leads` and click the **Create** button." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:33 +msgid "From the contact form, provide all the details in your possession (contact name, email, phone, address, etc.) as well as some additional information in the **Internal notes** field. You can also link the lead to an existing company by editing the**Customer** field. Click on save and the contact will be visible as a lead in your pipeline ." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:41 +msgid "your lead can be directly handed over to specific sales team and salesperson by clicking on **Convert to Opportunity** on the upper left corner of the screen." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:45 +msgid "Create a new opportunity" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:47 +msgid "You can also directly add a contact into a specific sales team without having to convert the lead first. On the Sales module, go to your dashboard and click on the **Pipeline** button of the desired sales team. If you don't have any sales team yet, :doc:`you need to create one first <../../salesteam/setup/create_team>`. Then, click on **Create** and fill in the contact details as shown here above. By default, the newly created opportunity will appear on the first stage of your sales pipeline." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:55 +msgid "Another way to create an opportunity is by adding it directly on a specific stage. For example, if you have have spoken to Mr. Smith at a meeting and you want to send him a quotation right away, you can add his contact details on the fly directly into the **Proposition** stage. From the Kanban view of your sales team, just click on the **+** icon at the right of your stage to create the contact. The new opportunity will then pop up into the corresponding stage and you can then fill in the contact details by clicking on it." +msgstr "" + +#: ../../crm/leads/generate/website.rst:3 +msgid "How to generate leads from my website?" +msgstr "" + +#: ../../crm/leads/generate/website.rst:5 +msgid "Your website should be your company's first lead generation tool. With your website being the central hub of your online marketing campaigns, you will naturally drive qualified traffic to feed your pipeline. When a prospect lands on your website, your objective is to capture his information in order to be able to stay in touch with him and to push him further down the sales funnel." +msgstr "" + +#: ../../crm/leads/generate/website.rst:12 +msgid "This is how a typical online lead generation process work :" +msgstr "" + +#: ../../crm/leads/generate/website.rst:14 +msgid "Your website visitor clicks on a call-to action (CTA) from one of your marketing materials (e.g. an email newsletter, a social media message or a blog post)" +msgstr "" + +#: ../../crm/leads/generate/website.rst:18 +msgid "The CTA leads your visitor to a landing page including a form used to collect his personal information (e.g. his name, his email address, his phone number)" +msgstr "" + +#: ../../crm/leads/generate/website.rst:22 +msgid "The visitor submits the form and automatically generates a lead into Odoo CRM" +msgstr "" + +#: ../../crm/leads/generate/website.rst:27 +msgid "Your calls-to-action, landing pages and forms are the key pieces of the lead generation process. With Odoo Website, you can easily create and optimize those critical elements without having to code or to use third-party applications. Learn more `here `__." +msgstr "" + +#: ../../crm/leads/generate/website.rst:32 +msgid "In Odoo, the Website and CRM modules are fully integrated, meaning that you can easily generate leads from various ways through your website. However, even if you are hosting your website on another CMS, it is still possible to fill Odoo CRM with leads generated from your website." +msgstr "" + +#: ../../crm/leads/generate/website.rst:40 +msgid "By default, the lead stage is not activated in Odoo CRM. Therefore, new leads automatically become opportunities. You can easily activate the option of adding the lead step. If you want to import your contacts as leads rather than opportunities, from the Sales module go to :menuselection:`Configuration --> Settings`, select the option **use leads if…** as shown below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/website.rst:50 +msgid "Note that even without activating this step, the information that follows is still applicable - the lead generated will land in the opportunities dashboard." +msgstr "" + +#: ../../crm/leads/generate/website.rst:55 +msgid "From an Odoo Website" +msgstr "" + +#: ../../crm/leads/generate/website.rst:57 +msgid "Let's assume that you want to get as much information as possible about your website visitors. But how could you make sure that every person who wants to know more about your company's products and services is actually leaving his information somewhere? Thanks to Odoo's integration between its CRM and Website modules, you can easily automate your lead acquisition process thanks to the **contact form** and the **form builder** modules" +msgstr "" + +#: ../../crm/leads/generate/website.rst:67 +msgid "another great way to generate leads from your Odoo Website is by collecting your visitors email addresses thanks to the Newsletter or Newsletter Popup CTAs. These snippets will create new contacts in your Email Marketing's mailing list. Learn more `here `__." +msgstr "" + +#: ../../crm/leads/generate/website.rst:75 +msgid "Start by installing the Website builder module. From the main dashboard, click on **Apps**, enter \"**Website**\" in the search bar and click on **Install**. You will be automatically redirected to the web interface." +msgstr "" + +#: ../../crm/leads/generate/website.rst:84 +msgid "A tutorial popup will appear on your screen if this is the first time you use Odoo Website. It will help you get started with the tool and you'll be able to use it in minutes. Therefore, we strongly recommend you to use it." +msgstr "" + +#: ../../crm/leads/generate/website.rst:89 +msgid "Create a lead by using the Contact Form module" +msgstr "" + +#: ../../crm/leads/generate/website.rst:91 +msgid "You can effortlessly generate leads via a contact form on your **Contact us** page. To do so, you first need to install the Contact Form module. It will add a contact form in your **Contact us** page and automatically generate a lead from forms submissions." +msgstr "" + +#: ../../crm/leads/generate/website.rst:96 +msgid "To install it, go back to the backend using the square icon on the upper-left corner of your screen. Then, click on **Apps**, enter \"**Contact Form**\" in the search bar (don't forget to remove the **Apps** tag otherwise you will not see the module appearing) and click on **Install**." +msgstr "" + +#: ../../crm/leads/generate/website.rst:104 +msgid "Once the module is installed, the below contact form will be integrated to your \"Contact us\" page. This form is linked to Odoo CRM, meaning that all data entered through the form will be captured by the CRM and will create a new lead." +msgstr "" + +#: ../../crm/leads/generate/website.rst:112 +msgid "Every lead created through the contact form is accessible in the Sales module, by clicking on :menuselection:`Sales --> Leads`. The name of the lead corresponds to the \"Subject\" field on the contact form and all the other information is stored in the corresponding fields within the CRM. As a salesperson, you can add additional information, convert the lead into an opportunity or even directly mark it as Won or Lost." +msgstr "" + +#: ../../crm/leads/generate/website.rst:123 +msgid "Create a lead using the Form builder module" +msgstr "" + +#: ../../crm/leads/generate/website.rst:125 +msgid "You can create fully-editable custom forms on any landing page on your website with the Form Builder snippet. As for the Contact Form module, the Form Builder will automatically generate a lead after the visitor has completed the form and clicked on the button **Send**." +msgstr "" + +#: ../../crm/leads/generate/website.rst:130 +msgid "From the backend, go to Settings and install the \"**Website Form Builder**\" module (don't forget to remove the **Apps** tag otherwise you will not see the modules appearing). Then, back on the website, go to your desired landing page and click on Edit to access the available snippets. The Form Builder snippet lays under the **Feature** section." +msgstr "" + +#: ../../crm/leads/generate/website.rst:140 +msgid "As soon as you have dropped the snippet where you want the form to appear on your page, a **Form Parameters** window will pop up. From the **Action** drop-down list, select **Create a lead** to automatically create a lead in Odoo CRM. On the **Thank You** field, select the URL of the page you want to redirect your visitor after the form being submitted (if you don't add any URL, the message \"The form has been sent successfully\" will confirm the submission)." +msgstr "" + +#: ../../crm/leads/generate/website.rst:151 +msgid "You can then start creating your custom form. To add new fields, click on **Select container block** and then on the blue **Customize** button. 3 options will appear:" +msgstr "" + +#: ../../crm/leads/generate/website.rst:158 +msgid "**Change Form Parameters**: allows you to go back to the Form Parameters and change the configuration" +msgstr "" + +#: ../../crm/leads/generate/website.rst:161 +msgid "**Add a model field**: allows you to add a field already existing in Odoo CRM from a drop-down list. For example, if you select the Field *Country*, the value entered by the lead will appear under the *Country* field in the CRM - even if you change the name of the field on the form." +msgstr "" + +#: ../../crm/leads/generate/website.rst:167 +msgid "**Add a custom field**: allows you to add extra fields that don't exist by default in Odoo CRM. The values entered will be added under \"Notes\" within the CRM. You can create any field type : checkbox, radio button, text, decimal number, etc." +msgstr "" + +#: ../../crm/leads/generate/website.rst:172 +msgid "Any submitted form will create a lead in the backend." +msgstr "" + +#: ../../crm/leads/generate/website.rst:175 +msgid "From another CMS" +msgstr "" + +#: ../../crm/leads/generate/website.rst:177 +msgid "If you use Odoo CRM but not Odoo Website, you can still automate your online lead generation process using email gateways by editing the \"Submit\" button of any form and replacing the hyperlink by a mailto corresponding to your email alias (learn how to create your sales alias :doc:`here `)." +msgstr "" + +#: ../../crm/leads/generate/website.rst:183 +msgid "For example if the alias of your company is **salesEMEA@mycompany.com**, add ``mailto:salesEMEA@mycompany.com`` into the regular hyperlink code (CTRL+K) to generate a lead into the related sales team in Odoo CRM." +msgstr "" + +#: ../../crm/leads/manage.rst:3 +msgid "Manage leads" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:3 +msgid "Automate lead assignation to specific sales teams or salespeople" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:5 +msgid "Depending on your business workflow and needs, you may need to dispatch your incoming leads to different sales team or even to specific salespeople. Here are a few example:" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:9 +msgid "Your company has several offices based on different geographical regions. You will want to assign leads based on the region;" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:12 +msgid "One of your sales teams is dedicated to treat opportunities from large companies while another one is specialized for SMEs. You will want to assign leads based on the company size;" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:16 +msgid "One of your sales representatives is the only one to speak foreign languages while the rest of the team speaks English only. Therefore you will want to assign to that person all the leads from non-native English-speaking countries." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:21 +msgid "As you can imagine, manually assigning new leads to specific individuals can be tedious and time consuming - especially if your company generates a high volume of leads every day. Fortunately, Odoo CRM allows you to automate the process of lead assignation based on specific criteria such as location, interests, company size, etc. With specific workflows and precise rules, you will be able to distribute all your opportunities automatically to the right sales teams and/or salesman." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:32 +msgid "If you have just started with Odoo CRM and haven't set up your sales team nor registered your salespeople, :doc:`read this documentation first <../../overview/started/setup>`." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:36 +msgid "Define rules for a sales team" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:38 +msgid "From the sales module, go to your dashboard and click on the **More** button of the desired sales team, then on **Settings**. If you don't have any sales team yet, :doc:`you need to create one first <../../salesteam/setup/create_team>`." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:46 +msgid "On your sales team menu, use in the **Domain** field a specific domain rule (for technical details on the domain refer on the `Building a Module tutorial `__ or `Syntax reference guide `__) which will allow only the leads matching the team domain." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:52 +msgid "For example, if you want your *Direct Sales* team to only receive leads coming from United States and Canada, your domain will be as following :" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:55 +msgid "``[[country_id, 'in', ['United States', 'Canada']]]``" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:62 +msgid "you can also base your automatic assignment on the score attributed to your leads. For example, we can imagine that you want all the leads with a score under 100 to be assigned to a sales team trained for lighter projects and the leads over 100 to a more experienced sales team. Read more on :doc:`how to score leads here `." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:68 +msgid "Define rules for a salesperson" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:70 +msgid "You can go one step further in your assignment rules and decide to assign leads within a sales team to a specific salesperson. For example, if I want Toni Buchanan from the *Direct Sales* team to receive only leads coming from Canada, I can create a rule that will automatically assign him leads from that country." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:76 +msgid "Still from the sales team menu (see here above), click on the salesperson of your choice under the assignment submenu. Then, enter your rule in the *Domain* field." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:85 +msgid "In Odoo, a lead is always assigned to a sales team before to be assigned to a salesperson. Therefore, you need to make sure that the assignment rule of your salesperson is a child of the assignment rule of the sales team." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:91 +#: ../../crm/salesteam/manage/create_salesperson.rst:67 +msgid ":doc:`../../overview/started/setup`" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:3 +msgid "How to do efficient Lead Scoring?" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:5 +msgid "Odoo's Lead Scoring module allows you to give a score to your leads based on specific criteria - the higher the value, the more likely the prospect is “ready for sales”. Therefore, the best leads are automatically assigned to your salespeople so their pipe are not polluted with poor-quality opportunities." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:12 +msgid "Lead scoring is a critical component of an effective lead management strategy. By helping your sales representative determine which leads to engage with in order of priority, you will increase their overall conversion rate and your sales team's efficiency." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:22 +msgid "Install the Lead Scoring module" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:24 +msgid "Start by installing the **Lead Scoring** module." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:26 +msgid "Once the module is installed, you should see a new menu :menuselection:`Sales --> Leads Management --> Scoring Rules`" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:33 +msgid "Create scoring rules" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:35 +msgid "Leads scoring allows you to assign a positive or negative score to your prospects based on any demographic or behavioral criteria that you have set (country or origin, pages visited, type of industry, role, etc.). To do so you'll first need to create rules that will assign a score to a given criteria." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:43 +msgid "In order to assign the right score to your various rules, you can use these two methods:" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:45 +msgid "Establish a list of assets that your ideal customer might possess to interest your company. For example, if you run a local business in California, a prospect coming from San Francisco should have a higher score than a prospect coming from New York." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:49 +msgid "Dig into your data to uncover characteristics shared by your closed opportunities and most important clients." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:52 +msgid "Please note that this is not an exact science, so you'll need time and feedback from your sales teams to adapt and fine tune your rules until getting the desired result." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:56 +msgid "In the **Scoring Rules** menu, click on **Create** to write your first rule." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:61 +msgid "First name your rule, then enter a value and a domain (refer on the `official python documentation `__ for more information). For example, if you want to assign 8 points to all the leads coming from **Belgium**, you'll need to give ``8`` as a **value** and ``[['country\\_id',=,'Belgium']]`` as a domain." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:68 +msgid "Here are some criteria you can use to build a scoring rule :" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:70 +msgid "country of origin : ``'country_id'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:72 +msgid "stage in the sales cycle : ``'stage_id'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:74 +msgid "email address (e.g. if you want to score the professional email addresses) : ``'email_from'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:76 +msgid "page visited : ``'score_pageview_ids.url'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:78 +msgid "name of a marketing campaign : ``'campaign_id'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:80 +msgid "After having activated your rules, Odoo will give a value to all your new incoming leads. This value can be found directly on your lead's form view." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:88 +msgid "Assign high scoring leads to your sales teams" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:90 +msgid "The next step is now to automatically convert your best leads into opportunities. In order to do so, you need to decide what is the minimum score a lead should have to be handed over to a given sales team. Go to your **sales dashboard** and click on the **More** button of your desired sales team, then on **Settings**. Enter your value under the **Minimum score** field." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:100 +msgid "From the example above, the **Direct Sales** team will only receive opportunities with a minimum score of ``50``. The prospects with a lower score can either stay in the lead stage or be assigned to another sales team which has set up a different minimum score." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:106 +msgid "Organize a meeting between your **Marketing** and **Sales** teams in order to align your objectives and agree on what minimum score makes a sales-ready lead." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:110 +msgid ":doc:`automatic_assignation`" +msgstr "" + +#: ../../crm/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../crm/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:3 +msgid "Odoo CRM Terminologies" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:10 +msgid "**CRM (Customer relationship management)**:" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:6 +msgid "System for managing a company's interactions with current and future customers. It often involves using technology to organize, automate, and synchronize sales, marketing, customer service, and technical support." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:14 +msgid "**Sales cycle** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:13 +msgid "Sequence of phases used by a company to convert a prospect into a customer." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:20 +msgid "**Pipeline :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:17 +msgid "Visual representation of your sales process, from the first contact to the final sale. It refers to the process by which you generate, qualify and close leads through your sales cycle." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:24 +msgid "**Sales stage** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:23 +msgid "In Odoo CRM, a stage defines where an opportunity is in your sales cycle and its probability to close a sale." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:29 +msgid "**Lead :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:27 +msgid "Someone who becomes aware of your company or someone who you decide to pursue for a sale, even if they don't know about your company yet." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:34 +msgid "**Opportunity :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:32 +msgid "A lead that has shown an interest in knowing more about your products/services and therefore has been handed over to a sales representative" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:39 +msgid "**Customer :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:37 +msgid "In Odoo CRM, a customer refers to any contact within your database, whether it is a lead, an opportunity, a client or a company." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:45 +msgid "**Key Performance Indicator (KPI)** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:42 +msgid "A KPI is a measurable value that demonstrates how effectively a company is achieving key business objectives. Organizations use KPIs to evaluate their success at reaching targets." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:51 +msgid "**Lead scoring** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:48 +msgid "System assigning a positive or negative score to prospects according to their web activity and personal informations in order to determine whether they are \"ready for sales\" or not." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:62 +msgid "**Kanban view :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:54 +msgid "In Odoo, the Kanban view is a workflow visualisation tool halfway between a `list view `__ and a non-editable `form view `__ and displaying records as \"cards\". Records may be grouped in columns for use in workflow visualisation or manipulation (e.g. tasks or work-progress management), or ungrouped (used simply to visualize records)." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:66 +msgid "**List view :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:65 +msgid "View allowing you to see your objects (contacts, companies, tasks, etc.) listed in a table." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:71 +msgid "**Lead generation:**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:69 +msgid "Process by which a company collects relevant datas about potential customers in order to enable a relationship and to push them further down the sales cycle." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:76 +msgid "**Campaign:**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:74 +msgid "Coordinated set of actions sent via various channels to a target audience and whose goal is to generate leads. In Odoo CRM, you can link a lead to the campaign which he comes from in order to measure its efficiency." +msgstr "" + +#: ../../crm/overview/process.rst:3 +msgid "Process Overview" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:3 +msgid "Generating leads with Odoo CRM" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:6 +msgid "What is lead generation?" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:8 +msgid "Lead generation is the process by which a company acquires leads and collects relevant datas about potential customers in order to enable a relationship and to turn them into customers." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:12 +msgid "For example, a website visitor who fills in your contact form to know more about your products and services becomes a lead for your company. Typically, a Customer Relationship Management tool such as Odoo CRM is used to centralize, track and manage leads." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:18 +msgid "Why is lead generation important for my business?" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:20 +msgid "Generating a constant flow of high-quality leads is one of the most important responsibility of a marketing team. Actually, a well-managed lead generation process is like the fuel that will allow your company to deliver great performances - leads bring meetings, meetings bring sales, sales bring revenue and more work." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:27 +msgid "How to generate leads with Odoo CRM?" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:29 +msgid "Leads can be captured through many sources - marketing campaigns, exhibitions and trade shows, external databases, etc. The most common challenge is to successfully gather all the data and to track any lead activity. Storing leads information in a central place such as Odoo CRM will release you of these worries and will help you to better automate your lead generation process, share information with your teams and analyze your sales processes easily." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:37 +msgid "Odoo CRM provides you with several methods to generate leads:" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:39 +msgid ":doc:`../../leads/generate/emails`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:41 +msgid "An inquiry email sent to one of your company's generic email addresses can automatically generate a lead or an opportunity." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:44 +msgid ":doc:`../../leads/generate/manual`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:46 +msgid "You may want to follow up with a prospective customer met briefly at an exhibition who gave you his business card. You can manually create a new lead and enter all the needed information." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:50 +msgid ":doc:`../../leads/generate/website`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:52 +msgid "A website visitor who fills in a form automatically generates a lead or an opportunity in Odoo CRM." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:55 +msgid ":doc:`../../leads/generate/import`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:57 +msgid "You can provide your salespeople lists of prospects - for example for a cold emailing or a cold calling campaign - by importing them from any CSV file." +msgstr "" + +#: ../../crm/overview/started.rst:3 +msgid "Getting started" +msgstr "" + +#: ../../crm/overview/started/setup.rst:3 +msgid "How to setup your teams, sales process and objectives ?" +msgstr "" + +#: ../../crm/overview/started/setup.rst:5 +msgid "This quick step-by-step guide will lead you through Odoo CRM and help you handle your sales funnel easily and constantly manage your sales funnel from lead to customer." +msgstr "" + +#: ../../crm/overview/started/setup.rst:12 +msgid "Create your database from `www.odoo.com/start `__, select the CRM icon as first app to install, fill in the form and click on *Create now*. You will automatically be directed to the module when the database is ready." +msgstr "" + +#: ../../crm/overview/started/setup.rst:22 +msgid "You will notice that the installation of the CRM module has created the submodules Chat, Calendar and Contacts. They are mandatory so that every feature of the app is running smoothly." +msgstr "" + +#: ../../crm/overview/started/setup.rst:27 +msgid "Introduction to the Sales Planner" +msgstr "" + +#: ../../crm/overview/started/setup.rst:29 +msgid "The Sales Planner is a useful step-by-step guide created to help you implement your sales funnel and define your sales objectives easier. We strongly recommend you to go through every step of the tool the first time you use Odoo CRM and to follow the requirements. Your input are strictly personal and intended as a personal guide and mentor into your work. As it does not interact with the backend, you are free to adapt any detail whenever you feel it is needed." +msgstr "" + +#: ../../crm/overview/started/setup.rst:37 +msgid "You can reach the Sales Planner from anywhere within the CRM module by clicking on the progress bar located on the upper-right side of your screen. It will show you how far you are in the use of the Sales Planner." +msgstr "" + +#: ../../crm/overview/started/setup.rst:46 +msgid "Set up your first sales team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:49 +msgid "Create a new team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:51 +msgid "A Direct Sales team is created by default on your instance. You can either use it or create a new one. Refer to the page :doc:`../../salesteam/setup/create_team` for more information." +msgstr "" + +#: ../../crm/overview/started/setup.rst:56 +msgid "Assign salespeople to your sales team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:58 +msgid "When your sales teams are created, the next step is to link your salespeople to their team so they will be able to work on the opportunities they are supposed to receive. For example, if within your company Tim is selling products and John is selling maintenance contracts, they will be assigned to different teams and will only receive opportunities that make sense to them." +msgstr "" + +#: ../../crm/overview/started/setup.rst:65 +msgid "In Odoo CRM, you can create a new user on the fly and assign it directly to a sales team. From the **Dashboard**, click on the button **More** of your selected sales team, then on **Settings**. Then, under the **Assignation** section, click on **Create** to add a new salesperson to the team." +msgstr "" + +#: ../../crm/overview/started/setup.rst:71 +msgid "From the **Create: salesman** pop up window (see screenshot below), you can assign someone on your team:" +msgstr "" + +#: ../../crm/overview/started/setup.rst:74 +msgid "Either your salesperson already exists in the system and you will just need to click on it from the drop-down list and it will be assigned to the team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:77 +msgid "Or you want to assign a new salesperson that doesn't exist into the system yet - you can do it by creating a new user on the fly from the sales team. Just enter the name of your new salesperson and click on Create (see below) to create a new user into the system and directly assign it to your team. The new user will receive an invite email to set his password and log into the system. Refer to :doc:`../../salesteam/manage/create_salesperson` for more information about that process" +msgstr "" + +#: ../../crm/overview/started/setup.rst:90 +msgid "Set up your pipeline" +msgstr "" + +#: ../../crm/overview/started/setup.rst:92 +msgid "Now that your sales team is created and your salespeople are linked to it, you will need to set up your pipeline -create the process by which your team will generate, qualify and close opportunities through your sales cycle. Refer to the document :doc:`../../salesteam/setup/organize_pipeline` to define the stages of your pipeline." +msgstr "" + +#: ../../crm/overview/started/setup.rst:99 +msgid "Set up incoming email to generate opportunities" +msgstr "" + +#: ../../crm/overview/started/setup.rst:101 +msgid "In Odoo CRM, one way to generate opportunities into your sales team is to create a generic email address as a trigger. For example, if the personal email address of your Direct team is `direct@mycompany.example.com `__\\, every email sent will automatically create a new opportunity into the sales team." +msgstr "" + +#: ../../crm/overview/started/setup.rst:108 +msgid "Refer to the page :doc:`../../leads/generate/emails` to set it up." +msgstr "" + +#: ../../crm/overview/started/setup.rst:111 +msgid "Automate lead assignation" +msgstr "" + +#: ../../crm/overview/started/setup.rst:113 +msgid "If your company generates a high volume of leads every day, it could be useful to automate the assignation so the system will distribute all your opportunities automatically to the right department." +msgstr "" + +#: ../../crm/overview/started/setup.rst:117 +msgid "Refer to the document :doc:`../../leads/manage/automatic_assignation` for more information." +msgstr "" + +#: ../../crm/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../crm/reporting/analysis.rst:3 +msgid "How to analyze the sales performance of your team and get customize reports" +msgstr "" + +#: ../../crm/reporting/analysis.rst:5 +msgid "As a manager, you need to constantly monitor your team's performance in order to help you take accurate and relevant decisions for the company. Therefore, the **Reporting** section of **Odoo Sales** represents a very important tool that helps you get a better understanding of where your company's strengths, weaknesses and opportunities are, showing you trends and forecasts for key metrics such as the number of opportunities and their expected revenue over time , the close rate by team or the length of sales cycle for a given product or service." +msgstr "" + +#: ../../crm/reporting/analysis.rst:14 +msgid "Beyond these obvious tracking sales funnel metrics, there are some other KPIs that can be very valuable to your company when it comes to judging sales funnel success." +msgstr "" + +#: ../../crm/reporting/analysis.rst:19 +msgid "Review pipelines" +msgstr "" + +#: ../../crm/reporting/analysis.rst:21 +msgid "You will have access to your sales funnel performance from the **Sales** module, by clicking on :menuselection:`Sales --> Reports --> Pipeline analysis`. By default, the report groups all your opportunities by stage (learn more on how to create and customize stage by reading :doc:`../salesteam/setup/organize_pipeline`) and expected revenues for the current month. This report is perfect for the **Sales Manager** to periodically review the sales pipeline with the relevant sales teams. Simply by accessing this basic report, you can get a quick overview of your actual sales performance." +msgstr "" + +#: ../../crm/reporting/analysis.rst:30 +msgid "You can add a lot of extra data to your report by clicking on the **measures** icon, such as :" +msgstr "" + +#: ../../crm/reporting/analysis.rst:33 +msgid "Expected revenue." +msgstr "" + +#: ../../crm/reporting/analysis.rst:35 +msgid "overpassed deadline." +msgstr "" + +#: ../../crm/reporting/analysis.rst:37 +msgid "Delay to assign (the average time between lead creation and lead assignment)." +msgstr "" + +#: ../../crm/reporting/analysis.rst:40 +msgid "Delay to close (average time between lead assignment and close)." +msgstr "" + +#: ../../crm/reporting/analysis.rst:42 +msgid "the number of interactions per opportunity." +msgstr "" + +#: ../../crm/reporting/analysis.rst:44 +msgid "etc." +msgstr "" + +#: ../../crm/reporting/analysis.rst:50 +msgid "By clicking on the **+** and **-** icons, you can drill up and down your report in order to change the way your information is displayed. For example, if I want to see the expected revenues of my **Direct Sales** team, I need to click on the **+** icon on the vertical axis then on **Sales Team**." +msgstr "" + +#: ../../crm/reporting/analysis.rst:55 +msgid "Depending on the data you want to highlight, you may need to display your reports in a more visual view. Odoo **CRM** allows you to transform your report in just a click thanks to 3 graph views : **Pie Chart**, **Bar Chart** and **Line Chart**. These views are accessible through the icons highlighted on the screenshot below." +msgstr "" + +#: ../../crm/reporting/analysis.rst:65 +msgid "Customize reports" +msgstr "" + +#: ../../crm/reporting/analysis.rst:67 +msgid "You can easily customize your analysis reports depending on the **KPIs** (see :doc:`../overview/main_concepts/terminologies`) you want to access. To do so, use the **Advanced search view** located in the right hand side of your screen, by clicking on the magnifying glass icon at the end of the search bar button. This function allows you to highlight only selected data on your report. The **filters** option is very useful in order to display some categories of opportunities, while the **Group by** option improves the readability of your reports according to your needs. Note that you can filter and group by any existing field from your CRM, making your customization very flexible and powerful." +msgstr "" + +#: ../../crm/reporting/analysis.rst:82 +msgid "You can save and reuse any customized filter by clicking on **Favorites** from the **Advanced search view** and then on **Save current search**. The saved filter will then be accessible from the **Favorites** menu." +msgstr "" + +#: ../../crm/reporting/analysis.rst:87 +msgid "Here are a few examples of customized reports that you can use to monitor your sales' performances :" +msgstr "" + +#: ../../crm/reporting/analysis.rst:91 +msgid "Evaluate the current pipeline of each of your salespeople" +msgstr "" + +#: ../../crm/reporting/analysis.rst:93 +msgid "From your pipeline analysis report, make sure first that the **Expected revenue** option is selected under the **Measures** drop-down list. Then, use the **+** and **-** icons and add **Salesperson** and **Stage** to your vertical axis, and filter your desired salesperson. Then click on the **graph view** icon to display a visual representation of your salespeople by stage. This custom report allows you to easily overview the sales activities of your salespeople." +msgstr "" + +#: ../../crm/reporting/analysis.rst:105 +msgid "Forecast monthly revenue by sales team" +msgstr "" + +#: ../../crm/reporting/analysis.rst:107 +msgid "In order to predict monthly revenue and to estimate the short-term performances of your teams, you need to play with two important metrics : the **expected revenue** and the **expected closing**." +msgstr "" + +#: ../../crm/reporting/analysis.rst:111 +msgid "From your pipeline analysis report, make sure first that the **Expected revenue** option is selected under the **Measures** drop-down list. Then click on the **+** icon from the vertical axis and select **Sales team**. Then, on the horizontal axis, click on the **+** icon and select **Expected closing.**" +msgstr "" + +#: ../../crm/reporting/analysis.rst:121 +msgid "In order to keep your forecasts accurate and relevant, make sure your salespeople correctly set up the expected closing and the expected revenue for each one of their opportunities" +msgstr "" + +#: ../../crm/reporting/analysis.rst:126 +msgid ":doc:`../salesteam/setup/organize_pipeline`" +msgstr "" + +#: ../../crm/reporting/review.rst:3 +msgid "How to review my personal sales activities (new sales dashboard)" +msgstr "" + +#: ../../crm/salesteam.rst:3 +#: ../../crm/salesteam/setup.rst:3 +msgid "Sales Team" +msgstr "" + +#: ../../crm/salesteam/manage.rst:3 +msgid "Manage salespeople" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:3 +msgid "How to create a new salesperson?" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:6 +msgid "Create a new user" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:8 +msgid "From the Settings module, go to the submenu :menuselection:`Users --> Users` and click on **Create**. Add first the name of your new salesperson and his professional email address - the one he will use to log in to his Odoo instance - and a picture." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:16 +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. For the Sales application, you can choose between three levels:" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:20 +msgid "**See own leads**: the user will be able to access his own data only" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:22 +msgid "**See all leads**: the user will be able to access all records of every salesman in the sales module" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:25 +msgid "**Manager**: the user will be able to access the sales configuration as well as the statistics reports" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:28 +msgid "When you're done editing the page and have clicked on **Save**, an invitation email will automatically be sent to the user, from which he will be able to log into his personal account." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:36 +msgid "Register your user into his sales team" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:38 +msgid "Your user is now registered in Odoo and can log in to his own session. You can also add him to the sales team of your choice. From the sales module, go to your dashboard and click on the **More** button of the desired sales team, then on **Settings**." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:49 +msgid "If you need to create a new sales team first, refer to the page :doc:`../setup/create_team`" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:51 +msgid "Then, under \"Team Members\", click on **Add** and select the name of your salesman from the list. The salesperson is now successfully added to your sales team." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:60 +msgid "You can also add a new salesperson on the fly from your sales team even before he is registered as an Odoo user. From the above screenshot, click on \"Create\" to add your salesperson and enter his name and email address. After saving, the salesperson will receive an invite containing a link to set his password. You will then be able to define his accesses rights under the :menuselection:`Settings --> Users` menu." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:69 +msgid ":doc:`../setup/create_team`" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:3 +msgid "How to create a new team?" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:5 +msgid "In the Sales module, your sales teams are accessible from the **Dashboard** menu. If you start from a new instance, you will find a sales team installed by default : Direct sales. You can either start using that default sales team and edit it (refer to the section *Create and Organize your stages* from the page :doc:`organize_pipeline`) or create a new one from scratch." +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:12 +msgid "To create a new team, go to :menuselection:`Configuration --> Sales Teams` and click on **Create**." +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:18 +msgid "Fill in the fields :" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:20 +msgid "Enter the name of your team" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:22 +msgid "Select your team leader" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:24 +msgid "Select your team members" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:26 +msgid "Don't forget to tick the \"Opportunities\" box if you want to manage opportunities from it and to click on SAVE when you're done. Your can now access your new team from your Dashboard." +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:35 +msgid "If you started to work on an empty database and didn't create new users, refer to the page :doc:`../manage/create_salesperson`." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:3 +msgid "Set up and organize your sales pipeline" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:5 +msgid "A well structured sales pipeline is crucial in order to keep control of your sales process and to have a 360-degrees view of your leads, opportunities and customers." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:9 +msgid "The sales pipeline is a visual representation of your sales process, from the first contact to the final sale. It refers to the process by which you generate, qualify and close leads through your sales cycle. In Odoo CRM, leads are brought in at the left end of the sales pipeline in the Kanban view and then moved along to the right from one stage to another." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:16 +msgid "Each stage refers to a specific step in the sale cycle and specifically the sale-readiness of your potential customer. The number of stages in the sales funnel varies from one company to another. An example of a sales funnel will contain the following stages: *Territory, Qualified, Qualified Sponsor, Proposition, Negotiation, Won, Lost*." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:26 +msgid "Of course, each organization defines the sales funnel depending on their processes and workflow, so more or fewer stages may exist." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:30 +msgid "Create and organize your stages" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:33 +msgid "Add/ rearrange stages" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:35 +msgid "From the sales module, go to your dashboard and click on the **PIPELINE** button of the desired sales team. If you don't have any sales team yet, you need to create one first." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:46 +msgid "From the Kanban view of your pipeline, you can add stages by clicking on **Add new column.** When a column is created, Odoo will then automatically propose you to add another column in order to complete your process. 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." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:58 +msgid "You can add as many stages as you wish, even if we advise you not having more than 6 in order to keep a clear pipeline" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:64 +msgid "Some companies use a pre qualification step to manage their leads before to convert them into opportunities. To activate the lead stage, go to :menuselection:`Configuration --> Settings` and select the radio button as shown below. It will create a new submenu **Leads** under **Sales** that gives you access to a listview of all your leads." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:74 +msgid "Set up stage probabilities" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:77 +msgid "What is a stage probability?" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:79 +msgid "To better understand what are the chances of closing a deal for a given opportunity in your pipe, you have to set up a probability percentage for each of your stages. That percentage refers to the success rate of closing the deal." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:84 +msgid "Setting up stage probabilities is essential if you want to estimate the expected revenues of your sales cycle" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:88 +msgid "For example, if your sales cycle contains the stages *Territory, Qualified, Qualified Sponsor, Proposition, Negotiation, Won and Lost,* then your workflow could look like this :" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:92 +msgid "**Territory** : opportunity just received from Leads Management or created from a cold call campaign. Customer's Interest is not yet confirmed." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:96 +msgid "*Success rate : 5%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:98 +msgid "**Qualified** : prospect's business and workflow are understood, pains are identified and confirmed, budget and timing are known" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:101 +msgid "*Success rate : 15%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:103 +msgid "**Qualified sponsor**: direct contact with decision maker has been done" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:106 +msgid "*Success rate : 25%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:108 +msgid "**Proposition** : the prospect received a quotation" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:110 +msgid "*Success rate : 50%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:112 +msgid "**Negotiation**: the prospect negotiates his quotation" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:114 +msgid "*Success rate : 75%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:116 +msgid "**Won** : the prospect confirmed his quotation and received a sales order. He his now a customer" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:119 +msgid "*Success rate : 100%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:121 +msgid "**Lost** : the prospect is no longer interested" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:123 +msgid "*Success rate : 0%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:127 +msgid "Within your pipeline, each stage should correspond to a defined goal with a corresponding probability. Every time you move your opportunity to the next stage, your probability of closing the sale will automatically adapt." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:131 +msgid "You should consider using probability value as **100** when the deal is closed-won and **0** for deal closed-lost." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:135 +msgid "How to set up stage probabilities?" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:137 +msgid "To edit a stage, click on the **Settings** icon at the right of the desired stage then on EDIT" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:143 +msgid "Select the Change probability automatically checkbox to let Odoo adapt the probability of the opportunity to the probability defined in the stage. For example, if you set a probability of 0% (Lost) or 100% (Won), Odoo will assign the corresponding stage when the opportunity is marked as Lost or Won." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:151 +msgid "Under the requirements field you can enter the internal requirements for this stage. It will appear as a tooltip when you place your mouse over the name of a stage." +msgstr "" + diff --git a/locale/sources/expenses.pot b/locale/sources/expenses.pot new file mode 100644 index 000000000..d3313d74f --- /dev/null +++ b/locale/sources/expenses.pot @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2015-11-03 11:43+0100\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" + +#: ../../expenses.rst:5 +msgid "Expenses" +msgstr "" + diff --git a/locale/sources/index.pot b/locale/sources/index.pot new file mode 100644 index 000000000..eb674a11d --- /dev/null +++ b/locale/sources/index.pot @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2015-11-03 11:43+0100\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" + +#: ../../index.rst:3 +msgid "Odoo User Documentation" +msgstr "" + diff --git a/locale/sources/inventory.pot b/locale/sources/inventory.pot new file mode 100644 index 000000000..670bc7ffe --- /dev/null +++ b/locale/sources/inventory.pot @@ -0,0 +1,2873 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2015-11-03 11:43+0100\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" + +#: ../../inventory.rst:5 +#: ../../inventory/overview/double-entry.rst:64 +msgid "Inventory" +msgstr "" + +#: ../../inventory/delivery.rst:3 +msgid "Delivery Orders" +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:3 +msgid "How to send products to customers directly from suppliers (drop-shipping)?" +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:6 +msgid "What is drop-shipping?" +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:8 +msgid "Drop-Shipping is a system that allows orders taken from your store to be shipped straight from your supplier to your customer. On a usual delivery system, products are sent from your supplier to your warehouse to be put in stock, and then shipped to your customers after ordering. With drop-shipping, no item is stocked. When a customer places an order in your shop, the item is delivered straight from the supplier to the customer. Therefore, the product doesn't need to get through your warehouse." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:18 +msgid "Points to be considered while implementing drop-shipping" +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:20 +msgid "Use drop-shipping only for the products you can't or don't want to keep in stock. One reason is that you'll always make smaller margins on items that are drop-shipped, so you should keep it only for items that take up a lot of space in your warehouse." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:25 +msgid "Drop-shipping is best for niche products. Chances are that products that are in high demand are being offered by large suppliers at a fraction of the price you'll be able to charge, so using a more costly shipping method won't be financially rewarding. But if your product is unique, then it makes sense!" +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:31 +msgid "To protect your customers from bad experiences, test drop-shipping companies for yourself beforehand and list the best ones." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:34 +msgid "Make sure time is not against you. Drop-shipping should take a reasonable amount of time and surely not more than it would have taken you to handle it all by yourself. It's also nice to be able to provide your customers with a tracking number." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:39 +msgid "Items have to be available from your supplier. It's good to know if the product you're selling is available upstream. If you don't have that information, inform your customers that you don't hold the item in stock and that it's subject to availability from a third party." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:46 +msgid "For more information and insights on Drop-shipping, read our blog on `What is drop-shipping and how to use it `__." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:50 +msgid "Configuring drop-shipping" +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:52 +msgid "Open the menu :menuselection:`Inventory --> Configuration --> Settings`. Go to **Location & Warehouse**, locate the **Dropshipping** option and tick the box **Allow suppliers to deliver directly to your customers**. Then, click on **Apply**." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:60 +msgid "Then go to the menu :menuselection:`Sales --> Configuration --> Settings`. Locate **Order Routing** and tick the box **Choose specific routes on sales order lines (advanced)**. Click on **Apply**." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:67 +msgid "Now, open the menu :menuselection:`Sales --> Sales --> Products`. Add a supplier to the products you want to dropship." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:74 +msgid "How to send products from the customers directly to the suppliers" +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:76 +msgid "Create a **Sales Order** and specify on a sales order line for your products that the route is **Dropshipping**." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:82 +msgid "Open the menu :menuselection:`Purchases --> Purchases --> Requests for Quotation`. The draft purchase order is automatically created from the procurement with the drop-shipping route. Once the order is confirmed, you will see that one shipment has been created." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:90 +msgid "To confirm the sending from the vendor to the customer, go back to **Inventory** app. On the dashboard, click on **# TO RECEIVE** on the dropship card." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:97 +msgid "It will open the list of drop-shipping transfers. Validate the transfer once it has been done. The items will be directly delivered from the partner to the customer without transiting to your warehouse." +msgstr "" + +#: ../../inventory/delivery/dropshipping.rst:103 +msgid ":doc:`inventory_flow`" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:3 +msgid "How to choose the right inventory flow to handle delivery orders?" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:5 +msgid "Depending on factors such as the type of items you sell, the size of your warehouse, the number of orders you register everyday... the way you handle deliveries to your customers can vary a lot." +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:9 +msgid "Odoo allows you to handle shipping from your warehouse in 3 different ways:" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:12 +msgid "**One step (shipping)**: Ship directly from stock" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:14 +msgid "**Two steps (pick + ship)**: Bring goods to output location before shipping" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:17 +msgid "**Three steps (pick + pack + ship)**: Make packages into a dedicated location, then bring them to the output location for shipping" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:20 +msgid "For companies having a rather small warehouse and that do not require high stock of items or don't sell perishable items, a one step shipping is the simplest solution, as it does not require a lot of configuration and allows to handle orders very quickly." +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:25 +msgid "Using inventory methods such as FIFO, LIFO and FEFO require to have at least two steps to handle a shipment. The picking method will be determined by the removal strategy, and the items removed will then be shipped to the customer. This method is also interesting if you hold larger stocks and especially when the items you stock are big in size." +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:31 +msgid "The three steps system becomes useful in more specific situations, the main one being for handling very large stocks. The items are transferred to a packing area, where they will be assembled by area of destination, and then set to outbound trucks for final delivery to the customers." +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:37 +#: ../../inventory/delivery/one_step.rst:13 +#: ../../inventory/delivery/three_steps.rst:34 +#: ../../inventory/delivery/two_steps.rst:29 +#: ../../inventory/incoming/handle_receipts.rst:50 +#: ../../inventory/incoming/three_steps.rst:28 +#: ../../inventory/incoming/two_steps.rst:21 +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:30 +#: ../../inventory/misc/owned_stock.rst:22 +#: ../../inventory/misc/scrap.rst:25 +#: ../../inventory/overview/double-entry.rst:159 +#: ../../inventory/overview/double-entry.rst:164 +#: ../../inventory/settings/products/variants.rst:114 +#: ../../inventory/settings/warehouses/location_creation.rst:6 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:6 +#: ../../inventory/shipping/setup/delivery_method.rst:17 +msgid "Configuration" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:40 +#: ../../inventory/incoming/handle_receipts.rst:53 +msgid "One step flow" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:42 +msgid "Please read documentation on :doc:`one_step`" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:45 +#: ../../inventory/incoming/handle_receipts.rst:58 +msgid "Two steps flow" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:47 +#: ../../inventory/incoming/handle_receipts.rst:60 +msgid "Please read documentation on :doc:`two_steps`" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:50 +#: ../../inventory/incoming/handle_receipts.rst:63 +msgid "Three steps flow" +msgstr "" + +#: ../../inventory/delivery/inventory_flow.rst:52 +#: ../../inventory/incoming/handle_receipts.rst:65 +msgid "Please read documentation on :doc:`three_steps`" +msgstr "" + +#: ../../inventory/delivery/one_step.rst:3 +msgid "How to process delivery orders in one step (shipping)?" +msgstr "" + +#: ../../inventory/delivery/one_step.rst:6 +#: ../../inventory/delivery/three_steps.rst:6 +#: ../../inventory/delivery/two_steps.rst:6 +#: ../../inventory/incoming/handle_receipts.rst:6 +#: ../../inventory/incoming/three_steps.rst:6 +#: ../../inventory/incoming/two_steps.rst:6 +#: ../../inventory/misc/scrap.rst:6 +#: ../../inventory/overview.rst:3 +#: ../../inventory/shipping/setup/delivery_method.rst:6 +msgid "Overview" +msgstr "" + +#: ../../inventory/delivery/one_step.rst:8 +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/delivery/one_step.rst:15 +msgid "There is no configuration needed. The default outgoing shipments are configured to be directly delivered from the stock." +msgstr "" + +#: ../../inventory/delivery/one_step.rst:18 +msgid "However, if **advance routes** is activated and you set another shipping configuration on your warehouse, you can set it back to the one-step delivery configuration. Go to :menuselection:`Configuration --> Warehouses` and edit the concerned warehouse." +msgstr "" + +#: ../../inventory/delivery/one_step.rst:23 +msgid "Set the outgoing shippings the option to **Ship directly from stock (Ship Only)**" +msgstr "" + +#: ../../inventory/delivery/one_step.rst:30 +#: ../../inventory/delivery/two_steps.rst:68 +msgid "Create a Sales Order" +msgstr "" + +#: ../../inventory/delivery/one_step.rst:32 +msgid "Create a sales order (From quotation to sales order) with some products to deliver." +msgstr "" + +#: ../../inventory/delivery/one_step.rst:35 +msgid "Notice that we now see ``1`` delivery associated with this sales order in the **stat button** above the sales order." +msgstr "" + +#: ../../inventory/delivery/one_step.rst:41 +msgid "If you click on the **1 Delivery** stat button, you should now see your picking." +msgstr "" + +#: ../../inventory/delivery/one_step.rst:45 +#: ../../inventory/delivery/three_steps.rst:99 +#: ../../inventory/delivery/two_steps.rst:88 +msgid "Process a Delivery" +msgstr "" + +#: ../../inventory/delivery/one_step.rst:47 +#: ../../inventory/delivery/three_steps.rst:143 +#: ../../inventory/delivery/two_steps.rst:113 +msgid "Go to **Inventory** and click on the **# TO DO** link under the **Delivery Orders** kanban card." +msgstr "" + +#: ../../inventory/delivery/one_step.rst:53 +#: ../../inventory/delivery/three_steps.rst:110 +#: ../../inventory/delivery/three_steps.rst:130 +#: ../../inventory/delivery/three_steps.rst:149 +#: ../../inventory/delivery/two_steps.rst:99 +#: ../../inventory/delivery/two_steps.rst:119 +#: ../../inventory/incoming/three_steps.rst:99 +msgid "Click on the picking that you want to process." +msgstr "" + +#: ../../inventory/delivery/one_step.rst:55 +msgid "Click on **Validate** to complete the move from **WH/Output** to the **customer**." +msgstr "" + +#: ../../inventory/delivery/one_step.rst:58 +msgid "This has completed the **Shipping Step** and the WH/OUT should now show **Done** in the status column at the top of the page, which means the product has been shipped to the customer." +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:3 +msgid "How is the scheduled delivery date computed?" +msgstr "" + +#: ../../inventory/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/delivery/scheduled_dates.rst:13 +msgid "Configuring lead times" +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:15 +msgid "Configuring **lead times** is a first essentiel 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/delivery/scheduled_dates.rst:19 +msgid "Configuration of the different lead times are made as follows:" +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:22 +msgid "At a product level" +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:24 +msgid "**Supplier lead time**:" +msgstr "" + +#: ../../inventory/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/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/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/delivery/scheduled_dates.rst:46 +msgid "**Customer lead time**:" +msgstr "" + +#: ../../inventory/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/delivery/scheduled_dates.rst:56 +msgid "**Manufacturing lead time**:" +msgstr "" + +#: ../../inventory/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/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/delivery/scheduled_dates.rst:67 +msgid "At the company level" +msgstr "" + +#: ../../inventory/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/delivery/scheduled_dates.rst:74 +msgid "**Sales Safety days**:" +msgstr "" + +#: ../../inventory/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/delivery/scheduled_dates.rst:84 +msgid "To set ut your security dates, go to :menuselection:`Settings --> General settings` and click on **Configure your company data**." +msgstr "" + +#: ../../inventory/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/delivery/scheduled_dates.rst:93 +msgid "**Purchase Safety days**:" +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:95 +msgid "Purchase days follow to the same logic than sales security days." +msgstr "" + +#: ../../inventory/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/delivery/scheduled_dates.rst:106 +msgid "Note that you can also configure a default Manufacturing lead time from here." +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:110 +msgid "At route level" +msgstr "" + +#: ../../inventory/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/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/delivery/scheduled_dates.rst:118 +msgid "Go to the push rules section on a route form to set a delay." +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:124 +msgid "At sale order level:" +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:126 +msgid "**Requested date**:" +msgstr "" + +#: ../../inventory/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/delivery/scheduled_dates.rst:137 +msgid "Example" +msgstr "" + +#: ../../inventory/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/delivery/scheduled_dates.rst:144 +msgid "January 19: actual scheduled delivery (1 day of Sales Safety days)" +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:146 +msgid "January 18: receive the product from your supplier (1 day of Purchase days)" +msgstr "" + +#: ../../inventory/delivery/scheduled_dates.rst:149 +msgid "January 10: deadline to order at your supplier (9 days of supplier delivery lead time)" +msgstr "" + +#: ../../inventory/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/delivery/three_steps.rst:3 +msgid "How to process delivery orders in three steps (pick + pack + ship)?" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:8 +msgid "When an order goes to the shipping department for final delivery, Odoo is set up by default on a **one-step** operation: once all goods are available, they can be shipped in bulk in a single delivery order. However, that process may not reflect the reality and your company may require more steps before shipping." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:14 +msgid "With the **three steps** process (**Pick + Pack + Ship**), the items are transferred to a packing area, where they will be assembled by area of destination, and then set to outbound trucks for final delivery to the customers." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:19 +msgid "A few configuration steps are necessary in order to accomplish **Pick + Pack + Ship** in Odoo. These steps create some additional locations, which by default are called **Output** and **Packing Zone**. So, if your warehouse's code is ``WH``, this configuration will create a location called ``WH/Output`` and another one called ``WH/Packing Zone``." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:25 +msgid "Goods will move from **WH/Stock** to **WH/Packing Zone** in the first step. Then move from **WH/Packing Zone** to **WH/Output**. Then finally it will be delivered from **WH/Output** to its **final destination**." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:30 +#: ../../inventory/delivery/two_steps.rst:25 +msgid "Check out :doc:`inventory_flow` to determine if this inventory flow is the correct method for your needs." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:37 +msgid "Install the Inventory module" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:39 +msgid "From the **App** menu, search and install the **Inventory** module." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:44 +msgid "You will also need to install the **Sales** module to be able to issue sales orders." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:48 +msgid "Allow managing routes" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:50 +msgid "Odoo configures movement of delivery orders via **routes**. Routes provide a mechanism to link different actions together. In this case, we will link the picking step to the shipping step." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:54 +msgid "To allow management of routes, go to :menuselection:`Configuration --> Settings`" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:56 +msgid "Under :menuselection:`Location & Warehouse --> Routes`, activate the radio button **Advanced routing of products using rules**. Make sure that the option **Manage several locations per warehouse** is activated as well." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:64 +msgid "Configure the warehouse for Pick + Pack + Ship" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:66 +msgid "Go to :menuselection:`Configuration --> Warehouses` and edit the warehouse that will be used." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:69 +msgid "For outgoing shippings, set the option to **Make packages into a dedicated location, bring them to the output location for shipping (Pick + Pack + Ship).**" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:77 +msgid "Create a Sale Order" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:79 +msgid "From the **Sale** module, create a sales order with some products to deliver." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:81 +msgid "Notice that we now see ``3`` transfers associated with this sales order in the **stat button** above the sales order." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:87 +msgid "If you click the button, you should now see three different pickings:" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:89 +msgid "The first with a reference **PICK** to designate the picking process," +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:91 +msgid "The second one with the reference **PACK** that is the packing process," +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:93 +msgid "The last with a reference **OUT** to designate the shipping process." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:102 +#: ../../inventory/delivery/two_steps.rst:91 +msgid "How to Process the Picking Step?" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:104 +msgid "Ensure that you have enough product in stock and Go to **Inventory** and click on the **Waiting** link under the **Pick** kanban card." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:112 +#: ../../inventory/delivery/two_steps.rst:101 +msgid "Click on **Reserve** to reserve the products if they are available." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:114 +msgid "Click on **Validate** to complete the move from **WH/Stock** to **WH/Packing Zone**." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:116 +msgid "This has completed the picking Step and the **WH/PICK** should now show **Done** in the status column at the top of the page. The product has been moved from **WH/Stock** to **WH/Packing Zone** location, which makes the product available for the next step (Packing)." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:122 +msgid "How to Process the Packing Step?" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:124 +msgid "Go to **Inventory** and click on the **# TRANSFERS** link under the **Pack** kanban card." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:132 +msgid "Click on **Validate** to complete the move from **WH/Packing Zone** to **WH/Output**." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:135 +msgid "This has completed the packing step and the **WH/PACK** should now show **Done** in the status column at the top of the page. The product has been moved from **WH/Packing Zone** to **WH/Output location**, which makes the product available for the next step (Shipping)." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:141 +#: ../../inventory/delivery/two_steps.rst:111 +msgid "How to Process the Shipping Step?" +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:151 +msgid "Click on **Validate** to complete the move from **WH/Output** to the **customer** (Click **Apply** to assign the quantities based on the quantities listed in the **To Do** column)." +msgstr "" + +#: ../../inventory/delivery/three_steps.rst:155 +msgid "This has completed the shipping step and the **WH/OUT** should now show **Done** in the status column at the top of the page. The product has been shipped to the customer." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:3 +msgid "How to process delivery orders in two steps (pick + ship)?" +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:8 +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, your company's business process may have one or more steps that happen before shipping. In the **two steps** process, the items in a delivery order are **picked** in the warehouse and brought to an **output location** for **shipping**. The goods are then shipped." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:16 +msgid "In order to accomplish a **Pick + Ship** delivery in Odoo, there are a few necessary configuration steps. These steps create an additional location, which by default is called **Output**. So, if your warehouse's code is ``WH``, this configuration will create a location called ``WH/Output``. Goods will move from ``WH/Stock`` to ``WH/Output`` in the first step (picking). Then, they move from ``WH/Output`` to ``WH/Customers`` (in the case of sales orders) in the second step (shipping)." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:32 +msgid "Allow management of routes" +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:34 +msgid "Odoo configures movement of delivery orders via the **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/delivery/two_steps.rst:38 +msgid "To allow management of routes, go to :menuselection:`Configuration --> Settings`." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:40 +msgid "Ensure that the radio button **Advanced routing of products using rules** is checked." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:46 +msgid "Click on **Apply** at the top of the page to save changes (if you needed to check the radio button above)." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:50 +msgid "If you checked option **Advanced routing of products using rules** you may need to activate **Manage several locations per warehouse** if it wasn't activated beforehand." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:55 +msgid "Configure warehouse for Pick + Ship" +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:57 +msgid "To configure a **Pick + Ship** move, go to :menuselection:`Configuration --> Warehouses` and edit the warehouse that will be used." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:61 +msgid "For outgoing shippings, set the option to **Bring goods to output location before shipping (Pick + Ship)**" +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:70 +msgid "Install the **Sale** if it is not the case, and create a sales order with some products to deliver." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:73 +msgid "Notice that we now see ``2`` transfers associated with this sales order in the **Delivery** stat button above the sales order." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:79 +msgid "If you click on the **2 Transfers** stat button, you should now see two different pickings, one with a reference **PICK** to designate the picking process and another with a reference **OUT** to designate the shipping process." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:93 +msgid "Ensure that you have enough product in stock, and go to **Inventory** and click on the **Waiting** link under the **Pick** kanban card." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:103 +msgid "Click on **Validate** to complete the move from **WH/Stock** to **WH/Output**." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:105 +msgid "This has completed the picking step and the **WH/PICK** move should now show **Done** in the status column at the top of the page. The product has been moved from **WH/Stock** to **WH/Output** location, which makes the product **available for the next step** (Shipping)." +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:121 +msgid "Click on **Validate** to complete the move from **WH/Output** to the customer (Click **Apply** to assign the quantities based on the quantities listed in the **To Do** column)" +msgstr "" + +#: ../../inventory/delivery/two_steps.rst:125 +msgid "This has completed the shipping step and the **WH/OUT** move should now show **Done** in the status column at the top of the page. The product has been shipped to the customer." +msgstr "" + +#: ../../inventory/incoming.rst:3 +msgid "Incoming Shipments" +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:3 +msgid "How to choose the right flow to handle receipts?" +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:8 +msgid "Depending on factors such as the type of items you receive, the size of your warehouse, the number of receipt you register everyday... the way you handle receipts to your customers can vary a lot." +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:12 +msgid "Odoo allows you to handle receipts from your warehouse in 3 different ways:" +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:15 +msgid "**One step**: Receive goods directly in stock." +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:17 +msgid "**Two steps**: Unload in input location then go to stock." +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:19 +msgid "**Three steps**: Unload in input location, go through a quality control before being admitted in stock." +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:22 +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. In standard, the reception is a one step process, but changing the configuration can allow to have 2 or even 3 steps." +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:27 +msgid "The principles are the following:" +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:29 +msgid "**One step**: You receive the goods directly in your stock." +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:31 +msgid "**Two steps**: You receive the goods in an input area then transfer them from input area to your stock. As long as the goods are not transferred in your stock, they will not be available for further processing." +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:36 +msgid "**Three steps**: 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. Adding a quality control step in the goods receipt process can become essential." +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:42 +msgid "You receive the goods in an input area, then transfer them into quality area for quality control. When your quality check process finishes then 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/incoming/handle_receipts.rst:55 +msgid "This is the default configuration in Odoo." +msgstr "" + +#: ../../inventory/incoming/handle_receipts.rst:68 +#: ../../inventory/incoming/three_steps.rst:126 +#: ../../inventory/incoming/two_steps.rst:97 +msgid ":doc:`../delivery/inventory_flow`" +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:3 +msgid "How to add a quality control step in goods receipt? (3 steps)" +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:8 +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." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:13 +#: ../../inventory/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 level of the warehouse. By default, the reception is a one step process, but changing the configuration can allow to have 2 or even 3 steps." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:18 +msgid "The 3 steps flow is as follows: You receive the goods in an input area, then transfer them into 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/incoming/three_steps.rst:25 +#: ../../inventory/incoming/two_steps.rst:18 +msgid "This is the case that will be explained in this document." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:31 +#: ../../inventory/incoming/two_steps.rst:24 +msgid "Use advanced routes" +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:33 +msgid "To allow management of routes, go to the menu :menuselection:`Inventory --> Configuration --> Settings`." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:39 +#: ../../inventory/incoming/two_steps.rst:32 +msgid "Ensure that the routes option **Advance routing of product using rules** is checked, then click on **Apply** to save changes." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:42 +msgid "Make sure that **Manage several locations per warehouse** is also ticked." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:46 +msgid "How to add a quality control step in goods receipt?" +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:48 +msgid "Go to the menu :menuselection:`Inventory --> Configuration --> Warehouse` and choose the warehouse where you want to change reception methods." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:51 +msgid "By default, warehouses are configured with one step reception (**Receive goods directly into stock**)." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:54 +msgid "To add quality control before transfer goods into stock location, tick **Unload in input location, go through a quality control before being admitted in stock (3 steps)**." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:62 +msgid "How to control a receipt ?" +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:65 +msgid "How to process the receipt step ?" +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:67 +msgid "In the **Purchase** app, create a **Request for Quotation**. Click on the **Confirm order** button. You can see that there is one **Shipment** related to purchase order in the stat button above the purchase order form view. This is the receipt step." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:75 +msgid "Go to **Inventory** and click on the link **# TO RECEIVE** in the **Receipts** card." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:80 +msgid "Click on the receipt that you want to process. Click on **Validate** to complete the move from the **Vendor** location to **WH/Input**." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:83 +msgid "This has completed the receipt step and the status column at the top of the page for **WH/IN** should now show **Done**. The product has been moved from the **Vendor** to the **WH/Input** location, which makes the product available for the next step (Move to the quality control zone)" +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:89 +msgid "How to move your product from the receipt zone to the quality control zone ?" +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:91 +msgid "Go to the **Inventory** dashboard. You will see that there is one transfer ready (the move to the quality control zone) and one waiting (the move to the stock after the control). Click on the link **# TRANSFERS** in the **Internal Transfers** to process the quality control." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:101 +msgid "Click on **Validate** to complete the move from **WH/Input** to **WH/Quality Control**." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:104 +msgid "This has completed the internal transfer step and the status column at the top of the page for **WH/INT** should now show **Done**. The receipt is now ready to be controlled." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:109 +msgid "How to to process the quality control ?" +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:111 +msgid "Go back to the **Inventory** dashboard. The waiting transfer is now ready. Click on the link **# TRANSFERS** in the **Internal Transfers** card to process the quality control." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:118 +msgid "Click on the last picking to process. Click on **Validate** to complete the move from **WH/Quality Control** to **WH/Stock**." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:121 +msgid "This has completed the quality control step and the status column at the top of the page for **WH/INT** should now show **Done**. The receipt has been controlled and has moved to your stock." +msgstr "" + +#: ../../inventory/incoming/three_steps.rst:127 +msgid ":doc:`two_steps`" +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:3 +msgid "How to unload your shipment to an input location? (2 steps)" +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:13 +msgid "The 2 steps flow is the following : You receive the goods in an input area then transfer them from input area to your stock. As long as the goods are not transferred in your stock, they will not be available for further processing." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:26 +msgid "To allow management of routes, go to the menu :menuselection:`Inventory --> Configuration --> Settings`" +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:35 +msgid "Make sure that **“Manage several locations per warehouse”** is also ticked." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:39 +msgid "How to configure your warehouse ?" +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:41 +msgid "Go to the the menu :menuselection:`Inventory --> Configuration --> Warehouse` and choose the warehouse where you want to change reception methods." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:44 +msgid "By default, warehouses are configured with one step reception (option **Receive goods directly into stock**)." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:47 +msgid "To add the control step, tick **Unload in input location then go to stock (2 steps)**." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:54 +msgid "How to receipt a shipment in 2 steps ?" +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:57 +msgid "How to process the Receipt step ?" +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:59 +msgid "In the purchase module, create a **Request for Quotation**, then click on the **Confirm order** button. You can see that there is one **Shipment** related to purchase order in the **stat button** above the purchase order form view. This is the receipt step." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:67 +msgid "Go to **Inventory** and click on the **# TO RECEIVE** link on the **Receipts** card." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:73 +msgid "Click on the receipt that you want to process, then click on **Validate** to complete the move from the **Vendor** to **WH/Input**." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:76 +msgid "This has completed the Receipt Step and the move refered with **WH/IN**. The product has been moved from the **Vendor** to the **WH/Input** location, which makes the product available for the next step." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:81 +msgid "How to to transfer the receipt to your stock ?" +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:83 +msgid "Go back to the **Inventory** dashboard. The waiting transfer is now ready. Click on the **# TRANSFERS** in the **Internal Transfers** to process the quality control." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:90 +msgid "Click on the picking you want to process. Click on **Validate** to complete the move from **WH/Input** to **WH/Stock**." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:93 +msgid "This has completed the internal transfer step and the move refered with **WH/INT**. The receipt has been moved to your stock." +msgstr "" + +#: ../../inventory/incoming/two_steps.rst:98 +msgid ":doc:`three_steps`" +msgstr "" + +#: ../../inventory/lots_serial_numbers.rst:3 +msgid "Lots and Serial Numbers" +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:3 +msgid "What's the difference between lots and serial numbers?" +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:6 +#: ../../inventory/misc/owned_stock.rst:6 +#: ../../inventory/settings/products/variants.rst:170 +msgid "Introduction" +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:8 +msgid "In Odoo, lots and serial numbers have similarities in their functional system but are different in their behavior. They are both managed within the **Inventory**, **Purchases** and **Sales** app." +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:12 +msgid "**Lots** correspond to a certain number of products you received and store altogether in one single pack." +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:15 +msgid "**Serial numbers** are identification numbers given to one product in particular, to allow to track the history of the item from reception to delivery and after-sales." +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:20 +msgid "When to use" +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:22 +msgid "**Lots** are interesting for products you receive in great quantity and for which a lot number can help in reportings, quality controls, or any other info. Lots will help identify a number of pieces having for instance a production fault. It can be useful for a batch production of clothes or food." +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:28 +msgid "**Serial numbers** are interesting for items that could require after-sales service, such as smartphones, laptops, fridges, and any electronic devices. You could use the manufacturer’s serial number or your own, depending on the way you manage these products" +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:34 +msgid "When not to use" +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:36 +msgid "Storing consumable products such as kitchen roll, toilet paper, pens and paper blocks in lots would make no sense at all, as there are very few chances that you can return them for production fault." +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:40 +msgid "On the other hand, giving a serial number to every product is a time-consuming task that will have a purpose only in the case of items that have a warranty and/or after-sales services. Putting a serial number on bread, for instance, makes no sense at all." +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:46 +msgid ":doc:`serial_numbers`" +msgstr "" + +#: ../../inventory/lots_serial_numbers/differences.rst:47 +msgid ":doc:`lots`" +msgstr "" + +#: ../../inventory/lots_serial_numbers/lots.rst:3 +msgid "How to manage lots of identical products?" +msgstr "" + +#: ../../inventory/lots_serial_numbers/serial_numbers.rst:3 +msgid "How to work with serial numbers?" +msgstr "" + +#: ../../inventory/management.rst:3 +msgid "Warehouse Management" +msgstr "" + +#: ../../inventory/management/adjustment.rst:3 +msgid "Inventory Adjustment" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:3 +msgid "How to make the initial inventory?" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:5 +msgid "One of the most important feature in an warehouse management software is to keep the inventory right." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:8 +msgid "Once your products have been defined, it is time to make your initial inventory. You will reflect reality by inventorying the right quantities in the right locations." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:13 +msgid "Product Configuration" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:15 +msgid "In the Inventory module, open the :menuselection:`Inventory Control --> Products`, then click on **Create** to create a new product. Configure the product type so that it is **Stockable** and not a consumable." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:23 +msgid "Start the initial inventory" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:26 +msgid "Update the product quantity for one product" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:28 +msgid "In the product you just created, you can see in the upper tiles that we have 0 product On Hand. Click on the **Update qty on Hand** button." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:31 +msgid "A new window opens. In the **New Quantity on Hand** field, type the quantity of product you currently hold in stock, then click on **Apply**." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:39 +msgid "if you are using multiple locations for your warehouse, you will be able to set the location of your product from this screen." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:42 +msgid "You can now see from the On Hand tab that the quantity has been updated." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:47 +msgid "Now, if you check the **Inventory Adjustments** in the **Inventory Control** menu, you will see that a new line named \"INV: (name of your product)\" has automatically been created and validated by the system." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:55 +msgid "Multiple products at once" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:57 +msgid "Create all the products for which you want to follow the stock (as stockable products). Once the required products in stock have been defined, use an initial inventory operation to put the current quantities into the system by location. Go to :menuselection:`Inventory Control --> Inventory Adjustments` to start your initial inventory." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:63 +msgid "Give it a name (for example Initial Inventory) and select the stock location of your inventory. Note that when you select a parent location (such as Stock, which might be split into sub locations), you can also select the sub (or child) locations." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:71 +msgid "You can choose between making an inventory for all products, for a few or only for one. In this case, we choose the **All products** option." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:79 +msgid "If you need your stock valuation to be done in a different period than the one that will be selected by default according to the inventory end date, enter the corresponding accounting period in the Force Valuation Period field. The accounting module needs to be installed." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:84 +msgid "Click the **Start Inventory** button. Depending on the type of inventory you have chosen (all products or selected ones) you might have to add products manually by clicking on **Add an item**." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:88 +msgid "Add the **Real Quantity** that you have in your stock for each product." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:92 +msgid "additional information will be available according to the options you activated (multi-locations, serial number, consignee stocks)." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:98 +msgid "Click the **Validate Inventory** button to confirm the inventory and post it." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:102 +msgid "Reporting" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:104 +msgid "To check the current stock, go to :menuselection:`Inventory Control --> Products`, and click on the **list button**:" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:3 +msgid "How to choose between minimum stock rule and make to order" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:5 +msgid "**Minimum Stock rules** and **Make to Order** have similar consequences but different rules. They should be used depending on your manufacturing and delivery strategies." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:10 +msgid "Terminology" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:13 +msgid "Minimum stock rule" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:15 +msgid "**Minimum Stock** rules are used to ensure that you always have the minimum amount of a product in stock in order to manufacture your products and/or answer to your customer needs. When the stock level of a product reaches its minimum the system will automatically generate a procurement with the quantity needed to reach the maximum stock level." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:22 +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:56 +msgid "Make to Order" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:24 +msgid "The **Make to Order** function will trigger a **Purchase Order** of the amount of the **Sales Order** related to the product. The system will **not** check the current stock valuation. This means that a draft purchase order will be generated regardless of the quantity on hand of the product." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:33 +msgid "Minimum stock rules" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:35 +msgid "The Minimum Stock Rules configuration is available through the menu :menuselection:`Inventory --> Inventory Control --> Reordering Rule` in the drop down menu. There, click on **Create** to set minimum and maximum stock values for a given product." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:45 +msgid "Then, click on your product to access the related product form and, on the **Inventory submenu**, do not forget to select a supplier." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:52 +msgid "Don't forget to select the right product type in the product form. A consumable can not be stocked and will thus not be accounted for in the stock valuation." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:58 +msgid "The Make to Order configuration is available on your product form through your :menuselection:`Inventory module --> Inventory control --> Products` (or any other module where products are available)." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:62 +msgid "On the product form, under **Inventory**, click on **Make To Order**." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:68 +msgid "Choice between the two options" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:70 +msgid "The choice between the two options is thus dependent of your inventory strategy. If you prefer to have a buffer and always have at least a minimum amount, the minimum stock rule should be used. If you want to reorder your stocks only if your sale is confirmed it is better to use the Make to Order." +msgstr "" + +#: ../../inventory/management/miscellaneous.rst:3 +msgid "Miscellaneous Operations" +msgstr "" + +#: ../../inventory/management/miscellaneous/schedulers.rst:3 +#: ../../inventory/misc/schedulers.rst:3 +msgid "How to configure and run schedulers?" +msgstr "" + +#: ../../inventory/misc.rst:3 +msgid "Miscellaneous" +msgstr "" + +#: ../../inventory/misc/owned_stock.rst:3 +msgid "How to manage stock that you don't own?" +msgstr "" + +#: ../../inventory/misc/owned_stock.rst:8 +msgid "Some suppliers can sometimes offer you to store and sell products without having to buy those items: this technique is called **consignee stock**." +msgstr "" + +#: ../../inventory/misc/owned_stock.rst:12 +msgid "Consignee stock is a great way for manufacturers and suppliers to launch new products. As resellers may be reluctant to buying a product that they are not sure to be able to sell, consignee stock will allow them to propose an item to check its market without having to pay for it in the first place." +msgstr "" + +#: ../../inventory/misc/owned_stock.rst:18 +msgid "Odoo has the ability to manage consignee stocks through the advanced settings." +msgstr "" + +#: ../../inventory/misc/owned_stock.rst:24 +msgid "Open the menu :menuselection:`Inventory --> Configuration --> Settings`, and in the **Product Owners** section, select **Manage consignee stocks (advanced)**, then click on **Apply**." +msgstr "" + +#: ../../inventory/misc/owned_stock.rst:32 +msgid "Reception of Consignee Stock" +msgstr "" + +#: ../../inventory/misc/owned_stock.rst:34 +msgid "In the Inventory's Dashboard, open the **Receipts** and create a new reception. You can see that in the right side of the page, a new **Owner** line has appeared. You can specify the partner which owns the stock or leave it blank if you are the owner." +msgstr "" + +#: ../../inventory/misc/schedulers.rst:6 +msgid "What is a scheduler" +msgstr "" + +#: ../../inventory/misc/schedulers.rst:8 +msgid "The scheduler is the calculation engine which plans and prioritises production and purchasing automatically according to the rules defined on products. By default, the scheduler is set to run once a day (Odoo automatically creates a **Scheduled Action** for this)." +msgstr "" + +#: ../../inventory/misc/schedulers.rst:14 +msgid "Calculating Requirements / Scheduling" +msgstr "" + +#: ../../inventory/misc/schedulers.rst:16 +msgid "Scheduling only validates procurements that are confirmed but not yet started. These procurement reservations will themselves start production, tasks or purchases depending on the configuration of the requested product." +msgstr "" + +#: ../../inventory/misc/schedulers.rst:21 +msgid "You take into account the priority of operations when starting reservations and procurements. Urgent requests, those with a date in the past, or requests with a date earlier than the others will be started first. In case there are not enough products in stock to satisfy all the requests, you can be sure that the most urgent requests will be produced first." +msgstr "" + +#: ../../inventory/misc/schedulers.rst:29 +msgid "Configure and run the scheduler" +msgstr "" + +#: ../../inventory/misc/schedulers.rst:32 +msgid "Run the scheduler manually" +msgstr "" + +#: ../../inventory/misc/schedulers.rst:34 +msgid "This feature is not visible by default. You have to enable **debug mode** to see this. To enable debug mode, go to :menuselection:`Help --> About` and click on **Activate the developer mode**." +msgstr "" + +#: ../../inventory/misc/schedulers.rst:38 +msgid "You can also start the scheduler manually from the menu :menuselection:`Inventory --> Schedulers --> Run Schedulers`. The scheduler uses all the relevant parameters defined for products, suppliers and the company to determine the priorities between the different production orders, deliveries and supplier purchases." +msgstr "" + +#: ../../inventory/misc/schedulers.rst:48 +msgid "Configure and run the scheduler (only for advanced users)" +msgstr "" + +#: ../../inventory/misc/schedulers.rst:50 +msgid "This feature is not visible by default. You have to enable **debug mode** to see this. To enable debug mode, go to :menuselection:`Help -> About` and click on **Activate the developer mode**." +msgstr "" + +#: ../../inventory/misc/schedulers.rst:54 +msgid "You can set the starting time of the scheduler by modifying the corresponding action in the menu :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`. Modify the Run mrp Scheduler configuration." +msgstr "" + +#: ../../inventory/misc/schedulers.rst:63 +msgid ":doc:`../delivery/scheduled_dates`" +msgstr "" + +#: ../../inventory/misc/scrap.rst:3 +msgid "How to scrap products?" +msgstr "" + +#: ../../inventory/misc/scrap.rst:8 +msgid "Scrap means waste that either has no economic value or only the value of its basic material" +msgstr "" + +#: ../../inventory/misc/scrap.rst:11 +msgid "content recoverable through recycling." +msgstr "" + +#: ../../inventory/misc/scrap.rst:13 +msgid "In your warehouse you sometimes find products that are damaged or that are unusable due to expiry or for some other reason. You often notice this during picking or physical inventory." +msgstr "" + +#: ../../inventory/misc/scrap.rst:17 +msgid "Since you cannot normally sell or store these products, you have to scrap product." +msgstr "" + +#: ../../inventory/misc/scrap.rst:20 +msgid "When goods are scrapped they are not reflected in the system as a part of the inventory. The scrapped material will be physically moved to scrap area." +msgstr "" + +#: ../../inventory/misc/scrap.rst:27 +msgid "When you install inventory management, odoo automatically creates one default scrap location, namely **Virtual location/Scrapped**." +msgstr "" + +#: ../../inventory/misc/scrap.rst:30 +msgid "To create an extra scrap location, Go to :menuselection:`Inventory --> Configuration --> Setting` and check **Manage several locations per warehouse**, then click on **Apply**." +msgstr "" + +#: ../../inventory/misc/scrap.rst:38 +msgid "After applying **Manage several location per warehouse**, you can create a new scrap location in :menuselection:`Configuration --> Warehouse Management --> Locations.`" +msgstr "" + +#: ../../inventory/misc/scrap.rst:43 +msgid "To define a scrap location, you have to check **Is a Scrap Location?** on location form view." +msgstr "" + +#: ../../inventory/misc/scrap.rst:47 +msgid "Different ways to scrap product" +msgstr "" + +#: ../../inventory/misc/scrap.rst:49 +msgid "Odoo provides several ways to scrap products." +msgstr "" + +#: ../../inventory/misc/scrap.rst:52 +msgid "1) Scrap from Receipt (Initial Demand tab)." +msgstr "" + +#: ../../inventory/misc/scrap.rst:54 +msgid "To scrap product from incoming shipment, Go to :menuselection:`Inventory --> Dashboard --> Receipts`." +msgstr "" + +#: ../../inventory/misc/scrap.rst:60 +msgid "Open the incoming shipment, and in the **Initial demand** tab, click on the scrap products button." +msgstr "" + +#: ../../inventory/misc/scrap.rst:67 +msgid "2) Scrap from delivery order (Initial Demand tab) ." +msgstr "" + +#: ../../inventory/misc/scrap.rst:69 +msgid "To scrap product from outgoing shipment, Go to :menuselection:`Inventory --> Dashboard --> Delivery Orders`" +msgstr "" + +#: ../../inventory/misc/scrap.rst:75 +msgid "Open the outgoing shipment, and in the **Initial demand** tab, click on the scrap products button on stock move in initial demand tab." +msgstr "" + +#: ../../inventory/misc/scrap.rst:82 +msgid "3) Scrap from internal transfer (Initial Demand tab)." +msgstr "" + +#: ../../inventory/misc/scrap.rst:84 +msgid "To scrap product from internal transfer, Go to :menuselection:`Inventory --> Dashboard --> Receipts`" +msgstr "" + +#: ../../inventory/misc/scrap.rst:90 +msgid "Open the internal transfer, and in the **Initial demand** tab, click on the scrap products button on stock move in initial demand tab." +msgstr "" + +#: ../../inventory/misc/scrap.rst:96 +msgid "When you click on scrap button, a popup will open. You can enter the quantity of products, and specify the scrap location, then click on **Scrap**." +msgstr "" + +#: ../../inventory/misc/scrap.rst:104 +msgid "To allow change scrap location on wizard, you have to select **Manage several location per warehouse** in the settings at :menuselection:`Inventory --> Configuration --> Setting`" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:5 +msgid "Double-Entry Inventory Management" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:7 +msgid "A double-entry inventory has no stock input, output (disparition of products) or transformation. Instead, all operations are stock moves between locations (possibly virtual)." +msgstr "" + +#: ../../inventory/overview/double-entry.rst:16 +msgid "Operations" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:18 +msgid "Stock moves represent the transit of goods and materials between locations." +msgstr "" + +#: ../../inventory/overview/double-entry.rst:30 +msgid "Production Order" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:24 +msgid "Consume:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "2 Wheels: Stock → Production" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "1 Bike Frame: Stock → Production" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:26 +msgid "Produce:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:27 +msgid "1 Bicycle: Production → Stock" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:30 +#: ../../inventory/overview/double-entry.rst:45 +#: ../../inventory/overview/double-entry.rst:52 +#: ../../inventory/overview/double-entry.rst:57 +#: ../../inventory/overview/double-entry.rst:64 +#: ../../inventory/overview/double-entry.rst:72 +#: ../../inventory/overview/valuation.rst:208 +#: ../../inventory/overview/valuation.rst:237 +msgid "Configuration:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "Stock: the location the Manufacturing Order is initiated from" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "Production: on the product form, field \"Production Location\"" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:36 +msgid "Drop-shipping" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:33 +msgid "1 Bicycle: Supplier → Customer" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:36 +msgid "Configurarion:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "Supplier: on the product form" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "Customer: on the sale order itself" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:45 +msgid "Client Delivery" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:39 +msgid "Pick" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:40 +msgid "1 Bicycle: Stock → Packing Zone" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:41 +msgid "Pack" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:42 +msgid "1 Bicycle: Packing Zone → Output" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:43 +#: ../../inventory/shipping.rst:3 +msgid "Shipping" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:44 +msgid "1 Bicycle: Output → Customer" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "on the pick+pack+ship route for the warehouse" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:52 +msgid "Inter-Warehouse transfer" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:49 +msgid "Transfer:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "1 Bicycle: Warehouse 1 → Transit" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "1 Bicycle: Transit → Warehouse 2" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "Warehouse 2: the location the transfer is initiated from" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "Warehouse 1: on the transit route" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:57 +msgid "Broken Product (scrapped)" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:55 +msgid "1 Bicycle: Warehouse → Scrap" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:58 +msgid "Scrap: Scrap Location when creating the scrapping" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:60 +msgid "Missing products in inventory" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:61 +msgid "1 Bicycle: Warehouse → Inventory Loss" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:62 +msgid "Extra products in inventory" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:63 +msgid "1 Bicycle: Inventory Loss → Warehouse" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:65 +msgid "Inventory Loss: \"Inventory Location\" field on the product" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:72 +msgid "Reception" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "1 Bicycle: Supplier → Input" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "1 Bicycle: Input → Stock" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "Supplier: purchase order supplier" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:0 +msgid "Input: \"destination\" field on the purchase order" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:75 +msgid "Analysis" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:77 +msgid "Inventory analysis can use products count or products value (= number of products * product cost)." +msgstr "" + +#: ../../inventory/overview/double-entry.rst:80 +msgid "For each inventory location, multiple data points can be analysed:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:148 +msgid "Procurements & Procurement Rules" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:150 +msgid "A procurement is a request for a specific quantity of products to a specific location. They can be created manually or automatically triggered by:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:159 +msgid "New sale orders" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:157 +#: ../../inventory/overview/double-entry.rst:162 +#: ../../inventory/overview/double-entry.rst:168 +msgid "Effect" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:157 +msgid "A procurement is created at the customer location for every product ordered by the customer (you have to deliver the customer)" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:160 +msgid "Procurement Location: on the customer, field \"Customer Location\" (property)" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:164 +msgid "Minimum Stock Rules" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:163 +msgid "A procurement is created at the rule's location." +msgstr "" + +#: ../../inventory/overview/double-entry.rst:165 +msgid "Procurement location: on the rule, field \"Location\"" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:168 +msgid "Procurement rules" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:168 +msgid "A new procurement is created on the rule's source location" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:170 +msgid "*Procurement rules* describe how procurements on specific locations should be fulfilled e.g.:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:173 +msgid "where the product should come from (source location)" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:174 +msgid "whether the procurement is :abbr:`MTO (Made To Order)` or :abbr:`MTS (Made To Stock)`" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:182 +msgid "Routes" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:184 +msgid "Procurement rules are grouped in routes. Routes define paths the product must follow. Routes may be applicable or not, depending on the products, sales order lines, warehouse,..." +msgstr "" + +#: ../../inventory/overview/double-entry.rst:188 +msgid "To fulfill a procurement, the system will search for rules belonging to routes that are defined in (by order of priority):" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:202 +#: ../../inventory/settings/warehouses.rst:3 +msgid "Warehouses" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:194 +msgid "Warehouse Route Example: Pick → Pack → Ship" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:196 +msgid "Picking List:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:197 +msgid "Pick Zone → Pack Zone" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:198 +msgid "Pack List:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:199 +msgid "Pack Zone → Gate A" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:201 +msgid "Delivery Order:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:201 +msgid "Gate A → Customer" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:203 +msgid "Routes that describe how you organize your warehouse should be defined on the warehouse." +msgstr "" + +#: ../../inventory/overview/double-entry.rst:212 +msgid "A Product" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:205 +msgid "Product Route Example: Quality Control" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:207 +#: ../../inventory/overview/double-entry.rst:217 +msgid "Reception:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:208 +#: ../../inventory/overview/double-entry.rst:218 +msgid "Supplier → Input" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:209 +msgid "Confirmation:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:210 +msgid "Input → Quality Control" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:212 +msgid "Storage:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:212 +msgid "Quality Control → Stock" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:221 +msgid "Product Category" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:215 +msgid "Product Category Route Example: cross-dock" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:219 +msgid "Cross-Docks:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:220 +msgid "Input → Output" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:221 +msgid "Delivery:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:222 +msgid "Output → Customer" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:227 +msgid "Sale Order Line" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:224 +msgid "Sale Order Line Example: Drop-shipping" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:227 +msgid "Order:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:227 +msgid "Supplier → Customer" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:230 +msgid "Push Rules" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:232 +msgid "Push rules trigger when products enter a specific location. They automatically move the product to a new location. Whether a push rule can be used depends on applicable routes." +msgstr "" + +#: ../../inventory/overview/double-entry.rst:240 +msgid "Quality Control" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:239 +msgid "Product lands in Input" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:240 +msgid "Push 1: Input → Quality Control" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:241 +msgid "Push 2: Quality Control → Stock" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:244 +msgid "Warehouse Transit" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:243 +msgid "Product lands in Transit" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:244 +msgid "Push: Transit → Warehouse 2" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:247 +msgid "Procurement Groups" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:249 +msgid "Routes and rules define inventory moves. For every rule, a document type is provided:" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:252 +msgid "Picking" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:253 +msgid "Packing" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:254 +msgid "Delivery Order" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:255 +msgid "Purchase Order" +msgstr "" + +#: ../../inventory/overview/double-entry.rst:256 +msgid "..." +msgstr "" + +#: ../../inventory/overview/double-entry.rst:258 +msgid "Moves are grouped within the same document type if their procurement group and locations are the same." +msgstr "" + +#: ../../inventory/overview/double-entry.rst:261 +msgid "A sale order creates a procurement group so that pickings and delivery orders of the same order are grouped. But you can define specific groups on reordering rules too. (e.g. to group purchases of specific products together)" +msgstr "" + +#: ../../inventory/overview/settings.rst:3 +#: ../../inventory/overview/setup.rst:3 +msgid "How to setup Odoo inventory?" +msgstr "" + +#: ../../inventory/overview/settings.rst:5 +#: ../../inventory/overview/setup.rst:5 +msgid "The Odoo Inventory application has an implementation guide that you should follow to configure it. It's a step-by-step manual with links to the different screens you will need." +msgstr "" + +#: ../../inventory/overview/settings.rst:9 +#: ../../inventory/overview/setup.rst:9 +msgid "Once you have installed the **Inventory** application, you should click on the top-right progressbar to get access to the implementation guide." +msgstr "" + +#: ../../inventory/overview/settings.rst:15 +#: ../../inventory/overview/setup.rst:15 +msgid "The implementation guide will help you through the following steps:" +msgstr "" + +#: ../../inventory/overview/settings.rst:17 +#: ../../inventory/overview/setup.rst:17 +msgid "Setup your warehouse" +msgstr "" + +#: ../../inventory/overview/settings.rst:19 +#: ../../inventory/overview/setup.rst:19 +msgid "Import your vendors" +msgstr "" + +#: ../../inventory/overview/settings.rst:21 +#: ../../inventory/overview/setup.rst:21 +msgid "Import your products" +msgstr "" + +#: ../../inventory/overview/settings.rst:23 +#: ../../inventory/overview/setup.rst:23 +msgid "Make the initial inventory" +msgstr "" + +#: ../../inventory/overview/settings.rst:25 +#: ../../inventory/overview/setup.rst:25 +msgid "Configure your sales and purchase flows" +msgstr "" + +#: ../../inventory/overview/settings.rst:27 +#: ../../inventory/overview/setup.rst:27 +msgid "Set-up replenishment mechanisms" +msgstr "" + +#: ../../inventory/overview/settings.rst:29 +#: ../../inventory/overview/setup.rst:29 +msgid "Configure advanced features like package, traceability, routes and inventory valuation." +msgstr "" + +#: ../../inventory/overview/settings.rst:37 +#: ../../inventory/overview/setup.rst:37 +msgid "If you want to set up operations with barcode scanner in your warehouse, you should install the **Barcode** application that will add features on top of the inventory application. The barcode application will guide you to configure and use your scanner optimally." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:3 +msgid "Terminologies" +msgstr "" + +#: ../../inventory/overview/terminologies.rst:5 +msgid "**Warehouse**: A warehouse in Odoo is a location where you store products. It is either a physical or a virtual warehouse. It could be a store or a repository." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:9 +msgid "**Location**: Locations are used to structure storage zones within a warehouse. In addition to internal locations (your warehouse), Odoo has locations for suppliers, customers, inventory loss counter-parts, etc." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:14 +msgid "**Lots**: Lots are a batch of products identified with a unique barcode or serial number. All items of a lot are from the same product. (e.g. a set of 24 bottle) Usually, lots come from manufacturing order batches or procurements." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:19 +msgid "**Serial Number**: A serial number is a unique identifier of a specific product. Technically, serial numbers are similar to having a lot of 1 unique item." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:23 +msgid "**Unit of Measure**: Define how the quantity of products is expressed. Meters, Pounds, Pack of 24, Kilograms,… Unit of measure of the same category (ex: size) can be converted to each others (m, cm, mm) using a fixed ratio." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:28 +msgid "**Consumable**: A product for which you do not want to manage the inventory level (no quantity on hand or forecasted) but that you can receive and deliver. When this product is needed Odoo suppose that you always have enough stock." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:33 +msgid "**Stockable**: A product for which you want to manage the inventory level." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:36 +msgid "**Package:** A package contains several products (identified by their serial number/lots or not). Example: a box containing knives and forks." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:40 +msgid "**Procurement**: A procurement is a request for a specific quantity of products to a specific location. Procurement are automatically triggered by other documents: Sale orders, Minimum Stock Rules, and Procurement rules. You can trigger the procurement manually. When procurements are triggered automatically, you should always pay attention for the exceptions (e.g. a product should be purchased from a vendor, but no supplier is defined)." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:48 +msgid "**Routes**: Routes define paths the product must follow. Routes may be applicable or not, depending on the products, sales order lines, warehouse,… To fulfill a procurement, the system will search for rules belonging to routes that are defined in the related product/sale order." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:54 +msgid "**Push Rules**: Push rules trigger when products enter a specific location. They automatically move the product to a new location. Whether a push rule can be used depends on applicable routes." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:58 +msgid "**Procurement Rules** or **Pull Rules**: Procurement rules describe how procurements on specific locations should be fulfilled e.g.: where the product should come from (source location), whether the procurement is MTO or MTS,..." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:63 +msgid "**Procurement Group**: Routes and rules define inventory moves. For every rule, a document type is provided: Picking, Packing, Delivery Order, Purchase Order,… Moves are grouped within the same document type if their procurement group and locations are the same." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:69 +msgid "**Stock Moves**: Stock moves represent the transit of goods and materials between locations." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:72 +msgid "**Quantity On Hand**: The quantity of a specific product that is currently in a warehouse or location." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:75 +msgid "**Forecasted Quantity**: The quantity of products you can sell for a specific warehouse or location. It is defined as the Quantity on Hand - Future Delivery Orders + Future incoming shipments + Future manufactured units." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:80 +msgid "**Reordering Rules**: It defines the conditions for Odoo to automatically trigger a request for procurement (buying at a supplier or launching a manufacturing order). It is triggered when the forecasted quantity meets the minimum stock rule." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:85 +msgid "**Cross-Dock**: Cross-docking is a practice in the logistics of unloading materials from an incoming semi-trailer truck or railroad car and loading these materials directly into outbound trucks, trailers, or rail cars, with no storage in between. (does not go to the stock, directly from incoming to packing zone)" +msgstr "" + +#: ../../inventory/overview/terminologies.rst:91 +msgid "**Drop-Shipping**: move products from the vendor/manufacturer directly to the customer (could be retailer or consumer) without going through the usual distribution channels. Products are sent directly from the vendor to the customer, without passing through your own warehouse." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:97 +msgid "**Removal Strategies**: the strategy to use to select which product to pick for a specific operation. Example: FIFO, LIFO, FEFO." +msgstr "" + +#: ../../inventory/overview/terminologies.rst:100 +msgid "**Putaway Strategies**: the strategy to use to decide in which location a specific product should be set when arriving somewhere. (example: cables goes in rack 3, storage A)" +msgstr "" + +#: ../../inventory/overview/terminologies.rst:104 +msgid "**Scrap**: A product that is broken or outdated. Scrapping a product removes it from the stock." +msgstr "" + +#: ../../inventory/overview/valuation.rst:5 +msgid "Inventory Valuations" +msgstr "" + +#: ../../inventory/overview/valuation.rst:8 +msgid "Costing Method" +msgstr "" + +#: ../../inventory/overview/valuation.rst:10 +msgid "International accounting standards define several ways to compute product costs:" +msgstr "" + +#: ../../inventory/overview/valuation.rst:52 +msgid "Standard Price" +msgstr "" + +#: ../../inventory/overview/valuation.rst:23 +#: ../../inventory/overview/valuation.rst:62 +#: ../../inventory/overview/valuation.rst:101 +#: ../../inventory/overview/valuation.rst:140 +msgid "Operation" +msgstr "" + +#: ../../inventory/overview/valuation.rst:24 +#: ../../inventory/overview/valuation.rst:63 +#: ../../inventory/overview/valuation.rst:102 +#: ../../inventory/overview/valuation.rst:141 +msgid "Unit Cost" +msgstr "" + +#: ../../inventory/overview/valuation.rst:25 +#: ../../inventory/overview/valuation.rst:64 +#: ../../inventory/overview/valuation.rst:103 +#: ../../inventory/overview/valuation.rst:142 +msgid "Qty On Hand" +msgstr "" + +#: ../../inventory/overview/valuation.rst:26 +#: ../../inventory/overview/valuation.rst:65 +#: ../../inventory/overview/valuation.rst:104 +#: ../../inventory/overview/valuation.rst:143 +msgid "Delta Value" +msgstr "" + +#: ../../inventory/overview/valuation.rst:27 +#: ../../inventory/overview/valuation.rst:66 +#: ../../inventory/overview/valuation.rst:105 +#: ../../inventory/overview/valuation.rst:144 +msgid "Inventory Value" +msgstr "" + +#: ../../inventory/overview/valuation.rst:29 +#: ../../inventory/overview/valuation.rst:34 +#: ../../inventory/overview/valuation.rst:39 +#: ../../inventory/overview/valuation.rst:44 +#: ../../inventory/overview/valuation.rst:50 +#: ../../inventory/overview/valuation.rst:73 +#: ../../inventory/overview/valuation.rst:112 +#: ../../inventory/overview/valuation.rst:151 +#: ../../inventory/overview/valuation.rst:161 +msgid "$10" +msgstr "" + +#: ../../inventory/overview/valuation.rst:30 +#: ../../inventory/overview/valuation.rst:69 +#: ../../inventory/overview/valuation.rst:108 +#: ../../inventory/overview/valuation.rst:147 +msgid "0" +msgstr "" + +#: ../../inventory/overview/valuation.rst:32 +#: ../../inventory/overview/valuation.rst:68 +#: ../../inventory/overview/valuation.rst:71 +#: ../../inventory/overview/valuation.rst:107 +#: ../../inventory/overview/valuation.rst:110 +#: ../../inventory/overview/valuation.rst:146 +#: ../../inventory/overview/valuation.rst:149 +msgid "$0" +msgstr "" + +#: ../../inventory/overview/valuation.rst:33 +#: ../../inventory/overview/valuation.rst:72 +#: ../../inventory/overview/valuation.rst:111 +#: ../../inventory/overview/valuation.rst:150 +msgid "Receive 8 Products at $10" +msgstr "" + +#: ../../inventory/overview/valuation.rst:35 +#: ../../inventory/overview/valuation.rst:74 +#: ../../inventory/overview/valuation.rst:113 +#: ../../inventory/overview/valuation.rst:152 +msgid "8" +msgstr "" + +#: ../../inventory/overview/valuation.rst:36 +#: ../../inventory/overview/valuation.rst:75 +#: ../../inventory/overview/valuation.rst:114 +#: ../../inventory/overview/valuation.rst:153 +msgid "+8*$10" +msgstr "" + +#: ../../inventory/overview/valuation.rst:37 +#: ../../inventory/overview/valuation.rst:76 +#: ../../inventory/overview/valuation.rst:115 +#: ../../inventory/overview/valuation.rst:154 +msgid "$80" +msgstr "" + +#: ../../inventory/overview/valuation.rst:38 +#: ../../inventory/overview/valuation.rst:77 +#: ../../inventory/overview/valuation.rst:116 +#: ../../inventory/overview/valuation.rst:155 +msgid "Receive 4 Products at $16" +msgstr "" + +#: ../../inventory/overview/valuation.rst:40 +#: ../../inventory/overview/valuation.rst:79 +#: ../../inventory/overview/valuation.rst:118 +#: ../../inventory/overview/valuation.rst:157 +msgid "12" +msgstr "" + +#: ../../inventory/overview/valuation.rst:41 +msgid "+4*$10" +msgstr "" + +#: ../../inventory/overview/valuation.rst:42 +msgid "$120" +msgstr "" + +#: ../../inventory/overview/valuation.rst:43 +#: ../../inventory/overview/valuation.rst:121 +#: ../../inventory/overview/valuation.rst:160 +msgid "Deliver 10 Products" +msgstr "" + +#: ../../inventory/overview/valuation.rst:45 +#: ../../inventory/overview/valuation.rst:84 +#: ../../inventory/overview/valuation.rst:123 +#: ../../inventory/overview/valuation.rst:162 +msgid "2" +msgstr "" + +#: ../../inventory/overview/valuation.rst:0 +msgid "-10*$10" +msgstr "" + +#: ../../inventory/overview/valuation.rst:48 +#: ../../inventory/overview/valuation.rst:165 +msgid "$20" +msgstr "" + +#: ../../inventory/overview/valuation.rst:49 +msgid "Receive 2 Products at $9" +msgstr "" + +#: ../../inventory/overview/valuation.rst:51 +#: ../../inventory/overview/valuation.rst:90 +#: ../../inventory/overview/valuation.rst:129 +#: ../../inventory/overview/valuation.rst:168 +msgid "4" +msgstr "" + +#: ../../inventory/overview/valuation.rst:52 +msgid "+2*$10" +msgstr "" + +#: ../../inventory/overview/valuation.rst:53 +msgid "$40" +msgstr "" + +#: ../../inventory/overview/valuation.rst:91 +msgid "Average Price" +msgstr "" + +#: ../../inventory/overview/valuation.rst:78 +#: ../../inventory/overview/valuation.rst:83 +#: ../../inventory/overview/valuation.rst:117 +#: ../../inventory/overview/valuation.rst:156 +msgid "$12" +msgstr "" + +#: ../../inventory/overview/valuation.rst:80 +#: ../../inventory/overview/valuation.rst:119 +#: ../../inventory/overview/valuation.rst:158 +msgid "+4*$16" +msgstr "" + +#: ../../inventory/overview/valuation.rst:81 +#: ../../inventory/overview/valuation.rst:120 +#: ../../inventory/overview/valuation.rst:159 +msgid "$144" +msgstr "" + +#: ../../inventory/overview/valuation.rst:82 +msgid "Deliver 10 Products [#average-removal]_" +msgstr "" + +#: ../../inventory/overview/valuation.rst:0 +msgid "-10*$12" +msgstr "" + +#: ../../inventory/overview/valuation.rst:87 +msgid "$24" +msgstr "" + +#: ../../inventory/overview/valuation.rst:88 +#: ../../inventory/overview/valuation.rst:127 +#: ../../inventory/overview/valuation.rst:166 +msgid "Receive 2 Products at $6" +msgstr "" + +#: ../../inventory/overview/valuation.rst:89 +msgid "$9" +msgstr "" + +#: ../../inventory/overview/valuation.rst:91 +#: ../../inventory/overview/valuation.rst:130 +#: ../../inventory/overview/valuation.rst:169 +msgid "+2*$6" +msgstr "" + +#: ../../inventory/overview/valuation.rst:92 +msgid "$36" +msgstr "" + +#: ../../inventory/overview/valuation.rst:130 +msgid "FIFO" +msgstr "" + +#: ../../inventory/overview/valuation.rst:122 +msgid "$16" +msgstr "" + +#: ../../inventory/overview/valuation.rst:0 +msgid "-8*$10" +msgstr "" + +#: ../../inventory/overview/valuation.rst:0 +msgid "-2*$16" +msgstr "" + +#: ../../inventory/overview/valuation.rst:126 +#: ../../inventory/overview/valuation.rst:170 +msgid "$32" +msgstr "" + +#: ../../inventory/overview/valuation.rst:128 +msgid "$11" +msgstr "" + +#: ../../inventory/overview/valuation.rst:131 +msgid "$44" +msgstr "" + +#: ../../inventory/overview/valuation.rst:170 +msgid "LIFO (not accepted in IFRS)" +msgstr "" + +#: ../../inventory/overview/valuation.rst:0 +msgid "-4*$16" +msgstr "" + +#: ../../inventory/overview/valuation.rst:0 +msgid "-6*$10" +msgstr "" + +#: ../../inventory/overview/valuation.rst:167 +msgid "$8" +msgstr "" + +#: ../../inventory/overview/valuation.rst:172 +msgid "The costing method is defined on the product form: standard, average or real price." +msgstr "" + +#: ../../inventory/overview/valuation.rst:175 +msgid "For \"real price\", the costing is further refined by the removal strategy (on the warehouse location or product category), FIFO by default." +msgstr "" + +#: ../../inventory/overview/valuation.rst:179 +msgid "Periodic Inventory Valuation" +msgstr "" + +#: ../../inventory/overview/valuation.rst:181 +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 post one journal entry representing the value of the physical inventory." +msgstr "" + +#: ../../inventory/overview/valuation.rst:208 +msgid "Supplier Invoice" +msgstr "" + +#: ../../inventory/overview/valuation.rst:192 +#: ../../inventory/overview/valuation.rst:216 +msgid "\\" +msgstr "" + +#: ../../inventory/overview/valuation.rst:192 +#: ../../inventory/overview/valuation.rst:216 +msgid "Debit" +msgstr "" + +#: ../../inventory/overview/valuation.rst:192 +#: ../../inventory/overview/valuation.rst:216 +msgid "Credit" +msgstr "" + +#: ../../inventory/overview/valuation.rst:194 +#: ../../inventory/overview/valuation.rst:221 +msgid "Assets: Inventory" +msgstr "" + +#: ../../inventory/overview/valuation.rst:194 +#: ../../inventory/overview/valuation.rst:221 +#: ../../inventory/overview/valuation.rst:222 +msgid "50" +msgstr "" + +#: ../../inventory/overview/valuation.rst:195 +msgid "Assets: Deferred Tax Assets" +msgstr "" + +#: ../../inventory/overview/valuation.rst:195 +msgid "4.68" +msgstr "" + +#: ../../inventory/overview/valuation.rst:196 +msgid "Liabilities: Accounts Payable" +msgstr "" + +#: ../../inventory/overview/valuation.rst:196 +msgid "54.68" +msgstr "" + +#: ../../inventory/overview/valuation.rst:203 +#: ../../inventory/overview/valuation.rst:229 +msgid "Explanation:" +msgstr "" + +#: ../../inventory/overview/valuation.rst:200 +msgid "A temporary account is used to note goods to receive" +msgstr "" + +#: ../../inventory/overview/valuation.rst:201 +msgid "The purchase order provides prices of goods, the actual invoice may include extra costs such as shipping" +msgstr "" + +#: ../../inventory/overview/valuation.rst:203 +msgid "The company still needs to pay the vendor (traded an asset against a liability)" +msgstr "" + +#: ../../inventory/overview/valuation.rst:206 +msgid "Inventory: defined on the product or the category of related product, field: Stock Input Account" +msgstr "" + +#: ../../inventory/overview/valuation.rst:208 +msgid "Deferred Tax Assets: defined on the tax used on the purchase order line" +msgstr "" + +#: ../../inventory/overview/valuation.rst:209 +msgid "Accounts Payable: defined on the supplier related to the bill" +msgstr "" + +#: ../../inventory/overview/valuation.rst:210 +msgid "Goods Receptions" +msgstr "" + +#: ../../inventory/overview/valuation.rst:211 +#: ../../inventory/overview/valuation.rst:242 +#: ../../inventory/overview/valuation.rst:244 +msgid "No Journal Entry" +msgstr "" + +#: ../../inventory/overview/valuation.rst:239 +msgid "Customer Invoice" +msgstr "" + +#: ../../inventory/overview/valuation.rst:218 +msgid "Revenue: Goods" +msgstr "" + +#: ../../inventory/overview/valuation.rst:218 +msgid "100" +msgstr "" + +#: ../../inventory/overview/valuation.rst:219 +msgid "Liabilities: Deferred Tax Liabilities" +msgstr "" + +#: ../../inventory/overview/valuation.rst:219 +msgid "9" +msgstr "" + +#: ../../inventory/overview/valuation.rst:220 +msgid "Assets: Accounts Receivable" +msgstr "" + +#: ../../inventory/overview/valuation.rst:220 +msgid "109" +msgstr "" + +#: ../../inventory/overview/valuation.rst:222 +msgid "Expenses: Cost of Goods Sold" +msgstr "" + +#: ../../inventory/overview/valuation.rst:226 +msgid "Revenues increase by $100" +msgstr "" + +#: ../../inventory/overview/valuation.rst:227 +msgid "A tax to pay at the end of the month of $9" +msgstr "" + +#: ../../inventory/overview/valuation.rst:228 +msgid "The customer owns you $109" +msgstr "" + +#: ../../inventory/overview/valuation.rst:229 +msgid "The inventory is decreased by $50 (shipping of the goods)" +msgstr "" + +#: ../../inventory/overview/valuation.rst:230 +msgid "The cost of goods sold decreases the gross profit by $50" +msgstr "" + +#: ../../inventory/overview/valuation.rst:232 +msgid "Revenue: defined on the product, or the product category if not on the product, field Income Account" +msgstr "" + +#: ../../inventory/overview/valuation.rst:234 +msgid "Deferred Tax Liabilities: defined on the tax used on the invoice line" +msgstr "" + +#: ../../inventory/overview/valuation.rst:235 +msgid "Accounts Receivable: defined on the customer (property)" +msgstr "" + +#: ../../inventory/overview/valuation.rst:236 +msgid "Inventory: defined on the category of the related product (property)" +msgstr "" + +#: ../../inventory/overview/valuation.rst:237 +msgid "Expenses: defined on the product, or the category of product (property)" +msgstr "" + +#: ../../inventory/overview/valuation.rst:239 +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/overview/valuation.rst:241 +msgid "Customer Shipping" +msgstr "" + +#: ../../inventory/overview/valuation.rst:244 +msgid "Manufacturing Orders" +msgstr "" + +#: ../../inventory/overview/valuation.rst:250 +msgid "At the end of the month/year, the company do a physical inventory (or just rely on the inventory in Odoo). They multiply the quantity of each product by its cost to know the inventory value of the company." +msgstr "" + +#: ../../inventory/overview/valuation.rst:256 +msgid "If the real value of the inventory is $4800 but the *14000 Inventory* account has a balance of $4200, the following journal entry is created manually:" +msgstr "" + +#: ../../inventory/overview/valuation.rst:263 +msgid "14000 Inventory" +msgstr "" + +#: ../../inventory/overview/valuation.rst:263 +#: ../../inventory/overview/valuation.rst:264 +msgid "$600" +msgstr "" + +#: ../../inventory/overview/valuation.rst:264 +msgid "14700 Inventory Variations" +msgstr "" + +#: ../../inventory/overview/valuation.rst:268 +msgid "Perpetual Inventory Valuation" +msgstr "" + +#: ../../inventory/overview/valuation.rst:270 +msgid "In a perpetual inventory valuation, goods reception and outgoing shipments are directly posted in the accounting. The inventory valuation is always up-to-date." +msgstr "" + +#: ../../inventory/overview/valuation.rst:278 +msgid "products leaving the stock have no impact on the average price." +msgstr "" + +#: ../../inventory/settings.rst:3 +msgid "Settings" +msgstr "" + +#: ../../inventory/settings/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:3 +msgid "Using product variants" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:5 +msgid "Product variants are used to manage products having different variations, like size, color, etc. It allows managing the product at the template level (for all variations) and at the variant level (specific attributes)." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:10 +msgid "As an example, a company selling t-shirts may have the following product:" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:13 +msgid "B&C T-shirt" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:15 +msgid "Sizes: S, M, L, XL, XXL" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:16 +msgid "Colors: Blue, Red, White, Black" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:18 +msgid "In this example, **B&C T-Shirt** is called the product template and **B&C T-Shirt, S, Blue** is a variant. Sizes and color are **attributes**." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:22 +msgid "The above example has a total of 20 different products (5 sizes x 4 colors). Each one of these products has its own inventory, sales, etc." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:26 +msgid "Impact of variants" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:28 +msgid "**Barcode**: the code and barcode is associated to a variant, not the template. Every variant may have its own barcode / SKU." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:31 +msgid "**Price**: every product variant has its own public price that is computed based on the template price ($20) with an optional extra for every variant (+$3 for color red). However, you can define pricelist rules that apply on the template or the variant." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:36 +msgid "**Inventory**: the inventory is managed by product variant. You don't own t-shirts, you only own \"T-shirts, S, Red\", or \"T-Shirts, M, Blue\". For information purpose, on the product template form, you get the inventory that is the sum of every variant. (but the actual inventory is computed by variant)" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:42 +msgid "**Picture**: the picture is related to the variant, every variation of a product may have its own primary picture." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:45 +msgid "**Other fields**: most of the other fields belongs to the product template. If you update them, it updates automatically all the variants. (example: Income Account, Taxes)" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:50 +msgid "Should you use variants?" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:53 +msgid "When should you use variants?" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:55 +msgid "Using variants has the following impacts:" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:57 +msgid "**eCommerce**: in your online shop, the customer will only see product templates in the catalog page. Once the visitor click on such a product, he will have options to choose amongst the variants (colors, sizes, …)" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:62 +msgid "**Manufacturing**: Using variants allows to define only one bill of material for a product template and slight variations for some of the variants. Example: instead of creating a Bill of Material for \"T-shirt, Red, S\", you create a bill of material for \"T-shirt\" and add some lines that are specific to the dimension S, and other lines specific to the color Red." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:69 +msgid "**Pricing**: The default price of a product is computed using the price of the product template and add the optional extra price on each dimension of the variant. This way, variant prices are easier to maintain since you don't have to set the price for every variant. However, it's possible to create pricelist rules to fix price per variants too." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:77 +msgid "When should you avoid using variants?" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:79 +msgid "Using variants may add a level of complexity on the way you use Odoo. You should consider using variants only if you need it to reduce the complexity of managing lots of products that are similars." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:83 +msgid "As an example, importing your initial product catalog is more complex if you use variants. You can't just import a list of products, you must import product templates and all their related variations." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:87 +msgid "In addition to that, you should also carefully select the dimensions that you manage as separate product templates and those as variants. As an example, a company having these products:" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:91 +msgid "Quality: T-Shirts, Polos, Shirts" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:93 +#: ../../inventory/settings/products/variants.rst:105 +#: ../../inventory/settings/products/variants.rst:110 +msgid "Color: Red, Blue" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:95 +#: ../../inventory/settings/products/variants.rst:106 +#: ../../inventory/settings/products/variants.rst:111 +msgid "Size: S, M, L, XL" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:97 +msgid "In such a use case, you could create 1 template with three dimensions of variants (Layout, T-Shirts, Polos). But, it's recommended to create two different product templates as T-shirts may highly differ from polos or shirts and customer expect to see these as two different products in the e-Commerce:" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:103 +msgid "Product Template: T-shirt" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:108 +msgid "Product Template: Polos" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:117 +msgid "Activate the variant feature" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:119 +msgid "Before you can use product variants, you must first activate the product variants in the settings. To do so, you must go to the Sales app. In the menu :menuselection:`Configuration --> Settings`, locate the **Products Variants** line, and tick the option **Products can have several attributes**, then click on **Apply**." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:129 +msgid "Creating products with variants" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:131 +msgid "Once you have activated the variant option, you can add variants to your products. To do so, go to the Sales module, :menuselection:`Sales --> Products`. It is also accessible from the Purchase and inventory modules." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:135 +msgid "Now, click on the product you wish to add variants to." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:137 +msgid "In the product page, a new tab called Variants has appeared. The number in purple written on top is the number of variants this product currently has. To add new variants, click on the tile. In the new window, click on **Create**." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:142 +msgid "In **Attributes**, click on the rolldown menu and select the type of variance you wish to add. If the variant does not yet exist, you can create it on the fly by clicking on Create and edit…" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:149 +msgid "In the Attributes window, the **Value** field is the description of the attribute such as Green, Plastic or 32GB. The **Attribute** field is the type of variant such as Color, Material or Memory." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:156 +msgid "You can add a cost for the variant on the fly by adding it in the **Attribute Price Extra** field, or choose to modify it later. Click on **Save**." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:160 +msgid "You can also add a different barcode and internal reference to the variant." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:163 +msgid "When you have entered all the specifications of the variant, click on **Save**." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:167 +msgid "Managing Product Variants" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:172 +msgid "The examples below are all based on this product template that has two variant attributes :" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:175 +msgid "T-Shirt B&C" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:177 +msgid "Color: Red, Blue, White" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:179 +msgid "Size: S, M, L, XL, XXL" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:182 +msgid "Managing combination possibilities" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:184 +msgid "By default, with the above product template, you get 15 different products (3 colors, 5 sizes). If the XXL size does not exist for red and blue t-shirts, you can deactivate this product variant." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:188 +msgid "To do this, click on the **Variants** button, select the XXL, White T-shirt. From the product form, uncheck the **Active** box of the T-shirt White, XXL." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:197 +msgid "That deactivating a product is different than having an inventory of 0." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:200 +msgid "Setting a price per variant" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:202 +msgid "You can add a cost over the main price for some of the variants of a product." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:205 +msgid "Once you have activated the variant option, you can add variants to your products. To do so, go to the Sales module, open :menuselection:`Sales --> Products` and click on the product you want to modify. Click on the **Variant Prices** button to access the list of variant values." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:213 +msgid "Click on the variant name you wish to add a value to, to make the 3 fields editable. In the **Attribute Price Extra** field, add the cost of the variant that will be added to the original price." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:220 +msgid "When you have entered all the extra values, click on **Save**." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:3 +msgid "What is the difference between warehouses and locations?" +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:5 +msgid "In Odoo, a **Warehouse** is the actual building/place in which your items are stocked. You can setup multiple warehouses and create moves between warehouses." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:9 +msgid "A **Location**, is a specific space within your warehouse. It can be considered as a sublocation of your warehouse, as a shelf, a floor, an aisle, etc. Therefore, a location is part of one warehouse only and it is not possible to link one location to multiple warehouses. You can configure as much locations as you need under one warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:15 +msgid "There are 3 types of locations:" +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:17 +msgid "The **Physical Locations** are internal locations that are part of the warehouses for which you are the owner. They can be the loading and unloading area of your warehouse, a shelf or a department, etc." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:21 +msgid "The **Partner Locations** are spaces within a customer and/or vendor's warehouse. They work the same way as Physical Locations with the only difference being that you are not the owner of the warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:25 +msgid "The **Virtual Locations** are places that do not exist, but in which products can be placed when they are not physically in an inventory yet (or anymore). They come in handy when you want to place lost products out of your stock (in the **Inventory loss**), or when you want to take into account products that are on their way to your warehouse (**Procurements**)." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:31 +msgid "In Odoo, locations are structured hierarchically. You can structure your locations as a tree, dependent on a parent-child relationship. This gives you more detailed levels of analysis of your stock operations and the organization of your warehouses." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:37 +#: ../../inventory/settings/warehouses/location_creation.rst:44 +msgid ":doc:`warehouse_creation`" +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:38 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:48 +msgid ":doc:`location_creation`" +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:3 +msgid "How to create a new location?" +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:9 +msgid "Creating a new location" +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:11 +msgid "In order to be able to create new locations, you must allow the system to manage multiple locations. In the **Inventory** module, open the menu :menuselection:`Configuration --> Settings`. In the **Location & Warehouse** section, tick the **Manage several locations per warehouse** box, then click on **Apply**." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:20 +msgid "In the **Inventory** module, open :menuselection:`Configuration --> Warehouse Management --> Locations` In the Locations window, click on **Create**." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:24 +msgid "Type the name of the location in the **Location Name** field, and select the **Parent Location** in the list. The parent location can be a physical, partner or virtual location, and you can add as many sub-locations as needed to a location." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:29 +msgid "You can also fill in the **Additional Information** fields and add a note to describe your location." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:35 +msgid "When you are finished, click on **Save**." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:38 +msgid "A warehouse also corresponds to a location. As the locations are hierarchical, Odoo will create the parent location of the warehouse, containing all the sublocations in it." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:43 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:47 +msgid ":doc:`difference_warehouse_location`" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:3 +msgid "How to create a new warehouse?" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:9 +msgid "Creating a new warehouse" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:11 +msgid "In order to be able to create a new warehouse, you must allow the system to manage multiple locations. In the **Inventory** module, open the menu :menuselection:`Settings --> Configuration`. In the **Location & Warehouse** section, tick the **Manage several locations per warehouse** box, then click on **apply**." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:20 +msgid "Open the menu :menuselection:`Configuration --> Warehouse Management --> Warehouses`" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:22 +msgid "In the warehouses screen, click on **Create**. A new screen appears, with 3 fields :" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:25 +msgid "In **Warehouse Name**, insert the full name of the warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:27 +msgid "In the **Short Name** field, insert a 5-characters code for your warehouse. Keep in mind that this code is the one that will appear in the lists, so make sure you choose a name that is easy to understand and easy to enter." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:32 +msgid "In the **Address** field, you can select an existing company or create one on-the-go. Therefore, the address of your warehouse will be the same as the one of the company you selected. You can also leave this field empty and edit it afterwards." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:40 +msgid "Click on **Save** to finish configuring your new warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:43 +msgid "When you create a warehouse, the system will create the necessary picking types and main child locations for this main location in the background." +msgstr "" + +#: ../../inventory/shipping/operation.rst:3 +msgid "Shipping Operations" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:3 +msgid "How to cancel a shipping request to a shipper?" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:3 +msgid "How to invoice the shipping cost to the customer ?" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:3 +msgid "How to print shipping labels?" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:3 +msgid "How to manage multiple packs for the same delivery order?" +msgstr "" + +#: ../../inventory/shipping/setup.rst:3 +msgid "Shipping Setup" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:3 +msgid "How to setup a delivery method?" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:8 +msgid "Odoo can handle various delivery methods, but it is not activated by default. Delivery methods can be used for your sale orders, your deliveries but also on your e-commerce." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:12 +msgid "Delivery methods allow you to manage the transport company, the price and the destination. You can even integrate Odoo with external shippers to compute the real price and the packagings." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:20 +msgid "Install the inventory module" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:22 +msgid "Delivery methods are handled by the **Delivery costs** module. Go to **Apps** and search for the module. You should remove the **Apps** filter in order to see it :" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:30 +msgid "If you want to integrate delivery methods in your e-commerce, you'll have to install the **eCommerce Delivery** module." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:34 +msgid "Configure the delivery method" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:36 +msgid "To configure your delivery methods, go to the **Inventory** module, click on :menuselection:`Configuration --> Delivery Methods`." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:39 +msgid "First set a name and a transporter company." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:44 +msgid "Then you'll have to set the pricing. It can be fixed or based on rules." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:46 +msgid "If the price is fixed, tick **Fixed price**. You'll just have to define the price. If you want the delivery to be free above a certain amount, tick the option **Free if Order total is more than** and set a price." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:54 +msgid "If the price varies according to rules, tick **Based on Rules**. Click on **add an item to a pricing rule**. Choose a condition based on either the weight, the volume, the price or the quantity." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:61 +msgid "Finally you can limit the delivery method to a few destinations. The limit can be applied to some countries, states or even zip codes. This feature limits the list of countries on your e-commerce." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:69 +msgid "You can integrate Odoo with external shippers in order to compute the real price and packagings, and handle the printing the shipping labels. See :doc:`third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:74 +msgid "Delivery process" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:77 +msgid "Sale order" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:82 +msgid "You can now choose the **Delivery Method** on your sale order. If you want to invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:88 +msgid "Delivery" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:90 +msgid "You can add or change the delivery method on the delivery itself." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:95 +msgid "On the delivery, check the **Carrier Information**. The carrier is the chosen delivery method." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:99 +msgid ":doc:`third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:100 +msgid ":doc:`../operation/invoicing`" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:3 +msgid "How to integrate a third party shipper?" +msgstr "" + diff --git a/locale/sources/point_of_sale.pot b/locale/sources/point_of_sale.pot new file mode 100644 index 000000000..3f5d38ddd --- /dev/null +++ b/locale/sources/point_of_sale.pot @@ -0,0 +1,638 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2015-11-03 11:43+0100\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" + +#: ../../point_of_sale.rst:5 +msgid "Point of Sale" +msgstr "" + +#: ../../point_of_sale/posbox.rst:3 +msgid "Overview" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:3 +msgid "POSBox" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:6 +msgid "POSBox Setup Guide" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:11 +#: ../../point_of_sale/posbox/index.rst:210 +msgid "Prerequisites" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:13 +msgid "Before you start setting up your POSBox make sure you have everything. You will need :" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:16 +msgid "The POSBox" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:17 +msgid "A 2A Power adapter" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:18 +msgid "A computer or tablet with an up-to-date web browser" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:19 +msgid "A running SaaS or Odoo instance with the Point of Sale installed" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:20 +msgid "A local network set up with DHCP (this is the default setting)" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:21 +msgid "An RJ45 Ethernet Cable or a Linux compatible USB Wi-Fi adapter" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:22 +msgid "An Epson USB TM-T20 Printer or another compatible printer (officially supported printers are listed at the `POS Hardware page `_)" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:25 +msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:26 +msgid "An Epson compatible cash drawer" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:29 +#: ../../point_of_sale/posbox/index.rst:218 +msgid "Step By Step Setup Guide" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:32 +msgid "Current version of the POSBox (since 2015)" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:36 +msgid "Old version of the POSBox (before 2015)" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:40 +msgid "Connect peripheral devices" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:42 +msgid "Officially supported hardware is listed on `the POS Hardware page `_, but other hardware might work as well." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:46 +msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:49 +msgid "**Cash drawer**: The cash drawer should be connected to the printer with an RJ25 cable." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:52 +msgid "**Barcode scanner**: Connect your barcode scanner. In order for your barcode scanner to be compatible it must behave as a keyboard and must be configured in **US QWERTY**. It also must end barcodes with an Enter character (keycode 28). This is most likely the default configuration of your barcode scanner." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:58 +msgid "**Scale**: Connect your scale and power it on." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:60 +msgid "**Ethernet**: If you do not wish to use Wi-Fi, plug in the Ethernet cable. Make sure this will connect the POSBox to the same network as your POS device." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:64 +msgid "**Wi-Fi**: If you do not wish to use Ethernet, plug in a Linux compatible USB Wi-Fi adapter. Most commercially available Wi-Fi adapters are Linux compatible. Officially supported are Wi-Fi adapters with a Ralink 5370 chipset. Make sure not to plug in an Ethernet cable, because all Wi-Fi functionality will be bypassed when a wired network connection is available." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:72 +msgid "Power the POSBox" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:74 +msgid "Plug the power adapter into the POSBox, a bright red status led should light up." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:78 +msgid "Make sure the POSBox is ready" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:80 +msgid "Once powered, The POSBox needs a while to boot. Once the POSBox is ready, it should print a status receipt with its IP address. Also the status LED, just next to the red power LED, should be permanently lit green." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:86 +#: ../../point_of_sale/posbox/index.rst:297 +msgid "Setup the Point of Sale" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:88 +msgid "To setup the POSBox in the Point of Sale go to :menuselection:`Point of Sale --> Configuration --> Settings` and select your Point of Sale. Scroll down to the ``Hardware Proxy / POSBox`` section and activate the options for the hardware you want to use through the POSBox. Specifying the IP of the POSBox is recommended (it is printed on the receipt that gets printed after booting up the POSBox). When the IP is not specified the Point of Sale will attempt to find it on the local network." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:97 +msgid "If you are running multiple Point of Sales on the same POSBox, make sure that only one of them has Remote Scanning/Barcode Scanner activated." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:100 +msgid "It might be a good idea to make sure the POSBox IP never changes in your network. Refer to your router documentation on how to achieve this." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:105 +msgid "Launch the Point of Sale" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:107 +msgid "If you didn't specify the POSBox's IP address in the configuration, the POS will need some time to perform a network scan to find the POSBox. This is only done once." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:111 +msgid "The Point of Sale is now connected to the POSBox and your hardware should be ready to use." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:115 +msgid "Wi-Fi configuration" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:117 +msgid "The POSBox is Wi-Fi-capable. In order to use it you'll need a Linux compatible USB Wi-Fi adapter. Most commercially available Wi-Fi adapters are Linux compatible. Officially supported are Wi-Fi adapters with a Ralink 5370 chipset." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:122 +msgid "Make sure not to plug in an Ethernet cable, as all Wi-Fi related functionality will be disabled when a wired network connection is available." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:126 +msgid "When the POSBox boots with a Wi-Fi adapter it will start its own Wi-Fi Access Point called \"Posbox\" you can connect to. The receipt that gets printed when the POSBox starts will reflect this. In order to make the POSBox connect to an already existing Wi-Fi network, go to the homepage of the POSBox (indicated on the receipt) and go to the Wi-Fi configuration page. On there you can choose a network to connect to. Note that we only support open and WPA(2)-PSK networks. When connecting to a WPA-secured network, fill in the password field. The POSBox will attempt to connect to the specified network and will print a new POSBox status receipt after it has connected." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:137 +msgid "If you plan on permanently setting up the POSBox with Wi-Fi, you can use the \"persistent\" checkbox on the Wi-Fi configuration page when connecting to a network. This will make the network choice persist across reboots. This means that instead of starting up its own \"Posbox\" network it will always attempt to connect to the specified network after it boots." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:144 +msgid "When the POSBox fails to connect to a network it will fall back to starting it's own \"Posbox\" Access Point. If connection is lost with a Wi-Fi network after connecting to it, the POSBox will attempt to re-establish connection automatically." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:150 +msgid "Multi-POS Configuration" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:152 +msgid "The advised way to setup a multi Point of Sale shop is to have one POSBox per Point of Sale. In this case it is mandatory to manually specify the IP address of each POSBox in each Point of Sale. You must also configure your network to make sure the POSBox's IP addresses don't change. Please refer to your router documentation." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:159 +msgid "POSBoxless Guide (advanced)" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:163 +msgid "If you are running your Point of Sale on a Debian-based Linux distribution, you do not need the POSBox as you can run its software locally. However the installation process is not foolproof. You'll need at least to know how to install and run Odoo. You may also run into issues specific to your distribution or to your particular setup and hardware configuration." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:170 +msgid "Drivers for the various types of supported hardware are provided as Odoo modules. In fact, the POSBox runs an instance of Odoo that the Point of Sale communicates with. The instance of Odoo running on the POSBox is very different from a 'real' Odoo instance however. It does not handle *any* business data (eg. POS orders), but only serves as a gateway between the Point of Sale and the hardware." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:177 +msgid "The goal of this section will be to setup a local Odoo instance that behaves like the Odoo instance running on the POSBox." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:181 +msgid "Image building process" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:183 +msgid "We generate the official POSBox images using the scripts in https://github.com/odoo/odoo/tree/8.0/addons/point_of_sale/tools/posbox. More specifically, we run `posbox_create_image.sh `_. This builds an image called ``posbox.img``, which we zip and upload to `nightly.odoo.com `_ for users to download." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:191 +msgid "The scripts in this directory might be useful as a reference if you get stuck or want more detail about something." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:195 +msgid "Summary of the image creation process" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:197 +msgid "The image creation process starts by downloading the latest `Raspbian `_ image. It then locally mounts this Raspbian image and copies over some files and scripts that will make the Raspbian image turn itself into a POSBox when it boots. These scripts will update Raspbian, remove non-essential packages and install required packages. In order to boot Raspbian we use qemu, which is capable of providing ARM emulation. After this, the emulated Raspbian OS will shut itself down. We then once again locally mount the image, remove the scripts that were used to initialize the image at boot and we copy over some extra configuration files. The resulting image is then ready to be tested and used." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:212 +msgid "A Debian-based Linux distribution (Debian, Ubuntu, Mint, etc.)" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:213 +msgid "A running Odoo instance you connect to to load the Point of Sale" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:214 +msgid "You must uninstall any ESC/POS printer driver as it will conflict with Odoo's built-in driver" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:221 +msgid "Extra dependencies" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:223 +msgid "Because Odoo runs on Python 2, you need to check which version of pip you need to use." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:226 +msgid "``# pip --version``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:228 +#: ../../point_of_sale/posbox/index.rst:234 +msgid "If it returns something like::" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:232 +msgid "You need to try pip2 instead." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:238 +msgid "You can use pip." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:240 +msgid "The driver modules requires the installation of new python modules:" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:242 +msgid "``# pip install pyserial``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:244 +msgid "``# pip install pyusb==1.0.0b1``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:246 +msgid "``# pip install qrcode``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:249 +msgid "Access Rights" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:251 +msgid "The drivers need raw access to the printer and barcode scanner devices. Doing so requires a bit system administration. First we are going to create a group that has access to USB devices" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:255 +msgid "``# groupadd usbusers``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:257 +msgid "Then we add the user who will run the OpenERP server to ``usbusers``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:259 +msgid "``# useradd -G usbusers USERNAME``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:261 +msgid "Then we need to create a udev rule that will automatically allow members of ``usbusers`` to access raw USB devices. To do so create a file called ``99-usbusers.rule`` in the ``/etc/udev/rules.d/`` directory with the following content::" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:269 +msgid "Then you need to reboot your machine." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:272 +msgid "Start the local Odoo instance" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:274 +msgid "We must launch the Odoo server with the correct settings" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:276 +msgid "``$ ./odoo.py --load=web,hw_proxy,hw_posbox_homepage,hw_posbox_upgrade,hw_scale, hw_scanner,hw_escpos``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:279 +msgid "Test the instance" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:281 +msgid "Plug all your hardware to your machine's USB ports, and go to ``http://localhost:8069/hw_proxy/status`` refresh the page a few times and see if all your devices are indicated as *Connected*. Possible source of errors are: The paths on the distribution differ from the paths expected by the drivers, another process has grabbed exclusive access to the devices, the udev rules do not apply or a superseded by others." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:289 +msgid "Automatically start Odoo" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:291 +msgid "You must now make sure that this Odoo install is automatically started after boot. There are various ways to do so, and how to do it depends on your particular setup. Using the init system provided by your distribution is probably the easiest way to accomplish this." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:299 +msgid "The IP address field in the POS configuration must be either ``127.0.0.1`` or ``localhost`` if you're running the created Odoo server on the machine that you'll use as the Point of Sale device. You can also leave it empty." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:305 +msgid "POSBox Technical Documentation" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:308 +msgid "Technical Overview" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:311 +msgid "The POSBox Hardware" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:313 +msgid "The POSBox's Hardware is based on a `Raspberry Pi 2 `_, a popular single-board computer. The Raspberry Pi 2 is powered with a 2A micro-usb power adapter. 2A is needed to give enough power to the barcode scanners. The Software is installed on a 8Gb Class 10 or Higher SD Card. All this hardware is easily available worldwide from independent vendors." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:322 +msgid "Compatible Peripherals" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:324 +msgid "Officially supported hardware is listed on the `POS Hardware page `_." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:328 +msgid "The POSBox Software" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:330 +msgid "The POSBox runs a heavily modified Raspbian Linux installation, a Debian derivative for the Raspberry Pi. It also runs a barebones installation of Odoo which provides the webserver and the drivers. The hardware drivers are implemented as Odoo modules. Those modules are all prefixed with ``hw_*`` and they are the only modules that are running on the POSBox. Odoo is only used for the framework it provides. No business data is processed or stored on the POSBox. The Odoo instance is a shallow git clone of the ``8.0`` branch." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:339 +msgid "The root partition on the POSBox is mounted read-only, ensuring that we don't wear out the SD card by writing to it too much. It also ensures that the filesystem cannot be corrupted by cutting the power to the POSBox. Linux applications expect to be able to write to certain directories though. So we provide a ramdisk for /etc and /var (Raspbian automatically provides one for /tmp). These ramdisks are setup by ``setup_ramdisks.sh``, which we run before all other init scripts by running it in ``/etc/init.d/rcS``. The ramdisks are named /etc_ram and /var_ram respectively. Most data from /etc and /var is copied to these tmpfs ramdisks. In order to restrict the size of the ramdisks, we do not copy over certain things to them (eg. apt related data). We then bind mount them over the original directories. So when an application writes to /etc/foo/bar it's actually writing to /etc_ram/foo/bar. We also bind mount / to /root_bypass_ramdisks to be able to get to the real /etc and /var during development." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:355 +msgid "Logs of the running Odoo server can be found at:" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:357 +msgid "``/var/log/odoo/odoo.log``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:359 +msgid "Various POSBox related scripts (eg. wifi-related scripts) running on the POSBox will log to /var/log/syslog and those messages are tagged with ``posbox_*``." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:364 +msgid "Accessing the POSBox" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:367 +msgid "Local Access" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:369 +msgid "If you plug a QWERTY USB keyboard into one of the POSBox's USB ports, and if you connect a computer monitor to the *HDMI* port of the POSBox, you can use it as a small GNU/Linux computer and perform various administration tasks, like viewing some logs." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:374 +msgid "The POSBox will automatically log in as root on the default tty." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:377 +msgid "Remote Access" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:379 +msgid "If you have the POSBox's IP address and an SSH client you can access the POSBox's system remotely. The login credentials are ``pi``/``raspberry``." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:384 +msgid "Updating The POSBox Software" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:386 +msgid "Only upgrade the POSBox if you experience problems or want to use newly implemented features." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:389 +msgid "The best way to update the POSBox software is to download a new version of the image and flash the SD-Card with it. This operation is described in detail in `this tutorial `_, just replace the standard Raspberry Pi image with the latest one found at `the official POSBox image page `_. This method of upgrading will ensure that you're running the latest version of the POSBox software." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:398 +msgid "The second way of upgrading is through the built in upgrade interface that can be reached through the POSBox homepage. The nice thing about upgrading like this is that you don't have to flash a new image. This upgrade method is limited to what it can do however. It can not eg. update installed configuration files (like eg. /etc/hostapd.conf). It can only upgrade:" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:405 +msgid "The internal Odoo application" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:406 +msgid "Scripts in the folder ``odoo/addons/point_of_sale/tools/posbox/configuration/``" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:408 +msgid "When in doubt, always use the first method of upgrading." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:411 +msgid "Troubleshoot" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:414 +msgid "The POS cannot connect to the POSBox" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:416 +msgid "The easiest way to make sure the POSBox is properly set-up is to turn it on with the printer plugged in as it will print a receipt indicating any error if encountered or the POSBox's IP address in case of success. If no receipt is printed, check the following steps:" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:420 +msgid "Make sure the POSBox is powered on, indicated by a brightly lit red status LED." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:422 +msgid "Make sure the POSBox is ready, this is indicated by a brightly lit green status LED just next to the red power status LED. The POSBox should be ready ~2 minutes after it is started." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:425 +msgid "Make sure the POSBox is connected to the same network as your POS device. Both the device and the POSBox should be visible in the list of connected devices on your network router." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:428 +msgid "Make sure that your LAN is set up with DHCP, and gives IP addresses in the range 192.168.0.X, 192.168.1.X, 10.0.0.X. If you cannot setup your LAN that way, you must manually set up your POSBox's IP address. See the relevant paragraph in the Setup chapter of this documentation." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:433 +msgid "If you have specified the POSBox's IP address in the configuration, make sure it correspond to the printed on the POSBox's status receipt." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:436 +msgid "Make sure that the POS is not loaded over HTTPS." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:437 +msgid "A bug in Firefox's HTTP implementation prevents the autodiscovery from working reliably. When using Firefox you should manually set up the POSBox's IP address in the POS configuration." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:442 +msgid "The Barcode Scanner is not working" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:444 +msgid "The barcode scanner must be configured in US QWERTY and emit an Enter after each barcode. This is the default configuration of most barcode readers. Refer to the barcode reader documentation for more information." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:448 +msgid "The POSBox needs a 2A power supply to work with some barcode scanners. If you are not using the provided power supply, make sure the one you use has enough power." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:451 +msgid "Some barcode scanners will need more than 2A and will not work, or will work unreliably, even with the provided power supply. In those case you can plug the barcode scanner in a self-powered USB hub." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:454 +msgid "Some poorly built barcode scanners do not advertise themselves as barcode scanners but as a usb keyboard instead, and will not be recognized by the POSBox." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:459 +msgid "The Barcode Scanner is not working reliably" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:461 +msgid "Make sure that no more than one device with 'Scan via Proxy'/'Barcode Scanner' enabled are connected to the POSBox at the same time." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:466 +msgid "Printing the receipt takes too much time" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:468 +msgid "A small delay before the first print is expected, as the POSBox will do some preprocessing to speed up the next printings. If you suffer delays afterwards it is most likely due to poor network connection between the POS and the POSBox." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:474 +msgid "Some characters are not correctly printed on the receipt" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:476 +msgid "The POSBox does not support all languages and characters. It currently supports Latin and Cyrillic based scripts, with basic Japanese support." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:481 +msgid "The printer is offline" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:483 +msgid "Make sure the printer is connected, powered, has enough paper and has its lid closed, and is not reporting an error. If the error persists, please contact support." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:488 +msgid "The cashdrawer does not open" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:490 +msgid "The cashdrawer should be connected to the printer and should be activated in the POS configuration." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:494 +msgid "Credits" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:495 +msgid "The POSBox project was developed by Frédéric van der Essen with the kind help of Gary Malherbe, Fabien Meghazi, Nicolas Wisniewsky, Dimitri Del Marmol, Joren Van Onder and Antony Lesuisse." +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:499 +msgid "This development would not have been possible without the Indiegogo campaign and those who contributed to it. Special thanks goes to the partners who backed the campaign with founding partner bundles:" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:503 +msgid "Camptocamp" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:504 +msgid "BHC" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:505 +msgid "openBig" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:506 +msgid "Eeezee-IT" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:507 +msgid "Solarsis LDA" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:508 +msgid "ACSONE" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:509 +msgid "Vauxoo" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:510 +msgid "Ekomurz" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:511 +msgid "Datalp" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:512 +msgid "Dao Systems" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:513 +msgid "Eggs Solutions" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:514 +msgid "OpusVL" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:516 +msgid "And also the partners who've backed the development with the Founding POSBox Bundle:" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:519 +msgid "Willow IT" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:520 +msgid "E\\. Akhalwaya & Sons" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:521 +msgid "Multibase" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:522 +msgid "Mindesa" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:523 +msgid "bpso.biz" +msgstr "" + +#: ../../point_of_sale/posbox/index.rst:524 +msgid "Shine IT." +msgstr "" + diff --git a/locale/sources/purchase.pot b/locale/sources/purchase.pot new file mode 100644 index 000000000..953d7637e --- /dev/null +++ b/locale/sources/purchase.pot @@ -0,0 +1,469 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2015-11-03 11:43+0100\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" + +#: ../../purchase.rst:5 +msgid "Purchase" +msgstr "" + +#: ../../purchase/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../purchase/overview/difference.rst:3 +msgid "Request for Quotation, Purchase Tender or Purchase Order?" +msgstr "" + +#: ../../purchase/overview/difference.rst:5 +msgid "Although they are intimately related, Requests for Quotation, Purchase Tenders and Purchase Orders are not the same." +msgstr "" + +#: ../../purchase/overview/difference.rst:8 +msgid "A **Request for Quotation** (RfQ) is used when you plan to purchase some products and you would like to receive a quote for those products. In Odoo, the Request for Quotation is used to send your list of desired products to your supplier. Once your supplier has answered your request, you can choose to go ahead with the offer and purchase or to turn down the offer." +msgstr "" + +#: ../../purchase/overview/difference.rst:15 +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:5 +msgid "A **Purchase Tender** (PT), also known as Call for Bids, is used to drive competition between several suppliers in order to get the best offer for a list of products. In comparison to the RfQ, a Purchase Tender is sent to multiple suppliers, stating each are competing with one another, and that the best offer will win. The main interest is that it usually leads to better offers." +msgstr "" + +#: ../../purchase/overview/difference.rst:22 +msgid "The **Purchase Order** (PO) is the actual order that you place to the supplier that you chose, either through a RfQ, a Purchase Tender, or simply when you already know which supplier to order from." +msgstr "" + +#: ../../purchase/overview/difference.rst:27 +msgid "When to use?" +msgstr "" + +#: ../../purchase/overview/difference.rst:29 +msgid "A **RfQ** is interesting when you have never purchased the products with that supplier before and therefore don't know their price. It is also useful if you want to challenge your suppliers once you have a well-established relationship with them. You can also use it to assess the cost of a project and see if it makes it feasible." +msgstr "" + +#: ../../purchase/overview/difference.rst:35 +msgid "A **Purchase Tender** is used for public offers that require an open offering from several suppliers. It is also useful when you need to make a one-off order for a product and you would like to get the best offer, no matter which supplier it is. It may be used when your supplier has not been up to your standards and you would like to either push them to deliver a better service, or find a replacement in their competitors." +msgstr "" + +#: ../../purchase/overview/difference.rst:43 +msgid "When not to use?" +msgstr "" + +#: ../../purchase/overview/difference.rst:45 +msgid "**RfQ**\\ s become unnecessary once you have established your favorite supplier for each item, and will only increase the delay in the delivery of your items. In that case, the process will be simpler by starting straight from a Purchase Order." +msgstr "" + +#: ../../purchase/overview/difference.rst:50 +msgid "**Purchase Tenders** are a long and tedious process that will likely take more than several weeks in the best cases. If you need a quick delivery, this is not the way to go. Also, if you have a well-established relationship with one supplier, think twice before you initiate a PT with them as it might tear the relationship and finally lead to less interesting deals." +msgstr "" + +#: ../../purchase/overview/difference.rst:58 +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:39 +msgid "Example" +msgstr "" + +#: ../../purchase/overview/difference.rst:60 +msgid "My company builds wooden furniture. For the new series of table we are designing, we need some screws, metal frames and rubber protections." +msgstr "" + +#: ../../purchase/overview/difference.rst:63 +msgid "I create a Request for Quotation in Odoo with those products to my usual supplier, and send it by email. He answers back with an offer. However, I am not convinced by the offer, and I want to see if anyone can give a better one." +msgstr "" + +#: ../../purchase/overview/difference.rst:68 +msgid "I decide to push competition a bit and set up a Purchase Tender, that Odoo will send to a list of suppliers I specified. Out of the 8 offers I receive, one gets my attention and I decide to go ahead with that one." +msgstr "" + +#: ../../purchase/overview/difference.rst:72 +msgid "I confirm the order to the supplier by creating a Purchase Order from the PT, and Odoo automatically asks delivery of the items to the supplier." +msgstr "" + +#: ../../purchase/overview/difference.rst:77 +#: ../../purchase/purchases/rfq/create.rst:15 +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:15 +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:58 +msgid "Configuration" +msgstr "" + +#: ../../purchase/overview/difference.rst:79 +msgid "If you want to know how to create a **Purchase Order**, read the documentation on :doc:`from_po_to_invoice`" +msgstr "" + +#: ../../purchase/overview/difference.rst:82 +msgid "If you want to know how to create a **RfQ**, read the documentation on :doc:`../purchases/rfq/create`" +msgstr "" + +#: ../../purchase/overview/difference.rst:85 +msgid "If you want to know how to create a **Purchase Tender**, read the documentation on :doc:`../purchases/tender/manage_multiple_offers`" +msgstr "" + +#: ../../purchase/overview/from_po_to_invoice.rst:3 +msgid "From purchase order to invoice and receptions" +msgstr "" + +#: ../../purchase/purchases.rst:3 +msgid "Purchases" +msgstr "" + +#: ../../purchase/purchases/rfq.rst:3 +msgid "Request for Quotatations" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:3 +msgid "How to create a Request for Quotation?" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:5 +msgid "A Request for Quotation (RfQ) is used when you plan to purchase some products and you would like to receive a quote for those products. In Odoo, the Request for Quotation is used to send your list of desired products to your supplier. Once your supplier has answered your request, you can choose to go ahead with the offer and purchase or to turn down the offer." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:12 +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:12 +msgid "For more information on best uses, please read the chapter :doc:`../../overview/difference`" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:18 +msgid "Creating a Request for Quotation" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:20 +msgid "In the Purchases module, open :menuselection:`Purchase --> Requests for Quotation` and click on **Create**." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:26 +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:34 +msgid "View *Request for Quotation* in our Online Demonstration" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:36 +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:50 +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:56 +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:61 +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:67 +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 "" + +#: ../../purchase/purchases/rfq/create.rst:75 +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:131 +msgid ":doc:`../../overview/from_po_to_invoice`" +msgstr "" + +#: ../../purchase/purchases/rfq/subcontracting.rst:3 +msgid "How to manage sub-contracting (purchase of services)?" +msgstr "" + +#: ../../purchase/purchases/tender.rst:3 +msgid "Purchase Tenders" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:3 +msgid "How to manage multiple offers from suppliers with purchase tenders?" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:18 +msgid "Activating the Purchase Tender function" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:20 +msgid "By default, the Purchase Tender is not activated. To be able to use PTs, you must first activate the option." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:23 +msgid "In the Purchases module, open the Configuration menu and click on Settings. In the Purchase Order section, locate the **Calls for Tenders** and tick the box Allow using call for tenders… (advanced), then click on **Apply**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:32 +msgid "Creating a Purchase Tender" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:34 +msgid "To create a new Purchase Tender, open :menuselection:`Purchase --> Purchase Tenders`." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:39 +msgid "In the Purchase Tenders window, click on **Create**. A new Purchase Tenders window opens." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:42 +msgid "By default, Odoo names PTs \"TEXXXXX\" but you can change it as you like." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:47 +msgid "In the **Responsible** field, you can select the person who will be in charge of the PT." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:50 +msgid "In the **Tender Selection Type** menu, you can decide to:" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:52 +msgid "select only one RfQ and automatically cancel all other bid: *Select only one RFQ (exclusive)*" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:54 +msgid "allow multiple purchase orders for this PT: *Select multiple RFQ*" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:56 +msgid "Tick in the box **Multiple RFQ per vendor** if you wish to allow suppliers to send in more than one Request for Quotation." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:62 +msgid "In the **Tender Closing Deadline** field, select the date to bids are closed for suppliers." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:65 +msgid "In the **Scheduled Ordering Date** field, select the date to which you will place the order." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:68 +msgid "In the **Scheduled Date** field, select the date to which the products should be delivered." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:71 +msgid "In the **Source Document** field, you can insert a previous PO to use as a template." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:77 +msgid "In the Products section, click on **Add an item**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:79 +msgid "Select the product in the **Product** list, then insert **Quantity**. You can add as many products as you wish." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:85 +msgid "Click on **Save**, then on **Confirm Call**. Two new RFQs/Bids and Request a Quotation tabs have appeared on the right side of the window." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:91 +msgid "Click on **Request a Quotation** and type in the names of the suppliers you wish to include in the PT, then click on **Create Request for Quotation**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:97 +msgid "A list of suppliers has appeared in the **Requests for Quotation** section." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:103 +msgid "To send the RfQs to your suppliers, click on the green V icon. You can also review the RfQ before sending them by clicking on them." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:106 +msgid "When you receive offers, click on the RFQs/Bids tab. In the list view, select the company and click on **Edit** to adapt the details as stated in the offer." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:113 +msgid "When you have edited all the corresponding fields, click on **Save**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:115 +msgid "When the deadline has been reached, click on **Close Call for Tenders**. The status of the PT is now **Bid Selection**. Open the RFQs/Bids tab and open the RfQ(s) you wish to proceed with." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:122 +msgid "Click on **Approve Order** to convert the RfQ into a Purchase Order, the go back to your PT and click on **Done** to close the PT." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:127 +msgid "View *Purchase Tenders* in our Online Demonstration" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:133 +msgid ":doc:`../../overview/difference`" +msgstr "" + +#: ../../purchase/replenishment.rst:3 +msgid "Replenishment" +msgstr "" + +#: ../../purchase/replenishment/flows.rst:3 +msgid "Replenishment Flows" +msgstr "" + +#: ../../purchase/replenishment/flows/replenishment_methods.rst:3 +msgid "What are the available automated replenishment methods?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:3 +msgid "How to setup a minimum stock rule?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:5 +msgid "For some items you hold in stock, it might be useful to have rules making sure you never run out of stocks (for example, products with a high demand, or large items requiring a lot of storage space meaning they're harder to stock)." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:10 +msgid "Odoo allows you to set up rules so that an automatic replenishment for those items is made, based on minimum stocks available." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:14 +msgid "When should I use Reordering Rules?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:16 +msgid "Reordering Rules work best for items that have a high demand and high flow. It will relieve you from a lot of work to focus on the rest of your activities knowing that stocks will always be right." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:20 +msgid "It can also be used when you have limited storage space and you need to keep large items in stock. In this case, you can keep as little as 1 item in stock, and have a new one ordered as a stock replenishment as soon as the item in stock is sold." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:26 +msgid "When should I avoid Reordering Rules?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:28 +msgid "If you are offering a new product and don't know yet how fast it will go, you should handle stocks yourself first, and setup reordering rules only a few months into the sale to have better forecasts of the demand." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:32 +msgid "If you sell items that have a limited lifetime, such as fashion items, technology items, or products working together with a system that is meant to evolve, you have to be very well informed on when to stop automated replenishments, in order to avoid having to sell these items at a price that will not allow you to break even." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:41 +msgid "My company sells modern furniture. We sell a set of table and chairs that are available in 4 seatings and 6 seatings." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:44 +msgid "To keep things simple, we stock tables and chairs separately, but sell them all together to our clients as a kit. In order to make sure we can always deliver a complete set of table and chairs, I setup a Reordering Rule for the chairs to make sure I always have at least 10 chairs in stock, but no more than 20. This way, I can sell up to 5 sets of table at once while keeping my stock low enough not to eat up all my storage space." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:52 +msgid "The last table I sold was a 4 seatings, and there were 12 chairs left in my stock. Because the stock in chairs is now only 8 chairs, Odoo will automatically order 12 new chairs to fill up my stock to the maximum amount." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:61 +msgid "Set up your product" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:63 +msgid "In the Purchases module, open the Purchase menu and click on Products. Open the product to which you would like to add a Reordering Rule (or create a new one)." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:67 +msgid "3 conditions for correct reordering rule :" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:69 +msgid "In :menuselection:`General information --> Product type`, make the product stockable (as soon as this is done, the icon \"Reordering rule will appear)" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:71 +msgid "In :menuselection:`Inventory --> route`, tick the \"Buy\" box (and untick the Make To Order box)" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:73 +msgid "Select a vendor (don't forget to put a minimal quantity greater than 0)" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:76 +msgid "Create a reordering rule" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:78 +msgid "Click on the Reordering Rules tab, click on Create. A new page opens." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:83 +msgid "By default, Reordering Rules in Odoo are named as \"OP/XXXXX\" but you are free to use any nomenclature. You can modify it via the **Name** field." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:86 +msgid "The **Product** field is the product you are creating the rule for." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:88 +msgid "Select the warehouse to which the product should be delivered in the **Warehouse** field." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:91 +msgid "If you have configured multiple warehouses and location, specify the location in which the product will be stored in the **Location** field." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:96 +msgid ":doc:`../../../inventory/settings/warehouses/difference_warehouse_location`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:102 +msgid "In the **Minimum Quantity** field, insert the quantity to which the system will trigger a new order for replenishment." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:105 +msgid "In the **Maximum Quantity** field, insert the maximum of items that has to be stocked. The replenishing order will be based on that quantity to reorder." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:109 +msgid "The **Quantity Multiple** is the lowest number of items that can be ordered at once. For instance, some items may be only available for purchase in a set of 2." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:113 +msgid "In the Misc section, the **Active** box allows you to activate or deactivate the rule." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:116 +msgid "In the **Lead Time** section, you can enter:" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:118 +msgid "the number of Day(s) to purchase: correspond to the number of days for the supplier to receive the order" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:120 +msgid "the number of Day(s) to get the products" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:122 +msgid "By default, the lead times are in calendar days. You can change that in :menuselection:`Inventory --> Configuration --> Settings --> Minimum Stock Rules`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:125 +msgid "When you have entered all the info, click on Save." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:127 +msgid "From now on, every time a product with a reordering rule reaches the minimum stock, the system will automatically send a RfQ to your supplier based on your maximum quantity to replenish your stock." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:131 +msgid "The replenishments will take place when the scheduler in the Inventory module runs. By default in Odoo, the schedulers will run every night at 12:00PM." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:135 +msgid "To know how to configure and run the schedulers manually, read the document on :doc:`../../../inventory/management/miscellaneous/schedulers`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:140 +msgid ":doc:`replenishment_methods`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:142 +msgid ":doc:`../../../inventory/management/miscellaneous/schedulers`" +msgstr "" + diff --git a/locale/sources/recruitment.pot b/locale/sources/recruitment.pot new file mode 100644 index 000000000..e4dab148c --- /dev/null +++ b/locale/sources/recruitment.pot @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2015-11-03 11:43+0100\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" + +#: ../../recruitment.rst:5 +msgid "Recruitment" +msgstr "" +