From 42c6d3ceaba8b6eeb6ab45a6d5d0fe256c7841f0 Mon Sep 17 00:00:00 2001 From: Odoo Translation Bot Date: Sun, 30 Jul 2023 01:40:23 +0200 Subject: [PATCH] [I18N] Update translation terms from Transifex --- locale/de/LC_MESSAGES/administration.po | 7 +- locale/de/LC_MESSAGES/finance.po | 1274 +- locale/de/LC_MESSAGES/inventory_and_mrp.po | 17 +- locale/de/LC_MESSAGES/marketing.po | 12 +- locale/de/LC_MESSAGES/productivity.po | 4 +- locale/de/LC_MESSAGES/sales.po | 299 +- locale/de/LC_MESSAGES/sphinx.po | 2 +- locale/de/LC_MESSAGES/websites.po | 7 +- locale/es/LC_MESSAGES/administration.po | 6 +- locale/es/LC_MESSAGES/finance.po | 848 +- locale/es/LC_MESSAGES/general.po | 186 +- locale/es/LC_MESSAGES/inventory_and_mrp.po | 452 +- locale/es/LC_MESSAGES/productivity.po | 8 +- locale/es/LC_MESSAGES/sales.po | 274 +- locale/fr/LC_MESSAGES/administration.po | 82 +- locale/fr/LC_MESSAGES/finance.po | 1376 +- locale/fr/LC_MESSAGES/inventory_and_mrp.po | 22 + locale/fr/LC_MESSAGES/sales.po | 334 +- locale/fr/LC_MESSAGES/services.po | 6 + locale/fr/LC_MESSAGES/websites.po | 27 +- locale/nl/LC_MESSAGES/finance.po | 543 +- locale/nl/LC_MESSAGES/settings.po | 12 +- locale/pl/LC_MESSAGES/administration.po | 9669 ++++++ locale/pl/LC_MESSAGES/applications.po | 26 + locale/pl/LC_MESSAGES/finance.po | 29971 +++++++++++++++++++ locale/pl/LC_MESSAGES/general.po | 4616 +++ locale/pl/LC_MESSAGES/index.po | 22 + locale/pl/LC_MESSAGES/inventory_and_mrp.po | 13062 ++++++++ locale/pl/LC_MESSAGES/marketing.po | 4284 +++ locale/pl/LC_MESSAGES/productivity.po | 6275 ++++ locale/pl/LC_MESSAGES/sales.po | 9209 ++++++ locale/pl/LC_MESSAGES/services.po | 1700 ++ locale/pl/LC_MESSAGES/settings.po | 198 + locale/pl/LC_MESSAGES/sphinx.po | 239 + locale/pl/LC_MESSAGES/websites.po | 3313 ++ locale/ro/LC_MESSAGES/finance.po | 554 +- locale/uk/LC_MESSAGES/finance.po | 541 +- locale/zh_CN/LC_MESSAGES/finance.po | 559 +- 38 files changed, 88917 insertions(+), 1119 deletions(-) create mode 100644 locale/pl/LC_MESSAGES/administration.po create mode 100644 locale/pl/LC_MESSAGES/applications.po create mode 100644 locale/pl/LC_MESSAGES/finance.po create mode 100644 locale/pl/LC_MESSAGES/general.po create mode 100644 locale/pl/LC_MESSAGES/index.po create mode 100644 locale/pl/LC_MESSAGES/inventory_and_mrp.po create mode 100644 locale/pl/LC_MESSAGES/marketing.po create mode 100644 locale/pl/LC_MESSAGES/productivity.po create mode 100644 locale/pl/LC_MESSAGES/sales.po create mode 100644 locale/pl/LC_MESSAGES/services.po create mode 100644 locale/pl/LC_MESSAGES/settings.po create mode 100644 locale/pl/LC_MESSAGES/sphinx.po create mode 100644 locale/pl/LC_MESSAGES/websites.po diff --git a/locale/de/LC_MESSAGES/administration.po b/locale/de/LC_MESSAGES/administration.po index 9e4d790c2..1fd4bba30 100644 --- a/locale/de/LC_MESSAGES/administration.po +++ b/locale/de/LC_MESSAGES/administration.po @@ -1195,7 +1195,7 @@ msgstr "" #: ../../content/administration/install/install.rst:6 msgid "Installing Odoo" -msgstr "" +msgstr "Odoo installieren" #: ../../content/administration/install/install.rst:8 msgid "" @@ -2462,6 +2462,11 @@ msgid "" "website with an address such as ``www.example.com`` rather than the default " "``example.odoo.com``." msgstr "" +"Odoo bietet für alle Odoo-Online-Datenbanken ein Jahr lang einen " +":ref:`kostenlosen benutzerdefinierten Domainnamen `. Besucher können dann mit einer Adresse wie ``www.example.com`` " +"auf Ihre Website zugreifen und nicht mit der Standardadresse " +"``example.odoo.com``." #: ../../content/administration/maintain/domain_names.rst:25 msgid "" diff --git a/locale/de/LC_MESSAGES/finance.po b/locale/de/LC_MESSAGES/finance.po index a47ab3515..694e22af6 100644 --- a/locale/de/LC_MESSAGES/finance.po +++ b/locale/de/LC_MESSAGES/finance.po @@ -27,7 +27,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:47+0000\n" "Last-Translator: Larissa Manderfeld, 2023\n" "Language-Team: German (https://app.transifex.com/odoo/teams/41243/de/)\n" @@ -680,7 +680,6 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:18 #: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:16 #: ../../content/applications/finance/accounting/reporting/budget.rst:11 -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:19 #: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 #: ../../content/applications/finance/accounting/taxes.rst:53 #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 @@ -3785,6 +3784,9 @@ msgid "" "**Deferred revenues**, or **unearned revenue**, are payments made in advance" " by customers for products yet to deliver or services yet to render." msgstr "" +"**Passive Rechnungsabgrenzungen** oder **transitorische Passiva** sind " +"Vorauszahlungen von Kunden für Produkte, die noch nicht geliefert oder " +"Dienstleistungen, die noch nicht erbracht wurden." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:8 msgid "" @@ -3793,6 +3795,11 @@ msgid "" "report them on the current **Profit and Loss statement**, or *Income " "Statement*, since the payments will be effectively earned in the future." msgstr "" +"Solche Zahlungen sind eine **Verbindlichkeit** für das Unternehmen, das sie " +"erhält, da es seinen Kunden diese Produkte oder Dienstleistungen noch " +"schuldet. Das Unternehmen kann sie nicht in der aktuellen **Gewinn- und " +"Verlustrechnung** oder der *Erfolgsrechnung* ausweisen, da die Zahlungen " +"erst in der Zukunft effektiv verdient werden." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:12 msgid "" @@ -3800,6 +3807,9 @@ msgid "" "the moment in time they can be **recognized**, at once or over a defined " "period, on the Profit and Loss statement." msgstr "" +"Diese zukünftigen Einnahmen müssen in der Bilanz des Unternehmens so lange " +"abgegrenzt werden, bis sie in der Gewinn- und Verlustrechnung auf einmal " +"oder über einen bestimmten Zeitraum **verbucht** werden können." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:15 msgid "" @@ -3809,6 +3819,11 @@ msgid "" "a yearly basis. Each year, for the next 5 years, $ 70 will be recognized as " "revenue." msgstr "" +"Nehmen wir zum Beispiel an, wir verkaufen eine fünfjährige verlängerte " +"Garantie für 350 €. Wir erhalten das Geld bereits jetzt, haben es aber noch " +"nicht verdient. Daher verbuchen wir diese neuen Einnahmen auf einem Konto " +"für abgegrenzte Einnahmen und beschließen, sie jährlich zu verbuchen. In den" +" nächsten 5 Jahren werden jedes Jahr 70 € als Einnahmen verbucht." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:20 msgid "" @@ -3816,6 +3831,9 @@ msgid "" "entries that are automatically created in *draft mode* and then posted " "periodically." msgstr "" +"Odoo Buchhaltung behandelt abgegrenzte Einnahmen, indem es sie auf mehrere " +"Buchungen verteilt, die automatisch im *Entwurfsmodus* erstellt und dann " +"periodisch gebucht werden." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:24 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:28 @@ -3824,6 +3842,9 @@ msgid "" "The server checks once a day if an entry must be posted. It might then take " "up to 24 hours before you see a change from *draft* to *posted*." msgstr "" +"Der Server prüft einmal am Tag, ob ein Posten gebucht werden muss. Es kann " +"dann bis zu 24 Stunden dauern, bis Sie eine Änderung von *Entwurf* zu " +"*Gestellt* sehen." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:28 #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:20 @@ -3837,10 +3858,13 @@ msgid "" "Such transactions must be posted on a **Deferred Revenue Account** rather " "than on the default income account." msgstr "" +"Solche Transaktionen müssen auf einem **Konto für passive " +"Rechnungsabgrenzung** gebucht werden und nicht auf dem Standard-" +"Ertragskonto." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:34 msgid "Configure a Deferred Revenue Account" -msgstr "" +msgstr "Konto für Passive Rechnungsabgrenzung konfigurieren" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:36 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:40 @@ -3850,62 +3874,76 @@ msgid "" ":menuselection:`Accounting --> Configuration --> Chart of Accounts`, click " "on *Create*, and fill out the form." msgstr "" +"Um Ihr Konto im **Kontenplan** zu konfigurieren, gehen Sie auf " +":menuselection:`Buchhaltung --> Konfiguration --> Kontenplan`, klicken Sie " +"auf *Neu* und füllen Sie das Formular aus." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 msgid "Configuration of a Deferred Revenue Account in Odoo Accounting" msgstr "" +"Konfiguration des Kontos für passive Rechnungsabgrenzung in Odoo Buchhaltung" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:44 msgid "" "This account's type must be either *Current Liabilities* or *Non-current " "Liabilities*" msgstr "" +"Der Typ dieses Kontos muss entweder *Kurzfristige Verbindlichkeiten* oder " +"*Langfristige Verbindlichkeiten*" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:47 msgid "Post an income to the right account" -msgstr "" +msgstr "Ein Einkommen im richtigen Konto buchen" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:50 msgid "Select the account on a draft invoice" -msgstr "" +msgstr "Das Konto aus einem Rechnungsentwurf auswählen" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:52 msgid "" "On a draft invoice, select the right account for all the products of which " "the incomes must be deferred." msgstr "" +"Wählen Sie auf einem Rechnungsentwurf das richtige Konto für alle Produkte, " +"deren Einnahmen abgegrenzt werden müssen." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 msgid "" "Selection of a Deferred Revenue Account on a draft invoice in Odoo " "Accounting" msgstr "" +"Auswahl des Kontos für passive Rechnungsabgrenzung auf einem " +"Rechnungsentwurf in Odoo Buchhaltung" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:60 msgid "Choose a different Income Account for specific products" -msgstr "" +msgstr "Für bestimmte Produkte ein anderes Ertragskonto auswählen" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:62 msgid "" "Start editing the product, go to the *Accounting* tab, select the right " "**Income Account**, and save." msgstr "" +"Beginnen Sie mit der Bearbeitung des Produkts, gehen Sie auf den Reiter " +"*Buchhaltung*, wählen Sie das richtige **Ertragskonto** und speichern Sie." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 msgid "Change of the Income Account for a product in Odoo" -msgstr "" +msgstr "Änderung des Etragskontos für ein Produkt in Odoo" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:70 msgid "" "It is possible to automate the creation of revenue entries for these " "products (see: `Automate the Deferred Revenues`_)." msgstr "" +"Es ist möglich, die Erstellung von Ertragsbuchungen für diese Produkte zu " +"automatisieren (siehe: `Passive Rechnungsabgrenzung automatisieren`_)." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:74 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:81 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:75 msgid "Change the account of a posted journal item" -msgstr "" +msgstr "Das Konto einer gebuchten Buchungszeile ändern" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:76 msgid "" @@ -3913,16 +3951,21 @@ msgid "" " Accounting --> Sales`, select the journal item you want to modify, click on" " the account, and select the right one." msgstr "" +"Öffnen Sie dazu Ihr Verkaufsjournal, indem Sie zu " +":menuselection:`Buchhaltung --> Buchhaltung --> Verkäufe` gehen, die " +"Buchungszeile auswählen, die Sie ändern möchten, auf das Konto klicken und " +"das richtige Konto auswählen." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 msgid "Modification of a posted journal item's account in Odoo Accounting" msgstr "" +"Bearbeitung des Kontos einer gebuchten Buchungszeile in Odoo Buchhaltung" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:85 msgid "Deferred Revenues entries" -msgstr "" +msgstr "Passive Rechnungsabgrenzungsposten" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:88 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:97 @@ -3936,12 +3979,19 @@ msgid "" " *draft mode*. They are then posted one by one at the right time until the " "full amount of the income is recognized." msgstr "" +"Einen **Passiven Rechnungsabgrenzungsposten** erzeugt automatisch alle " +"Journalbuchungen im *Entwurfsmodus*. Sie werden dann eine nach der anderen " +"zum richtigen Zeitpunkt gebucht, bis der volle Betrag der Einnahmen verbucht" +" ist." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:93 msgid "" "To create a new entry, go to :menuselection:`Accounting --> Accounting --> " "Deferred Revenues`, click on *Create*, and fill out the form." msgstr "" +"Um eine neue Buchung zu erstellen, gehen Sie auf :menuselection:`Buchhaltung" +" --> Buchhaltung --> Passive Rechnungsabgrenzung`, klicken Sie auf *Neu* und" +" füllen Sie das Formular aus." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:96 msgid "" @@ -3949,10 +3999,14 @@ msgid "" "this new entry. Some fields are then automatically filled out, and the " "journal item is now listed under the **Related Sales** tab." msgstr "" +"Klicken Sie auf **Zugehörige Einkäufe auswählen**, um eine bestehende " +"Buchungszeile mit diesem neuen Posten zu verknüpfen. Einige Felder werden " +"dann automatisch ausgefüllt, und die Buchungszeile wird nun im Reiter " +"**Zugehörige Einkäufe** aufgeführt." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 msgid "Deferred Revenue entry in Odoo Accounting" -msgstr "" +msgstr "Passiver Rechnungsabgrenzungsposten in Odoo Buchhaltung" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:104 msgid "" @@ -3961,22 +4015,28 @@ msgid "" "all the entries that Odoo will post to recognize your revenue, and at which " "date." msgstr "" +"Sobald dies geschehen ist, können Sie auf *Ertrag berechnen* (neben der " +"Schaltfläche *Bestätigen*) klicken, um alle Werte der **Ertragsübersicht** " +"zu generieren. Diese Tabelle zeigt Ihnen alle Buchungen, die Odoo zur " +"Erkennung Ihres Ertrags vornehmen wird, und zwar zu welchem Datum." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 msgid "Revenue Board in Odoo Accounting" -msgstr "" +msgstr "Ertragsübersicht in Odoo Buchhaltung" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:113 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:122 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:114 msgid "What does \"Prorata Temporis\" mean?" -msgstr "" +msgstr "Was bedeutet „Prorata Temporis“?" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:115 msgid "" "The **Prorata Temporis** feature is useful to recognize your revenue the " "most accurately possible." msgstr "" +"Die Funktion **Prorata Temporis** ist nützlich, um Ihre Einnahmen so genau " +"wie möglich zu erfassen." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:117 msgid "" @@ -3984,6 +4044,10 @@ msgid "" " the time left between the *Prorata Date* and the *First Recognition Date* " "rather than the default amount of time between recognitions." msgstr "" +"Mit dieser Funktion wird die erste Buchung in der Ertragsübersicht auf der " +"Grundlage der Zeit berechnet, die zwischen dem *Pro-Rata-Datum* und dem " +"*Erstes Realisierungsdatum* verbleibt, anstatt der Standardzeitspanne " +"zwischen den Erfassungen." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:121 msgid "" @@ -3991,16 +4055,21 @@ msgid "" " $ 4.22 rather than $ 70.00. Consequently, the last entry is also lower and " "has an amount of $ 65.78." msgstr "" +"Zum Beispiel hat die obige Ertragsübersicht ihre erste Einnahme mit einem " +"Betrag von 4,22 € und nicht 70,00 €. Folglich ist auch die letzte Buchung " +"niedriger und hat einen Betrag von 65,78 €." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:125 msgid "Deferred Entry from the Sales Journal" -msgstr "" +msgstr "Rechnungsabgrenzungsposten aus dem Verkaufsjournal" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:127 msgid "" "You can create a deferred entry from a specific journal item in your **Sales" " Journal**." msgstr "" +"Sie können aus einer bestimmten Buchungszeilen in Ihrem **Verkaufsjournal** " +"einen Rechnungsabgrenzungsposten erstellen." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:129 msgid "" @@ -4009,6 +4078,11 @@ msgid "" "sure that it is posted in the right account (see: `Change the account of a " "posted journal item`_)." msgstr "" +"Öffnen Sie dazu Ihr Verkaufsjournal, indem Sie zu " +":menuselection:`Buchhaltung --> Buchhaltung --> Verkauf` gehen, und wählen " +"Sie die Buchungszeile aus, die Sie abgrenzen möchten. Vergewissern Sie sich," +" dass sie auf dem richtigen Konto gebucht ist (siehe: `Das Konto einer " +"gebuchten Buchungszeile ändern`)." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:134 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:134 @@ -4016,11 +4090,16 @@ msgid "" "Then, click on *Action*, select **Create Deferred Entry**, and fill out the " "form the same way you would do to `create a new entry`_." msgstr "" +"Klicken Sie dann auf *Aktion*, wählen Sie **Rechnungsaufgrenzungsposten " +"erstellen** und füllen Sie das Formular genauso aus, wie Sie es bei der " +"Erstellung einer neuen Buchung tun würden." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 msgid "Create Deferred Entry from a journal item in Odoo Accounting" msgstr "" +"Rechungsabgrenzungsposten aus einer Buchungszeile in Odoo Buchhaltung " +"erstellen" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:142 msgid "Deferred Revenue Models" @@ -4031,6 +4110,8 @@ msgid "" "You can create **Deferred Revenue Models** to create your Deferred Revenue " "entries faster." msgstr "" +"Sie können **Modelle für Passive Rechnungsabgrenzung** erstellen, um passive" +" Rechnungsabgrenzungsposten schneller zu erfassen." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:146 msgid "" @@ -4038,6 +4119,10 @@ msgid "" "Deferred Revenue Models`, click on *Create*, and fill out the form the same " "way you would do to create a new entry." msgstr "" +"Um ein Modell zu erstellen, gehen Sie auf :menuselection:`Buchhaltung --> " +"Konfiguration --> Modelle für Passive Rechnungsabgrenzung`, klicken Sie auf " +"*Neu* und füllen Sie das Formular genauso aus, wie Sie es für eine neue " +"Buchung tun würden." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:150 msgid "" @@ -4045,16 +4130,24 @@ msgid "" "opening it from :menuselection:`Accounting --> Accounting --> Deferred " "Revenues` and then, by clicking on the button *Save Model*." msgstr "" +"Sie können einen *bestätigten passiven Rechnungsabgrenzungsposten* auch in " +"ein Modell umwandeln, indem Sie ihn über :menuselection:`Buchhaltung --> " +"Buchhaltung --> Passive Rechnungsabgrenzung` öffnen und dann auf die " +"Schaltfläche *Modell speichern* klicken." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:155 msgid "Apply a Deferred Revenue Model to a new entry" msgstr "" +"Ein Modell für Passive Rechnungsabgrenzung auf eine neue Buchung anwenden" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:157 msgid "" "When you create a new Deferred Revenue entry, fill out the **Deferred " "Revenue Account** with the right recognition account." msgstr "" +"Wenn Sie einen neuen passiven Rechnungsabgrenzungsposten erstellen, füllen " +"Sie das Feld **Konto für Passive Rechnungsabgrenzung** mit dem richtigen " +"Buchungskonto aus." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:160 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:222 @@ -4064,10 +4157,15 @@ msgid "" "the form. Clicking on a model button fills out the form according to that " "model." msgstr "" +"Neue Schaltflächen mit allen Modellen, die mit diesem Konto verknüpft sind, " +"erscheinen am oberen Rand des Formulars. Wenn Sie auf eine Modell-" +"Schaltfläche klicken, wird das Formular entsprechend diesem Modell " +"ausgefüllt." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 msgid "Deferred Revenue model button in Odoo Accounting" msgstr "" +"Schaltfläche für Modell für Passive Rechnungsabgrenzung in Odoo Buchhaltung" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:170 msgid "Automate the Deferred Revenues" @@ -4079,16 +4177,22 @@ msgid "" "Liabilities* or *Non-current Liabilities*, you can configure it to defer the" " revenues that are credited on it automatically." msgstr "" +"Wenn Sie ein Konto erstellen oder bearbeiten, dessen Typ entweder " +"*Kurzfristige Verbindlichkeiten* oder *Langfristige Verbindlichkeiten* ist, " +"können Sie es so konfigurieren, dass die Einnahmen, die darauf " +"gutgeschrieben werden, automatisch verschoben werden." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:175 msgid "You have three choices for the **Automate Deferred Revenue** field:" msgstr "" +"Sie haben drei Möglichkeiten für das Feld **Automatische " +"Rechnungsabgrenzung**:" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:177 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:240 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:177 msgid "**No:** this is the default value. Nothing happens." -msgstr "" +msgstr "**Nein:** Dies ist der Standardwert. Nichts passiert." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:178 msgid "" @@ -4097,6 +4201,11 @@ msgid "" "first fill out the form in :menuselection:`Accounting --> Accounting --> " "Deferred Revenues`." msgstr "" +"**Als Entwurf erstellen:** Jedes Mal, wenn eine Transaktion auf dem Konto " +"gebucht wird, wird ein Entwurf der Buchung *Passiver " +"Rechnungsabgrenzungsposten* erstellt, aber nicht validiert. Sie müssen " +"zunächst das Formular in :menuselection:`Buchhaltung --> Buchhaltung --> " +"Passive Rechnungsabgrenzung` ausfüllen." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:181 msgid "" @@ -4104,10 +4213,17 @@ msgid "" " `Deferred Revenue Models`_). Whenever a transaction is posted on the " "account, a *Deferred Revenues entry* is created and immediately validated." msgstr "" +"**Erstellen und validieren:** müssen Sie auch ein Modell für Passive " +"Rechnungsabgrenzung auswählen (siehe: `Modelle für Passive " +"Rechnungsabgrenzung`_). Immer, wenn eine Transaktion auf dem Konto gebucht " +"wird, wird ein *Passiver Rechnungsabgrenzungsposten* erstellt und sofort " +"validiert." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 msgid "Automate Deferred Revenue on an account in Odoo Accounting" msgstr "" +"Passive Rechnungsabgrenzung auf einem Konto in Odoo Buchhaltung " +"automatisieren" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:190 msgid "" @@ -4115,22 +4231,28 @@ msgid "" "of a product to fully automate its sale. (see: `Choose a different Income " "Account for specific products`_)." msgstr "" +"Sie können dieses Konto z. B. als Standard-**Ertragskonto** für ein Produkt " +"auswählen, um dessen Verkauf vollständig zu automatisieren. (siehe: `Ein " +"anderes Ertragskonto für bestimmte Produkte auswählen`_)." #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:194 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:256 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:195 msgid ":doc:`../get_started/chart_of_accounts`" -msgstr "" +msgstr ":doc:`../get_started/chart_of_accounts`" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:195 msgid "" "`Odoo Academy: Deferred Revenues (Recognition) " "`_" msgstr "" +"`Odoo-Akademie: Passive Rechnungsabgrenzung (Realisierung) " +"`_" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:3 msgid "Electronic invoicing (:abbr:`EDI (electronic data interchange)`)" msgstr "" +"Elektronische Rechnungsstellung (:abbr:`EDI (electronic data interchange)`)" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:5 msgid "" @@ -4141,6 +4263,13 @@ msgid "" "Various EDI file formats exist and are available depending on your company's" " country." msgstr "" +"EDI, oder elektronischer Datenaustausch, ist die unternehmensübergreifende " +"Kommunikation von Geschäftsdokumenten, wie z. B. Bestellungen und " +"Rechnungen, in einem Standardformat. Das Versenden von Dokumenten gemäß " +"einem EDI-Standard stellt sicher, dass das Gerät, das die Nachricht " +"empfängt, die Informationen richtig interpretieren kann. Es gibt " +"verschiedene EDI-Dateiformate, die je nach Land Ihres Unternehmens verfügbar" +" sind." #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:10 msgid "" @@ -4148,16 +4277,21 @@ msgid "" "might also be required by some governments for fiscal control or to " "facilitate the administration." msgstr "" +"Die EDI-Funktion ermöglicht die Automatisierung der Verwaltung zwischen " +"Unternehmen und kann auch von einigen Regierungen zur Steuerkontrolle oder " +"zur Erleichterung der Verwaltung verlangt werden." #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:13 msgid "" "Electronic invoicing of your documents such as customer invoices, credit " "notes or vendor bills is one of the application of EDI." msgstr "" +"Die elektronische Rechnungsstellung für Ihre Dokumente wie Kundenrechnungen," +" Gutschriften oder Lieferantenrechnungen ist eine der Anwendungen von EDI." #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:16 msgid "Odoo supports, among others, the following formats." -msgstr "" +msgstr "Odoo unterstützt unter anderem folgende Formate." #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:21 msgid "Format Name" @@ -4177,101 +4311,103 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:25 msgid "Peppol BIS Billing 3.0 (UBL)" -msgstr "" +msgstr "Peppol BIS Billing 3.0 (UBL)" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:26 msgid "" "For companies whose countries are part of the `EAS list " "`_" msgstr "" +"Für Unternehmen, dessen Land auf der `EAS-Liste " +"`_ steht" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:28 msgid "E-FFF" -msgstr "" +msgstr "E-FFF" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:29 msgid "For Belgian companies" -msgstr "" +msgstr "Für belgische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:30 msgid "XRechnung (UBL)" -msgstr "" +msgstr "XRechnung (UBL)" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:31 msgid "For German companies" -msgstr "" +msgstr "Für deutsche Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:32 msgid "Fattura PA (IT)" -msgstr "" +msgstr "Fattura PA (IT)" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:33 msgid "For Italian companies" -msgstr "" +msgstr "Für italienische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:34 msgid "CFDI (4.0)" -msgstr "" +msgstr "CFDI (4.0)" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:35 msgid "For Mexican companies" -msgstr "" +msgstr "Für mexikanische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:36 msgid "Peru UBL 2.1" -msgstr "" +msgstr "Peru UBL 2.1" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:37 msgid "For Peruvian companies" -msgstr "" +msgstr "Für peruanische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:38 msgid "SII IVA Llevanza de libros registro (ES)" -msgstr "" +msgstr "SII IVA Llevanza de libros registro (ES)" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:39 msgid "For Spanish companies" -msgstr "" +msgstr "Für spanische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:40 msgid "UBL 2.1 (Columbia)" -msgstr "" +msgstr "UBL 2.1 (Columbia)" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:41 msgid "For Colombian companies" -msgstr "" +msgstr "Für kolumbianische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:42 msgid "Egyptian Tax Authority" -msgstr "" +msgstr "Egyptian Tax Authority" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:43 msgid "For Egyptian companies" -msgstr "" +msgstr "Für ägyptische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:44 msgid "E-Invoice (IN)" -msgstr "" +msgstr "E-Invoice (IN)" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:45 msgid "For Indian companies" -msgstr "" +msgstr "Für indiische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:46 msgid "NLCIUS (Netherlands)" -msgstr "" +msgstr "NLCIUS (Netherlands)" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:47 msgid "For Dutch companies" -msgstr "" +msgstr "Für niederländische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:48 msgid "EHF 3.0" -msgstr "" +msgstr "EHF 3.0" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:49 msgid "For Norwegian companies" -msgstr "" +msgstr "Für norwegische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:50 msgid "SG BIS Billing 3.0" @@ -4279,11 +4415,11 @@ msgstr "SG BIS Billing 3.0" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:51 msgid "For Singaporean companies" -msgstr "" +msgstr "Für singapurische Unternehmen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:54 msgid ":ref:`fiscal_localizations/packages`" -msgstr "" +msgstr ":ref:`fiscal_localizations/packages`" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:61 msgid "" @@ -4291,10 +4427,14 @@ msgid "" " Invoices --> Advanced Settings --> Electronic Invoicing` and enable the " "formats you need for this journal." msgstr "" +"Gehen Sie auf :menuselection:`Buchhaltung --> Konfiguration --> Journale -->" +" Kundenrechnungen --> Erweiterte Einstellungen --> Elektronische " +"Rechnungsstellung` und aktivieren Sie die Formate, die Sie für dieses " +"Journal benötigen." #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 msgid "Select the EDI format you need" -msgstr "" +msgstr "Das von Ihnen benötigte EDI-Format auswählen" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:68 msgid "" @@ -4303,6 +4443,10 @@ msgid "" "notes, etc. These documents are either visible in the attachment section, or" " embedded in the PDF." msgstr "" +"Sobald ein elektronisches Rechnungsformat aktiviert ist, werden XML-" +"Dokumente erzeugt, wenn Sie in Dokumenten wie Rechnungen, Gutschriften usw. " +"auf :guilabel:`Bestätigen` klicken. Diese Dokumente sind entweder im " +"Anhangsbereich sichtbar oder in die PDF-Datei eingebettet." #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:73 msgid "" @@ -4310,6 +4454,9 @@ msgid "" "(:guilabel:`Print` or :guilabel:`Send & Print` button), since the PDF needs " "to be embedded inside the xml." msgstr "" +"Bei E-FFF erscheint die xml-Datei erst nach der Erstellung der PDF-Datei " +"(:guilabel:`Drucken` oder :guilabel:`Senden & Drucken`), da die PDF-Datei in" +" die xml-Datei eingebettet werden muss." #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:75 msgid "" @@ -4322,12 +4469,16 @@ msgid "" "The formats available depend on the country registered in your company's " ":guilabel:`General Information`." msgstr "" +"Die verfügbaren Formate hängen von dem Land ab, das in den " +":guilabel:`Allgemeine Informationen` Ihres Unternehmens registriert ist." #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:79 msgid "" "Odoo supports the **Peppol BIS Billing 3.0** format that can be used via " "existing access points." msgstr "" +"Odoo unterstützt das Format **Peppol BIS Billing 3.0**, das über bestehende " +"Zugriffspunkte verwendet werden kann." #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:83 msgid "Add new formats to a database created before July 2022" @@ -4400,7 +4551,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:3 msgid "EPC QR codes" -msgstr "" +msgstr "EPC-QR-Codes" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:5 msgid "" @@ -4409,29 +4560,39 @@ msgid "" " applications** to initiate a **SEPA credit transfer (SCT)** and pay their " "invoices instantly." msgstr "" +"QR-Code für den Europäischen Zahlungsraums (European Payments Council Quick " +"Response Codes) oder **EPC-QR-Codes** sind zweidimensionale Barcodes, die " +"Kunden mit ihren **Mobile-Banking-Apps** scannen können, um eine **SEPA-" +"Überweisung (SCT)** zu initiieren und ihre Rechnungen sofort zu bezahlen." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:9 msgid "" "In addition to bringing ease of use and speed, it greatly reduces typing " "errors that would potentially make for payment issues." msgstr "" +"Das System ist nicht nur benutzerfreundlich und schnell, sondern reduziert " +"auch Tippfehler, die zu Zahlungsproblemen führen könnten, erheblich." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:13 msgid "" "This feature is only available for companies in several European countries " "such as Austria, Belgium, Finland, Germany, and the Netherlands." msgstr "" +"Diese Funktion ist nur für Unternehmen in einigen europäischen Ländern wie " +"Österreich, Belgien, Finnland, Deutschland und den Niederlanden verfügbar." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:17 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:122 msgid ":doc:`../bank`" -msgstr "" +msgstr ":doc:`../bank`" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:18 msgid "" "`Odoo Academy: QR Code on Invoices for European Customers " "`_" msgstr "" +"`Odoo-Akademie: QR-Code aus Rechnungen für europäische Kunden " +"`_" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:23 msgid "" @@ -4439,16 +4600,21 @@ msgid "" "activate the :guilabel:`QR Codes` feature in the :guilabel:`Customer " "Payments` section." msgstr "" +"Gehen Sie auf :menuselection:`Buchhaltung --> Konfiguration --> " +"Einstellungen` und aktivieren Sie die Funktion :guilabel:`QR-Codes` im " +"Abschnitt :guilabel:`Kundenzahlungen`." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:27 msgid "Configure your bank account's journal" -msgstr "" +msgstr "Das Journal Ihres Bankkontos konfigurieren" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:29 msgid "" "Make sure that your :guilabel:`Bank Account` is correctly configured in Odoo" " with your IBAN and BIC." msgstr "" +"Stellen Sie sicher, dass Ihr :guilabel:`Bankkonto` korrekt in Odoo mit Ihrer" +" IBAN und BIC konfiguriert ist." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:31 msgid "" @@ -4456,14 +4622,18 @@ msgid "" "open your bank journal, then fill out the :guilabel:`Account Number` and " ":guilabel:`Bank` under the :guilabel:`Bank Account Number` column." msgstr "" +"Gehen Sie dazu auf :menuselection:`Buchhaltung --> Konfiguration --> " +"Journale`, öffnen Sie Ihr Bankjournal, füllen Sie die " +":guilabel:`Kontonummer` und :guilabel:`Bank` in der Spalte " +":guilabel:`Bankkontonummer` aus." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst-1 msgid "Bank account number column in the bank journal" -msgstr "" +msgstr "Spalte der Bankkontonummer im Bankjournal" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:39 msgid "Issue invoices with EPC QR codes" -msgstr "" +msgstr "Rechnungen mit EPC-QR-Codes ausstellen" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:41 msgid "" @@ -4471,18 +4641,26 @@ msgid "" "supports making payments via EPC QR codes will be able to scan the code and " "pay the invoice." msgstr "" +"EPC QR-Codes werden automatisch zu Ihren Rechnungen hinzugefügt. Kunden, " +"deren Bank Zahlungen über EPC-QR-Codes unterstützt, können den Code scannen " +"und die Rechnung bezahlen." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:44 msgid "" "Go to :menuselection:`Accounting --> Customers --> Invoices`, and create a " "new invoice." msgstr "" +"Gehen Sie auf :menuselection:`Buchhaltung --> Kunden --> Rechnungen` und " +"erstellen Sie eine neue Rechnungen." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:46 msgid "" "Before posting it, open the :guilabel:`Other Info` tab. Odoo automatically " "fills out the :guilabel:`Recipient Bank` field with your IBAN." msgstr "" +"Öffnen Sie vor der Buchung den Reiter :guilabel:`Weitere Informationen`. " +"Odoo füllt das Feld :guilabel:`Empfängerbank` automatisch mit Ihrer IBAN " +"aus." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:50 msgid "" @@ -4491,16 +4669,22 @@ msgid "" " Odoo automatically populates this field with your IBAN by default and uses " "it to generate the EPC QR code." msgstr "" +"Im Reiter :guilabel:`Weitere Informationen` wird das im Feld " +":guilabel:`Empfängerbank` angegebene Konto für den Zahlungseingang Ihres " +"Kunden verwendet. Odoo füllt dieses Feld standardmäßig automatisch mit Ihrer" +" IBAN aus und verwendet es, um den EPC QR-Code zu generieren." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:54 msgid "" "When the invoice is printed or previewed, the QR code is included at the " "bottom." msgstr "" +"Wenn die Rechnung gedruckt oder als Vorschau angezeigt wird, wird der QR-" +"Code unten eingefügt." #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst-1 msgid "QR code on a customer invoice" -msgstr "" +msgstr "QR-Code auf einer Kundenrechnung" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:60 msgid "" @@ -4508,10 +4692,13 @@ msgid "" "indicated in the :guilabel:`Recipient Bank` field, under the " ":guilabel:`Other Info` tab of the invoice." msgstr "" +"Wenn Sie eine Rechnung ohne einen EPC-QR-Code ausstellen möchten, entfernen " +"Sie die IBAN, die im Feld :guilabel:`Empfängerbank` im Reiter " +":guilabel:`Weitere Informationen` der Rechnung angegeben ist." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:3 msgid "Invoicing processes" -msgstr "" +msgstr "Abrechnungsverfahren" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:5 msgid "" @@ -4522,16 +4709,24 @@ msgid "" "validate draft invoices and send the invoices in batch (by regular mail or " "email)." msgstr "" +"Je nach Ihrem Betrieb und der von Ihnen verwendeten App gibt es verschiedene" +" Möglichkeiten, die Erstellung von Kundenrechnungen in Odoo zu " +"automatisieren. Normalerweise werden Rechnungsentwürfe vom System erstellt " +"(mit Informationen aus anderen Dokumenten wie Verkaufsaufträgen oder " +"Verträgen), und der Buchhalter muss die Rechnungsentwürfe nur noch " +"validieren und die Rechnungen im Stapel versenden (per Post oder E-Mail)." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:12 msgid "" "Depending on your business, you may opt for one of the following way to " "create draft invoices:" msgstr "" +"Je nach Ihrem Betrieb können Sie sich für eine der folgenden Möglichkeiten " +"entscheiden, um Rechnungsentwürfe zu erstellen:" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:19 msgid "Sales Order ‣ Invoice" -msgstr "" +msgstr "Verkaufsauftrag ‣ Rechnung" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:21 msgid "" @@ -4539,28 +4734,39 @@ msgid "" "once they are validated. Then, draft invoices are created based on the sales" " order. You have different options like:" msgstr "" +"In den meisten Unternehmen erstellen die Vertriebsmitarbeiter Angebote, die " +"nach ihrer Validierung zu Verkaufsaufträgen werden. Anschließend werden auf " +"der Grundlage des Verkaufsauftrags Rechnungsentwürfe erstellt. Sie haben " +"verschiedene Optionen wie:" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:25 msgid "" "Invoice manually: use a button on the sale order to trigger the draft " "invoice" msgstr "" +"Manuell abrechnen: Verwenden Sie eine Schaltfläche auf dem Verkaufsauftrag, " +"um einen Rechnungsentwurf zu erstellen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:28 msgid "" "Invoice before delivery: invoice the full order before triggering the " "delivery order" msgstr "" +"Vor Lieferung abrechnen: Stellen Sie den gesamten Auftrag in Rechnung, bevor" +" Sie den Lieferauftrag erstellen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:31 msgid "Invoice based on delivery order: see next section" -msgstr "" +msgstr "Auf Grundlage eines Lieferauftrags: siehe nächsten Abschnitt" #: ../../content/applications/finance/accounting/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 "" +"Rechnung vor Lieferung wird in der Regel von der E-Commerce-App verwendet, " +"wenn der Kunde bei der Bestellung bezahlt und wir anschließend liefern. " +"(vorausbezahlt)" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:37 msgid "" @@ -4569,18 +4775,25 @@ msgid "" "whole order, invoice a percentage (advance), invoice some lines, invoice a " "fixed advance." msgstr "" +"Für die meisten anderen Anwendungsfälle empfiehlt es sich, die Rechnung " +"manuell zu erstellen. Es ermöglicht dem Vertriebsmitarbeiter, die Rechnung " +"bei Bedarf auszulösen, mit den Optionen: den gesamten Auftrag abrechnen, " +"einen Prozentsatz (Vorauszahlung) abrechnen, einige Zeilen abrechnen, eine " +"feste Vorauszahlung abrechnen." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:42 msgid "This process is good for both services and physical products." msgstr "" +"Dieser Prozess ist sowohl für Dienstleistungen als auch für physische " +"Produkte geeignet." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:45 msgid ":doc:`/applications/sales/sales/invoicing/proforma`" -msgstr "" +msgstr ":doc:`/applications/sales/sales/invoicing/proforma`" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:48 msgid "Sales Order ‣ Delivery Order ‣ Invoice" -msgstr "" +msgstr "Verkaufauftrag ‣ Lieferauftrag ‣ Rechnung" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:50 msgid "" @@ -4589,6 +4802,11 @@ msgid "" "you deliver may differs from the ordered quantities: foods (invoice based on" " actual Kg)." msgstr "" +"Einzelhändler und E-Commerce fakturieren in der Regel auf der Grundlage von " +"Lieferaufträgen und nicht auf der Grundlage von Verkaufsaufträgen. Dieser " +"Ansatz eignet sich für Unternehmen, bei denen die von Ihnen gelieferten " +"Mengen von den bestellten Mengen abweichen können: Lebensmittel (Rechnung " +"auf Basis der tatsächlichen Kilos)." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:55 msgid "" @@ -4596,14 +4814,18 @@ msgid "" "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 "" +"Auf diese Weise stellen Sie bei einer Teillieferung nur das in Rechnung, was" +" Sie wirklich geliefert haben. Wenn Sie Nachbestellungen machen (einen Teil " +"liefern und den Rest später), erhält der Kunde zwei Rechnungen, eine für " +"jeden Lieferauftrag." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:61 msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" -msgstr "" +msgstr ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:64 msgid "eCommerce Order ‣ Invoice" -msgstr "" +msgstr "E-Commerce-Auftrag ‣ Rechnung" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:66 msgid "" @@ -4612,6 +4834,11 @@ msgid "" "creates an order and the invoice will be triggered once the payment is " "received." msgstr "" +"Bei einer E-Commerce-Bestellung wird die Erstellung der Bestellung ebenfalls" +" ausgelöst, wenn sie vollständig bezahlt ist. Wenn Sie die Bezahlung von " +"Bestellungen per Scheck oder Überweisung zulassen, erstellt Odoo nur eine " +"Bestellung und die Rechnung wird ausgelöst, sobald die Zahlung eingegangen " +"ist." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:72 msgid "Contracts" @@ -4619,7 +4846,7 @@ msgstr "Verträge" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:75 msgid "Regular Contracts ‣ Invoices" -msgstr "" +msgstr "Reguläre Verträge ‣ Rechnungen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:77 msgid "" @@ -4627,28 +4854,39 @@ msgid "" "spent, expenses or fixed lines of services/products. Every month, the " "salesperson will trigger invoice based on activities on the contract." msgstr "" +"Wenn Sie mit Verträgen arbeiten, können Sie Rechnungen auf der Grundlage von" +" Zeit- und Materialaufwand, Ausgaben oder festen Zeilen von " +"Dienstleistungen/Produkten auslösen. Jeden Monat wird der " +"Vertriebsmitarbeiter die Rechnung auf der Grundlage der Aktivitäten im " +"Vertrag auslösen." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:81 msgid "Activities can be:" -msgstr "" +msgstr "Aktivitäten könnten sein:" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:83 msgid "" "fixed products/services, coming from a sale order linked to this contract" msgstr "" +"feste Produkte/Dienstleistungen, die aus einem Verkaufsauftrag stammen, die " +"mit diesem Vertrag verknüpft sind" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:84 msgid "materials purchased (that you will re-invoice)" -msgstr "" +msgstr "eingekaufte Materialien (die Sie weiterberechnen)" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:85 msgid "time and material based on timesheets or purchases (subcontracting)" msgstr "" +"Zeit und Material auf Grundlage von Zeiterfassungen oder Einkäufen " +"(Unterauftragvergabe)" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:86 msgid "" "expenses like travel and accommodation that you re-invoice to the customer" msgstr "" +"Spesen wie Kosten für Reisen und Unterkunft, die Sie an den Kunden " +"weiterberechnen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:88 msgid "" @@ -4657,22 +4895,27 @@ msgid "" "time and material. For services companies that invoice on fix price, they " "use a regular sales order." msgstr "" +"Sie können die Rechnung am Ende des Vertrags ausstellen oder " +"Zwischenrechnungen auslösen. Dieser Ansatz wird von " +"Dienstleistungsunternehmen verwendet, die meist nach Zeit und Material " +"abrechnen. Für Dienstleistungsunternehmen, die auf Festpreisbasis abrechnen," +" verwenden sie einen regulären Kundenauftrag." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:94 msgid ":doc:`/applications/sales/sales/invoicing/time_materials`" -msgstr "" +msgstr ":doc:`/applications/sales/sales/invoicing/time_materials`" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:95 msgid ":doc:`/applications/sales/sales/invoicing/expense`" -msgstr "" +msgstr ":doc:`/applications/sales/sales/invoicing/expense`" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:96 msgid ":doc:`/applications/sales/sales/invoicing/milestone`" -msgstr "" +msgstr ":doc:`/applications/sales/sales/invoicing/milestone`" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:99 msgid "Recurring Contracts ‣ Invoices" -msgstr "" +msgstr "Wiederkehrende Verträge ‣ Rechnungen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:101 msgid "" @@ -4680,6 +4923,9 @@ msgid "" "frequency of the invoicing and the services/products invoiced are defined on" " the contract." msgstr "" +"Bei Abonnements wird in regelmäßigen Abständen automatisch eine Rechnung " +"erstellt. Die Häufigkeit der Rechnungsstellung und die in Rechnung " +"gestellten Dienstleistungen/Produkte werden im Vertrag festgelegt." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:106 msgid ":doc:`/applications/sales/sales/invoicing/subscriptions`" @@ -4691,7 +4937,7 @@ msgstr "Andere" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:112 msgid "Creating an invoice manually" -msgstr "" +msgstr "Eine Rechnung manuell erstellen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:114 msgid "" @@ -4699,88 +4945,110 @@ msgid "" "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 "" +"Sie können Rechnungen auch manuell erstellen, ohne Verträge oder einen " +"Verkaufsauftrag zu verwenden. Diese Vorgehensweise ist empfehlenswert, wenn " +"Sie den Verkaufsprozess (Angebote) oder die Lieferung der Produkte oder " +"Dienstleistungen nicht verwalten müssen." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:119 msgid "" "Even if you generate the invoice from a sales order, you may need to create " "invoices manually in exceptional use cases:" msgstr "" +"Auch wenn Sie die Rechnung aus einem Verkaufsauftrag erstellen, müssen Sie " +"Rechnungen in Ausnahmefällen gegebenenfalls manuell erfassen:" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:122 msgid "if you need to create a refund" -msgstr "" +msgstr "wenn Sie eine Rückerstattung erstellen müssen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:124 msgid "If you need to give a discount" -msgstr "" +msgstr "wenn Sie einen Rabatt gewähren müssen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:126 msgid "if you need to change an invoice created from a sales order" msgstr "" +"wenn Sie eine Rechnung ändern müssen, die aus einem Verkaufsauftrag stammt" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:128 msgid "if you need to invoice something not related to your core business" msgstr "" +"wenn Sie etwas in Rechnung stellen müssen, das nicht Teil Ihres " +"Kerngeschäfts ist" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:131 msgid "Specific modules" -msgstr "" +msgstr "Spezifische Module" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:133 msgid "Some specific modules are also able to generate draft invoices:" -msgstr "" +msgstr "Spezifische Module können auch Rechnungsentwürfe erzeugen:" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:135 msgid "**membership**: invoice your members every year" -msgstr "" +msgstr "**Mitgliedschaft**: Ihre Mitglieder jährlich abrechnen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:137 msgid "**repairs**: invoice your after-sale services" -msgstr "" +msgstr "**Reparaturen**: Ihre After-Sales-Dienste abrechnen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:140 msgid "Resequencing of the invoices" -msgstr "" +msgstr "Neue Sequenzierung von Rechnungen" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:142 msgid "" "It remains possible to resequence the invoices but with some restrictions:" msgstr "" +"Es ist weiterhin möglich, die Rechnungen neu zu sequenzieren, allerdings mit" +" einigen Einschränkungen:" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:144 msgid "The feature does not work when entries are previous to a lock date." msgstr "" +"Die Funktion funktioniert nicht, wenn Buchungen vor einem Sperrdatum liegen." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:145 msgid "" "The feature does not work if the sequence is inconsistent with the month of " "the entry." msgstr "" +"Die Funktion funktioniert nicht, wenn die Sequenz nicht mit dem Monat der " +"Buchung übereinstimmt." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:146 msgid "It does not work if the sequence leads to a duplicate." -msgstr "" +msgstr "Es funktioniert nicht, wenn die Sequenz zu einem Duplikat führt." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:147 msgid "The order of the invoice remains unchanged." -msgstr "" +msgstr "Die Reihenfolge der Rechnung unverändert bleibt." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:148 msgid "" "It is useful for people who use a numbering from another software and who " "want to continue the current year without starting over from the beginning." msgstr "" +"Sie ist nützlich für Personen, die eine Nummerierung aus einer anderen " +"Software verwenden und die das aktuelle Jahr fortsetzen möchten, ohne von " +"vorne zu beginnen." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:152 #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:3 msgid "Invoice digitization with optical character recognition (OCR)" msgstr "" +"Digitalisierung von Rechnungen mit optischer Zeichenerkennung (Optical " +"Character Recognition, OCR)" #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:154 msgid "" "**Invoice digitization** is the process of automatically encoding " "traditional paper invoices into invoices forms in your accounting." msgstr "" +"**Rechnungsdigitalisierung** ist das Verfahren der automatischen Codierung " +"von traditionellen Papierrechnungen in Rechnungsformulare in Ihrer " +"Buchhaltung." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:157 msgid "" @@ -4788,84 +5056,103 @@ msgid "" "content of the documents. Vendor bills and customer invoices forms are " "automatically created and populated based on scanned invoices." msgstr "" +"Odoo verwendet OCR und Technologien der künstlichen Intelligenz, um den " +"Inhalt der Dokumente zu erkennen. Die Formulare für Lieferantenrechnungen " +"und Kundenrechnungen werden automatisch erstellt und auf der Grundlage der " +"gescannten Rechnungen ausgefüllt." #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:162 msgid "" ":doc:`/applications/finance/accounting/vendor_bills/invoice_digitization`" msgstr "" +":doc:`/applications/finance/accounting/vendor_bills/invoice_digitization`" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:3 msgid "Payment terms and installment plans" -msgstr "" +msgstr "Zahlungsbedingungen und Teilzahlungspläne" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:5 msgid "" "**Payment Terms** specify all the conditions under which a sale is paid, " "mostly to ensure customers pay their invoices correctly and on time." msgstr "" +"**Zahlungsbedingungen** legen alle Bedingungen fest, unter denen ein Verkauf" +" bezahlt wird, meist um sicherzustellen, dass die Kunden ihre Rechnungen " +"korrekt und pünktlich bezahlen." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:8 msgid "" "Payment Terms can be applied to sales orders, customer invoices, supplier " "bills, and contacts. These conditions cover:" msgstr "" +"Zahlungsbedingungen können auf Verkaufsaufträge, Kundenrechnungen, " +"Lieferantenrechnungen und Kontakte angewendet werden. Diese Bedingungen " +"umfassen:" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:11 msgid "The due date" -msgstr "" +msgstr "Das Fälligkeitsdatum" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:12 msgid "Some discounts" -msgstr "" +msgstr "Einige Rabatte" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:13 msgid "Any other condition on the payment" -msgstr "" +msgstr "Jede andere Bedingung für die Zahlung" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:15 msgid "" "Defining Payment Terms automatically calculates the payments' due dates. " "This is particularly helpful for managing installment plans." msgstr "" +"Wenn Sie Zahlungsbedingungen festlegen, werden die Fälligkeitsdaten der " +"Zahlungen automatisch berechnet. Dies ist besonders hilfreich bei der " +"Verwaltung von Zahlungsplänen." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:18 msgid "" "An **installment plan** allows the customers to pay an invoice in parts, " "with the amounts and payment dates defined beforehand by the seller." msgstr "" +"Ein **Zahlungsplan** ermöglicht den Kunden, eine Rechnungen in Teilen zu " +"zahlen, bei dem die Beträge und Zahldaten vorab vom Verkäufer festgelegt " +"wurden." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:21 msgid "**Examples of Payment Terms:**" -msgstr "" +msgstr "**Beispiele von Zahlungsbedingungen:**" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "**Immediate Payment**" -msgstr "" +msgstr "**Sofortige Zahlung**" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "The full payment is due on the day of the invoice's issuance." -msgstr "" +msgstr "Die vollständige Zahlung ist am Tag der Rechnungsaustellung fällig." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "**15 Days** (or **Net 15**)" -msgstr "" +msgstr "**15 Tage** (oder **Netto 15**)" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "The full payment is due 15 days after the invoice date." -msgstr "" +msgstr "Die vollständige Zahlung ist 15 Tage nach dem Rechnungsdatum fällig." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "**21 MFI**" -msgstr "" +msgstr "**21 MNR**" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "" "The full payment is due by the 21st of the month following the invoice date." msgstr "" +"Die vollständige Zahlung ist am 21. Tag des Monats nach dem Rechnungsdatum " +"fällig." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "**2% 10, Net 30 EOM**" -msgstr "" +msgstr "**2 % 10, Netto 30 EDM**" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "" @@ -4873,6 +5160,9 @@ msgid "" "ten days. Otherwise, the full payment is due at the end of the month " "following the invoice date." msgstr "" +"2 % :doc:`Skonto `, wenn die Zahlung innerhalb von zehn " +"Tagen eingeht. Andernfalls ist die gesamte Zahlung am Ende des Monats nach " +"dem Rechnungsdatum fällig." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:34 msgid "" @@ -4880,98 +5170,124 @@ msgid "" "specific order, you issue several invoices to your customer, that is neither" " a payment term nor an installment plan, but an invoicing policy." msgstr "" +"Zahlungsbedingungen sind nicht mit Anzahlungsrechnungen zu verwechseln. Wenn" +" Sie Ihrem Kunden für einen bestimmten Auftrag mehrere Rechnungen " +"ausstellen, handelt es sich weder um eine Zahlungsbedingung noch um einen " +"Zahlungsplan, sondern um eine Rechnungsstellungspolitik." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:39 msgid "" "This document is about the *Payment Terms* feature, not *Terms & " "Conditions*." msgstr "" +"Dieses Dokument handelt von der Funktion *Zahlungsbedingungen*, nicht von " +"*Allgemeinen Geschäftsbedingungen*." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:42 msgid ":doc:`cash_discounts`" -msgstr "" +msgstr ":doc:`cash_discounts`" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:43 msgid "" "`Odoo Tutorials: Payment Terms `_" msgstr "" +"`Odoo Tutorials: Zahlungsbedingungen " +"`_" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:48 msgid "" "Go to :menuselection:`Accounting --> Configuration --> Payment Terms` and " "click on *Create*." msgstr "" +"Gehen Sie auf :menuselection:`Buchhaltung --> Konfiguration --> " +"Zahlungsbedingungen` und klicken Sie auf *Neu*." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:50 msgid "" "The **Description on the Invoice** is the text displayed on the document " "(sale order, invoice, etc.)." msgstr "" +"Die **Beschreibung auf der Rechnung** ist der Text, der auf dem Dokument " +"angezeigt wird (Verkaufsauftrag, Rechnung etc.)." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:53 msgid "" "In the **Terms** section, you can add a set of rules, called *terms*, to " "define what needs to be paid and by which due date." msgstr "" +"Im Abschnitt **Bedingungen** können Sie einige Regeln festlegen, die " +"*Bedingungen* genannt werden, um zu bestimmen, was bis zu welchem " +"Fälligkeitsdatum gezahlt werden muss." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:56 msgid "" "To add a term, click on *Add a line*, and define its *Type*, *Value*, and " "*Due Date Computation*." msgstr "" +"Um eine Bedingung festzulegen, klicken Sie auf *Zeile hinzufügen* und " +"bestimmen Sie den *Typ*, *Wert* und *Berechnung des Fälligkeitsdatums*." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:59 msgid "Terms are computed in the order they are set up." msgstr "" +"Bedingungen werden im Auftrag, in dem sie eingestellt sind, berechnet." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:60 msgid "The **balance** should always be used for the last line." -msgstr "" +msgstr "Das **Saldo** sollte immer für die letzte Zeile verwendet werden." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:62 msgid "" "In the following example, 30% is due on the day of issuance, and the balance" " is due at the end of the following month." msgstr "" +"Im folgenden Beispiel sind 30 % am Tag der Erstellung fällig und der " +"Restbetrag am Ende des folgenden Monats." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst-1 msgid "" "Example of Payment Terms. The last line is the balance due on the 31st of the following\n" "month." msgstr "" +"Beispiel von Zahlungsbedingungen. Die letzte Zeile ist der Saldo, der am 31." +" des folgenden Monats fällig ist." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:71 msgid "Using Payment Terms" -msgstr "" +msgstr "Zahlungsbedingungen verwenden" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:73 msgid "" "Payment Terms can be defined in the **Due Date** field, with the **Terms** " "drop-down list, on:" msgstr "" +"Zahlungsbedingungen können im Feld **Fälligkeitsdatum** mit der Drop-down-" +"Liste **Bedingungen** bestimmt werden für" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "**Quotations**" -msgstr "" +msgstr "**Angeboten**" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "" "To set specific payment terms automatically on all invoices generated from a" " quotation." msgstr "" +"Um bestimmte Zahlungsbedingungen automatisch für alle Rechnungen " +"festzulegen, die aus einem Angebot erstellt werden." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "**Customer Invoices**" -msgstr "" +msgstr "**Kundenrechnungen**" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "To set specific payment terms on an invoice." -msgstr "" +msgstr "Um bestimmte Zahlungsbedingungen für eine Rechnung festzulegen." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "**Vendor Bills**" -msgstr "" +msgstr "**Lieferantenrechnungen**" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "" @@ -4979,20 +5295,29 @@ msgid "" " to manage vendor terms with several installments. Otherwise, setting the " "*Due Date* is enough." msgstr "" +"Um bestimmte Zahlungsbedingungen auf einer Eingangsrechnung festzulegen. " +"Dies ist vor allem dann nützlich, wenn Sie Lieferantenbedingungen mit " +"mehreren Raten verwalten müssen. Andernfalls genügt es, das " +"*Fälligkeitsdatum* festzulegen." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:84 msgid "" "You can also define a **Due Date** manually. If Payment Terms are already " "defined, empty the field so you can select a date." msgstr "" +"Sie können auch manuell ein **Fälligkeitsdatum** festlegen. Wenn die " +"Zahlungsbedingungen bereits definiert sind, leeren Sie das Feld, damit Sie " +"ein Datum auswählen können." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:87 msgid "Payment Terms can be defined with the **Payment Terms** field on:" msgstr "" +"Zahlungsbedingungen können im Feld **Zahlungsbedingungen** bestimmt werden " +"auf:" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "**Contacts**" -msgstr "" +msgstr "**Kontakten**" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 msgid "" @@ -5000,12 +5325,19 @@ msgid "" "and bills of a contact. This can be modified in the contact’s *Form View*, " "under the *Sales & Purchase* tab." msgstr "" +"Um bestimmte Zahlungsbedingungen für neue Verkaufsaufträge, Ein- und " +"Ausgangsrechnungen eines Kontakts festzulegen. Dies kann in der " +"*Formularansicht* des Kontakts im Reiter *Verkauf & Einkauf* geändert " +"werden." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:96 msgid "" "Invoices with specific Payment Terms generate different *Journal Entries*, " "with one *Journal Item* for every computed *Due Date*." msgstr "" +"Rechnungen mit bestimmten Zahlungsbedingungen erzeugen verschiedene " +"*Journalbuchungen*, mit einer *Buchungszeile* für jedes berechnete " +"*Fälligkeitsdatum*." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:99 msgid "" @@ -5013,12 +5345,18 @@ msgid "" "each due date into account, rather than just the balance due date. It also " "helps to get an accurate *Aged Receivable report*." msgstr "" +"Dies erleichtert *Mahnungen* und *Abstimmungen*, da Odoo jedes " +"Fälligkeitsdatum berücksichtigt und nicht nur das Fälligkeitsdatum des " +"Saldos. Es hilft auch dabei, einen genauen *Bericht über überfällige " +"Forderungen* zu erhalten." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst-1 msgid "" "The amount debited on the Account Receivable is split into two Journal Items with distinct\n" "Due Dates" msgstr "" +"Der auf dem Debitorenkonto belastete Betrag wird in zwei Buchungszeilen mit " +"unterschiedlichen Fälligkeitsdaten aufgeteilt." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:107 msgid "" @@ -5026,6 +5364,9 @@ msgid "" "payment terms: *30% is due on the day of issuance, and the balance is due at" " the end of the following month.*" msgstr "" +"In diesem Beispiel wurde eine Rechnung über 1.000 € mit den folgenden " +"Zahlungsbedingungen ausgestellt: *30 % sind am Tag der Ausstellung der " +"Rechnung fällig, der Restbetrag am Ende des folgenden Monats." #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:111 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 @@ -5076,19 +5417,19 @@ msgstr "Debitorenkonto" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:113 msgid "February 21" -msgstr "" +msgstr "21. Februar" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:113 msgid "300" -msgstr "" +msgstr "300" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:115 msgid "March 31" -msgstr "" +msgstr "31. März" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:115 msgid "700" -msgstr "" +msgstr "700" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:117 msgid "Product Sales" @@ -5097,13 +5438,15 @@ msgstr "Produktverkäufe" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:117 #: ../../content/applications/finance/fiscal_localizations/peru.rst:140 msgid "1000" -msgstr "" +msgstr "1000" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:120 msgid "" "The $1000 debited on the Account Receivable is split into two distinct " "*Journal Items*. Both of them have their own **Due Date**." msgstr "" +"Die auf dem Debitorenkonto abgebuchten 1000 € wird in zwei *Buchungszeilen* " +"aufgeteilt. Beide haben ihr eigenes **Fälligkeitsdatum**." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:5 msgid "Snailmail" @@ -5116,26 +5459,37 @@ msgid "" "you have the ability to send invoices and follow-up reports through postal " "mail worldwide, all from within your database." msgstr "" +"Der Versand von Postwurfsendungen kann eine wirksame Strategie sein, um die " +"Aufmerksamkeit der Menschen zu wecken, insbesondere wenn deren E-Mail-" +"Postfächer überfüllt sind. Mit Odoo haben Sie die Möglichkeit, Rechnungen " +"und Mahnungen per Post weltweit zu versenden, und zwar direkt aus Ihrer " +"Datenbank heraus." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:14 msgid "" "Go to :menuselection:`Accounting --> Configuration --> Settings --> Customer" " invoices` section to activate :guilabel:`Snailmail`." msgstr "" +"Gehen Sie auf :menuselection:`Buchhaltung --> Konfiguration --> " +"Einstellungen --> Kundenrechnungen`, um :guilabel:`Postversand` zu " +"aktivieren." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:17 msgid "" "To make it a by-default feature, select :guilabel:`Send by Post` in the " ":guilabel:`Default Sending Options` section." msgstr "" +"Um diese Funktion standardmäßig zu aktivieren, wählen Sie :guilabel:`Per " +"Post versenden` im Abschnitt :guilabel:`Standard-Versandoptionen`." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst-1 msgid "Under settings enable the snailmail feature in Odoo Accounting" msgstr "" +"Die Postversandfunktion unter Einstellungen in Odoo Buchhaltung aktivieren." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:25 msgid "Send invoices by post" -msgstr "" +msgstr "Rechnungen per Post versenden" #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:27 msgid "" @@ -5143,12 +5497,18 @@ msgid "" ":guilabel:`Send by Post`. Make sure your customer’s address is set " "correctly, including the country, before sending the letter." msgstr "" +"Öffnen Sie Ihre Rechnung, klicken Sie auf :guilabel:`Senden & Drucken` und " +"wählen Sie :guilabel:`Per Post versenden` aus. Vergewissern Sie sich, dass " +"die Adresse Ihres Kunden korrekt angegeben ist, einschließlich des Landes, " +"bevor Sie den Brief versenden." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:31 msgid "" "Your document must respect the following rules to pass the validation before" " being sent:" msgstr "" +"Ihr Dokument muss folgende Regeln respektieren, um die Validierung vor dem " +"Versand zu bestehen:" #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:33 msgid "" @@ -5159,17 +5519,29 @@ msgid "" ":menuselection:`General Settings --> Technical --> Reporting section: Paper " "Format`." msgstr "" +"Die Ränder müssen auf allen Seiten **5 mm** betragen. Da Odoo die äußeren " +"Ränder erzwingt, indem es sie vor dem Versenden des Postbriefs mit weißer " +"Farbe füllt, kann es dazu führen, dass der Text des Benutzers abgeschnitten " +"wird, wenn er über die Ränder hinausragt. Um die Ränder zu überprüfen, " +"aktivieren Sie den :ref:`Entwicklermodus`, gehen Sie zu " +":menuselection:`Allgemeine Einstellungen --> Technisch --> Berichtswesen: " +"Papierformat`." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:38 msgid "" "A square of **15mm by 15mm** on the bottom left corner has to stay clear." msgstr "" +"Ein Quadrat von **15mm mal 15mm** in der unteren linken Ecke muss frei " +"bleiben." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:39 msgid "" "The postage area has to stay clear (click :download:`here " "` to get more info about the area)." msgstr "" +"Der Postbereich muss frei bleiben (klicken Sie :download:`hier " +"`, um weitere Informationen über den " +"Bereich zu erhalten)." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:41 msgid "" @@ -5177,6 +5549,9 @@ msgid "" "address, so if something gets written outside the area, it is not counted as" " part of the address." msgstr "" +"Pingen (Odoos Anbieter für den Postversand) scannt den Bereich, um die " +"Adresse zu verarbeiten. Wenn also etwas außerhalb des Bereichs geschrieben " +"wird, wird es nicht als Teil der Adresse gezählt." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:45 #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:65 @@ -5189,6 +5564,9 @@ msgid "" "requires prepaid stamps (=credits) to work. Sending one document consumes " "one stamp." msgstr "" +"Postversand ist ein :doc:`/applications/general/in_app_purchase`-Dienst, der" +" im Voraus bezahlte Briefmarken (=Guthaben) erfordert, damit er " +"funktioniert. Der Versand eines Dokuments verbraucht eine Briefmarke," #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:50 msgid "" @@ -5197,6 +5575,11 @@ msgid "" "credits`, or go to :menuselection:`Settings --> In-App Purchases: Odoo IAP`," " and click on :guilabel:`View my Services`." msgstr "" +"Um Briefmarken zu kaufen, gehen Sie zu :menuselection:`Buchhaltung --> " +"Konfiguration --> Einstellungen --> Kundenrechnungen: Postversand`, klicken " +"Sie auf :guilabel:`Guthaben kaufen` oder gehen Sie zu " +":menuselection:`Einstellungen --> In-App-Käufe: Odoo IAP`, und klicken Sie " +"auf :guilabel:`Meine Services anzeigen`." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:55 #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:74 @@ -5204,12 +5587,16 @@ msgid "" "If you are on Odoo Online and have the Enterprise version, you benefit from " "free trial credits to test the feature." msgstr "" +"Wenn Sie mit Odoo Online arbeiten und die Enterprise-Version haben, können " +"Sie die Funktion kostenlos testen." #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:57 msgid "" "Click `here `_ to know about our " "*Privacy Policy*." msgstr "" +"Klicken Sie `hier `_, um mehr über " +"unsere *Datenschutzrichtlinien* zu erfahren." #: ../../content/applications/finance/accounting/get_started.rst:5 msgid "Get started" @@ -5222,12 +5609,19 @@ msgid "" " get started. This onboarding banner is displayed until you choose to close " "it." msgstr "" +"Wenn Sie Ihre Odoo Buchhaltungsapp zum ersten Mal öffnen, werden Sie auf der" +" Seite *Buchhaltungsübersicht* mit einem Einführungsbanner begrüßt, einem " +"Assistenten, der Ihnen Schritt für Schritt den Einstieg erleichtert. Dieser " +"Einführungsbanner wird so lange angezeigt, bis Sie ihn schließen." #: ../../content/applications/finance/accounting/get_started.rst:11 msgid "" "The settings visible in the onboarding banner can still be modified later by" " going to :menuselection:`Accounting --> Configuration --> Settings`." msgstr "" +"Die im Einführungsbanner sichtbaren Einstellungen können später noch " +"geändert werden, indem Sie auf :menuselection:`Buchhaltung --> Konfiguration" +" --> Einstellungen` gehen." #: ../../content/applications/finance/accounting/get_started.rst:15 msgid "" @@ -5237,35 +5631,43 @@ msgid "" "are ready-to-go. :ref:`Click here ` for more " "information about Fiscal Localization Packages." msgstr "" +"Odoo Buchhaltung installiert automatisch das passende **steuerliche " +"Lokalisierungspaket** für Ihr Unternehmen, je nach dem Land, das bei der " +"Erstellung der Datenbank ausgewählt wurde. Auf diese Weise sind die " +"richtigen Konten, Berichte und Steuern sofort einsatzbereit. :ref:`Klicken " +"Sie hier ` für weitere Informationen über " +"Steuerliche Lokalisierungspakete." #: ../../content/applications/finance/accounting/get_started.rst:21 msgid "Accounting onboarding banner" -msgstr "" +msgstr "Einführungsbanner für Buchhaltung" #: ../../content/applications/finance/accounting/get_started.rst:23 msgid "" "The step-by-step Accounting onboarding banner is composed of four steps:" msgstr "" +"Das Schritt-für-Schritt-Banner für die Einführung in der Buchhaltung besteht" +" aus vier Schritten:" #: ../../content/applications/finance/accounting/get_started.rst-1 msgid "Step-by-step onboarding banner in Odoo Accounting" -msgstr "" +msgstr "Schritt-für-Schritt-Einführungsbanner in Odoo Buchhaltung" #: ../../content/applications/finance/accounting/get_started.rst:28 msgid ":ref:`accounting-setup-company`" -msgstr "" +msgstr ":ref:`accounting-setup-company`" #: ../../content/applications/finance/accounting/get_started.rst:29 msgid ":ref:`accounting-setup-bank`" -msgstr "" +msgstr ":ref:`accounting-setup-bank`" #: ../../content/applications/finance/accounting/get_started.rst:30 msgid ":ref:`accounting-setup-periods`" -msgstr "" +msgstr ":ref:`accounting-setup-periods`" #: ../../content/applications/finance/accounting/get_started.rst:31 msgid ":ref:`accounting-setup-chart`" -msgstr "" +msgstr ":ref:`accounting-setup-chart`" #: ../../content/applications/finance/accounting/get_started.rst:36 #: ../../content/applications/finance/accounting/get_started.rst:137 @@ -5279,10 +5681,16 @@ msgid "" "number. These details are then displayed on your documents, such as on " "invoices." msgstr "" +"In diesem Menü können Sie Details zu Ihrem Unternehmen hinzufügen, z. B. " +"Name, Adresse, Logo, Website, Telefonnummer, E-Mail-Adresse und Steuernummer" +" oder Umsatzsteueridentifikationsnummer. Diese Angaben werden dann auf Ihren" +" Dokumenten, z. B. auf Rechnungen, angezeigt." #: ../../content/applications/finance/accounting/get_started.rst-1 msgid "Add your company's details in Odoo Accounting and Odoo Invoicing" msgstr "" +"Ihre Unternehmensangaben in Odoo Buchhaltung und Odoo Rechnungsstellung " +"hinzufügen" #: ../../content/applications/finance/accounting/get_started.rst:46 msgid "" @@ -5290,6 +5698,9 @@ msgid "" "General Settings --> Settings --> Companies` and clicking on **Update " "Info**." msgstr "" +"Sie können diese Einstellungen auch ändern, indem Sie zu " +":menuselection:`Einstellungen --> Allgemeine Einstellungen --> Einstellungen" +" --> Unternehmen` gehen und auf **Infos aktualisieren** klicken." #: ../../content/applications/finance/accounting/get_started.rst:52 msgid "Bank Account" @@ -5301,12 +5712,18 @@ msgid "" "synced automatically. To do so, find your bank in the list, click on " "*Connect*, and follow the instructions on-screen." msgstr "" +"Verbinden Sie Ihr Bankkonto mit Ihrer Datenbank und lassen Sie Ihre " +"Kontoauszüge automatisch synchronisieren. Suchen Sie dazu Ihre Bank in der " +"Liste, klicken Sie auf *Verbinden*, und folgen Sie den Anweisungen auf dem " +"Bildschirm." #: ../../content/applications/finance/accounting/get_started.rst:58 msgid "" ":doc:`Click here ` for more information about " "this feature." msgstr "" +":doc:`Klicken Sie hier ` für weitere " +"Informationen über diese Funktion." #: ../../content/applications/finance/accounting/get_started.rst:60 msgid "" @@ -5314,6 +5731,10 @@ msgid "" "prefer not to sync it with your database, you may also configure your bank " "account manually by clicking on *Create it*, and filling out the form." msgstr "" +"Wenn Ihr Bankinstitut nicht automatisch synchronisiert werden kann oder wenn" +" Sie es nicht mit Ihrer Datenbank synchronisieren möchten, können Sie Ihr " +"Bankkonto auch manuell konfigurieren, indem Sie auf *Erstellen* klicken und " +"das Formular ausfüllen." #: ../../content/applications/finance/accounting/get_started.rst:64 msgid "**Name**: the bank account's name, as displayed on Odoo." @@ -5360,10 +5781,14 @@ msgid "" ":menuselection:`Accounting --> Configuration`, and clicking on *Add a Bank " "Account*." msgstr "" +"Sie können mit diesem Tool so viele Bankkonten wie nötig hinzufügen, indem " +"Sie auf :menuselection:`Buchhaltung --> Konfiguration` gehen und auf " +"*Bankkonto hinzufügen* klicken." #: ../../content/applications/finance/accounting/get_started.rst:77 msgid ":doc:`Click here ` for more information about Bank Accounts." msgstr "" +":doc:`Klicken Sie hier ` für weitere Informationen über Bankkonten." #: ../../content/applications/finance/accounting/get_started.rst:83 msgid "Accounting Periods" @@ -5375,18 +5800,28 @@ msgid "" " to generate reports automatically, and your **Tax Return Periodicity**, " "along with a reminder to never miss a tax return deadline." msgstr "" +"Definieren Sie hier das Eröffnungs- und Abschlussdatum Ihres " +"**Geschäftsjahres**, das für die automatische Generierung von Berichten " +"verwendet wird, sowie Ihre **Periodizität der Steuererklärung**, zusammen " +"mit einer Erinnerung, um keine Steuererklärungsfrist zu verpassen." #: ../../content/applications/finance/accounting/get_started.rst:89 msgid "" "By default, the opening date is set on the 1st of January and the closing " "date on the 31st of December, as this is the most common use." msgstr "" +"Standardmäßig ist das Eröffnungsdatum auf den 1. Januar und das " +"Abschlussdatum auf den 31. Dezember festgelegt, da dies die häufigste " +"Verwendung ist." #: ../../content/applications/finance/accounting/get_started.rst:93 msgid "" "You can also change these settings by going to :menuselection:`Accounting " "--> Configuration --> Settings --> Fiscal Periods` and updating the values." msgstr "" +"Sie können diese Einstellungen auch ändern, indem Sie zu " +":menuselection:`Buchhaltung --> Konfiguration --> Einstellungen --> " +"Steuerperioden` gehen und die Werte aktualisieren." #: ../../content/applications/finance/accounting/get_started.rst:99 msgid "Chart of Accounts" @@ -5397,6 +5832,8 @@ msgid "" "With this menu, you can add accounts to your **Chart of Accounts** and " "indicate their initial opening balances." msgstr "" +"Mit diesem Menü können Sie Konten zu Ihrem **Kontenplan** hinzufügen und die" +" ursprünglichen Eröffnungssalden angeben." #: ../../content/applications/finance/accounting/get_started.rst:104 msgid "" @@ -5404,21 +5841,28 @@ msgid "" "Accounts. To access all the settings of an account, click on the *double " "arrow button* at the end of the line." msgstr "" +"Auf dieser Seite werden grundlegende Einstellungen angezeigt, die Ihnen die " +"Überprüfung Ihres Kontenplans erleichtern. Um auf alle Einstellungen eines " +"Kontos zuzugreifen, klicken Sie auf die Schaltfläche *Doppelpfeil* am Ende " +"der Zeile." #: ../../content/applications/finance/accounting/get_started.rst-1 msgid "" "Setup of the Chart of Accounts and their opening balances in Odoo Accounting" msgstr "" +"Einstellung des Kontenplans und der Eröffnungssalden in Odoo Buchhaltung" #: ../../content/applications/finance/accounting/get_started.rst:111 msgid "" ":doc:`Click here ` for more information on " "how to configure your Chart of Accounts." msgstr "" +":doc:`Klicken Sie hier ` für weitere " +"Informationen, wie Sie Ihren Kontenplan konfigurieren." #: ../../content/applications/finance/accounting/get_started.rst:115 msgid "Invoicing onboarding banner" -msgstr "" +msgstr "Einführungsbanner für Rechnungsstellung" #: ../../content/applications/finance/accounting/get_started.rst:117 msgid "" @@ -5427,42 +5871,52 @@ msgid "" "onboarding banner* is the one that welcomes you if you use the Invoicing app" " rather than the Accounting app." msgstr "" +"Es gibt ein weiteres Einführungsbanner, das Ihnen hilft, die Vorteile Ihrer " +"Odoo Rechnungsstellungs- und Buchhaltungsapps Schritt für Schritt zu nutzen." +" Das Einführungsbanner *Rechnungsstellung* ist das Banner, das Sie begrüßt, " +"wenn Sie die Rechnungsstellungsapp und nicht die Buchhaltungs-App verwenden." #: ../../content/applications/finance/accounting/get_started.rst:121 msgid "" "If you have Odoo Accounting installed on your database, you can reach it by " "going to :menuselection:`Accounting --> Customers --> Invoices`." msgstr "" +"Wenn Sie Odoo Buchhaltung in Ihrer Datenbank installiert haben, können Sie " +"diese unter :menuselection:`Buchhaltung --> Kunden --> Rechnungen` " +"erreichen." #: ../../content/applications/finance/accounting/get_started.rst:124 msgid "The Invoicing onboarding banner is composed of four main steps:" msgstr "" +"Das Einführungsbanner in der Rechnungsstellung besteht aus vier Schritten:" #: ../../content/applications/finance/accounting/get_started.rst-1 msgid "Step-by-step onboarding banner in Odoo Invoicing" -msgstr "" +msgstr "Schritt-für-Schritt-Einführungsbanner in Odoo Rechnungsstellung" #: ../../content/applications/finance/accounting/get_started.rst:129 msgid ":ref:`invoicing-setup-company`" -msgstr "" +msgstr ":ref:`invoicing-setup-company`" #: ../../content/applications/finance/accounting/get_started.rst:130 msgid ":ref:`invoicing-setup-layout`" -msgstr "" +msgstr ":ref:`invoicing-setup-layout`" #: ../../content/applications/finance/accounting/get_started.rst:131 msgid ":ref:`invoicing-setup-payment`" -msgstr "" +msgstr ":ref:`invoicing-setup-payment`" #: ../../content/applications/finance/accounting/get_started.rst:132 msgid ":ref:`invoicing-setup-sample`" -msgstr "" +msgstr ":ref:`invoicing-setup-sample`" #: ../../content/applications/finance/accounting/get_started.rst:139 msgid "" "This form is the same as :ref:`the one presented in the Accounting " "onboarding banner `." msgstr "" +"Dieses Formular ist dasselbe wie :ref:`das im Einführungsbanner der " +"Buchhaltung präsentiert wird `." #: ../../content/applications/finance/accounting/get_started.rst:145 msgid "Invoice Layout" @@ -5474,6 +5928,9 @@ msgid "" " which layout template, paper format, colors, font, and logo you want to " "use." msgstr "" +"Mit diesem Tool können Sie das Erscheinungsbild Ihrer Dokumente gestalten, " +"indem Sie die Layoutvorlage, das Papierformat, die Farben, die Schriftart " +"und das Logo auswählen, die Sie verwenden möchten." #: ../../content/applications/finance/accounting/get_started.rst:150 msgid "" @@ -5486,7 +5943,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started.rst-1 msgid "Document layout configuration in Odoo Invoicing" -msgstr "" +msgstr "Konfiguration des Dokumentlayouts in Odoo Rechnungsstellung" #: ../../content/applications/finance/accounting/get_started.rst:159 msgid "" @@ -5510,6 +5967,8 @@ msgid "" "This menu helps you configure the payment methods with which your customers " "can pay you." msgstr "" +"Dieses Menü hilft Ihnen bei der Konfiguration der Zahlungsmethoden, über die" +" Ihre Kunden sie bezahlen kann." #: ../../content/applications/finance/accounting/get_started.rst:175 msgid "" @@ -5530,15 +5989,15 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:186 msgid ":doc:`bank`" -msgstr "" +msgstr ":doc:`bank`" #: ../../content/applications/finance/accounting/get_started.rst:187 msgid ":doc:`get_started/chart_of_accounts`" -msgstr "" +msgstr ":doc:`get_started/chart_of_accounts`" #: ../../content/applications/finance/accounting/get_started.rst:189 msgid ":doc:`../fiscal_localizations`" -msgstr "" +msgstr ":doc:`../fiscal_localizations`" #: ../../content/applications/finance/accounting/get_started.rst:190 msgid "`Odoo Tutorials: Accounting Basics `_" @@ -5661,7 +6120,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 #: ../../content/applications/finance/fiscal_localizations/france.rst:240 msgid "0" -msgstr "" +msgstr "0" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 @@ -5670,7 +6129,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 msgid "+8\\*$10" -msgstr "" +msgstr "+8\\*$10" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 @@ -5957,16 +6416,20 @@ msgid "" "The **chart of accounts (COA)** is the list of all the accounts used to " "record financial transactions in the general ledger of an organization." msgstr "" +"Der **Kontenplan** ist eine Liste aller Konten, die verwendet werden, um " +"Finanztransaktionen im Hauptbuch einer Organisation zu erfassen." #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:8 msgid "" "The accounts are usually listed in the order of appearance in the financial " "reports. Most of the time, they are listed as follows :" msgstr "" +"Die Konten werden in der Regel in der Reihenfolge aufgeführt, in der sie in " +"den Finanzberichten erscheinen. Meistens werden sie wie folgt aufgelistet:" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:11 msgid "Balance Sheet accounts:" -msgstr "" +msgstr "Bilanzkonten:" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:13 #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 @@ -5985,7 +6448,7 @@ msgstr "EIGENKAPITAL" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:17 msgid "Profit & Loss:" -msgstr "" +msgstr "Gewinn & Verlust:" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:19 #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:91 @@ -6002,14 +6465,17 @@ msgid "" "When browsing your chart of accounts, you can filter the accounts by number," " in the left column, and also group them by :guilabel:`Account Type`." msgstr "" +"Wenn Sie Ihren Kontenplan durchsuchen, können Sie die Konten in der linken " +"Spalte nach Nummern filtern und sie außerdem nach :guilabel:`Kontotyp` " +"gruppieren." #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 msgid "Group the accounts by type in Odoo Accounting" -msgstr "" +msgstr "Die Konten nach Typ in Odoo Buchhaltung gruppieren" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:30 msgid "Configuration of an account" -msgstr "" +msgstr "Konfiguration eines Kontos" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:32 msgid "" @@ -6019,34 +6485,49 @@ msgid "" "already configured according to the country's regulations. You can use it " "directly or set it according to your company's needs." msgstr "" +"Das Land, das Sie bei der Erstellung Ihrer Datenbank (oder eines " +"zusätzlichen Unternehmens in Ihrer Datenbank) auswählen, bestimmt, welches " +"**Steuerliche Lokalisierungspaket** standardmäßig installiert wird. Dieses " +"Paket enthält einen Standardkontenplan, der bereits entsprechend den " +"Vorschriften des Landes konfiguriert ist. Sie können ihn direkt verwenden " +"oder ihn nach den Bedürfnissen Ihres Unternehmens einstellen." #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:38 msgid "" "It is not possible to modify the **fiscal localization** of a company once a" " journal entry has been posted." msgstr "" +"Es ist nicht möglich, die **Steuerliche Lokalisierung** eines Unternehmens " +"zu ändern, sobald eine Journalbuchung gebucht worden ist." #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:41 msgid "" "To create a new account, go to :menuselection:`Accounting --> Configuration " "--> Chart of Accounts`, click on :guilabel:`Create`, and fill out the form." msgstr "" +"Um ein neues Konto zu erstellen, gehen Sie auf :menuselection:`Buchhaltung " +"--> Konfiguration --> Kontenplan`, klicken Sie auf :guilabel:`Neu` und " +"füllen Sie das Formular aus." #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:45 msgid "Code and name" -msgstr "" +msgstr "Code und Name" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 msgid "" "Each account is identified by its **code** and **name**, which also " "indicates the account's purpose." msgstr "" +"Jedes Konto wird durch seinen **Code** und **Namen** identifiziert, der auch" +" den Zweck des Kontos angibt." #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 msgid "" "Correctly configuring the **account type** is critical as it serves multiple" " purposes:" msgstr "" +"Die korrekte Konfiguration des **Kontotyps** ist von entscheidender " +"Bedeutung, da sie mehreren Zwecken dient:" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 msgid "Information on the account's purpose and behavior" @@ -6069,6 +6550,9 @@ msgid "" "To configure an account type, open the :guilabel:`Type` field's drop-down " "selector and select the right type among the following list:" msgstr "" +"Um einen Kontotyp zu konfigurieren, öffnen Sie die Drop-down-Liste des " +"Feldes :guilabel:`Typ` und wählen den richtigen Typ aus der folgenden Liste " +"aus:" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 msgid "Report" @@ -6176,7 +6660,7 @@ msgstr "Ausserbilanz" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:105 msgid "Assets, deferred expenses, and deferred revenues automation" -msgstr "" +msgstr "Automatisierung von Aktiva, aktiver und passiver Rechnungsabgrenzung" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:107 msgid "" @@ -6211,13 +6695,15 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:120 #: ../../content/applications/finance/accounting/taxes.rst:14 msgid "Default taxes" -msgstr "" +msgstr "Standardsteuern" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:122 msgid "" "Select a **default tax** that will be applied when this account is chosen " "for a product sale or purchase." msgstr "" +"Wählen Sie eine **Standardsteuer**, die angewendet wird, wenn dieses Konto " +"für einen Produktverkauf oder -kauf ausgewählt wird." #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:126 msgid "Tags" @@ -6229,6 +6715,10 @@ msgid "" " By default, you can choose among the tags that are used by the *Cash Flow " "Statement*." msgstr "" +"Für einige Buchhaltungsberichte müssen **Stichwörter** für die " +"entsprechenden Konten festgelegt werden. Standardmäßig können Sie zwischen " +"den Stichwörtern wählen, die von der *Kapitalflussrechnung* verwendet " +"werden." #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:132 msgid "Account groups" @@ -6563,7 +7053,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:133 #: ../../content/applications/finance/accounting/payments/checks.rst:84 msgid "Journal entries" -msgstr "" +msgstr "Journalbuchungen" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:135 msgid "" @@ -6904,26 +7394,25 @@ msgstr "" msgid "" "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " "open the journal you want to edit, and select a currency in the field " -":guilabel:`Currency`. If left empty, all active currencies are handled " -"instead of just one." +":guilabel:`Currency`." msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency for the journal to handle." msgstr "" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:114 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 msgid "Multi-currency accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:119 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 msgid "Invoices, bills, and other documents" msgstr "" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:121 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 msgid "" "For all documents, you can select the currency and journal to use for the " -"transaction." +"transaction on the document itself." msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 @@ -10336,40 +10825,281 @@ msgstr "Intrastat" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 msgid "" -"**Intrastat** is the system for data collection and statistic production of " -"goods traded among the EU Member States. Organizations whose annual trade " -"surpasses a certain threshold must provide data about the goods traded with " -"other EU countries." +"`Intrastat `_ is the data collection and " +"statistics production system for goods traded among EU member states. It " +"collects data on:" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:10 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:9 msgid "" -"`Eurostat Statistics Explained - Glossary: Intrastat " -"`_" +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:14 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:11 msgid "" -"As of January 1, 2022, the reporting requirements have changed. One main " -"modification concerns the transaction codes which are now switching to a " -"2-digits format. All transactions recorded after this date have to follow " -"the new system’s rules." +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:21 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:13 +msgid "Returns of goods." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:16 msgid "" -"Go to :menuselection:`Accounting --> Settings --> Customer Invoices`, then " -"enable **Intrastat** and *Save*. Once the Intrastat has been activated you " -"are able to choose the **Default incoterm**." +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"`_, preferring instead " +"*intra-Union trade in goods statistics*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:23 +msgid "General configuration" msgstr "" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:25 msgid "" -"If you created your Odoo database prior to **January 13, 2022**, please " -":ref:`upgrade ` the ``account_intrastat`` module to add the" -" new transaction codes and :ref:`install ` the " -"``account_intrastat_expiry`` module to archive the old codes." +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the **Customer Invoices** section, tick " +":guilabel:`Intrastat` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:31 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located, and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:34 +msgid "" +"If your warehouses are located in multiple regions, you can define the " +"region code for each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:43 +msgid "Default Incoterm" +msgstr "Standard-Incoterms" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "" +"You can set **default Incoterms** for your company by selecting an Intrastat" +" **code** in the :guilabel:`Default Incoterm` field of the **Customer " +"Invoices** section, and then clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "Product configuration" +msgstr "Produktkonfiguration" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:54 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:59 +msgid "Commodity code" +msgstr "Warennummer" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:61 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature `_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:64 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:68 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:74 +msgid "Country of origin" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:76 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:82 +msgid "Invoices and bills configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:84 +msgid "" +"Once products are properly configured, several settings must be enabled on " +"the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:90 +msgid "Transaction code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:92 +msgid "" +"Transaction codes are used to identify a transaction's nature. To set a " +"transaction code on an invoice line, create an invoice or bill, click the " +":guilabel:`⋮` button, tick :guilabel:`Intrastat`, and use the newly-added " +":guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:101 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:107 +msgid "Partner country" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:109 +msgid "" +"The partner country is the vendor's or customer's country, depending on " +"whether it is an invoice or bill. It is automatically filled in using the " +":guilabel:`Country` field in the **contact form** of the partner." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:113 +msgid "" +"To edit the partner country manually, click on the :guilabel:`Other Info` " +"tab when on an invoice or bill, and select the :guilabel:`Intrastat " +"Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "Transport code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:121 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch). Once you have selected a :ref:`partner" +" country `, the :guilabel:`Intrastat Transport " +"Mode` becomes available." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "Value of the goods" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:130 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "Partner configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:138 +msgid "" +"Two fields from the partner's **contact form** are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set ` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:143 +msgid "Generate the Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:145 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration ` and the " +"information on the :ref:`products `, " +":ref:`invoices and bills `, and " +":ref:`partners `." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"Export the report as a PDF, XLSX, or XML file to submit it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:153 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:155 +msgid "Invoice or bill reference number;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:156 +msgid "" +":guilabel:`System`, which is a code automatically generated depending on " +"whether the document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:158 +msgid "" +":ref:`Country `, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:160 +msgid ":ref:`Transaction Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:161 +msgid "" +":ref:`Region Code ` (if your company is located in " +"Belgium);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:162 +msgid ":ref:`Commodity Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:163 +msgid ":ref:`Origin Country `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:164 +msgid ":ref:`Partner VAT `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid ":ref:`Transport Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:166 +msgid "" +":ref:`Value `, which is always expressed in EUR even if the" +" original invoice or bill used another currency." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 @@ -18676,7 +19406,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:839 msgid "Daily Sales Report" -msgstr "" +msgstr "Täglicher Verkaufsbericht" #: ../../content/applications/finance/fiscal_localizations/chile.rst:841 msgid "" @@ -21334,6 +22064,7 @@ msgid "2-digits comparison" msgstr "" #: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:61 msgid "Template" msgstr "Vorlage" @@ -26216,7 +26947,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 msgid "Cancel payment" -msgstr "" +msgstr "Zahlung abbrechen" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:810 msgid "" @@ -29553,7 +30284,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers.rst:145 msgid "Additional features" -msgstr "" +msgstr "Zusätzliche Funktionen" #: ../../content/applications/finance/payment_acquirers.rst:147 msgid "" @@ -29750,7 +30481,7 @@ msgid "" msgstr "" #: ../../content/applications/finance/payment_acquirers.rst:267 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:40 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:38 msgid "Configuration tab" msgstr "" @@ -29899,7 +30630,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/adyen.rst:10 #: ../../content/applications/finance/payment_acquirers/adyen.rst:137 #: ../../content/applications/finance/payment_acquirers/alipay.rst:36 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:53 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:51 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:47 #: ../../content/applications/finance/payment_acquirers/mollie.rst:31 #: ../../content/applications/finance/payment_acquirers/paypal.rst:162 @@ -30223,34 +30954,241 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:31 msgid "" -"If you are trying Authorize.Net as a test, with a *sandbox account*, change " -"the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a" -" test Odoo database, rather than on your main database." +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:35 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:34 msgid "" -"If you set :guilabel:`Test Mode` on Odoo and use an authorize.net account " -"instead of a sandbox.authorize.net account, it results in the following " -"error: *The merchant login ID or password is invalid or the account is " -"inactive*." +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:41 msgid "Place a hold on a card" msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:45 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 msgid "" -"With Authorize.net, you can enable the :ref:`manual capture " +"With Authorize.Net, you can enable the :ref:`manual capture " "`. If enabled, the funds are " "reserved for 30 days on the customer's card, but not charged yet." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:50 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:48 msgid "" "After **30 days**, the transaction is **voided automatically** by " -"Authorize.net." +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:54 +msgid "Import an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:57 +msgid "Export from Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:63 +msgid "" +"`Download the Excel import template " +"`_" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:65 +msgid "To export a statement:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:67 +msgid "Log in to Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:68 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:69 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:71 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:84 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:87 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:89 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:90 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:92 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:93 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:95 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:97 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template `. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:104 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:107 +msgid "Import into Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:109 +msgid "To import the data into Odoo:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:111 +msgid "Open the :ref:`Excel import template `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:112 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:114 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:117 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:118 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:120 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template ` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:125 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template ` for each invoice." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 +msgid "Chargeback description" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:133 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:135 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:137 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:139 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:141 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:143 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:148 +msgid "" +"List of `eCheck.Net return codes " +"`_" msgstr "" #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:3 diff --git a/locale/de/LC_MESSAGES/inventory_and_mrp.po b/locale/de/LC_MESSAGES/inventory_and_mrp.po index 2278706f5..33018cdb8 100644 --- a/locale/de/LC_MESSAGES/inventory_and_mrp.po +++ b/locale/de/LC_MESSAGES/inventory_and_mrp.po @@ -10,6 +10,7 @@ # Anja Funk , 2022 # Chris Egal , 2022 # Martin Trigaux, 2023 +# Larissa Manderfeld, 2023 # #, fuzzy msgid "" @@ -18,7 +19,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-07-07 06:24+0000\n" "PO-Revision-Date: 2021-11-02 08:48+0000\n" -"Last-Translator: Martin Trigaux, 2023\n" +"Last-Translator: Larissa Manderfeld, 2023\n" "Language-Team: German (https://app.transifex.com/odoo/teams/41243/de/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -28,7 +29,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp.rst:5 msgid "Inventory & MRP" -msgstr "" +msgstr "Lager & MRP" #: ../../content/applications/inventory_and_mrp/inventory.rst:8 msgid "Inventory" @@ -41,17 +42,23 @@ msgid "" " lead times, automate replenishments, and configure advanced routes like " "drop-shipping, cross-docks, etc." msgstr "" +"**Odoo Lager** ist sowohl eine Inventarisierungsapp als auch ein " +"Lagerverwaltungssystem mit einer erweiterten Barcode-Scanner-App. Erfahren " +"Sie, wie Sie Vorlaufzeiten verwalten, Auffüllungen automatisieren und " +"erweiterte Routen wie Streckengeschäfte, Lagerumschläge usw. konfigurieren " +"können." #: ../../content/applications/inventory_and_mrp/inventory.rst:15 msgid "" "`Odoo Tutorials: Inventory `_" -msgstr "" +msgstr "`Odoo Tutorials: Lager `_" #: ../../content/applications/inventory_and_mrp/inventory.rst:16 #: ../../content/applications/inventory_and_mrp/manufacturing.rst:16 msgid "" "`Odoo Tutorials: Barcode Scanner `_" msgstr "" +"`Odoo Tutorials: Barcode-Scanner `_" #: ../../content/applications/inventory_and_mrp/inventory/barcode.rst:5 msgid "Barcodes" @@ -8320,7 +8327,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:117 msgid "Closest Location" -msgstr "" +msgstr "Nächstgelegener Standort" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:119 msgid "" @@ -9088,7 +9095,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:68 #: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:90 msgid "Product configuration" -msgstr "" +msgstr "Produktkonfiguration" #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:70 #: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:92 diff --git a/locale/de/LC_MESSAGES/marketing.po b/locale/de/LC_MESSAGES/marketing.po index 3bc0b5cc9..2863d60e0 100644 --- a/locale/de/LC_MESSAGES/marketing.po +++ b/locale/de/LC_MESSAGES/marketing.po @@ -6,6 +6,7 @@ # Translators: # philku79 , 2023 # Martin Trigaux, 2023 +# Larissa Manderfeld, 2023 # #, fuzzy msgid "" @@ -14,7 +15,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-07-07 06:24+0000\n" "PO-Revision-Date: 2021-11-02 08:49+0000\n" -"Last-Translator: Martin Trigaux, 2023\n" +"Last-Translator: Larissa Manderfeld, 2023\n" "Language-Team: German (https://app.transifex.com/odoo/teams/41243/de/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -33,10 +34,11 @@ msgstr "Events" #: ../../content/applications/marketing/events.rst:8 msgid "`Odoo Tutorials: Events `_" msgstr "" +"`Odoo Tutorials: Veranstaltungen `_" #: ../../content/applications/marketing/events/event_essentials.rst:3 msgid "Event essentials" -msgstr "" +msgstr "Wesentliche Merkmale für Veranstaltung" #: ../../content/applications/marketing/events/event_essentials.rst:5 msgid "" @@ -50,7 +52,7 @@ msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:11 msgid "Kanban concepts and organization" -msgstr "" +msgstr "Kanban-Konzepte und -Organisation" #: ../../content/applications/marketing/events/event_essentials.rst:13 msgid "" @@ -3872,7 +3874,7 @@ msgstr "" #: ../../content/applications/marketing/surveys/create.rst:106 msgid "Options tab" -msgstr "" +msgstr "Reiter „Optionen“" #: ../../content/applications/marketing/surveys/create.rst:108 msgid "" @@ -4056,7 +4058,7 @@ msgstr "" #: ../../content/applications/marketing/surveys/create.rst:193 msgid "Description tab" -msgstr "" +msgstr "Reiter „Beschreibung“" #: ../../content/applications/marketing/surveys/create.rst:195 msgid "" diff --git a/locale/de/LC_MESSAGES/productivity.po b/locale/de/LC_MESSAGES/productivity.po index 645977050..b11bf5060 100644 --- a/locale/de/LC_MESSAGES/productivity.po +++ b/locale/de/LC_MESSAGES/productivity.po @@ -5356,7 +5356,7 @@ msgstr "" #: ../../content/applications/productivity/studio/pdf_reports.rst:111 msgid "Company tagline" -msgstr "" +msgstr "Slogan des Unternehmen" #: ../../content/applications/productivity/studio/pdf_reports.rst:113 msgid "" @@ -5658,7 +5658,7 @@ msgstr "" #: ../../content/applications/productivity/studio/pdf_reports.rst:306 msgid "Options tab" -msgstr "" +msgstr "Reiter „Optionen“" #: ../../content/applications/productivity/studio/pdf_reports.rst:308 msgid "" diff --git a/locale/de/LC_MESSAGES/sales.po b/locale/de/LC_MESSAGES/sales.po index 16fc3e16a..01370c9da 100644 --- a/locale/de/LC_MESSAGES/sales.po +++ b/locale/de/LC_MESSAGES/sales.po @@ -19,7 +19,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:49+0000\n" "Last-Translator: Larissa Manderfeld, 2023\n" "Language-Team: German (https://app.transifex.com/odoo/teams/41243/de/)\n" @@ -45,18 +45,23 @@ msgid "" "the pipeline and manage your day-to-day activities with meetings and next " "activities." msgstr "" +"**Odoo CRM** hilft Ihnen bei der Organisation Ihrer Vertriebsaktivitäten: " +"Verfolgen Sie Leads, schließen Sie Verkaufschancen ab und erhalten Sie " +"genaue Prognosen. Organisieren Sie Verkaufschancen mit der Pipeline und " +"verwalten Sie Ihre täglichen Aktivitäten mit Meetings und nächsten " +"Aktivitäten." #: ../../content/applications/sales/crm.rst:15 msgid "`Odoo Tutorials: CRM `_" -msgstr "" +msgstr "`Odoo Tutorials: CRM `_" #: ../../content/applications/sales/crm/acquire_leads.rst:5 msgid "Acquire leads" -msgstr "" +msgstr "Leads akquirieren" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:3 msgid "Convert leads into opportunities" -msgstr "" +msgstr "Leads in Verkaufschancen umwandeln" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:5 msgid "" @@ -64,6 +69,10 @@ msgid "" "qualification step before converting a *Lead* into an *Opportunity* and " "assigning to the right sales people." msgstr "" +"Das System kann Leads anstelle von Verkaufschancen generieren, um einen " +"Qualifizierungsschritt hinzuzufügen, bevor ein *Lead* in eine " +"*Verkaufschance* umgewandelt und den richtigen Vertriebsmitarbeitern " +"zugewiesen wird." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:9 msgid "" @@ -71,6 +80,9 @@ msgid "" "sales channels by default. But you can make it specific for specific " "channels from their configuration form." msgstr "" +"Sie können diesen Modus in den CRM-Einstellungen aktivieren. Er gilt " +"standardmäßig für alle Ihre Verkaufskanäle. Sie können ihn jedoch für " +"bestimmte Kanäle in deren Konfigurationsformular aktivieren." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:14 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 @@ -110,16 +122,20 @@ msgid "" "For this feature to work, go to :menuselection:`CRM --> Configuration --> " "Settings` and activate the *Leads* feature." msgstr "" +"Gehen Sie für diese Funktion auf :menuselection:`CRM --> Konfiguration --> " +"Einstellungen` und aktivieren Sie die *Leads*-Funktion." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:22 msgid "" "You will now have a new submenu *Leads* under *Leads* where they will " "aggregate." msgstr "" +"Sie werden nun ein neues Untermenü *Leads* unter *Leads* haben, in dem sie " +"zusammengefasst werden." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:29 msgid "Convert a lead into an opportunity" -msgstr "" +msgstr "Einen Lead in eine Verkaufschance umwandeln" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:31 msgid "" @@ -127,6 +143,10 @@ msgid "" "opportunity and decide if it should still be assigned to the same " "channel/person and if you need to create a new customer." msgstr "" +"Wenn Sie auf einen *Lead* klicken, haben Sie die Möglichkeit, ihn in eine " +"Verkaufschance umzuwandeln und zu entscheiden, ob er weiterhin demselben " +"Kanal/ derselben Person zugewiesen werden soll oder ob Sie einen neuen " +"Kunden erstellen müssen." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:38 msgid "" @@ -135,6 +155,10 @@ msgid "" "Odoo will automatically offer you to link to an existing customer if that " "customer already exists." msgstr "" +"Wenn Sie bereits eine Verkaufschance mit diesem Kunden haben, bietet Odoo " +"Ihnen automatisch an, diese mit dieser Verkaufschance zu verbinden. Auf die " +"gleiche Weise bietet Odoo Ihnen automatisch an, sie mit einem bestehenden " +"Kunden zu verknüpfen, wenn dieser Kunde bereits existiert." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:44 msgid "Merge opportunities" @@ -147,32 +171,46 @@ msgid "" " into the opportunity which was created first, giving priority to the " "information present on the first opportunity." msgstr "" +"Odoo schlägt auch automatisch vor, Verkaufschancen zusammenzuführen, wenn " +"sie dieselbe E-Mail-Adresse haben. Beim Zusammenführen von Verkaufschancen " +"führt Odoo die Informationen in der Verkaufschance zusammen, die zuerst " +"erstellt wurde, wobei die Informationen der ersten Verkaufschance Vorrang " +"haben." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:51 msgid "" "No information is lost: data from the other opportunity is logged in the " "chatter and the information fields for easy access." msgstr "" +"Es gehen keine Informationen verloren: Die Daten der anderen Verkaufschance " +"werden im Chat und in den Informationsfeldern protokolliert, damit sie " +"leicht zugänglich sind." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:57 msgid "" "Would you find a duplicate yourself, ...you can also merge opportunities or " "leads even if the system doesn't propose it." msgstr "" +"Würden Sie selbst ein Duplikat finden ... können Sie auch Verkaufschancen " +"oder Leads zusammenführen, selbst wenn das System dies nicht vorschlägt." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:60 msgid "" "Here’s how, from the list view. Select the opportunities or leads you want " "to merge and the action button will appear. Then, you can select merge." msgstr "" +"So gehen Sie in der Listenansicht vor. Wählen Sie die Verkaufschancen oder " +"Leads aus, die Sie zusammenführen möchten, und die Aktionsschaltfläche wird " +"angezeigt. Dann können Sie „Zusammenführen“ auswählen." #: ../../content/applications/sales/crm/acquire_leads/convert.rst:67 msgid "It is also possible to merge more than 2 opportunities or leads." msgstr "" +"Es ist auch möglich, mehr als 2 Verkaufschancen oder Leads zusammenzuführen." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:3 msgid "Generate leads/opportunities" -msgstr "" +msgstr "Leads/Verkaufschancen generieren" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:5 msgid "" @@ -181,10 +219,15 @@ msgid "" "leads in your CRM whenever someone sends a message to a Sales Team email " "alias or fills out a contact form on your website." msgstr "" +"Zwei wichtige Möglichkeiten, neue Leads oder Verkaufschancen für Ihr " +"Unternehmen zu generieren, sind E-Mail-Aliase und Website-Kontaktformulare. " +"Odoo erstellt automatisch Leads in Ihrem CRM, wenn jemand eine Nachricht an " +"einen E-Mail-Alias des Vertriebsteams sendet oder ein Kontaktformular auf " +"Ihrer Website ausfüllt." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:10 msgid "Configure email aliases" -msgstr "" +msgstr "E-Mail-Aliase" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:12 msgid "" @@ -195,14 +238,22 @@ msgid "" "email aliases on the configuration page for each Sales Team by navigating to" " :menuselection:`CRM --> Configuration --> Sales Teams`." msgstr "" +"Jedes Verkaufsteam kann seinen eigenen eindeutigen E-Mail-Alias verwenden, " +"um Leads/Verkaufschancen zu generieren. Jede E-Mail, die an den E-Mail-Alias" +" eines Verkaufsteams gesendet wird, erstellt automatisch einen Lead (wenn " +"Leads in Ihren CRM-Einstellungen aktiviert sind) oder eine Verkaufschance in" +" der Pipeline für dieses bestimmte Team. Konfigurieren Sie " +"benutzerdefinierte E-Mail-Aliasse auf der Konfigurationsseite für jedes " +"Verkaufsteam, indem Sie zu :menuselection:`CRM --> Konfiguration --> " +"Verkaufsteams` navigieren." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 msgid "Configuring Sales Teams" -msgstr "" +msgstr "Verkaufsteam konfigurieren" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:23 msgid "Use Contact Forms on your website" -msgstr "" +msgstr "Kontaktformulare auf Ihrer Website verwenden" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:25 msgid "" @@ -210,20 +261,27 @@ msgid "" "Contact Form. Whenever someone submits this form, a lead or an opportunity " "is generated in your database." msgstr "" +"Auf der Seite *Kontakt* Ihrer Website wird standardmäßig das " +"gebrauchsfertige Kontaktformular von Odoo angezeigt. Jedes Mal, wenn jemand " +"dieses Formular ausfüllt, wird in Ihrer Datenbank ein Lead oder eine " +"Verkaufschance generiert." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 msgid "Default Contact Us page" -msgstr "" +msgstr "Standardseite „Kontaktieren Sie uns“" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:32 msgid "" "The Contact Form can be activated or deactivated at any time by going to " ":menuselection:`Website --> Go to Website --> Customize --> Contact Form`." msgstr "" +"Das Kontaktformular kann jederzeit unter :menuselection:`Website --> Gehe zu" +" Website --> Anpassen --> Kontaktformular` aktiviert oder deaktiviert " +"werden." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 msgid "Contact Form toggle" -msgstr "" +msgstr "Kontaktformular Ein/Aus" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:39 msgid "" @@ -231,10 +289,14 @@ msgid "" " to email your company directly. Any email sent this way will generate a " "lead/opportunity." msgstr "" +"Wenn das Formular deaktiviert ist, wird auf der Seite *Kontaktieren Sie uns*" +" einfach eine Schaltfläche angezeigt, über die Sie direkt eine E-Mail an Ihr" +" Unternehmen senden können. Jede E-Mail, die auf diese Weise gesendet wird, " +"generiert einen Lead/eine Verkaufschance." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 msgid "Contact Us Page using email" -msgstr "" +msgstr "„Kontaktieren Sie uns“-Seite per E-Mail" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:46 msgid "" @@ -242,20 +304,26 @@ msgid "" "leads/opportunities created from the Contact Form by going to " ":menuselection:`Website --> Configuration --> Settings --> Communication`." msgstr "" +"Wählen Sie, welches Verkaufsteam oder welcher Verkäufer automatisch den " +"Leads/Verkaufschancen zugewiesen wird, die über das Kontaktformular erstellt" +" wurden, indem Sie auf :menuselection:`Website --> Konfiguration --> " +"Einstellungen --> Kommunikation` gehen." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 msgid "Contact Form settings" -msgstr "" +msgstr "Einstellungen des Kontaktformulars" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:55 msgid "Customize Contact Forms" -msgstr "" +msgstr "Kontaktformulare anpassen" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:57 msgid "" "Contact Forms can be customized for the specific information your team " "needs, using the free *Form Builder* module." msgstr "" +"Kontaktformulare können mit dem kostenlosen Modul *Formularbauer* an die " +"spezifischen Informationen angepasst werden, die Ihr Team benötigt." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:60 msgid "" @@ -263,10 +331,13 @@ msgid "" "added to a web page via the Website Builder. It can also be installed " "manually from the :guilabel:`Apps` page." msgstr "" +"Das Modul *Formular-Builder* wird automatisch installiert, wenn ein " +"Formularelement über den Website-Builder zu einer Webseite hinzugefügt wird." +" Es kann auch manuell über die Seite :guilabel:`Apps` installiert werden." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 msgid "Form Builder building blocks" -msgstr "" +msgstr "Bausteine des Formular-Builders" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:68 msgid "" @@ -274,22 +345,31 @@ msgid "" "However, Odoo's default *Contact Us* page is designed to fit most users' " "needs. Start with the default form and modify from there." msgstr "" +"Formulare können von Grund auf neu erstellt werden, um eine Vielzahl von " +"Zwecken zu erfüllen. Die standardmäßige „*Kontaktieren Sie uns*“-Seite von " +"Odoo ist jedoch für die meisten Benutzer geeignet. Beginnen Sie mit dem " +"Standardformular und ändern Sie es von dort aus." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:73 msgid "Edit Contact Form fields" -msgstr "" +msgstr "Felder des Kontaktformulars bearbeiten" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:75 msgid "" "In Edit mode on your website, click on any field to start editing it. The " "following information can be edited for each field on the Contact Form:" msgstr "" +"Klicken Sie im Bearbeitungsmodus Ihrer Website auf ein beliebiges Feld, um " +"es zu bearbeiten. Die folgenden Informationen können für jedes Feld des " +"Kontaktformulars bearbeitet werden:" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:78 msgid "" ":guilabel:`Type`: Choose a custom field option or an existing field. " "Examples include phone, file upload, language, etc." msgstr "" +":guilabel:`Typ`: Wählen Sie eine benutzerdefinierte Feldoption oder ein " +"bestehendes Feld. Beispiel sind Telefon, Datei hochladen, Sprache usw." #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:80 msgid "" @@ -1973,72 +2053,67 @@ msgid "" "<../../../productivity/iot/config/connect>` may require :doc:`the HTTPS " "protocol ` to establish a secure connection between the browser and " "the printer. However, trying to reach the printer's IP address using HTTPS " -"leads to a warning page on most web browsers." +"leads to a warning page on most web browsers. In that case, you can " +"temporarily :ref:`force the connection `, which " +"allows you to reach the page in HTTPS and use the ePOS printer in Odoo as " +"long as the browser window stays open." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:41 -msgid "warning page about the connection privacy on Google Chrome" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:41 -msgid "Warning page on Google Chrome, Windows 10" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:43 -msgid "" -"In that case, you can temporarily force the connection by clicking " -":guilabel:`Advanced` and :guilabel:`Proceed to [IP address] (unsafe)`. Doing" -" so allows you to reach the page in HTTPS and use the ePOS printer in Odoo " -"as long as the browser window stays open." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:48 -msgid "" -"The previous instructions apply to Google Chrome but are similar to other " -"browsers." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:51 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:40 msgid "" "The connection is lost after closing the browser window. Therefore, this " "method should only be used as a **workaround** or as a pre-requisite for the" " :ref:`following instructions `." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 msgid "Generate, export, and import self-signed certificates" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:60 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 msgid "" "For a long-term solution, you must generate a **self-signed certificate**. " "Then, export and import it into your browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 msgid "" "**Generating** an SSL certificate should only be done **once**. If you " "create another certificate, devices using the previous one will lose HTTPS " "access." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:69 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 msgid "Windows 10 & Linux OS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:73 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62 msgid "Generate a self-signed certificate" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:75 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 msgid "" -"After forcing the connection, sign in using your printer credentials to " -"access the ePOS printer settings. To sign in, enter `epson` in the " -":guilabel:`ID` field and your printer serial number in the " -":guilabel:`Password` field." +"Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force " +"the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to " +"[IP address] (unsafe)`." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:79 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "warning page about the connection privacy on Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72 +msgid "Warning page on Google Chrome, Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74 +msgid "" +"Then, sign in using your printer credentials to access the ePOS printer " +"settings. To sign in, enter `epson` in the :guilabel:`ID` field and your " +"printer serial number in the :guilabel:`Password` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78 msgid "" "Click :guilabel:`Certificate List` in the :guilabel:`Authentication` " "section, and click :guilabel:`create` to generate a new **Self-Signed " @@ -2049,7 +2124,7 @@ msgid "" "printer." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:86 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 msgid "" "The self-signed certificate is generated. Reload the page and click " ":guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure " @@ -2057,25 +2132,25 @@ msgid "" "Certificate` section." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:90 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 msgid "Export a self-signed certificate" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:92 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 msgid "" "The export process is heavily dependent on the :abbr:`OS (Operating System)`" " and the browser. Start by accessing your ePOS printer settings on your web " -"browser by navigating to its IP address, for example, " -"`https://192.168.1.25`. Then, force the connection as explained in the " -":ref:`introduction `." +"browser by navigating to its IP address (e.g., `https://192.168.1.25`). " +"Then, force the connection as explained in the **Generate a self-signed " +"certificate tab**." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:97 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:160 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 msgid "If you are using **Google Chrome**," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:99 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 msgid "" "click :guilabel:`Not secure` next to the search bar, and " ":guilabel:`Certificate is not valid`;" @@ -2085,43 +2160,43 @@ msgstr "" msgid "Connection to the printer not secure button in Google Chrome browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:107 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105 msgid "" "add `.crt` at the end of the file name to ensure it has the correct " "extension;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 msgid "" "select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom " "of the pop-up window;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:110 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:128 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125 msgid "save, and the certificate is exported." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:113 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 msgid "" "Make sure that the certificate ends with the extension `.crt`. Otherwise, " "some browsers might not see the file during the import process." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:172 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 msgid "If you are using **Mozilla Firefox**," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:118 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 msgid "click the **lock-shaped** icon on the left of the address bar;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:119 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 msgid "" "go to :menuselection:`Connection not secure --> More information --> " "Security tab --> View certificate`;" @@ -2131,173 +2206,173 @@ msgstr "" msgid "Connection is not secure button in Mozilla Firefox browser" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:126 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123 msgid "scroll down to the :guilabel:`Miscellaneous` section;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124 msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:130 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 msgid "Import a self-signed certificate" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:132 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 msgid "" "The import process is heavily dependent on the :abbr:`OS (Operating System)`" " and the browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:137 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 msgid "Windows 10" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 msgid "" "Windows 10 manages certificates, which means that self-signed certificates " "must be imported from the certification file rather than the browser. To do " "so," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 msgid "" "open the Windows File Explorer and locate the downloaded certification file;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:143 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 msgid "" "right-click on the certification file and click :guilabel:`Install " "Certificate`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 msgid "" "select where to install the certificate and for whom - either for the " ":guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, " "click :guilabel:`Next`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:148 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 msgid "" "on the `Certificate Store` screen, tick :guilabel:`Place all certificates in" " the following store`, click :guilabel:`Browse...`, and select " ":guilabel:`Trusted Root Certification Authorities`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:155 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:151 msgid "click :guilabel:`Finish`, accept the pop-up security window;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 msgid "restart the computer to make sure that the changes are applied." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 msgid "Linux" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:162 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 msgid "open Chrome;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 msgid "" "go to :menuselection:`Settings --> Privacy and security --> Security --> " "Manage certificates`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 msgid "" "go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select " "the exported certification file;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:167 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 msgid "accept all warnings;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:164 msgid "click :guilabel:`ok`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:169 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 msgid "restart your browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:170 msgid "open Firefox;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:171 msgid "" "go to :menuselection:`Settings --> Privacy & Security --> Security --> View " "Certificates... --> Import`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:173 msgid "select the exported certification file;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:178 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 msgid "tick the checkboxes and validate;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 msgid "Mac OS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:183 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 msgid "To secure the connection on a Mac:" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:185 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 msgid "" "open Safari and navigate to your printer's IP address. Doing so leads to a " "warning page;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 msgid "" "on the warning page, go to :menuselection:`Show Details --> visit this " "website --> Visit Website`, validate;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:184 msgid "reboot the printer so you can use it with any other browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:190 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 msgid "Android OS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188 msgid "" "To import an SSL certificate into an Android device, first create and export" " it from a computer. Next, transfer the `.crt` file to the device using " "email, Bluetooth, or USB. Once the file is on the device," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:196 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192 msgid "open the settings and search for `certificate`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 msgid "click :guilabel:`Certificate AC` (Install from device storage);" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:198 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:194 msgid "select the certificate file to install it on the device." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197 msgid "" "The specific steps for installing a certificate may vary depending on the " "version of Android and the device manufacturer." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:206 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:202 msgid "" "If you need to export SSL certificates from an operating system or web " "browser that has not been mentioned, search for `export SSL certificate` + " @@ -2305,18 +2380,18 @@ msgid "" "engine." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:209 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:205 msgid "" "Similarly, to import SSL certificates from an unmentioned OS or browser, " "search for `import SSL certificate root authority` + `the name of your " "browser or operating system` in your preferred search engine." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:210 msgid "Check if the certificate was imported correctly" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:216 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:212 msgid "" "To confirm your printer's connection is secure, connect to its IP address " "using HTTPS. For example, navigate to `https://192.168.1.25` in your " @@ -4167,7 +4242,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:3 msgid "Sales orders" -msgstr "" +msgstr "Verkaufsaufträge" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:5 msgid "" @@ -5627,7 +5702,7 @@ msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:62 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:184 msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" -msgstr "" +msgstr ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:64 msgid "" @@ -6892,7 +6967,7 @@ msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:3 msgid "Product variants" -msgstr "" +msgstr "Produktvarianten" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:5 msgid "" diff --git a/locale/de/LC_MESSAGES/sphinx.po b/locale/de/LC_MESSAGES/sphinx.po index c4777cf8c..9f0ca2963 100644 --- a/locale/de/LC_MESSAGES/sphinx.po +++ b/locale/de/LC_MESSAGES/sphinx.po @@ -92,7 +92,7 @@ msgstr "" #: ../../extensions/odoo_theme/layout_templates/homepage.html:41 msgid "Installing Odoo" -msgstr "" +msgstr "Odoo installieren" #: ../../extensions/odoo_theme/layout_templates/homepage.html:46 msgid "Bugfix updates" diff --git a/locale/de/LC_MESSAGES/websites.po b/locale/de/LC_MESSAGES/websites.po index a469958a3..22ef29b92 100644 --- a/locale/de/LC_MESSAGES/websites.po +++ b/locale/de/LC_MESSAGES/websites.po @@ -51,6 +51,11 @@ msgid "" "website with an address such as ``www.example.com`` rather than the default " "``example.odoo.com``." msgstr "" +"Odoo bietet für alle Odoo-Online-Datenbanken ein Jahr lang einen " +":ref:`kostenlosen benutzerdefinierten Domainnamen `. Besucher können dann mit einer Adresse wie ``www.example.com`` " +"auf Ihre Website zugreifen und nicht mit der Standardadresse " +"``example.odoo.com``." #: ../../content/applications/websites/ecommerce.rst:19 msgid ":doc:`Website Documentation `" @@ -1796,7 +1801,7 @@ msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:288 msgid "Customer accounts" -msgstr "" +msgstr "Kundenkonten" #: ../../content/applications/websites/website/configuration/multi_website.rst:290 msgid "" diff --git a/locale/es/LC_MESSAGES/administration.po b/locale/es/LC_MESSAGES/administration.po index c4cd642c1..c79a349d9 100644 --- a/locale/es/LC_MESSAGES/administration.po +++ b/locale/es/LC_MESSAGES/administration.po @@ -18,8 +18,8 @@ # Martin Trigaux, 2023 # Patricia Gutiérrez Capetillo , 2023 # Braulio D. López Vázquez , 2023 -# Fernanda Alvarez, 2023 # Iran Villalobos López, 2023 +# Fernanda Alvarez, 2023 # #, fuzzy msgid "" @@ -28,7 +28,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-07-07 06:24+0000\n" "PO-Revision-Date: 2022-03-18 14:59+0000\n" -"Last-Translator: Iran Villalobos López, 2023\n" +"Last-Translator: Fernanda Alvarez, 2023\n" "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -6402,7 +6402,7 @@ msgstr "N/A Nunca hubo para esta plataforma" #: ../../content/administration/maintain/supported_versions.rst:165 msgid "🏁 Future version, not released yet" -msgstr "🏁 Versión futura, aún no disponible" +msgstr "🏁 Versión futura, aún no está disponible" #: ../../content/administration/maintain/supported_versions.rst:176 msgid "I run an older version of Odoo/OpenERP/TinyERP" diff --git a/locale/es/LC_MESSAGES/finance.po b/locale/es/LC_MESSAGES/finance.po index 6a5cf0d39..5ce98fa19 100644 --- a/locale/es/LC_MESSAGES/finance.po +++ b/locale/es/LC_MESSAGES/finance.po @@ -42,21 +42,21 @@ # Leonardo J. Caballero G. , 2023 # Martin Trigaux, 2023 # Aimée Mendoza Sánchez, 2023 -# Braulio D. López Vázquez , 2023 # Pedro M. Baeza , 2023 -# Iran Villalobos López, 2023 -# Lucia Pacheco, 2023 # Patricia Gutiérrez Capetillo , 2023 +# Braulio D. López Vázquez , 2023 +# Iran Villalobos López, 2023 # Fernanda Alvarez, 2023 +# Lucia Pacheco, 2023 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:47+0000\n" -"Last-Translator: Fernanda Alvarez, 2023\n" +"Last-Translator: Lucia Pacheco, 2023\n" "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -701,7 +701,6 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:18 #: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:16 #: ../../content/applications/finance/accounting/reporting/budget.rst:11 -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:19 #: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 #: ../../content/applications/finance/accounting/taxes.rst:53 #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 @@ -7705,33 +7704,26 @@ msgstr "" msgid "" "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " "open the journal you want to edit, and select a currency in the field " -":guilabel:`Currency`. If left empty, all active currencies are handled " -"instead of just one." +":guilabel:`Currency`." msgstr "" -"Para hacerlo, vaya a :menuselection:`Contabilidad --> Configuración --> " -"Diarios`, abra el diario que desea editar y seleccione una divisa en el " -"campo :guilabel:`Divisa`. Si se deja en blanco, se pueden utilizar todas las" -" divisas activas en lugar de solo una." #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency for the journal to handle." msgstr "Seleccionar la divisa que el diario utilizará." -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:114 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 msgid "Multi-currency accounting" msgstr "Contabilidad multidivisa" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:119 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 msgid "Invoices, bills, and other documents" msgstr "Facturas de cliente, de proveedor y otros documentos" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:121 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 msgid "" "For all documents, you can select the currency and journal to use for the " -"transaction." +"transaction on the document itself." msgstr "" -"Puede seleccionar la divisa y el diario que se utilizará en la transacción " -"en todos los documentos." #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency and journal to use." @@ -12121,61 +12113,313 @@ msgstr "Intrastat" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 msgid "" -"**Intrastat** is the system for data collection and statistic production of " -"goods traded among the EU Member States. Organizations whose annual trade " -"surpasses a certain threshold must provide data about the goods traded with " -"other EU countries." +"`Intrastat `_ is the data collection and " +"statistics production system for goods traded among EU member states. It " +"collects data on:" msgstr "" -"**Intrastat** es el sistema de recopilación de datos y elaboración de " -"estadísticas sobre los bienes comercializados entre los Estados miembros de " -"la UE. Las organizaciones cuyo comercio anual supera un determinado límite " -"deben proporcionar datos sobre los bienes comercializados con otros países " -"de la UE." -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:10 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:9 msgid "" -"`Eurostat Statistics Explained - Glossary: Intrastat " -"`_" +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" msgstr "" -"Explicación de las estadísticas de Eurostat - Glosario: Intrastat " -"`_" +"Transacciones comerciales de bienes para su uso, consumo, inversión o " +"reventa con traspaso de propiedad;" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:14 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:11 msgid "" -"As of January 1, 2022, the reporting requirements have changed. One main " -"modification concerns the transaction codes which are now switching to a " -"2-digits format. All transactions recorded after this date have to follow " -"the new system’s rules." +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" msgstr "" -"Los requisitos de información cambiaron desde el 1 de enero de 2022. Una de " -"las principales modificaciones está relacionada con los códigos de " -"transacción, que pasan a tener un formato de dos dígitos. Todas las " -"transacciones registradas después de esta fecha tienen que seguir las normas" -" del nuevo sistema." +"Movimientos de bienes sin traspaso de propiedad (por ejemplo, traslados de " +"existencias o movimientos de bienes antes o después de la producción o " +"tratamiento externos, y después del mantenimiento o reparación);" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:21 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:13 +msgid "Returns of goods." +msgstr "Devolución de bienes" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:16 msgid "" -"Go to :menuselection:`Accounting --> Settings --> Customer Invoices`, then " -"enable **Intrastat** and *Save*. Once the Intrastat has been activated you " -"are able to choose the **Default incoterm**." +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"`_, preferring instead " +"*intra-Union trade in goods statistics*." msgstr "" -"Vaya a :menuselección:`Contabilidad --> Ajustes --> Facturas de clientes`, " -"luego active la opción **Intrastat** y haga clic en *Guardar*. Una vez " -"activado, podrá elegir el **incoterm predeterminado**." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:23 +msgid "General configuration" +msgstr "Configuración general" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:25 msgid "" -"If you created your Odoo database prior to **January 13, 2022**, please " -":ref:`upgrade ` the ``account_intrastat`` module to add the" -" new transaction codes and :ref:`install ` the " -"``account_intrastat_expiry`` module to archive the old codes." +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the **Customer Invoices** section, tick " +":guilabel:`Intrastat` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:31 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located, and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:34 +msgid "" +"If your warehouses are located in multiple regions, you can define the " +"region code for each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "Se añade la región intrastat a un almacén" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:43 +msgid "Default Incoterm" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "" +"You can set **default Incoterms** for your company by selecting an Intrastat" +" **code** in the :guilabel:`Default Incoterm` field of the **Customer " +"Invoices** section, and then clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "Product configuration" +msgstr "Configuración de productos" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:54 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" +"Para que los productos se añadan correctamente a un reporte intrastat deben " +"estar bien configurados." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:59 +msgid "Commodity code" +msgstr "Código de mercancía " + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:61 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature `_." +msgstr "" +"Los códigos de mercancía son números de referencia reconocidos en todo el " +"mundo que se usan para clasificar los bienes según sus **características**." +" El código intrastat usa la `nomenclatura combinada `_." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:64 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" +"Si desea añadir un código de mercancía, vaya a :menuselection:`Contabilidad " +"--> Clientes --> Productos` y seleccione un producto, luego, en la pestaña " +":guilabel:`contabilidad`, establezca el :guilabel:`código de mercancía` del " +"producto." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:68 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"`_" +msgstr "" +"`Códigos intrastat de mercancía - Banco Nacional de Bélgica " +"`_" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:74 +msgid "Country of origin" +msgstr "País de origen" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:76 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" +"Si desea establecer el país de origen de un producto, vaya a " +":menuselection:`Contabilidad --> Clientes --> Productos` y seleccione un " +"producto. Establezca el :guilabel:`país de origen` en la pestaña " +":guilabel:`contabilidad`." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:82 +msgid "Invoices and bills configuration" +msgstr "Configuración de las facturas" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:84 +msgid "" +"Once products are properly configured, several settings must be enabled on " +"the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:90 +msgid "Transaction code" +msgstr "Código de transacción" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:92 +msgid "" +"Transaction codes are used to identify a transaction's nature. To set a " +"transaction code on an invoice line, create an invoice or bill, click the " +":guilabel:`⋮` button, tick :guilabel:`Intrastat`, and use the newly-added " +":guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "Se añade la columna intrastat en una factura" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:101 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"`_" +msgstr "" +"`Intrastat: características de las transacciones desde enero 2022 - Banco " +"Nacional de Bélgica " +"`_" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:107 +msgid "Partner country" +msgstr "País del contacto" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:109 +msgid "" +"The partner country is the vendor's or customer's country, depending on " +"whether it is an invoice or bill. It is automatically filled in using the " +":guilabel:`Country` field in the **contact form** of the partner." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:113 +msgid "" +"To edit the partner country manually, click on the :guilabel:`Other Info` " +"tab when on an invoice or bill, and select the :guilabel:`Intrastat " +"Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "Transport code" +msgstr "Código de transporte" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:121 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch). Once you have selected a :ref:`partner" +" country `, the :guilabel:`Intrastat Transport " +"Mode` becomes available." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "Value of the goods" +msgstr "Valor de los bienes" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:130 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" +"El valor de un bien es el :guilabel:`subtotal` (:guilabel:`precio` " +"multiplicado por la :guilabel:`cantidad`) de una línea de factura." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "Partner configuration" +msgstr "Configuración de contacto" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:138 +msgid "" +"Two fields from the partner's **contact form** are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set ` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:143 +msgid "Generate the Intrastat report" +msgstr "Generar el reporte intrastat" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:145 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration ` and the " +"information on the :ref:`products `, " +":ref:`invoices and bills `, and " +":ref:`partners `." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"Export the report as a PDF, XLSX, or XML file to submit it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:153 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" +"Cada línea del reporte corresponde a una sola línea de la factura y contiene" +" la siguiente información:" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:155 +msgid "Invoice or bill reference number;" +msgstr "Número de referencia de la factura;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:156 +msgid "" +":guilabel:`System`, which is a code automatically generated depending on " +"whether the document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:158 +msgid "" +":ref:`Country `, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" +":ref:`País `; el país del proveedor para las " +"llegadas y el país del cliente para los envíos;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:160 +msgid ":ref:`Transaction Code `;" +msgstr ":ref:`Código de transacción `;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:161 +msgid "" +":ref:`Region Code ` (if your company is located in " +"Belgium);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:162 +msgid ":ref:`Commodity Code `;" +msgstr ":ref:`Código de mercancía `;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:163 +msgid ":ref:`Origin Country `;" +msgstr ":ref:`País de origen `;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:164 +msgid ":ref:`Partner VAT `;" +msgstr ":ref:`NIF del contacto `;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid ":ref:`Transport Code `;" +msgstr ":ref:`Código de transporte `;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:166 +msgid "" +":ref:`Value `, which is always expressed in EUR even if the" +" original invoice or bill used another currency." msgstr "" -"Si creó su base de datos Odoo antes del **13 de enero de 2022**, deberá " -":ref:`actualizar ` el módulo ``account_intrastat`` para " -"añadir los nuevos códigos de transacción e :ref:`instalar `" -" el módulo ``account_intrastat_expiry`` para archivar los códigos antiguos." #: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 msgid "Silverfin integration" @@ -12316,7 +12560,7 @@ msgstr "Creación de una clave API externa para un usuario de Odoo" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:3 msgid "Tax return (VAT declaration)" -msgstr "" +msgstr " Declaración de impuestos" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:5 msgid "" @@ -12329,6 +12573,16 @@ msgid "" " price when goods or services are purchased. Based on these values, the " "company can calculate the tax amount they have to pay or be refunded." msgstr "" +"Las empresas con un :abbr:`número de IVA` registrado deben presentar una " +"**declaración de impuestos** mensual o trimestral, según su volumen de " +"negocios y la normativa de registro. La declaración de la renta (o " +"declaración de impuestos) proporciona a las autoridades fiscales información" +" sobre las operaciones gravables realizadas por la empresa. El **impuesto " +"sobre ventas** se impone sobre el número de bienes y servicios vendidos por " +"una empresa, mientras que el **IVA soportado** corresponde al impuesto que " +"se añade al precio cuando se adquieren bienes o servicios. De acuerdo con " +"estos valores, la empresa puede calcular el importe del impuesto que tiene " +"que pagar o que se le devolverá." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:14 msgid "" @@ -12336,6 +12590,9 @@ msgid "" " from the European Commission: `\"What is VAT?\" " "`_." msgstr "" +"Puede encontrar información adicional sobre el IVA y su funcionamiento en " +"esta página de la Comisión Europea: `\"¿Qué es el IVA?\" " +"`_." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:25 msgid "Tax Return Periodicity" @@ -12347,39 +12604,52 @@ msgid "" "your tax return correctly and also to send you a reminder to never miss a " "tax return deadline." msgstr "" +"La configuración de la **periodicidad de la declaración de impuestos** " +"permite a Odoo calcular correctamente su declaración de impuestos y además " +"enviarle un recordatorio para que nunca se le pase la fecha límite." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:30 msgid "" "To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. " "Under the :guilabel:`Tax Return Periodicity`, you can set:" msgstr "" +"Para hacerlo, vaya a :menuselection:`Contabilidad --> Configuración --> " +"Ajustes` y en :guilabel:`periodicidad de la declaración`, puede establecer:" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:33 msgid "" ":guilabel:`Periodicity`: define here whether you submit your tax return on a" " monthly or quarterly basis;" msgstr "" +":guilabel:`Periodicidad`: defina si presenta la declaración de impuestos de " +"forma mensual o trimestral;" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:35 msgid "" ":guilabel:`Reminder`: define when Odoo should remind you to submit your tax " "return;" msgstr "" +":guilabel:`Recordatorio`: defina en qué momento Odoo debería recordarle que " +"presente su declaración de impuestos;" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:36 msgid "" ":guilabel:`Journal`: select the journal in which to record the tax return." msgstr "" +":guilabel:`Diario`: seleccione el diario en el cual se registrará la " +"declaración de impuestos." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 msgid "Configure how often tax returns have to be made in Odoo Accounting" -msgstr "" +msgstr "Frecuencia en la que deben realizarse las declaraciones de impuestos" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:43 msgid "" "This is usually configured during the :doc:`app's initial set up " "<../get_started>`." msgstr "" +"Suele configurarse durante la :doc:`instalación inicial de la aplicación " +"<../get_started>`." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:48 msgid "Tax Grids" @@ -12392,10 +12662,18 @@ msgid "" " recorded transactions use the right taxes. You can see the :guilabel:`Tax " "Grids` by opening the :guilabel:`Journal Items` tab of any invoice and bill." msgstr "" +"Odoo genera reportes de impuestos basados en los ajustes de las " +":guilabel:`tablas de impuestos` configuradas en sus impuestos. Por lo tanto," +" debe asegurarse de que todas las transacciones registradas utilizan los " +"impuestos correctos. Para más información, consulte las :guilabel:`reglas de" +" Impuestos` en la pestaña :guilabel:`artículos del diario` de cualquier " +"factura." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 msgid "see which tax grids are used to record transactions in Odoo Accounting" msgstr "" +"vea las tablas de impuestos que se utilizan para registrar las transacciones" +" en la aplicación Contabilidad de Odoo" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:59 msgid "" @@ -12404,10 +12682,15 @@ msgid "" "can edit your tax settings, along with the tax grids that are used to record" " invoices or credit notes." msgstr "" +"Si desea configurar sus tablas de impuestos, vaya a " +":menuselection:`Contabilidad --> Configuración --> Impuestos`, y abra el " +"impuesto que desee modificar. Una vez ahí, podrá editar la configuración de " +"sus impuestos, junto con las tablas de impuestos que se utilizan para " +"registrar facturas o notas de crédito." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 msgid "Configure taxes and their tax grids in Odoo Accounting" -msgstr "" +msgstr "Configuración de impuestos y sus tablas de impuestos" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:68 msgid "" @@ -12415,6 +12698,10 @@ msgid "" " localization package ` is installed " "according to the country you select at the creation of your database." msgstr "" +"Por lo general, los impuestos y los reportes ya están preconfigurados en " +"Odoo mediante los :ref:`paquetes de localización fiscal " +"` que se instalan dependiendo del país que " +"seleccione al crear su base de datos." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:75 msgid "Close a tax period" @@ -12431,6 +12718,10 @@ msgid "" "to make sure that no change can be made to a report once its period is " "closed." msgstr "" +"Cualquier nueva transacción con fecha contable anterior a la " +":guilabel:`fecha de bloqueo de impuestos` desplazará sus valores fiscales al" +" siguiente periodo fiscal abierto. Esta función es útil para evitar que se " +"realicen cambios en un reporte una vez que haya cerrado su periodo." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:86 msgid "" @@ -12439,16 +12730,26 @@ msgid "" "add transactions that would have an impact on the :guilabel:`Closing Journal" " Entry`, which can help you avoid some tax declaration errors." msgstr "" +"Por lo tanto, le recomendamos bloquear su fecha fiscal antes de realizar su " +":guilabel:`asiento contable de cierre`. De esta forma, otros usuarios no " +"podrán modificar o añadir transacciones que repercutirían en el " +":guilabel:`asiento contable de cierre`, lo que puede ayudarle a evitar " +"errores en la declaración de impuestos." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:91 msgid "" "To check the current :guilabel:`Tax Lock Date`, or to edit it, go to " ":menuselection:`Accounting --> Accounting --> Actions: Lock Dates`." msgstr "" +"Para consultar o editar su :guilabel:`fecha de bloqueo de impuestos` actual," +" vaya a :menuselection:`Contabilidad --> Contabilidad --> Acciones: bloquear" +" fechas`." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 msgid "Lock your tax for a specific period in Odoo Accounting" msgstr "" +"Bloquear impuestos durante un periodo específico en la aplicación " +"Contabilidad de Odoo" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:103 msgid "" @@ -12461,10 +12762,20 @@ msgid "" "`PDF` and XLSX. These include all the values to report to the tax " "authorities, along with the amount you have to pay or be refunded." msgstr "" +"Una vez que se hayan contabilizado todas las transacciones que incluyen " +"impuestos durante el periodo que desea reportar, haga clic en " +":guilabel:`Reporte de impuestos` en :menuselection: `Contabilidad --> " +"Reportes --> Reportes de auditoría: reporte de impuestos`. Asegúrese de " +"seleccionar el periodo correcto que desea declarar mediante el filtro de " +"fechas, de este modo podrá tener una visión general de su reporte de " +"impuestos. Desde esta vista, puede acceder fácilmente a diferentes formatos " +"de su reporte de impuestos, como `PDF` y XLSX. En estos se incluyen todos " +"los valores que debe declarar a Hacienda, junto con el importe que debe " +"pagar o que le será devuelto." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 msgid "download the PDF with your Tax Report in Odoo Accounting" -msgstr "" +msgstr "descargue el PDF con su reporte de impuestos" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:115 msgid "" @@ -12474,6 +12785,11 @@ msgid "" "prevent some fiscal errors, but it is advised to lock your tax date manually" " before, as described above." msgstr "" +"Si olvidó bloquear su fecha fiscal antes de hacer clic en :guilabel:`Cerrar " +"asiento contable`, Odoo bloqueará automáticamente su periodo fiscal en la " +"misma fecha que la fecha contable de su asiento. Este mecanismo de seguridad" +" puede prevenir algunos errores fiscales, pero se aconseja bloquear su fecha" +" fiscal de forma manual, como se describió anteriormente." #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:121 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:37 @@ -12488,7 +12804,7 @@ msgstr ":doc:`../get_started`" #: ../../content/applications/finance/accounting/reporting/year_end.rst:3 msgid "Year-end closing" -msgstr "" +msgstr "Cierre del ejercicio" #: ../../content/applications/finance/accounting/reporting/year_end.rst:5 msgid "" @@ -12535,7 +12851,7 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/year_end.rst:25 msgid "Manage fiscal years" -msgstr "" +msgstr "Administrar años fiscales" #: ../../content/applications/finance/accounting/reporting/year_end.rst:27 msgid "" @@ -12562,6 +12878,8 @@ msgid "" "Go to :menuselection:`accounting --> configuration --> settings` and " "activate the fiscal years." msgstr "" +"Vaya a :menuselection:`Contabilidad --> Configuración --> Ajustes` y active " +"los periodos fiscales." #: ../../content/applications/finance/accounting/reporting/year_end.rst:38 msgid "" @@ -12749,6 +13067,11 @@ msgid "" "the **Taxes** field with the Default Taxes when you create a new product or " "add a new line on an invoice." msgstr "" +"Los **Impuestos predeterminados** definen cuáles impuestos se seleccionan " +"automáticamente cuando no hay ninguna otra indicación sobre qué impuesto " +"usar. Por ejemplo, Odoo completa previamente el campo **Impuestos** con los " +"impuestos predeterminados cuando se crea un nuevo producto o se añade una " +"nueva línea en una factura." #: ../../content/applications/finance/accounting/taxes.rst-1 msgid "" @@ -13121,6 +13444,9 @@ msgid "" "**Tax Grids**: used to generate :doc:`Tax Reports ` " "automatically, according to your country's regulations." msgstr "" +"**Tablas de impuestos**: se usan para generar :doc:`reportes de impuestos " +"` de forma automática, de acuerdo a las normativas de" +" su país." #: ../../content/applications/finance/accounting/taxes.rst:197 msgid "Advanced Options tab" @@ -13166,6 +13492,9 @@ msgid "" "when you must record differently the same tax according to :doc:`Fiscal " "Positions `." msgstr "" +"Los grupos de impuestos incluyen diferentes repeticiones del mismo impuesto." +" Esto puede ser útil cuando se debe registrar de forma diferente el mismo " +"impuesto según las :doc:`posiciones fiscales `." #: ../../content/applications/finance/accounting/taxes.rst-1 msgid "The Tax Group name is different from the Label on Invoices" @@ -13242,6 +13571,8 @@ msgid "" "If you need to define prices accurately, both tax-included and tax-excluded," " please refer to the following documentation: :doc:`taxes/B2B_B2C`." msgstr "" +"Si necesita definir los precios con precisión, tanto con o sin impuestos, " +"consulte la siguiente documentación: :doc:`taxes/B2B_B2C`." #: ../../content/applications/finance/accounting/taxes.rst:262 msgid "" @@ -13340,7 +13671,7 @@ msgstr ":doc:`reporting/tax_returns`" #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:3 msgid "B2B (tax excluded) and B2C (tax included) pricing" -msgstr "" +msgstr "Precios B2B (impuestos no incluidos) y B2C (impuestos incluidos)" #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:5 msgid "" @@ -14084,6 +14415,12 @@ msgid "" "remotely, typically through online platforms, mail orders, telephone, or " "other means of communication." msgstr "" +"Las ventas a distancia intracomunitarias en la UE involucran el comercio " +"transfronterizo de bienes y servicios de proveedores registrados a efectos " +"del IVA a personas físicas (B2C) situadas en un Estado miembro de la Unión " +"Europea. La transacción se realiza a distancia, por lo general a través de " +"plataformas en línea, pedidos por correo, teléfono u otros medios de " +"comunicación." #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:10 msgid "" @@ -14091,12 +14428,16 @@ msgid "" "regulations. The vendor must charge VAT per the VAT rate applicable in the " "buyer's country." msgstr "" +"Las ventas a distancia intracomunitaria en la UE están sujeta a normas y " +"reglamentos específicos relacionados con el IVA. El proveedor debe cambiar " +"el IVA según el país del comprador." #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:14 msgid "" "This remains applicable even if the vendor is located outside of the " "European Union." msgstr "" +"Esto es válido incluso si el proveedor no forma parte de la Unión Europea." #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:19 msgid "" @@ -14106,6 +14447,12 @@ msgid "" ":menuselection:`Accounting --> Configuration --> Settings --> Taxes`, tick " ":guilabel:`EU Intra-community Distance Selling`, and :guilabel:`Save`." msgstr "" +"La función **venta a distancia intracomunitaria de la UE** le ayuda a " +"cumplir esta normativa con la creación y configuración de nuevas " +"**posiciones fiscales** e **impuestos** según el país de su empresa. Para " +"activarla, vaya a :menuselection:`Contabilidad --> Configuración --> Ajustes" +" --> Impuestos`, marque :guilabel:`venta a distancia intracomunitaria UE`, y" +" :guilabel:`guardar`." #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst-1 msgid "" @@ -14121,6 +14468,11 @@ msgid "" " --> Taxes --> EU Intra-community Distance Selling` and click on the " ":guilabel:`Refresh tax mapping`." msgstr "" +"Si desea que sus posiciones fiscales se actualicen automáticamente cada vez " +"que añada o modifique impuestos, vaya a " +":menuselection:`Contabilidad/Facturación --> Ajustes --> Impuestos --> Venta" +" a distancia intracomunitaria de la UE` y haga clic en :guilabel: " +"`Actualizar mapeo de impuestos`." #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:33 msgid "" @@ -14132,7 +14484,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:42 msgid "One-Stop Shop (OSS)" -msgstr "" +msgstr "Tienda todo en uno" #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:44 msgid "" @@ -14144,6 +14496,15 @@ msgid "" " are **two primary schemes**: the **Union OSS** scheme for cross-border " "services and the **Import OSS** scheme for goods valued at or below €150." msgstr "" +"El sistema `ventanilla única` (OSS, por sus siglas en inglés) introducido " +"por la Unión Europea simplifica la recaudación del IVA en las **ventas " +"transfronterizas** de bienes y servicios. Su uso principal es el de empresa " +"a consumidor **(B2C)**. Gracias al OSS, las empresas pueden registrarse a " +"efectos del IVA en su país de origen y utilizar un portal en línea único " +"para gestionar todos los trámites relacionados con el IVA de sus ventas en " +"la UE. Básicamente existen **dos regímenes**: el **OSS de la Unión** para " +"los servicios transfronterizos y el **OSS de importación** para los bienes " +"cuyo valor sea igual o inferior a 150 euros." #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:52 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:679 @@ -14164,7 +14525,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst-1 msgid "OSS reports view" -msgstr "" +msgstr "Vista de los reportes OSS" #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:65 msgid "" @@ -14429,7 +14790,7 @@ msgstr ":doc:`B2B_B2C`" #: ../../content/applications/finance/accounting/taxes/retention.rst:3 msgid "Withholding taxes" -msgstr "" +msgstr "Retención fiscal" #: ../../content/applications/finance/accounting/taxes/retention.rst:5 msgid "" @@ -22141,9 +22502,9 @@ msgid "" "As part of the configurable information that is sent in the XML, you can " "define the data for the fiscal section and the bank information in the PDF." msgstr "" -"Como parte de la información configurable que se envía en el XML, usted " -"puede definir los datos para la sección fiscal y la información bancaria en " -"el PDF." +"Como parte de la información configurable que se envía en el XML, puede " +"definir los datos para la sección fiscal y la información bancaria en el " +"PDF." #: ../../content/applications/finance/fiscal_localizations/colombia.rst:86 msgid "Configure data required in the XML" @@ -22160,9 +22521,9 @@ msgid "" "their identification number and document type set:" msgstr "" "Como parte de la localización colombiana, los tipos de documentos definidos " -"por el DIAN están ahora disponibles en el formulario del partner. Los " -"partners colombianos deben tener su número de identificación y tipo de " -"documento configurados." +"por el DIAN ahora están disponibles en el formulario del contacto. Deben " +"definir el número de identificación y tipo de documento para sus contactos " +"colombianos." #: ../../content/applications/finance/fiscal_localizations/colombia.rst:101 msgid "" @@ -22170,8 +22531,8 @@ msgid "" "configured in Odoo including the verification digit, Odoo will split this " "number when the data to the third party vendor is sent." msgstr "" -"Cuando el tipo de documento es RUT, el número de identificación necesita " -"configurarse en Odoo incluyendo el dígito verificador, Odoo dividirá este " +"Cuando el tipo de documento es RUT, debe configurar el número de " +"identificación en Odoo incluyendo el dígito verificador. Odoo dividirá este " "número cuando los datos se envíen al proveedor." #: ../../content/applications/finance/fiscal_localizations/colombia.rst:107 @@ -22257,9 +22618,9 @@ msgid "" "The default template that is used by Odoo on the invoice PDF includes the " "job position of the salesperson, so these fields should be configured:" msgstr "" -"La plantilla que Odoo usa automáticamente en el PDF de factura incluye el " -"puesto de trabajo de la o el vendedor, por lo tanto, estos son los campos " -"que deben estar configurados:" +"La plantilla que Odoo usa de manera automática en el PDF de factura incluye " +"el puesto de trabajo de la persona encargada de la venta, por lo que debe " +"configurar los siguientes campos:" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:173 msgid "" @@ -24773,6 +25134,7 @@ msgid "2-digits comparison" msgstr "Comparación de 2 dígitos " #: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:61 msgid "Template" msgstr "Plantilla" @@ -35098,7 +35460,7 @@ msgstr "" "información." #: ../../content/applications/finance/payment_acquirers.rst:267 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:40 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:38 msgid "Configuration tab" msgstr "Pestaña de configuración" @@ -35274,7 +35636,7 @@ msgstr ":ref:`payment_acquirers/add_new`" #: ../../content/applications/finance/payment_acquirers/adyen.rst:10 #: ../../content/applications/finance/payment_acquirers/adyen.rst:137 #: ../../content/applications/finance/payment_acquirers/alipay.rst:36 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:53 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:51 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:47 #: ../../content/applications/finance/payment_acquirers/mollie.rst:31 #: ../../content/applications/finance/payment_acquirers/paypal.rst:162 @@ -35693,49 +36055,317 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:31 msgid "" -"If you are trying Authorize.Net as a test, with a *sandbox account*, change " -"the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a" -" test Odoo database, rather than on your main database." +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." msgstr "" -"Si está probando Authorize.Net con una *cuenta sandbox* , cambie el " -":guilabel:`Estado` a :guilabel:`Modo de prueba`. Le recomendamos hacerlo en " -"una base de datos de prueba de Odoo, en vez de hacerlo en su base de datos " -"principal. " -#: ../../content/applications/finance/payment_acquirers/authorize.rst:35 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:34 msgid "" -"If you set :guilabel:`Test Mode` on Odoo and use an authorize.net account " -"instead of a sandbox.authorize.net account, it results in the following " -"error: *The merchant login ID or password is invalid or the account is " -"inactive*." +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." msgstr "" -"Si estableció el :guilabel:`Modo de prueba` en Odoo y usa una cuenta de " -"Authorize.net en lugar de una cuenta sandbox.authorize.net, causa el " -"siguiente error: *El ID del comerciante o su contraseña no es válida o la " -"cuenta está inactiva*." -#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:41 msgid "Place a hold on a card" msgstr "Hacer una retención de tarjeta de crédito" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:45 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 msgid "" -"With Authorize.net, you can enable the :ref:`manual capture " +"With Authorize.Net, you can enable the :ref:`manual capture " "`. If enabled, the funds are " "reserved for 30 days on the customer's card, but not charged yet." msgstr "" -"Con Authorize.net, puede activar la :ref:`captura manual " -"`. Si es así, los fondos se " -"reservan por 30 días en la tarjeta del cliente, pero no se realiza el cargo " -"aún. " -#: ../../content/applications/finance/payment_acquirers/authorize.rst:50 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:48 msgid "" "After **30 days**, the transaction is **voided automatically** by " -"Authorize.net." +"Authorize.Net." msgstr "" -"Después de **30 días**, Authorize.net **anula de forma automática** la " -"transacción." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:54 +msgid "Import an Authorize.Net statement" +msgstr "Importar un estado de cuenta de Authorize.Net " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:57 +msgid "Export from Authorize.Net" +msgstr "Exportar desde Authorize.Net" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:63 +msgid "" +"`Download the Excel import template " +"`_" +msgstr "" +"`Descargue la plantilla de Excel para realizar una importación " +"`_" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:65 +msgid "To export a statement:" +msgstr "Para exportar un estado de cuenta: " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:67 +msgid "Log in to Authorize.Net." +msgstr "Inicie sesión en Authorize.Net" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:68 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" +"Vaya a :menuselection:`Cuenta --> Estados de cuenta --> Estado de cuenta de " +"cierre eCheck.Net`." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:69 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" +"Defina un rango de exportación utilizando una liquidación por lotes de " +"*apertura* y de *cierre*. Todas las transacciones dentro de ambas " +"liquidaciones por lotes se exportarán a Odoo. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:71 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template `." +msgstr "" +"Seleccione todas las transacciones dentro del rango que desee, cópielas y " +"péguelas en la hoja :guilabel:`Descarga Reporte 1` de la :ref:`Plantilla de " +"Excel de importación `." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "Selección de las transacciones de Authorize.Net para importar" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "Liquidación por lotes de un extracto de Authorize.net" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:84 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" +"En este caso, el primer lote del año (01/01/2021) pertenece a la liquidación" +" del 31/12/2020, entonces la liquidación de **apertura** es del 31/12/2020. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:87 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" +"Una vez que los datos estén en la hoja :guilabel:`Descarga Reporte 1`: " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:89 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" +"Vaya a la pestaña de :guilabel:`Búsqueda de transacciones` en Authorize.Net." +" " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:90 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" +"En la sección :guilabel:`Fecha de liquidación` seleccione el rango de las " +"fechas de liquidación por lotes usado anteriormente en los campos " +":guilabel:`Desde:` y :guilabel:`Hasta:` y haga clic en :guilabel:`Buscar`." +" " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:92 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" +"Cuando se genere la lista, haga clic en :guilabel:`Descargar en el archivo`." +" " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:93 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" +"En la ventana emergente, seleccione :guilabel:`Campos expandidos con " +"respuesta CAVV/Separados por comas`, active la opción :guilabel:`Incluir " +"encabezados de las columnas` y haga clic en :guilabel:`Enviar`. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:95 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"`." +msgstr "" +"Abra el archivo de texto , seleccione :guilabel:`Todos`, copie los datos y " +"péguelos en la hoja :guilabel:`Descargra Reporte 2 Download` de la " +":ref:`plantilla de Excel para importar `." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:97 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template `. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" +"Las líneas de tránsito se completan y actualizan automáticamente en las " +"hojas :guilabel:`tránisto para el reporte 1` y :guilabel:`tránsito para el " +"reporte 2` de la :ref:`plantilla de Excel para importar `. Asegúrese de que todas las entradas estén presentes y **si no es" +" el caso**, copie la formula de las líneas previamente completadas de las " +"hojas :guilabel:`tránsito para el reporte 1` o del :guilabel:`2` y péguelas " +"en las líneas vacías. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:104 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" +"Para obtener el balance de cierre correcto, *no* elimine ninguna línea de " +"las hojas de Excel. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:107 +msgid "Import into Odoo" +msgstr "Importar a Odoo " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:109 +msgid "To import the data into Odoo:" +msgstr "Para importar los datos a Odoo: " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:111 +msgid "Open the :ref:`Excel import template `." +msgstr "" +"Abra la :ref:`plantilla de Excel para importar `." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:112 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" +"Copie los datos de la hoja :guilabel:`tránsito para el reporte 2` y use la " +"opción de *pegado especial* para pegar solo los valores en la hoja " +":guilabel:`Importar de Odoo a CSV`. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:114 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" +"Busque las celdas *azules* en la hoja :guilabel:`Importar de Odoo a CSV`. " +"Son asientos de devolución sin número de referencia. Puesto que no se pueden" +" importar así, vaya a :menuselection:`Authorize.Net --> Cuenta --> Extractos" +" --> Extracto de cierre eCheck.Net`. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:117 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" +"Busque la opción :guilabel:`Cobrar transacción/Devolución`, y haga clic ahí." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:118 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" +"Copie la descripción de la factura, péguela en la celda " +":guilabel:`Etiqueta` de la hoja :guilabel:`Importar de Odoo a CSV` y agregue" +" `Devolución /` antes de la descripción. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:120 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template ` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" +"Si hay varias facturas, agregue una línea a la :ref:`Plantilla de Excel de " +"importación ` por cada factura y copie y pegue la" +" descripción en cada respectiva línea de :guilabel:`Etiqueta`. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:125 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template ` for each invoice." +msgstr "" +"Para **devoluciones/reembolsos combinados** en los pagos, cree una nueva " +"línea en la :ref:`Plantilla de Excel de importación ` para cada factura. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 +msgid "Chargeback description" +msgstr "Descripción de un contracargo" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:133 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" +"Luego, elimine las líneas de apuntes de *transacción cero* y *transacción " +"anulada*, y cambie el formato de la columna :guilabel:`Importe` a *Número* " +"en la hoja :guilabel:`Importar de Odoo a CSV`. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:135 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" +"Regrese a :menuselection:`Extracto de cierre eCheck.Net --> Buscar una " +"transacción` y busque de nuevo las fechas de liquidación por lotes que uso " +"anteriormente. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:137 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" +"Verifique que las fechas de liquidación por lotes en eCheck.Net coincidan " +"con las fechas de los pagos correspondientes que se encuentran en la columna" +" de :guilabel:`Fecha` de la hoja :guilabel:`Importar de Odoo a Odoo CSV`. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:139 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" +"Si no coinciden, reemplace la fecha con la que aparece en eCheck.Net. Filtre" +" la columna por *fecha* y asegúrese de que el formato sea `MM/DD/AAAA`. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:141 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" +"Copie los datos, incluyendo los encabezados de la columna, de la hoja " +":guilabel:`Importar de Odoo a CSV`, péguelos en un nuevo archivo de Excel y " +"guárdelo como formato CSV. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:143 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" +"Abra la aplicación Contabilidad, vaya a :menuselection:`Configuración --> " +"Diarios`, seleccione la casilla :guilabel:`Authorize.Net` y haga clic en " +":menuselection:`Favoritos--> Importar registros --> Cargar archivo`. " +"Seleccione el archivo CSV y súbalo a Odoo. " + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:148 +msgid "" +"List of `eCheck.Net return codes " +"`_" +msgstr "" +"Lista de `eCheck.Net códigos de reembolso de " +"`_" #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:3 msgid "Buckaroo" diff --git a/locale/es/LC_MESSAGES/general.po b/locale/es/LC_MESSAGES/general.po index d234fd5a8..3c627d0f9 100644 --- a/locale/es/LC_MESSAGES/general.po +++ b/locale/es/LC_MESSAGES/general.po @@ -23,10 +23,10 @@ # Nelson Ramírez , 2023 # Pablo Rojas , 2023 # Fernanda Alvarez, 2023 -# Patricia Gutiérrez Capetillo , 2023 # Martin Trigaux, 2023 # Braulio D. López Vázquez , 2023 # Iran Villalobos López, 2023 +# Patricia Gutiérrez Capetillo , 2023 # #, fuzzy msgid "" @@ -35,7 +35,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-07-07 06:24+0000\n" "PO-Revision-Date: 2021-11-02 08:47+0000\n" -"Last-Translator: Iran Villalobos López, 2023\n" +"Last-Translator: Patricia Gutiérrez Capetillo , 2023\n" "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -71,7 +71,7 @@ msgstr "" #: ../../content/applications/general/apps_modules.rst-1 msgid "Add \"Extra\" filter in Odoo Apps" -msgstr "" +msgstr "Agregar un filtro \"Adicional\" en las aplicaciones de Odoo." #: ../../content/applications/general/apps_modules.rst:16 msgid "" @@ -198,6 +198,9 @@ msgid "" "Therefore, uninstalling one app may uninstall multiple apps and modules. " "Odoo warns you which dependent apps and modules are affected by it." msgstr "" +"Algunas aplicaciones dependen una de la otra, por lo que si desinstala una " +"de las aplicaciones, es posible que se desinstalen varias aplicaciones y " +"módulos." #: ../../content/applications/general/apps_modules.rst:72 msgid "To complete the uninstallation, click on *Confirm*." @@ -427,7 +430,7 @@ msgstr "" #: ../../content/applications/general/auth/azure.rst:3 msgid "Microsoft Azure sign-in authentication" -msgstr "" +msgstr "Autenticación de inicio de sesión de Microsoft Azure" #: ../../content/applications/general/auth/azure.rst:5 msgid "" @@ -456,6 +459,9 @@ msgid "" "The *Google Sign-In Authentication* is a useful function that allows Odoo " "users to sign in to their database with their Google account." msgstr "" +"La *autenticación de inicio de sesión de Odoo* es una función útil que " +"permite que los usuarios de Odoo inicien sesión en su base de datos desde su" +" cuenta de Goole." #: ../../content/applications/general/auth/google.rst:8 msgid "" @@ -463,6 +469,8 @@ msgid "" "wants employees within the organization to connect to Odoo using their " "Google Accounts." msgstr "" +"Esto es muy útil, en especial si la empresa usa Workspace de Google y quiere" +" que los empleados se conecten a Odoo con su cuenta de Google." #: ../../content/applications/general/auth/google.rst:12 msgid ":doc:`/applications/productivity/calendar/google`" @@ -484,6 +492,8 @@ msgid "" "The integration of the Google sign-in function requires configuration both " "on Google *and* Odoo." msgstr "" +"Integrar el inicio de sesión de Google requiere que se configure tanto " +"*Odoo* como *Google*." #: ../../content/applications/general/auth/google.rst:25 msgid "Google API Dashboard" @@ -502,14 +512,17 @@ msgid "" "on :guilabel:`Create Project`, fill out the project name and other details " "of the company, and click on :guilabel:`Create`." msgstr "" +"Asegúrese de que abrió el proyecto correcto. Si todavía no hay un proyecto, " +"haga clic en :guilabel:`Crear proyecto`, llene el nombre del proyecto y los " +"otros detalles de la empresa y después haga clic en :guilabel:`Crear`." #: ../../content/applications/general/auth/google.rst:0 msgid "Filling out the details of a new project." -msgstr "" +msgstr "Llenar los detalles de un nuevo proyecto." #: ../../content/applications/general/auth/google.rst:37 msgid "Choose the name of the company from the drop-down menu." -msgstr "" +msgstr "Elija el nombre de la empresa desde el menú desplegable." #: ../../content/applications/general/auth/google.rst:42 msgid "OAuth consent screen" @@ -523,17 +536,19 @@ msgstr "" #: ../../content/applications/general/auth/google.rst:0 msgid "Google OAuth consent selection menu." -msgstr "" +msgstr "Selección del menú de consentimiento de Google OAuth" #: ../../content/applications/general/auth/google.rst:50 msgid "" "Choose one of the options (:guilabel:`Internal` / :guilabel:`External`), and" " click on :guilabel:`Create`." msgstr "" +"Elija una de las opciones (:guilabel:`Interno` / :guilabel:`Externo`) y haga" +" clic en :guilabel:`Crear`." #: ../../content/applications/general/auth/google.rst:0 msgid "Choice of a user type in OAuth consent." -msgstr "" +msgstr "Elegir un tipo de usuario en el consentimiento de OAuth." #: ../../content/applications/general/auth/google.rst:58 msgid "" @@ -562,12 +577,16 @@ msgid "" "Fill out the required details and domain info, then click on :guilabel:`Save" " and Continue`." msgstr "" +"Llene los detalles requeridos y la información de dominio, después haga clic" +" en :guilabel:`Guardar y crear`." #: ../../content/applications/general/auth/google.rst:66 msgid "" "On the :menuselection:`Scopes` page, leave all fields as is, and click on " ":guilabel:`Save and Continue`." msgstr "" +"En la página de :guilabel:`Alcance` deje todos los campos como están y " +"después haga clic en :guilabel:`Guardar y continuar`." #: ../../content/applications/general/auth/google.rst:68 msgid "" @@ -576,6 +595,11 @@ msgid "" ":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " "summary of the app registration appears." msgstr "" +"Si sigue en el modo de prueba (*Externo*), para agregar las direcciones de " +"correo que configuró en el paso :guilabel:`Usuarios de prueba` haga clic en " +":guilabel:`Add Users` (agregar usuarios) y después en el botón " +":guilabel:`Save and Continue` (guardr y continuar). Aparecerá un resumen del" +" registro de la aplicación." #: ../../content/applications/general/auth/google.rst:71 msgid "" @@ -595,23 +619,27 @@ msgstr "" #: ../../content/applications/general/auth/google.rst:0 msgid "Credentials button menu." -msgstr "" +msgstr "Menú de botones de las credenciales" #: ../../content/applications/general/auth/google.rst:84 msgid "" "Click on :guilabel:`Create Credentials`, and select :guilabel:`OAuth client " "ID`." msgstr "" +"Haga clic en :guilabel:`Crear credenciales`, y seleccione :guilabel:`ID de " +"cliente de OAuth`." #: ../../content/applications/general/auth/google.rst:0 msgid "OAuth client id selection." -msgstr "" +msgstr "Selección del ID del cliente OAuth." #: ../../content/applications/general/auth/google.rst:90 msgid "" "Select :guilabel:`Web Application` as the :guilabel:`Application Type`. Now," " configure the allowed pages on which Odoo will be redirected." msgstr "" +"Seleccione :guilabel:`Aplicación Web` como :guilabel:`Tipo de aplicación`. " +"Ahora configure las páginas permitidas a las que se va a redirigir Odoo." #: ../../content/applications/general/auth/google.rst:93 msgid "" @@ -620,6 +648,11 @@ msgid "" "For example: `https://mydomain.odoo.com/auth_oauth/signin`, then click on " ":guilabel:`Create`." msgstr "" +"Para lograrlo, en el campo de :guilabel:`URL de redirección autorizadas` " +"ingrese el dominio de su base de datos inmediatamente seguido por " +"``/auth_oauth/signin``. Por ejemplo: " +"``https://midominio.odoo.com/auth_oauth/signin`` y luego haga clic en " +":guilabel:`Crear`." #: ../../content/applications/general/auth/google.rst:97 msgid "" @@ -628,6 +661,10 @@ msgid "" ":guilabel:`Client ID` for later, as it will be necessary for the " "configuration in Odoo, which will be covered in the following steps." msgstr "" +"Ya que se creó el *cliente OAuth*, aparecerá una pantalla con el " +":guilabel:`ID del cliente` y el :guilabel:`Secreto del cliente`. Copie el " +":guilabel:`ID del cliente` para después, ya que lo necesitará para realizar " +"la configuración en Odoo, la cual explicaremos en los siguientes pasos." #: ../../content/applications/general/auth/google.rst:104 msgid "Google Authentication on Odoo" @@ -643,10 +680,13 @@ msgid "" "API Dashboard: :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the" " :guilabel:`Client ID`." msgstr "" +"Una vez que se completen los pasos previos, se generan dos llaves en el " +"tablero del API de Google, :guilabel:`ID del cliente` y :guilabel:`Secreto " +"del cliente`. Copie el :guilabel:`ID del cliente`." #: ../../content/applications/general/auth/google.rst-1 msgid "Google OAuth Client ID generated." -msgstr "" +msgstr "ID del cliente de Google OAuth que se generío.," #: ../../content/applications/general/auth/google.rst:121 msgid "Odoo activation" @@ -657,10 +697,14 @@ msgid "" "Go to :menuselection:`Odoo General Settings --> Integrations` and activate " ":guilabel:`OAuth Authentication`." msgstr "" +"Vaya a :menuselection:`Ajustes generales de Odoo --> Integraciones` y active" +" la :guilabel:`Autenticación OAuth`." #: ../../content/applications/general/auth/google.rst:127 msgid "Odoo may prompt the user to log-in again after this step." msgstr "" +"Es posible que Odoo le pida al usuario volver a iniciar sesión después de " +"este paso." #: ../../content/applications/general/auth/google.rst:129 msgid "" @@ -671,10 +715,16 @@ msgid "" ":guilabel:`Client ID` with the key from the Google API Dashboard, and " ":guilabel:`Save`." msgstr "" +"Regrese a :menuselection:`Ajustes generales --> Integraciones --> " +"Autenticación OAuth`, active la selección y :guilabel:`Guarde`. Después, " +"regrese a :menuselection:`Ajustes generales --> Integraciones --> " +"Autenticación de Google` y active la selección. Ahora llene el :guilabel:`ID" +" del cliente` con la llave que obtuvo desde el tablero API de Google. " +"Después haga clie en :guilabel:`Guardar`." #: ../../content/applications/general/auth/google.rst:0 msgid "Filling out the client id in Odoo settings." -msgstr "" +msgstr "Llenar el ID del cliente en los ajustes de Odoo." #: ../../content/applications/general/auth/google.rst:139 msgid "" @@ -682,6 +732,9 @@ msgid "" ":guilabel:`OAuth Providers` under the :guilabel:`OAuth Authentication` " "heading in :menuselection:`Integrations`." msgstr "" +"También puede acceder a la configuración de Google OAuth desde " +":guilabel:`Proveedores OAuth` abajo del título :guilabel:`Autenticación " +"OAuth` en :menuselection:`Integraciones`." #: ../../content/applications/general/auth/google.rst:145 msgid "Log in to Odoo with Google" @@ -692,10 +745,15 @@ msgid "" "To link the Google account to the Odoo profile, click on :guilabel:`Log in " "with Google` when first logging into Odoo." msgstr "" +"Para vincular su cuenta de Google con el perfil de Odoo, haga clic en " +":guilabel:`Iniciar sesión con Google` la primera vez que inicie sesión en " +"Odoo." #: ../../content/applications/general/auth/google.rst:0 msgid "Reset password screen with \"Log in with Google\" button." msgstr "" +"Pantalla para cambiar la contraseña con el botón \"Iniciar sesión con " +"Google\"." #: ../../content/applications/general/auth/google.rst:155 msgid "" @@ -704,6 +762,10 @@ msgid "" "directly click on :guilabel:`Log in with Google`, instead of choosing a new " "password." msgstr "" +"Los usuarios existentes deben :ref:`restablecer su contraseña " +"` para ir a la página de " +":menuselection:`Restablcer contraseña`. Los usuarios nuevos puede hacer clic" +" en :guilabel:`Acceder con Google` en lugar de elegir una nueva contraseña." #: ../../content/applications/general/auth/google.rst:160 msgid "" @@ -792,6 +854,9 @@ msgid "" " the :ref:`command palette ` or the" " :ref:`URL `." msgstr "" +"El modo de desarrollador (o solución de bugs) desbloquea otras herramientas " +"de Odoo adicionales y más avanzadas. Hay muchas maneras de activar el modo " +"desarrollador: en los :ref:`ajustes`" #: ../../content/applications/general/developer_mode.rst:17 msgid "Activate through the Settings" @@ -805,10 +870,12 @@ msgid "" "to be installed for the :guilabel:`Developer Tools` section to appear in the" " :guilabel:`Settings` module." msgstr "" +"El modo de solución de bugs se puede activar desde los ajustes de la base de" +" datos. " #: ../../content/applications/general/developer_mode.rst-1 msgid "Overview of the debug options under settings in Odoo." -msgstr "" +msgstr "Resumen de las opciones de solución de bugs en los ajustes de Odoo." #: ../../content/applications/general/developer_mode.rst:29 msgid "" @@ -816,16 +883,21 @@ msgid "" " :guilabel:`Activate the developer mode (with tests assets)` is used by " "developers and testers." msgstr "" +"Los desarrolladores usan :guilabel:`Activar modo de desarrollador (con " +"activos)`, mientras que :guilabel:`Activar modo de desarrollador (con " +"activos de prueba)` los desarrolladores y testers." #: ../../content/applications/general/developer_mode.rst:32 msgid "" "Once activated, the :guilabel:`Deactivate the developer mode` option becomes" " available." msgstr "" +"Una vez que lo active, la opción :guilabel:`Desactivar el modo " +"desarrollador` se vuelve disponible." #: ../../content/applications/general/developer_mode.rst:37 msgid "Activate through the browser extension" -msgstr "" +msgstr "Activar a través de una extensión del navegador" #: ../../content/applications/general/developer_mode.rst:39 msgid "" @@ -833,6 +905,9 @@ msgid "" "search for the `Odoo Debug` extension. Once the extension is installed, a " "new icon will be shown on the browser's toolbar." msgstr "" +"Dentro del navegador, vaya a los ajustes, extensiones y después busque la " +"extensión `Solucionar bugs de Odoo`. Después de que instale la extensión " +"aparecerá un nuevo icono en la barra de herramientas del navegador." #: ../../content/applications/general/developer_mode.rst:43 msgid "" @@ -847,6 +922,8 @@ msgstr "" #: ../../content/applications/general/developer_mode.rst-1 msgid "View of Odoo's debug icon in a Google Chrome toolbar." msgstr "" +"Vista del icono de solución de bugs de Odoo en la barra de herramientas de " +"Google Chrome." #: ../../content/applications/general/developer_mode.rst:53 msgid "Activate through the command palette" @@ -858,10 +935,14 @@ msgid "" "First, open the command palette tool with the keyboard shortcut `ctrl+k` and" " then type `debug`. A command will show up to activate the debug mode." msgstr "" +"En Odoo, la paleta de comandos tiene un comando con el que puede activar el " +"modo de solución de bugs. Primero abra la herramienta de paleta de comandos " +"con el atajo `ctrl+k` y después escriba `solución de bugs`. Aparecerá un " +"comando con el que podrá activar el modo de solución de bugs." #: ../../content/applications/general/developer_mode.rst-1 msgid "Command palette with debug command." -msgstr "" +msgstr "La paleta de comandos con un comando de solución de bugs." #: ../../content/applications/general/developer_mode.rst:66 msgid "Activate through the URL" @@ -873,10 +954,14 @@ msgid "" "database's URL. In the URL, add `?debug=1` or `?debug=true` after `/web`. To" " deactivate the debug mode, change the value to `?debug=0` instead." msgstr "" +"También puede activar el modo de solución de bugs si agrega una string " +"adicional de query a la URL de la base de datos. En la URL agregue " +"`?debug=1` o `?debug=true` después de `/web`. Para desactivar el modo de " +"solución de bugs cambie el valor a `?debug=0`." #: ../../content/applications/general/developer_mode.rst-1 msgid "Overview of a URL with the debug mode command added." -msgstr "" +msgstr "Una URL con el comando del modo de solución de bugs agregado." #: ../../content/applications/general/developer_mode.rst:77 msgid "" @@ -892,7 +977,7 @@ msgstr "" #: ../../content/applications/general/developer_mode.rst:84 msgid "Locate the developer mode tools" -msgstr "" +msgstr "Localice las herramientas del modo de desarrollador." #: ../../content/applications/general/developer_mode.rst:86 msgid "" @@ -900,10 +985,14 @@ msgid "" "from the :guilabel:`Open Developer Tools` button, the bug icon located in " "the header of the Odoo database." msgstr "" +"Una vez que activó el modo de desarrollador, puede ingresar a las " +"herramientas del modo desarrollador con el botón :guilabel:`Abrir las " +"herramientas de desarrollador`, el icono de insecto que aparece en la parte " +"superior derecha de la base de datos de Odoo." #: ../../content/applications/general/developer_mode.rst-1 msgid "Overview of a console page and the debug icon being shown in Odoo." -msgstr "" +msgstr "La página de la consola y el icono de solución de bugs en Odoo." #: ../../content/applications/general/developer_mode.rst:93 msgid "" @@ -912,22 +1001,26 @@ msgid "" "filters, actions, and view options, the developer mode tools contain some " "useful menu items such as:" msgstr "" +"Este menú contiene herramientas adicionales que sirven para entender o " +"editar datos técnicos, como la vista o acciones de una página. En la página " +"que tiene filtros, acciones y opciones de vista las herramientas del modo de" +" desarrollador contienen opciones de menú como:" #: ../../content/applications/general/developer_mode.rst:97 msgid ":guilabel:`Edit Action`" -msgstr "" +msgstr ":guilabel:`Editar acción`" #: ../../content/applications/general/developer_mode.rst:98 msgid ":guilabel:`Manage Filters`" -msgstr "" +msgstr ":guilabel:`Gestionar filtros`" #: ../../content/applications/general/developer_mode.rst:99 msgid "Edit the current view (e.g. Kanban, List, Graph, etc.)" -msgstr "" +msgstr "Editar la vista actual (e.g. kanban, lista, gráfico, etc.)" #: ../../content/applications/general/developer_mode.rst:100 msgid "See the :guilabel:`Fields View Get`" -msgstr "" +msgstr "Vea la vista :guilabel:`Ver campos`" #: ../../content/applications/general/digest_emails.rst:3 msgid "Digest Emails" @@ -955,7 +1048,7 @@ msgstr "" #: ../../content/applications/general/digest_emails.rst-1 msgid "Digest Emails section inside General Settings." -msgstr "" +msgstr "Sección Correos electrónicos de resumen dentro los ajustes generales." #: ../../content/applications/general/digest_emails.rst:15 msgid "You can control a variety of settings for your Digest Emails, such as:" @@ -1053,6 +1146,8 @@ msgstr "**Personalizado** - añada sus propios KPI (se requiere Studio)." #: ../../content/applications/general/digest_emails.rst-1 msgid "Customize default Digest Email settings and custom KPIs." msgstr "" +"Personalice los ajustes de correos electrónicos de resumen y los KPI " +"personalizados." #: ../../content/applications/general/digest_emails.rst:52 msgid "Custom digest emails" @@ -1270,11 +1365,11 @@ msgstr "Comunicación por correo electrónico" #: ../../content/applications/general/email_communication/email_domain.rst:3 msgid "Configure DNS records to send emails in Odoo" -msgstr "" +msgstr "Configure los registros DNS para enviar correos en Odoo" #: ../../content/applications/general/email_communication/email_domain.rst:6 msgid "SPAM labels overview" -msgstr "" +msgstr "Resumen de las etiquetas SPAM" #: ../../content/applications/general/email_communication/email_domain.rst:8 msgid "" @@ -1283,6 +1378,11 @@ msgid "" "of Odoo's control, notably the way the different email providers classify " "Odoo's emails according to their own restriction policy and/or limitations." msgstr "" +"De vez en cuando, los proveedores de correo clasifican mal los correos de " +"Odoo y los mandan a la carpeta de spam. Por el momento, Odoo no puede " +"controlar algunos ajustes, sobre todo la forma en la que los proveedores de " +"correo electrónico clasifican los correos provenientes de Odoo según sus " +"propias políticas de restricción o sus limitaciones." #: ../../content/applications/general/email_communication/email_domain.rst:12 msgid "" @@ -1294,6 +1394,12 @@ msgid "" "is greatly improved with the :ref:`notifications configuration " "`." msgstr "" +"En Odoo es estándar recibir correos de `\"nombre del autor\" " +"``, que se puede traducir a ``\"nombre del" +" autor\" <{ICP.mail.from.filter}@{mail.catchall.domain}>``. En este caso, " +"ICP son las siglas de `ir.config.parameters`, que son los parámetros del " +"sistema. Gracias a la :ref:`configuración de notificaciones " +"` mejoramos las entregas." #: ../../content/applications/general/email_communication/email_domain.rst:18 msgid "" @@ -1304,6 +1410,13 @@ msgid "" "is also possible to add the Odoo database domain onto a safe senders list or" " whitelist on the receiving domain." msgstr "" +"Para que sea más fácil que los servidores acepten correos de Odoo, una de " +"las soluciones es que el cliente cree reglas deontro de su propia bandeja de" +" entrega. Se puede agregar un filtro a la bandeja de entrada de manera que " +"cuando se reciba un correo de Odoo (`notifications@mycompany.odoo.com`) este" +" se mueva a la bandeja de entrada. También es posible agregar el dominio de " +"la base de datos de Odoo a la lista de remitentes seguros o a la lista " +"blanca del proveedor de correos." #: ../../content/applications/general/email_communication/email_domain.rst:24 msgid "" @@ -1311,6 +1424,10 @@ msgid "" "ticket `_ and the support team will work to get " "the servers removed from the blacklist." msgstr "" +"Si el servidor de correo de Odoo aparece en una lista negra, notifíquenos " +"mediante un `ticket de soporte nuevo `_ y el " +"equipo de soporte técnico trabajará para que el servidor ya no esté en la " +"lista negra." #: ../../content/applications/general/email_communication/email_domain.rst:28 msgid "" @@ -1322,6 +1439,14 @@ msgid "" "Reporting, & Conformance)`. Ultimately though, it is up to the discretion of" " the final receiving mailbox." msgstr "" +"Si la base de datos de Odoo está usando un dominio personalizado para enviar" +" correos desde Odoo, debe implementar tres registros en el DNS del dominio " +"personalizado para asegurarse de que el correo se entregue. Esto incluye " +"configurar registros para el :abbr:`SPF (Convenio de remitentes, por su " +"sigla en inglés)`, :abbr:`DKIM (DomainKeys Identified Mail)` y :abbr:`DMARC " +"(Autenticación de Mensajes Basada en Dominios, Informes y Conformidad, por " +"sus siglas en inglés)`. Sin embargo, al final del día todo depende del " +"correo que recibe los mensajes." #: ../../content/applications/general/email_communication/email_domain.rst:38 msgid "Be SPF compliant" @@ -1335,6 +1460,12 @@ msgid "" " sending server is on the list of allowed IPs according to the sender's " ":abbr:`SPF (Sender Policy Framework)` record." msgstr "" +"El protocolo del Convenio de remitentes (SPF, por sus siglas en inglés) " +"permite que el dueño del nombre de dominio especifique qué servidores pueden" +" enviar correos desde ese dominio. Cuando un servidor recibe un correo, " +"revisa si la dirección IP del servidor saliente está en la lista de IP " +"permitidas según el registro :abbr:`SPF (Sender Policy Framework)` del " +"remitente." #: ../../content/applications/general/email_communication/email_domain.rst:46 msgid "" @@ -1371,12 +1502,17 @@ msgid "" " record, create one using the following input: `v=spf1 include:_spf.odoo.com" " ~all`" msgstr "" +"Si el nombre del dominio todavía no tiene un registro :abbr:`SPF (Sender " +"Policy Framework)`, escriba `v=spf1 include:_spf.odoo.com ~all` para crear " +"uno." #: ../../content/applications/general/email_communication/email_domain.rst:58 msgid "" "If the domain name already has a :abbr:`SPF (Sender Policy Framework)` " "record, the record must be updated (and do not create a new one)." msgstr "" +"Si el nombre de dominio ya tiene un registro :abbr:`SPF (Sender Policy " +"Framework)`, debe actualizar el registro (no cree uno nuevo)." #: ../../content/applications/general/email_communication/email_domain.rst:63 msgid "" diff --git a/locale/es/LC_MESSAGES/inventory_and_mrp.po b/locale/es/LC_MESSAGES/inventory_and_mrp.po index 74b12565b..8a0b9ceab 100644 --- a/locale/es/LC_MESSAGES/inventory_and_mrp.po +++ b/locale/es/LC_MESSAGES/inventory_and_mrp.po @@ -14,7 +14,6 @@ # José Cabrera Lozano , 2021 # Jesús Alan Ramos Rodríguez , 2021 # Pablo Rojas , 2021 -# Patricia Gutiérrez Capetillo , 2022 # Lina Maria Avendaño Carvajal , 2022 # Mariela Moreno , 2022 # Lucia Pacheco, 2023 @@ -23,6 +22,7 @@ # Braulio D. López Vázquez , 2023 # Fernanda Alvarez, 2023 # Iran Villalobos López, 2023 +# Patricia Gutiérrez Capetillo , 2023 # #, fuzzy msgid "" @@ -31,7 +31,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-07-07 06:24+0000\n" "PO-Revision-Date: 2021-11-02 08:48+0000\n" -"Last-Translator: Iran Villalobos López, 2023\n" +"Last-Translator: Patricia Gutiérrez Capetillo , 2023\n" "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -41,7 +41,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp.rst:5 msgid "Inventory & MRP" -msgstr "" +msgstr "Inventario y MRP" #: ../../content/applications/inventory_and_mrp/inventory.rst:8 msgid "Inventory" @@ -843,30 +843,41 @@ msgid "" " be made to reconcile the differences, and ensure that the recorded counts " "in the database match the actual counts in the warehouse." msgstr "" +"En cualquier sistema de gestión de almacén es posible que los números " +"registrados del inventario en la base de datos no sean los mismos que los " +"verdaderos números en el almacén. Esta discrepancia se puede deber a robo, " +"daños, errores humanos y otros factores. Por lo tanto, se tienen que " +"realizar ajustes de inventario para conciliar las diferencias y asegurarnos " +"de que los números registrados en la base de datos sean los mismos que los " +"número del almacén." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:11 msgid "" "In Odoo, inventory adjustments can be accessed through " ":menuselection:`Inventory --> Operations --> Inventory Adjustments`." msgstr "" +"En Odoo, puede acceder a los ajustes de inventario desde " +":menuselection:`Inventario --> Operaciones --> Ajustes de inventario`." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:14 msgid "" "The :guilabel:`Inventory Adjustments` page shows all products that are " "currently in stock. Each line contains the following information:" msgstr "" +"La página de :guilabel:`Ajustes de inventario` muestra todos los productos " +"que están en existencias. Cada línea contiene la siguiente información:" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:17 msgid ":guilabel:`Product`" -msgstr "" +msgstr ":guilabel:`Producto`" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:18 msgid ":guilabel:`Lot/Serial Number`" -msgstr "" +msgstr ":guilabel:`Lote/Número de serie`" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:19 msgid ":guilabel:`On Hand Quantity`" -msgstr "" +msgstr ":guilabel:`Cantidad a la mano`" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:22 msgid "Add a new line" @@ -878,6 +889,9 @@ msgid "" "the :guilabel:`Product` and :guilabel:`Counted Quantity` fields. Then click " ":guilabel:`Save`." msgstr "" +"Para agregar una línea de ajuste de inventario, haga clic en " +":guilabel:`Crear` y llene los campos de guilabel:`Producto` y " +":guilabel:`Cantidades contadas`. Después haga clic en :guilabel:`Guardar`." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:27 msgid "" @@ -885,6 +899,9 @@ msgid "" "quantity on hand is not yet updated to match the new :guilabel:`Counted " "Quantity`." msgstr "" +"Hasta este punto, registramos la cantidad, pero todavía no la *aplicamos*. " +"Esto significa que la cantidad a la mano no se ha actualizado para que sea " +"la misma que :guilabel:`las cantidades contadas`." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:30 msgid "" @@ -893,16 +910,23 @@ msgid "" ":guilabel:`Apply All` is clicked, a reference or reason can be entered " "before clicking :guilabel:`Apply`." msgstr "" +"Para aplicar la nueva :guilabel:`cantidad contada`, haga clic en " +":guilabel:`Aplicar` en la línea, o en el botón :guilabel:`Aplicar todo` en " +"la parte superior de la página. Si hace clic en :guilabel:`Aplicar todo`, " +"puede ingresar una referencia o una razón antes de hacer clic en " +":guilabel:`Aplicar`." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst-1 msgid "" "Apply all option applies the inventory adjustment once a reason is " "specified." msgstr "" +"La opción Aplicar todo aplica el ajuste de inventario una vez que se " +"especificó la razón." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:40 msgid "Count products" -msgstr "" +msgstr "Conteo de productos" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:42 msgid "" @@ -911,6 +935,10 @@ msgid "" "Adjustments` to update the :guilabel:`Counted Quantity` column for each " "product line." msgstr "" +"Contar productos es una actividad recurrente en los almacenes. Una vez que " +"se completa la cuenta, vaya a :menuselection:`Inventario --> Operaciones -->" +" Ajustes de inventario` para actualizar la columna :guilabel:`Cantidad " +"contada` para cada línea de producto." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:46 msgid "" @@ -920,6 +948,12 @@ msgid "" "Quantity` field. A move with `0.00` :guilabel:`Quantity Done` will be " "recorded in the product's inventory adjustment history." msgstr "" +"Si el conteo es el mismo que :guilabel:`la cantidad a la mano` que se " +"registró en la base de datos, haga clic en :guilabel:`Establecer`. Al hacer " +"esto se copiará el valor del campo :guilabel:`Cantidad a la mano` y se " +"pegará en el campo :guilabel:`Cantidades contadas`. En el historial de " +"ajustes del inventario se registrará un movimiento de `0.00` en " +":guilabel:`Cantidad hecha`." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:51 msgid "" @@ -929,12 +963,20 @@ msgid "" ":guilabel:`On Hand Quantity` and :guilabel:`Counted Quantity` will be " "recorded in the product's inventory adjustment history." msgstr "" +"Si un conteo *no* es igual a la :guilabel:`cantidad a la mano` registrada en" +" la base de datos, registre la cantidad en el campo :guilabel:`Cantidades " +"contadas`. Cuando haga clic en :guilabel:`Establecer` se registrará un " +"movimiento que muestre la diferencia entre :guilabel:`la cantidad a la mano`" +" y :guilabel:`las cantidades contadas` en el historial de ajuste de " +"inventario del producto." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst-1 msgid "" "Inventory Adjustments History dashboard detailing a list of prior product " "moves." msgstr "" +"Tablero del historial de ajustes de inventario donde se muestra la lista " +"antes de los movimientos del producto." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:61 msgid "" @@ -945,22 +987,31 @@ msgid "" "quantity. As an extra caution measure, Odoo will ask for confirmation before" " applying the inventory adjustment." msgstr "" +"A veces se realiza un conteo que no se puede aplicar a la base de datos de " +"inmediato. En el tiempo que pase entre que se realizó el conteo y se aplicó " +"el ajuste de inventario, es posible que ocurran movimientos de inventario. " +"En ese caso, la :guilabel:`cantidad a la mano` dentro de la base de datos " +"puede cambiar y no será consistente con la cantidad que se contó. Como una " +"medida de precaución, Odoo le pedirá confirmación antes de aplicar el ajuste" +" de inventario." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:68 msgid "Plan counts" -msgstr "" +msgstr "Planear conteos" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:70 msgid "Each inventory adjustment line contains the following information:" -msgstr "" +msgstr "Cada línea de ajuste de inventario contiene la información siguiente:" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:72 msgid ":guilabel:`Scheduled Date`: the date at which a count should be made." msgstr "" +":guilabel:`Fecha programada`: la fecha en la que se tiene que realizar el " +"conteo." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:73 msgid ":guilabel:`User`: the person in charge of the count." -msgstr "" +msgstr ":guilabel:`Usuario`: la persona encargada de realizar el conteo." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:74 msgid "" @@ -968,12 +1019,17 @@ msgid "" "accounted. The column is hidden by default, but can be made visible by " "opening the column options icon." msgstr "" +":guilabel:`Fecha contable`: la fecha en la que los ajustes de " +"contabilizarán. Por defecto, la columna estará oculta, pero se puede abrir " +"el icono de opciones de columna para desplegarla." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:78 msgid "" "In the Barcode app, users can only view counts assigned to them that are " "scheduled for today or earlier." msgstr "" +"En la aplicación Código de barras, los usuarios solo podrán ver los conteos " +"que se les han asignado y que están programados para el día de hoy o antes." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:81 msgid "" @@ -981,20 +1037,26 @@ msgid "" ":guilabel:`Inventory Adjustments` page. Then, click :guilabel:`Request a " "Count` and fill in the following information:" msgstr "" +"Para planear conteos grandes, seleccione las líneas de producto deseadas en " +"la página :guilabel:`Ajustes de inventario`. Después, haga clic en " +":guilabel:`Solicitar un recuento` y llene la siguiente información:" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:84 msgid ":guilabel:`Inventory Date`: the planned date of the count." msgstr "" +":guilabel:`Fecha de inventario`: la fecha en la que se programó el recuento." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:85 msgid ":guilabel:`User`: the user responsible for the count." -msgstr "" +msgstr ":guilabel:`Usuario`: la persona encargada de realizar el recuento." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:86 msgid "" ":guilabel:`Accounting Date`: the date at which the inventory adjustment will" " be accounted." msgstr "" +":guilabel:`Fecha contable`: la fecha en la que se registrará el ajuste de " +"inventario." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:87 msgid "" @@ -1003,10 +1065,16 @@ msgid "" "Hand Quantity` of each product line with the current value recorded in the " "database, select :guilabel:`Set Current Value`." msgstr "" +":guilabel:`Número`: para dejar la :guilabel:`cantidad a la mano` de cada " +"producto en blanco, seleccione :guilabel:`Dejar en blanco`. Para llenar " +"desde antes la :guilabel:`cantidad a la mano` de cada línea de producto con " +"el valor que se registró en la base de datos, seleccione " +":guilabel:`Configurar valor actual`." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:91 msgid "Finally, click :guilabel:`Confirm` to request the count." msgstr "" +"Finalmente, haga clic en :guilabel:`Confirmar` para solicitar el conteo." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:93 msgid "" @@ -1016,16 +1084,23 @@ msgid "" "--> Settings --> Operations` and change the date in the :guilabel:`Annual " "Inventory Day and Month` setting." msgstr "" +"Por defecto, después de que se aplica un ajuste de inventario, la fecha " +"programada para el siguiente conteo es el 31 de diciembre del año en curso. " +"Para modificar esta fecha predeterminada, vaya a :menuselection:`Inventario " +"--> Configuración --> Ajustes --> Operaciones` y cambie la fecha en el " +"ajuste :guilabel:`Día y mes del inventario anual`." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst-1 msgid "" "Adjust the next inventory count date with the Annual Inventory Day and Month" " setting." msgstr "" +"Con el ajuste Día y mes del inventario anual podrá ajustar la fecha del " +"siguiente conteo de inventario." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:3 msgid "Cycle counts" -msgstr "" +msgstr "Conteo por ciclos" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:5 msgid "" @@ -1034,12 +1109,19 @@ msgid "" "for the next count is set on the 31st of December. However, for some " "businesses it's crucial to have an accurate inventory count at all times." msgstr "" +"En la mayoría de las empresas, el inventario se cuenta una vez al año. Por " +"eso la siguiente fecha de conteo que se configura de manera automática " +"después de realizar un ajuste de inventario es el 31 de diciembre. Sin " +"embargo, para algunas empresas es muy importante tener un conteo de " +"inventario correcto en todo momento." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:10 msgid "" "The goal of cycle counts is to keep critical stock levels accurate by " "counting more often at key locations." msgstr "" +"La meta de hacer conteo por ciclos es asegurarnos de que los niveles de " +"inventario importantes se mantienen correctos en ubicaciones importantes-" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:16 msgid "" @@ -1049,20 +1131,29 @@ msgid "" "activate the :guilabel:`Storage Locations` setting. Next, click " ":guilabel:`Save` to apply the setting." msgstr "" +"En Odoo, los conteos por ciclo dependen de las ubicaciones; usted define la " +"frecuencia de las cuentas según la ubicación del almacén. Para activar las " +"ubicaciones de almacenes vaya a :menuselection:`Inventario --> Configuración" +" --> Ajustes --> Almacén` y active la opción :guilabel:`Opciones de " +"almacenamiento`. Después, haga clic en :guilabel:`Guardar` para aplicar los" +" ajustes." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst-1 msgid "Enable Storage Locations in Odoo settings." -msgstr "" +msgstr "Activar las ubicaciones de inventario en los ajustes de Odoo." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:26 msgid "Change the inventory frequency" -msgstr "" +msgstr "Cambie la frecuencia de inventario" #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:28 msgid "" "To change a location's inventory frequency, first, go to the locations by " "clicking :menuselection:`Inventory --> Configuration --> Locations`." msgstr "" +"Para cambiar la frecuencia de inventario de una ubicación, primero vaya a " +"las ubicaciones :menuselection:`Inventario --> Configuración --> " +"Ubicaciones`." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:31 msgid "" @@ -1075,10 +1166,19 @@ msgid "" "location, the next scheduled count date will be automatically set based on " "the number of days in the :guilabel:`Inventory Frequency (Days)` setting." msgstr "" +"Después, haga clic en una ubicación para abrir los ajustes de la ubicación y" +" haga clic en :guilabel:`Editar`. En el campo de :guilabel:`Frecuencia de " +"inventario (días)` configure el número de días. Por ejemplo, una ubicación " +"en la que se necesita contar el inventario cada 30 días, configurará el " +"valor de :guilabel:`Frecuencia de inventario (días)` a `30`. Una vez que " +"ingresó el valor, haga clic en :guilabel:`Guardar` para aplicar el ajuste en" +" la ubicación. Ya que se aplicó el ajuste de inventario en esta ubicación, " +"la siguiente fecha de conteo se programará según el número de días que se " +"ingresó en el ajuste :guilabel:`Frecuencia de inventario (días)`." #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst-1 msgid "Edit a location to change the inventory frequency." -msgstr "" +msgstr "Edite una ubicación para cambiar la frecuencia de inventario." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers.rst:5 msgid "Lots and Serial Numbers" @@ -1186,7 +1286,7 @@ msgstr ":doc:`lots`" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:3 msgid "Expiration dates" -msgstr "" +msgstr "Días de caducidad" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:5 msgid "" @@ -1195,6 +1295,10 @@ msgid "" "reduces product loss due to unexpected expiry, and helps to avoid sending " "expired products to customers." msgstr "" +"En Odoo, puede usar los *días de caducidad* para gestionar y dar seguimiento" +" a los ciclos de vida de productos perecederos. SI usa la fecha de caducidad" +" reducirá la pérdida de productos por una caducidad inesperada, además de " +"que ayuda a que evitemos enviar productos que ya caducaron a los clientes." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:9 msgid "" @@ -1204,6 +1308,11 @@ msgid "" "companies (such as food manufacturers) that consistently, or exclusively, " "buy and sell perishable products." msgstr "" +"En Odoo solo le puede agregar información de caducidad a productos que usen " +"*lotes* o *números de serie*. Una vez que asignó un lote o número de serie, " +"podrá configurar una fecha de caducidad. Esto es muy util para empresas que " +"siempre, o casi siempre, venden productos perecederos, como empresas de " +"preparación de alimentos." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:15 #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:17 @@ -1221,7 +1330,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:19 msgid "Enable expiration dates" -msgstr "" +msgstr "Activar las fechas de caducidad" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:21 msgid "" @@ -1230,6 +1339,10 @@ msgid "" ":guilabel:`Traceability` section. Then, click the checkbox to enable the " ":guilabel:`Lots & Serial Numbers` feature." msgstr "" +"Para activar el uso de *fechas de caducidad*, vaya a :menuselection:`la " +"aplicación Inventario --> Configuración --> Ajustes`, y navegue a la sección" +" :guilabel:`Trazabilidad`. Después haga clic en la caja para activar la " +"función de :guilabel:`Lotes y números de serie`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:25 msgid "" @@ -1237,10 +1350,15 @@ msgid "" ":guilabel:`Expiration Dates`. Click that checkbox to enable the feature, and" " be sure to :guilabel:`Save` changes." msgstr "" +"Una vez que active la función, aparecerá una nueva opción para activar las " +":guilabel:`fechas de caducidad`. Marque la casilla para activar la función y" +" asegúrese de :guilabel:`Guardar` los cambios." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 msgid "Enabled lots and serial numbers and expiration dates settings." msgstr "" +"Ajustes de los lotes y números de serie activados y fechas de caducidad " +"activados." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:33 msgid "" @@ -1251,10 +1369,17 @@ msgid "" "features helps with end-to-end traceability, making it easier to manage " "product recalls, identify \"bad\" batches of products, and more." msgstr "" +"Ya que haya activado la función :guilabel:`Lotes y números de serie` " +"aparecerán más funciones para :guilabel:`Mostrar números de lote y de serie " +"en recibos de entrega`, :guilabel:`Mostrar números de lote y de serie en las" +" facturas` y para :guilabel:`Mostrar fecha de caducidad en las notas de " +"remisión`. Activar estas funcionles le ayudará a tener trazabilidad " +"completa, lo que facilitará la gestión de productos que se hayan retirado, a" +" identificar \"malos\" lotes de productos y mucho más." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:40 msgid "Configure expiration dates on products" -msgstr "" +msgstr "Configure fechas de caducidad en productos" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:42 msgid "" @@ -1262,6 +1387,10 @@ msgid "" "features have been enabled in the settings of the *Inventory* app, " "expiration information can be configured on individual products." msgstr "" +"Una vez que haya activado las funciones de :guilabel:`Fechas de caducidad` y" +" :guilabel:`Lotes y números de serie` en los ajustes de la aplicación " +"Inventario, podrá configurar a información de caducidad en productos " +"individuales." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:46 msgid "" @@ -1270,6 +1399,11 @@ msgid "" "for that particular item. Once on the product form, click :guilabel:`Edit` " "in the upper-left corner to make changes." msgstr "" +"Para hacerlo, vaya a :menuselection:`Inventario --> Productos --> Productos`" +" y seleccione un producto para editarlo. Al seleccionar un producto se " +"mostrará el formulario de ese artículo en específico. Ya que esté en el " +"formulario del producto, haga clic en :guilabel:`Editar` en la esquina " +"superior izquierda para realizar cambios." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:51 msgid "" @@ -1277,6 +1411,10 @@ msgid "" "information, products *must* have their :guilabel:`Product Type` set as " ":guilabel:`Storable Product` under the :guilabel:`General Information` tab." msgstr "" +"Para que los productos se puedan rastrear con lotes o números de serie, o " +"para configurar la información de caducidad, el :guilabel:`Tipo de producto`" +" que aparezca en la pestaña de :guilabel:`Información general` *debe* ser " +":guilabel:`Producto almacenable`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:55 msgid "" @@ -1284,6 +1422,9 @@ msgid "" ":guilabel:`Traceability` section. From here, make sure that either " ":guilabel:`By Unique Serial Number` or :guilabel:`By Lots` is checked." msgstr "" +"Después, haga clic en la pestaña :guilabel:`Inventario` y baje a la sección " +"titulada :guilabel:`Trazabilidad`. Desde ahí asegúrese de que la casilla de " +":guilabel:`Por número de serie único` o :guilabel:`Por lotes` esté marcada." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:59 msgid "" @@ -1291,6 +1432,9 @@ msgid "" "also be clicked. When both are enabled, a new :guilabel:`Dates` field " "appears to the right." msgstr "" +"Una vez que esté, aparecerá una nueva casilla de :guilabel:`Fecha de " +"caducidad` que también debe estar marcada. Cuando ambas casillas estén " +"marcadas, aparecerá un nuevo campo llamado :guilabel:`Fechas` a la derecha." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:63 msgid "" @@ -1298,6 +1442,9 @@ msgid "" "serial numbers, an inventory adjustment might need to be performed in order " "to assign lot numbers to the existing stock." msgstr "" +"Si un producto tiene existencias a la mano antes de activar el seguimiento " +"por lote o número de serie, es posible que necesite realizar un ajuste de " +"inventario para poder asignar lotes a las existencias que ya tiene." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:68 msgid "" @@ -1305,16 +1452,21 @@ msgid "" " recommended to track using lots, so multiple products can be traced back to" " the same lot, if any issues arise." msgstr "" +"Para procesar grandes cantidades de productos que se recibieron o se " +"entregaron, le recomendamos rastrear los productos con lotes, para que " +"varios productos se puedan rastrear con el mismo lote si ocurren problemas." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 msgid "Expiration dates configuration on the product form." -msgstr "" +msgstr "Configuración de fechas de caducidad en el formulario del producto." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:75 msgid "" "Under the :guilabel:`Dates` field, there are four categories of expiration " "information to configure for the product:" msgstr "" +"En el campo de :guilabel:`fechas` hay cuatro categorías de información de " +"caducidad que debe configurar para el producto:" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:78 msgid "" @@ -1322,6 +1474,9 @@ msgid "" "(either from a vendor or in stock after production) in which goods may " "become dangerous and should not be used or consumed." msgstr "" +":guilabel:`Fecha de caducidad`: el número de días después de haber recibido " +"los productos (ya sea de un proveedor o después de producirlos) en los que " +"el producto ya no debería usarse o consumirse por seguridad." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:80 msgid "" @@ -1329,12 +1484,17 @@ msgid "" "in which the goods start deteriorating, **without** necessarily being " "dangerous yet." msgstr "" +":guilabel:`Consumir preferentemente antes de`: el número de días antes de la" +" fecha de caducidad en la que los productos se empezarán a deteriorar " +"**sin** que sean peligrosos todavía." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:82 msgid "" ":guilabel:`Removal Time`: the number of days before the expiration date in " "which the goods should be removed from stock." msgstr "" +":guilabel:`Tiempo de remoción`: el número de días antes de la fecha de " +"caducidad en los que el producto se debe quitar de existencias." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:84 msgid "" @@ -1342,6 +1502,9 @@ msgid "" "which an alert should be raised on goods in a particular lot or containing a" " particular serial number." msgstr "" +":guilabel:`Periodo de alerta`: el número de días antes de la fecha de " +"caducidad en los que se debería enviar una alerta sobre los bienes en un " +"lote que tengan un número de serie en especial. " #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:88 msgid "" @@ -1349,12 +1512,17 @@ msgid "" "date for goods entered into stock, whether purchased from a vendor or " "manufactured in-house." msgstr "" +"Con los valores que ingrese en estos campos se calculará la fecha de " +"caducidad para bienes que ingrese a sus existencias, no importa si los " +"compró a un proveedor o si usted los fabricó." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:91 msgid "" "Once all the expiration information has been configured, click " ":guilabel:`Save` to save all changes." msgstr "" +"Ya que configuró toda la información de fecha de caducidad, haga clic en " +":guilabel:`Guardar` para guardar todos los cambios." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:94 msgid "" @@ -1363,10 +1531,16 @@ msgid "" "receipts and deliveries in and out of the warehouse. Even when assigned, " "they can still be overwritten and changed manually if needed, as well." msgstr "" +"Si no ingresó ninguna información de caducidad al campo :guilabel:`Fechas`, " +"puede asignar fechas (o lotes) de manera manual al recibir y entregar " +"productos dentro y fuera del almacén. Incluso cuando ya están asignadas las " +"fechas, las puede cambiar usted mismo si lo necesita." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:99 msgid "Set expiration dates on receipts with lots & serial numbers" msgstr "" +"Configure fechas de caducidad al momento de recibir el producto con lotes y " +"números de serie." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:101 msgid "" @@ -1375,6 +1549,10 @@ msgid "" ":menuselection:`Purchase` app and click :guilabel:`Create` to create a new " "request for quotation (RFQ)." msgstr "" +"Puede generar fechas de caducidad para bienes **entrantes** directamente " +"desde la orden de compra. Para crear una orden de compra, vaya a " +":menuselection:`Compra` y haga clic en :guilabel:`Crear` para crear una " +"nueva solicitud de cotización." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:105 msgid "" @@ -1382,6 +1560,9 @@ msgid "" "products to the :guilabel:`Product` lines by clicking :guilabel:`Add a " "product`." msgstr "" +"Después, agregue un :guilabel:`Proveedor` y después haga clic en " +":guilabel:`Añadir un producto` para agregar :guilabel:`Productos` a las " +"líneas de productos." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:108 msgid "" @@ -1389,12 +1570,18 @@ msgid "" ":guilabel:`Quantity` column, and click :guilabel:`Confirm Order`. This " "converts the :abbr:`RFQ (request for quotation)` into a purchase order." msgstr "" +"Para elegir la cantidad que desea ordenar cambie el número de la columna " +":guilabel:`Cantidad`. Haga clic en :guilabel:`Confirmar orden`. De esta " +"manera convertirá la :abbr:`Solicitud de cotización (RFQ en inglés)` en una " +"orden de compra." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:112 msgid "" "Click the :guilabel:`Receipt` smart button at the top of the purchase order " "to be taken to the warehouse receipt form." msgstr "" +"Haga clic en el botón inteligente :guilabel:`Recepción` en la parte superior" +" de la orden de compra para llegar al formulario de recepción del almacén." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:116 msgid "" @@ -1404,10 +1591,18 @@ msgid "" " The :abbr:`RFQ (request for quotation)` cannot be validated without an " "assigned lot or serial number." msgstr "" +"Si hace clic en :guilabel:`Validar` antes de asignar un número de serie a " +"las cantidades del producto ordenado, aparecerá una ventana emergente de " +":guilabel:`Error del usuario`, que le pedirá que ingrese un número de serie " +"o lote para los productos ordenados. No se puede validar la :abbr:`Solicitud" +" de cotización (RFQ en inglés)` si no ha asignado un lote o un número de " +"serie." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:0 msgid "User error popup when validating an order with no lot number." msgstr "" +"Ventana emergente de error del usuario cuando se valida una orden sin número" +" de lote." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:125 msgid "" @@ -1415,24 +1610,35 @@ msgid "" "located on the far-right of the product line. When clicked, a " ":guilabel:`Detailed Operations` pop-up will appear." msgstr "" +"Desde aquí puede hacer clic en el icono de menú de :guilabel:`Opciones " +"adicionales` que se encuentra hasta la derecha de la línea del producto. Al " +"hacer clic en este icono, aparecerá una ventana emergente de " +":guilabel:`Operaciones detalladas`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:128 msgid "" "In this pop-up, click :guilabel:`Add a line`, and assign a lot or serial " "number under the :guilabel:`Lot/Serial Number Name` field." msgstr "" +"En esta ventana emergente haga clic en :guilabel:`Agregar una línea` y " +"asigne un lote o número de serie en el campo :guilabel:`Lote/número de " +"serie`" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:131 msgid "" "An expiration date automatically populates, based on the configuration on " "the product form (if previously configured)." msgstr "" +"De manera automática se llena una fecha de caducidad según la configuración " +"en el formulario del producto (si se configuró antes)." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:135 msgid "" "If the :guilabel:`Dates` field on the product form has not been configured, " "this date can be manually entered." msgstr "" +"Si no ha configurado el campo :guilabel:`Fechas` en el formulario del " +"producto, puede ingresar esta fecha de manera manual." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:138 msgid "" @@ -1440,11 +1646,16 @@ msgid "" "quantities, and click :guilabel:`Confirm` to close the pop-up. Finally, " "click :guilabel:`Validate`." msgstr "" +"Después de que se estableció la fecha de caducidad, marque :guilabel:`Hecho`" +" en las cantidades y haga clic en :guilabel:`Confirmar` para cerrar las " +"ventanas emergentes. Después, haga clic en :guilabel:`Validar`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 msgid "" "Detailed operations popup showing expiration dates for ordered products." msgstr "" +"Ventana emergente de operaciones detalladas en las que se muestran fechas de" +" caducidad para productos ordenados" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:145 msgid "" @@ -1454,10 +1665,15 @@ msgid "" "document; the :guilabel:`Product` being traced; the :guilabel:`Lot/Serial " "#`; and more." msgstr "" +"Cuando valide que recibió un producto, aparecerá un botón de " +":guilabel:`Trazabilidad`. Si hace clic en este botón podrá ver un " +":guilabel:`Reporte de trazabilidad` actualizado en el que se incluye un " +"documento de :guilabel:`referencia`, el :guilabel:`producto` que está " +"rastreando, el :guilabel:`Lote o número de serie` y más." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:151 msgid "Set expiration dates on manufactured products" -msgstr "" +msgstr "Configurar fechas de caducidad en productos fabricados" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:153 msgid "" @@ -1465,6 +1681,9 @@ msgid "" "To assign expiration dates to manufactured products, a manufacturing order " "(MO) needs to be completed." msgstr "" +"También puede generar fechas de caducidad para productos que usted fabrique." +" Para asignar fechas de caducidad a estos productos, debe completar una " +"orden de fabricación." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:156 msgid "" @@ -1474,10 +1693,15 @@ msgid "" ":guilabel:`Product` field drop-down menu, then select the " ":guilabel:`Quantity` to produce." msgstr "" +"Para crear una :guilabel:`Orden de fabricación` vaya a " +":menuselection:`Fabricación --> Operaciones --> Órdenes de fabricación` y " +"haga clic en :guilabel:`Crear`. Abra el menú extendible del campo " +":guilabel:`Producto` y elija el producto que quiere crear, después elija la " +"guilabel:`Cantidad` que quiere producir." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 msgid "Manufacturing order for product with expiration date." -msgstr "" +msgstr "Orden de fabricación para un producto que tiene fecha de caducidad." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:165 msgid "" @@ -1486,10 +1710,15 @@ msgid "" ":guilabel:`Bill of Material` for the :guilabel:`Product`, or manually adding" " materials to consume by clicking :guilabel:`Add a line`." msgstr "" +"Para fabricar un producto, debe haber materiales por consumir en las líneas " +"de la columna :guilabel:`Producto`. Para hacer esto debe crear una " +":guilabel:`Lista de materiales` para el :guilabel:`Producto` o debe agregar" +" materiales por consumir de manera manual, solo tiene que hacer clic en " +":guilabel:`Agregar una línea`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:170 msgid "Once ready, click :guilabel:`Confirm`." -msgstr "" +msgstr "Ya que esté listo, haga clic en :guilabel:`Confirmar`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:172 msgid "" @@ -1497,12 +1726,17 @@ msgid "" "from the drop-down menu, or click the green :guilabel:`+` sign to " "automatically assign a new lot number." msgstr "" +"Para asignar un número de lote, seleccione un número de lote existente desde" +" el menú desplegable junto a :guilabel:`Lote/Número de serie` o haga clic en" +" el :guilabel:`+` verde." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:175 msgid "" "Then, select a number of units for the :guilabel:`Quantity` field, and click" " :guilabel:`Mark as Done`." msgstr "" +"Después, seleccione un número de unidades para el campo :guilabel:`Cantidad`" +" y después haga clic en :guilabel:`Marcar como hecho`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:178 msgid "" @@ -1510,6 +1744,9 @@ msgid "" ":guilabel:`Lot/Serial Number` field. A pop-up appears, revealing a detail " "form for that specific number." msgstr "" +"Haga clic en el icono :guilabel:`Enlace externo` en el campo de " +":guilabel:`Lote/Número de serie` asignado. Aparecerá una ventana emergente " +"donde se mostrará todos los detalles de ese número específico." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:181 msgid "" @@ -1519,14 +1756,21 @@ msgid "" "or by going to :menuselection:`Inventory app --> Products --> Lots/Serial " "Numbers`." msgstr "" +"En esa ventana emergente, vaya a la pestaña :guilabel:`Fechas` y podrá ver " +"toda la información sobre fecha de caducidad que había configurado antes en " +"el producto. Esta información también está disponible en el formulario de " +"detalles de ese producto en específico, para verlo vaya a " +":menuselection:`Inventario --> Productos --> Lote/Número de serie`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 msgid "Dates tab with expiration information for specific lot number." msgstr "" +"Pestaña de fechas con información de caducidad para un número de lote " +"específico." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:191 msgid "Sell products with expiration dates" -msgstr "" +msgstr "Vender productos con fechas de caducidad" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:193 msgid "" @@ -1534,12 +1778,17 @@ msgid "" "other type of product. The first step in selling perishable products is to " "create a sales order." msgstr "" +"Los productos perecederos que tienen fecha de caducidad se venden de la " +"misma manera que cualquier otro tipo de producto. El primer paso es vender " +"el producto perecedero para crear una orden de venta." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:196 msgid "" "To do that, go to :menuselection:`Sales app --> Create` to create a new " "quotation, and fill out the information on the sales order form." msgstr "" +"Para hacer esto, vaya a :menuselection:`Ventas --> Crear`, cree una nueva " +"cotización y llene la información en la orden de venta." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:199 msgid "" @@ -1547,6 +1796,9 @@ msgid "" "desired products to the :guilabel:`Product` lines, and set a " ":guilabel:`Quantity` for the products." msgstr "" +"Agregue un :guilabel:`Cliente`, haga clic en :guilabel:`Agregar un producto`" +" para agregar los productos deseados a las líneas de :guilabel:`Producto` y " +"configure una :guilabel:`Cantidad` para los productos." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:202 msgid "" @@ -1555,12 +1807,20 @@ msgid "" "date, and click the :guilabel:`green checkmark` icon to confirm the date. " "Finally, click :guilabel:`Confirm` to confirm the sales order." msgstr "" +"Después haga clic en la pestaña :guilabel:`Other Info` tab. En la sección " +":guilabel:`Entrega` cambie la :guilabel:`Fecha de entrega` a una fecha " +"después de la fecha esperada y haga clic en :guilabel:`la palomita verde` " +"para confirmar la fecha. Finalmente, haga clic en :guilabel:`Confirmar` para" +" confirmar la orden de venta." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:206 msgid "" "Next, click the :guilabel:`Delivery` smart button at the top of the sales " "order to see the warehouse receipt form." msgstr "" +"Después, haga clic en el botón inteligente de :guilabel:`Entrega` que se " +"encuentra en la parte superior de la orden de ventas para poder ver el " +"formulario de entrega del almacén." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:209 msgid "" @@ -1569,12 +1829,18 @@ msgid "" "process all :guilabel:`Done` quantities, and deliver the products to the " "customer." msgstr "" +"En el formulario de recepción del almacén, haga clic en :guilabel:`Validar`," +" y después en :guilabel:`Aplicar` en la ventana emergente que saldrá. Así " +"podrá procesar todas las cantidades :guilabel:`Hechas` de manera automática " +"y podrá entregarle los productos al cliente." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:213 msgid "" "If the products are delivered before the :guilabel:`Alert Date` set on the " "product form, then no alerts will be created." msgstr "" +"Si los productos se entregan antes de que configure la :guilabel:`Fecha de " +"alerta` en el formulario del producto, no se crearán advertencias." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:217 msgid "" @@ -1586,6 +1852,14 @@ msgid "" "expiration date. Removal strategies can also be set on :guilabel:`Product " "Categories`." msgstr "" +"Para vender productos perecederos con fechas de caducidad, la " +":guilabel:`estrategia de remoción` para la :guilabel:`ubicación` en la que " +"se almacenan los productos debe configurarse como :abbr:`FEFO (primero en " +"caducar, primero en salir, por sus siglas en inglés)`. Si en un lote no hay " +"suficientes existencias de un producto perecedero, Odoo tomará de manera " +"automática la cantidad que todavía se necesita directamente del siguiente " +"lote que tenga la fecha de caducidad más cercana. Puede gestionar las " +"estrategias de remoción en las :guilabel:`Categorías de productos`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:224 #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:209 @@ -1596,13 +1870,15 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:227 msgid "View expiration dates for lots & serial numbers" -msgstr "" +msgstr "Ver las fechas de caducidad para lotes y números de sere. " #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:229 msgid "" "To view (and/or group) all products with expiration dates by lot number, go " "to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." msgstr "" +"Para ver (o agrupar) todos los productos con fecha de caducidad por lote, " +"vaya a :menuselection:`Inventario --> Productos --> Lotes/Números de serie`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:232 msgid "" @@ -1611,26 +1887,36 @@ msgid "" " and select the :guilabel:`Expiration Date` parameter from the drop-down " "menu. Finally, click :guilabel:`Apply` to apply the filter." msgstr "" +"Quite todos los filtros de búsqueda automáticos de la barra " +":guilabel:`Buscar...`. Después, haga clic en :guilabel:`Agrupar por`, elija " +":guilabel:`Agregar grupo personalizado` y seleccione el parámetro " +":guilabel:`Fecha de caducidad` desde el menú desplegable. Para aplicar el " +"filtro haga clic en :guilabel:`Aplicar`" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:236 msgid "" "Doing so breaks down all perishable products, their expiration dates, and " "the assigned lot number." msgstr "" +"Si sigue estos pasos obtendrá un desglose de todos los productos " +"perecederos, como sus fechas de caducidad y el número de lote que se les " +"asignó." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 msgid "Group by expiration dates on lots and serial numbers page." -msgstr "" +msgstr "Agrupar por fechas de caducidad en lotes y números de serie." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:243 msgid "Expiration alerts" -msgstr "" +msgstr "Alertas de caducidad" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:245 msgid "" "To see expiration alerts, go to :menuselection:`Inventory app --> Products " "--> Lots/Serial Numbers`." msgstr "" +"Para ver alertas de caducidad vaya a :menuselection:`Inventario --> " +"Productos --> Lotes/Números de serie`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:247 msgid "" @@ -1639,6 +1925,11 @@ msgid "" "form, click the :guilabel:`Dates` tab to see all expiration information " "related to the products." msgstr "" +"Después, haga clic en el :guilabel:`Lote/Número de serie` que tenga " +"productos perecederos para mostrar el formulario que contiene el número de " +"serie. En el formulario de número de serie, haga clic en la pestaña " +":guilabel:`Fechas` para ver toda la información de caducidad que se " +"relaciona a los productos." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:251 msgid "" @@ -1646,6 +1937,10 @@ msgid "" "form, then change the :guilabel:`Expiration Date` to today's date (or " "earlier), and click :guilabel:`Save` to save changes." msgstr "" +"Para editar el formulario haga clic en :guilabel:`Editar` en la esquina " +"superior izquierda del formulario, después cambie la :guilabel:`Fecha de " +"caducidad` a la fecha de hoy (o antes) y haga clic en :guilabel:`Guardar` " +"para guardar los cambios." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:255 msgid "" @@ -1654,6 +1949,11 @@ msgid "" "either expired or expiring soon. From here, click back to the " ":guilabel:`Lots/Serial Numbers` page (via the breadcrumbs)." msgstr "" +"Después de guarder, el formulario de número de lote mostrará una " +":guilabel:`alerta de caducidad` en rojo en la parte superior del formulario " +"para indicar que los productos de este lote ya caducaron o caducarán pronto." +" Desde aquí, regrese a la página de :guilabel:`Lote/Número de serie` (a " +"través de las migajas de pan)." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:259 msgid "" @@ -1661,19 +1961,25 @@ msgid "" "are expired (or will expire soon), remove all of the search filters from the" " :guilabel:`Search...` bar on the :guilabel:`Lots/Serial Numbers` dashboard." msgstr "" +"Para ver la alerta de caducidad nueva, o cualquier alerta de caducidad para " +"productos que ya caducaron (o caducarán pronto), quite todos los filtros de " +"búsqueda de la barra :guilabel:`Buscar...` en el tablero de " +":guilabel:`Lote/Número de serie`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:263 msgid "" "Then, click :guilabel:`Filters`, and choose :guilabel:`Expiration Alerts`." msgstr "" +"Después, haga clic en :guilabel:`Filtros` y elija :guilabel:`alerta de " +"caducidad`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 msgid "Expiration alert for product past the expiration date." -msgstr "" +msgstr "Alerta de caducidad para un producto que ya caducó." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:3 msgid "Use lots to manage groups of products" -msgstr "" +msgstr "Use lotes para gestionar grupos y productos" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:5 msgid "" @@ -1682,6 +1988,10 @@ msgid "" "currently stored, or was shipped from a warehouse, but can also pertain to a" " batch of products manufactured in-house, as well." msgstr "" +"Hay dos maneras de identificar y rastrear productos en Odoo, la primera son " +"los *lotes*. Un lote indica un grupo específico de artículos que se recibió," +" se almacenó o se envió de un almacén. También puede indicar un grupo de " +"productos que se fabricaron dentro de la empresa." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:9 msgid "" @@ -1691,6 +2001,11 @@ msgid "" "for end-to-end traceability of these products through each step in their " "lifecycles." msgstr "" +"Los fabricantes asignan un número de lote a grupos de producto que tienen " +"propiedades en común, por lo que es posible que muchos bienes compartan el " +"mismo número de lote. Esto ayuda a identificar un número de productos dentro" +" de un mismo grupo y permite dar seguimiento a estos productos durante todo " +"su ciclo de vida." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:14 msgid "" @@ -1699,11 +2014,15 @@ msgid "" "back to a group. This is especially useful when managing product recalls or " "expiration dates." msgstr "" +"Los lotes son muy útiles para productos que fabrica o recibe en grandes " +"cantidades (como ropa y comida), además de que ayuda a saber de qué grupo " +"salió un producto. Esto le ayudará cuando tenga que retirar un producto del " +"mercado o al gestionar fechas de caducidad." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:22 #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:20 msgid "Enable lots & serial numbers" -msgstr "" +msgstr "Activar lotes y números de serie" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:24 msgid "" @@ -1713,14 +2032,21 @@ msgid "" "the box next to :guilabel:`Lots & Serial Numbers`. Then, click the " ":guilabel:`Save` button to save changes." msgstr "" +"Para rastrear productos por medio de lotes, debe activar la función de " +"*Números de lote y de serie*. Vaya a :menuselection:`Inventario --> " +"Configuración --> Ajustes`, baje a la sección :guilabel:`Trazabilidad` y " +"haga clic en la casilla junto a :guilabel:`Número de serie y lote`. Después," +" haga clic en :guilabel:`Guardar` para guardar los cambios." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 msgid "Enabled lots and serial numbers feature in inventory settings." msgstr "" +"Active las funciones de lote y número de serie desde los ajustes del " +"inventario." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:34 msgid "Track products by lots" -msgstr "" +msgstr "Rastrear productos por lotes" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:36 msgid "" @@ -1729,6 +2055,10 @@ msgid "" "this, go to the :menuselection:`Inventory app --> Products --> Products`, " "and choose a product." msgstr "" +"Ya que activó los :guilabel:`Lotes y números de serie` podrá configurar " +"productos individuales para poder rastrearlos con lotes. Para usar esta " +"función vaya a :menuselection:`Inventario --> Productos --> Productos` y " +"elija un producto." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:40 msgid "" @@ -1738,6 +2068,12 @@ msgid "" ":guilabel:`Save` to save changes. Existing or new lot numbers can now be " "assigned to newly-received or manufactured batches of this product." msgstr "" +"Ya que esté en el formulario del producto, haga clic en :guilabel:`Editar` " +"para hacer cambios en el formulario y haga clic en la pestaña " +":guilabel:`Inventario`. En la sección de :guilabel:`Trazabilidad`, haga clic" +" en :guilabel:`Por lotes`, después haga clic en :guilabel:`Guardar` para " +"guardar los cambios. Puede asignar los número de lote existentes o nuevos a " +"grupos de productos que acabe de recibir o fabricar." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:46 msgid "" @@ -1745,14 +2081,18 @@ msgid "" "serial numbers, an inventory adjustment might need to be performed to assign" " lot numbers to the existing stock." msgstr "" +"Si un producto tiene existencias a la mano antes de activar el seguimiento " +"por lote o número de serie, es posible que necesite realizar un ajuste de " +"inventario para poder asignar lotes a las existencias que ya tiene." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 msgid "Enabled tracking by lots feature on product form." msgstr "" +"Función de seguimiento por lotes activada en el formulario del producto." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:54 msgid "Create new lots for products already in stock" -msgstr "" +msgstr "Cree nuevos lotes para productos que ya estén en existencias." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:56 msgid "" @@ -1762,6 +2102,11 @@ msgid "" "separate page where a new :guilabel:`Lot/Serial Number` is generated " "automatically." msgstr "" +"Puede crear lotes nuevos para productos que ya están en existencia y que no " +"tengan número de lote asignado. Para hacerlo, vaya a " +":menuselection:`Inventario --> Productos --> Lotes/Números de serie` y haga " +"clic en :guilabel:`Crear`. Al hacer esto obtendrá una nueva página donde se " +"generará un nuevo :guilabel:`Lote/Número de serie` de manera automática." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:62 msgid "" @@ -1770,6 +2115,11 @@ msgid "" "number, by clicking the line under the :guilabel:`Lot/Serial Number` field, " "and changing the generated number." msgstr "" +"Odoo genera de manera automática un :guilabel:`Lote/Número de serie` con el " +"que puede seguir los productos más recientes, pero usted puede editar este " +"número a cualquier otro. Solo tiene que hacer clic en la línea abajo del " +"campo :guilabel:`Lote/Número de serie` para cambiar el número que se había " +"generado." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:66 msgid "" @@ -1777,6 +2127,10 @@ msgid "" "field next to :guilabel:`Product` to reveal a drop-down menu. From this " "menu, select the product to which this new number will be assigned." msgstr "" +"Una vez que se genere el nuevo :guilabel:`Lote/Número de serie` haga clic en" +" el campo vacío junto a :guilabel:`Producto` para mostrar el menú " +"desplegable. En este menú, seleccione el producto al que se le asignará este" +" número." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:70 msgid "" @@ -1786,12 +2140,18 @@ msgid "" "specific website in the :guilabel:`Website` field (if working in a multi-" "website environment)." msgstr "" +"Con este formulario también puede ajustar la :guilabel:`Cantidad`, asignar " +"un número de :guilabel:`Referencia interna` (para trazabilidad) y asignar la" +" configuración de este lote o número de serie específico a un sitio web en " +"el campo :guilabel:`Sitio web` (si trabaja con un entorno multiempresa)." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:75 msgid "" "A detailed description of this specific lot or serial number can also be " "added in the :guilabel:`Description` tab below." msgstr "" +"También puede agregar una descripción detallada de este lote o número de " +"serie en la pestaña :guilabel:`Descripción` de abajo." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:78 #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:79 @@ -1799,10 +2159,13 @@ msgid "" "When all desired configurations are complete, click the :guilabel:`Save` " "button to save all changes." msgstr "" +"Cuando complete de realizar la configuración, haga clic en " +":guilabel:`Guardar` para guardar los cambios que hizo." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 msgid "New lot number creation form with assigned product." msgstr "" +"Nuevo formulario de creación de número de lote con un producto asignado." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:84 msgid "" @@ -1811,6 +2174,11 @@ msgid "" " app, by going to :menuselection:`Products --> Products`, and selecting the " "product to which this newly-created lot number was just assigned." msgstr "" +"Ya que creó, guardó y asignó el nuevo número de lote al producto deseado, " +"regrese al formulario de producto en la aplicación " +":menuselection:`Inventario`. Para hacerlo, vaya a :menuselection:`Productos " +"--> Productos` y seleccione el producto al que le asignó el número de lote " +"que acaba de crear." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:88 msgid "" @@ -1819,10 +2187,14 @@ msgid "" "product is received or manufactured, this new lot number can be selected and" " assigned to it." msgstr "" +"En el formulario de detalles de producto haga clic en el botón inteligente " +":guilabel:`Lote/Número de serie` para ver el nuevo número de lote. Cuando " +"reciba o fabrique más de este producto, puede seleccionar este número de " +"lote y asignarlo al nuevo producto." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:93 msgid "Manage lots for shipping and receiving" -msgstr "" +msgstr "Gestión de lotes para envío y recepción " #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:95 msgid "" @@ -1831,22 +2203,30 @@ msgid "" "form. For outgoing goods, lot numbers are assigned directly on the sales " "order form." msgstr "" +"Puede asignar números de lote tanto a bienes **entrantes** como a bienes " +"**salientes**. Para bienes entrantes, usted asigna el número de lote " +"directamente en la orden de compra, mientras que tiene que asignar el número" +" en la orden de venta para los bienes salientes." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:100 msgid "Manage lots on receipts" -msgstr "" +msgstr "Gestión de lotes al recibir productos" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:102 msgid "" "Assigning lot numbers to **incoming** goods can be done directly from the " "purchase order (PO)." msgstr "" +"Puede asignar lotes a los bienes **entrantes** directamente desde la orden " +"de compra." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:104 msgid "" "To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app " "--> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." msgstr "" +"Para crear una :guilabel:`Orden de compra` vaya a :menuselection:`Compra -->" +" Crear` y podrá ver una solicitud de cotización en blanco." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:107 msgid "" @@ -1855,12 +2235,18 @@ msgid "" "to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` " "(under the :guilabel:`Products` tab)." msgstr "" +"En esta :guilabel:`Solicitud de cotización`, llene la información necesaria." +" Agregue el :guilabel:`Proveedor` y haga clic en :guilabel:`Agregar un " +"producto` (en la pestaña de :guilabel:`Productos` ) para agregar los " +"productos deseados en las líneas de :guilabel:`Productos`." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:111 msgid "" "Choose the desired quantity of the product to order by changing the number " "in the :guilabel:`Quantity` column." msgstr "" +"Si cambia el número en la columna :guilabel:`Cantidad` se establecerá la " +"cantidad de productos que quiere ordenar." #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:114 msgid "" diff --git a/locale/es/LC_MESSAGES/productivity.po b/locale/es/LC_MESSAGES/productivity.po index d74a77a92..98ba3dc5a 100644 --- a/locale/es/LC_MESSAGES/productivity.po +++ b/locale/es/LC_MESSAGES/productivity.po @@ -12,9 +12,9 @@ # Braulio D. López Vázquez , 2023 # Raquel Iciarte , 2023 # Martin Trigaux, 2023 -# Patricia Gutiérrez Capetillo , 2023 # Iran Villalobos López, 2023 # Fernanda Alvarez, 2023 +# Patricia Gutiérrez Capetillo , 2023 # #, fuzzy msgid "" @@ -23,7 +23,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-07-07 06:24+0000\n" "PO-Revision-Date: 2021-11-02 08:49+0000\n" -"Last-Translator: Fernanda Alvarez, 2023\n" +"Last-Translator: Patricia Gutiérrez Capetillo , 2023\n" "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -218,8 +218,8 @@ msgstr "" "Si sigue en el modo de prueba (externo), para agregar las direcciones de " "correo que configuró en el paso :guilabel:`Usuarios de prueba` haga clic en " ":guilabel:`Add Users` (agregar usuarios) y después en el botón " -":guilabel:`Save and Continue` (guardr y continuar). Aparecerá un resumen del" -" registro de la aplicación." +":guilabel:`Save and Continue` (guardar y continuar). Aparecerá un resumen " +"del registro de la aplicación." #: ../../content/applications/productivity/calendar/google.rst:78 msgid "" diff --git a/locale/es/LC_MESSAGES/sales.po b/locale/es/LC_MESSAGES/sales.po index c6cdcfc1f..7575aa280 100644 --- a/locale/es/LC_MESSAGES/sales.po +++ b/locale/es/LC_MESSAGES/sales.po @@ -30,7 +30,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:49+0000\n" "Last-Translator: Fernanda Alvarez, 2023\n" "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n" @@ -2171,72 +2171,67 @@ msgid "" "<../../../productivity/iot/config/connect>` may require :doc:`the HTTPS " "protocol ` to establish a secure connection between the browser and " "the printer. However, trying to reach the printer's IP address using HTTPS " -"leads to a warning page on most web browsers." +"leads to a warning page on most web browsers. In that case, you can " +"temporarily :ref:`force the connection `, which " +"allows you to reach the page in HTTPS and use the ePOS printer in Odoo as " +"long as the browser window stays open." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:41 -msgid "warning page about the connection privacy on Google Chrome" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:41 -msgid "Warning page on Google Chrome, Windows 10" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:43 -msgid "" -"In that case, you can temporarily force the connection by clicking " -":guilabel:`Advanced` and :guilabel:`Proceed to [IP address] (unsafe)`. Doing" -" so allows you to reach the page in HTTPS and use the ePOS printer in Odoo " -"as long as the browser window stays open." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:48 -msgid "" -"The previous instructions apply to Google Chrome but are similar to other " -"browsers." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:51 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:40 msgid "" "The connection is lost after closing the browser window. Therefore, this " "method should only be used as a **workaround** or as a pre-requisite for the" " :ref:`following instructions `." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 msgid "Generate, export, and import self-signed certificates" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:60 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 msgid "" "For a long-term solution, you must generate a **self-signed certificate**. " "Then, export and import it into your browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 msgid "" "**Generating** an SSL certificate should only be done **once**. If you " "create another certificate, devices using the previous one will lose HTTPS " "access." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:69 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 msgid "Windows 10 & Linux OS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:73 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62 msgid "Generate a self-signed certificate" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:75 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 msgid "" -"After forcing the connection, sign in using your printer credentials to " -"access the ePOS printer settings. To sign in, enter `epson` in the " -":guilabel:`ID` field and your printer serial number in the " -":guilabel:`Password` field." +"Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force " +"the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to " +"[IP address] (unsafe)`." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:79 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "warning page about the connection privacy on Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72 +msgid "Warning page on Google Chrome, Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74 +msgid "" +"Then, sign in using your printer credentials to access the ePOS printer " +"settings. To sign in, enter `epson` in the :guilabel:`ID` field and your " +"printer serial number in the :guilabel:`Password` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78 msgid "" "Click :guilabel:`Certificate List` in the :guilabel:`Authentication` " "section, and click :guilabel:`create` to generate a new **Self-Signed " @@ -2247,7 +2242,7 @@ msgid "" "printer." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:86 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 msgid "" "The self-signed certificate is generated. Reload the page and click " ":guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure " @@ -2255,25 +2250,25 @@ msgid "" "Certificate` section." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:90 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 msgid "Export a self-signed certificate" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:92 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 msgid "" "The export process is heavily dependent on the :abbr:`OS (Operating System)`" " and the browser. Start by accessing your ePOS printer settings on your web " -"browser by navigating to its IP address, for example, " -"`https://192.168.1.25`. Then, force the connection as explained in the " -":ref:`introduction `." +"browser by navigating to its IP address (e.g., `https://192.168.1.25`). " +"Then, force the connection as explained in the **Generate a self-signed " +"certificate tab**." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:97 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:160 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 msgid "If you are using **Google Chrome**," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:99 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 msgid "" "click :guilabel:`Not secure` next to the search bar, and " ":guilabel:`Certificate is not valid`;" @@ -2283,43 +2278,43 @@ msgstr "" msgid "Connection to the printer not secure button in Google Chrome browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:107 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105 msgid "" "add `.crt` at the end of the file name to ensure it has the correct " "extension;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 msgid "" "select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom " "of the pop-up window;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:110 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:128 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125 msgid "save, and the certificate is exported." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:113 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 msgid "" "Make sure that the certificate ends with the extension `.crt`. Otherwise, " "some browsers might not see the file during the import process." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:172 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 msgid "If you are using **Mozilla Firefox**," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:118 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 msgid "click the **lock-shaped** icon on the left of the address bar;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:119 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 msgid "" "go to :menuselection:`Connection not secure --> More information --> " "Security tab --> View certificate`;" @@ -2329,173 +2324,173 @@ msgstr "" msgid "Connection is not secure button in Mozilla Firefox browser" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:126 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123 msgid "scroll down to the :guilabel:`Miscellaneous` section;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124 msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:130 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 msgid "Import a self-signed certificate" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:132 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 msgid "" "The import process is heavily dependent on the :abbr:`OS (Operating System)`" " and the browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:137 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 msgid "Windows 10" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 msgid "" "Windows 10 manages certificates, which means that self-signed certificates " "must be imported from the certification file rather than the browser. To do " "so," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 msgid "" "open the Windows File Explorer and locate the downloaded certification file;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:143 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 msgid "" "right-click on the certification file and click :guilabel:`Install " "Certificate`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 msgid "" "select where to install the certificate and for whom - either for the " ":guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, " "click :guilabel:`Next`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:148 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 msgid "" "on the `Certificate Store` screen, tick :guilabel:`Place all certificates in" " the following store`, click :guilabel:`Browse...`, and select " ":guilabel:`Trusted Root Certification Authorities`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:155 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:151 msgid "click :guilabel:`Finish`, accept the pop-up security window;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 msgid "restart the computer to make sure that the changes are applied." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 msgid "Linux" msgstr "Linux" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:162 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 msgid "open Chrome;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 msgid "" "go to :menuselection:`Settings --> Privacy and security --> Security --> " "Manage certificates`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 msgid "" "go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select " "the exported certification file;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:167 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 msgid "accept all warnings;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:164 msgid "click :guilabel:`ok`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:169 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 msgid "restart your browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:170 msgid "open Firefox;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:171 msgid "" "go to :menuselection:`Settings --> Privacy & Security --> Security --> View " "Certificates... --> Import`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:173 msgid "select the exported certification file;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:178 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 msgid "tick the checkboxes and validate;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 msgid "Mac OS" msgstr "Mac OS" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:183 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 msgid "To secure the connection on a Mac:" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:185 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 msgid "" "open Safari and navigate to your printer's IP address. Doing so leads to a " "warning page;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 msgid "" "on the warning page, go to :menuselection:`Show Details --> visit this " "website --> Visit Website`, validate;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:184 msgid "reboot the printer so you can use it with any other browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:190 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 msgid "Android OS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188 msgid "" "To import an SSL certificate into an Android device, first create and export" " it from a computer. Next, transfer the `.crt` file to the device using " "email, Bluetooth, or USB. Once the file is on the device," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:196 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192 msgid "open the settings and search for `certificate`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 msgid "click :guilabel:`Certificate AC` (Install from device storage);" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:198 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:194 msgid "select the certificate file to install it on the device." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197 msgid "" "The specific steps for installing a certificate may vary depending on the " "version of Android and the device manufacturer." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:206 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:202 msgid "" "If you need to export SSL certificates from an operating system or web " "browser that has not been mentioned, search for `export SSL certificate` + " @@ -2503,18 +2498,18 @@ msgid "" "engine." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:209 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:205 msgid "" "Similarly, to import SSL certificates from an unmentioned OS or browser, " "search for `import SSL certificate root authority` + `the name of your " "browser or operating system` in your preferred search engine." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:210 msgid "Check if the certificate was imported correctly" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:216 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:212 msgid "" "To confirm your printer's connection is secure, connect to its IP address " "using HTTPS. For example, navigate to `https://192.168.1.25` in your " @@ -2754,23 +2749,23 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21 msgid ":doc:`Adyen configuration `" -msgstr "" +msgstr ":doc:`Configuración de Adyen `" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:22 msgid ":doc:`Ingenico configuration `" -msgstr "" +msgstr ":doc:`Configuración de Ingenico `" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23 msgid ":doc:`SIX configuration `" -msgstr "" +msgstr ":doc:`Configuración de SIX `" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24 msgid ":doc:`Vantiv configuration `" -msgstr "" +msgstr ":doc:`Configuración de Vantiv `" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25 msgid ":doc:`Worldline configuration `" -msgstr "" +msgstr ":doc:`Configuración de Worldline `" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:27 msgid "" @@ -6617,7 +6612,7 @@ msgstr "Método de facturación" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:3 msgid "Down payments" -msgstr "" +msgstr "Anticipos" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:5 msgid "" @@ -6625,6 +6620,9 @@ msgid "" "is concluded. This implies both parties' (seller and buyer) full commitment " "to honor the contract." msgstr "" +"Un anticipo es un pago parcial que realiza el comprador cuando se celebra un" +" contrato de venta. Esto implica el compromiso total de ambas partes " +"(vendedor y comprador) de cumplir el contrato." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:8 msgid "" @@ -6633,10 +6631,15 @@ msgid "" "provides goods or services to the buyer after accepting the down payment, " "trusting that the remaining amount will be paid later on." msgstr "" +"Con un anticipo, el comprador paga una parte del importe total adeudado " +"mientras acepta pagar la cantidad restante después. Por otra parte, el " +"vendedor le proporciona los bienes o servicios al comprador después de " +"aceptar el anticipo, confiando en que este le pagará el importe restante más" +" adelante." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:13 msgid "Initial down payment request" -msgstr "" +msgstr "Solicitud inicial de anticipo" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:15 msgid "" @@ -6645,42 +6648,54 @@ msgid "" "left corner of the sales order form. When clicked, a :guilabel:`Create " "invoices` pop-up appears." msgstr "" +"Cuando se confirma una orden de venta, se habilita la opción de crear una " +"factura mediante el botón :guilabel:`Crear factura` ubicado en la esquina " +"superior izquierda del formulario de orden de venta. Cuando hace clic, " +"aparece la ventana emergente :guilabel:`Crear facturas`." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:20 msgid "" "Invoices are automatically created in drafts, so they can be reviewed before" " validation." msgstr "" +"Las facturas se crean como borradores de forma automática, por lo que pueden" +" revisarlas antes de validarlas." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:22 msgid "" "On the :guilabel:`Create invoices` pop-up, there are 3 options to choose " "from in the :guilabel:`Create Invoice` field:" msgstr "" +"En la ventana emergente :guilabel:`Crear facturas, hay 3 opciones para " +"elegir en el campo :guilabel:`Crear factura`:" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 msgid ":guilabel:`Regular invoice`" -msgstr "" +msgstr ":guilabel:`Factura normal`" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 msgid "" "If :guilabel:`Regular Invoice` is selected the other fields disappear, as " "they only pertain to down payment configurations." msgstr "" +"Si selecciona :guilabel:`factura normal` los otros campos desaparecen, ya " +"que solo corresponden a las configuraciones de anticipos." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:29 msgid ":guilabel:`Down payment (percentage)`" -msgstr "" +msgstr ":guilabel:`Anticipo (porcentaje)`" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:30 msgid ":guilabel:`Down payment (fixed amount)`" -msgstr "" +msgstr ":guilabel:`Anticipo (importe fijo)`" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:32 msgid "" "In terms of a down payment, it can either be a fixed amount or a percentage " "of the total amount." msgstr "" +"En términos de anticipos, puede ser un importe fija o un porcentaje del " +"importe total." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:34 msgid "" @@ -6688,6 +6703,9 @@ msgid "" "Invoice` field, designate the desired amount (either as a percentage or " "fixed amount) in the :guilabel:`Down Payment Amount` field." msgstr "" +"Una vez que haya seleccionado la opción de pago inicial deseada en el campo " +":guilabel:`Crear factura`, indique el importe deseado (ya sea como " +"porcentaje o importe fijo) en el campo :guilabel:`Importe del anticipo`." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:38 msgid "" @@ -6696,10 +6714,14 @@ msgid "" " :guilabel:`Customer Taxes` field. These settings will be reused for future " "down payments." msgstr "" +"Luego, seleccione la cuenta de ingresos apropiada para la factura en el " +"campo :guilabel:`` y si es necesario agregue un impuesto en el campo " +":guilabel:`Impuestos del cliente`. Estos ajustes se reutilizarán para " +"futuros pagos iniciales." #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "How to configure a down payment on Odoo Sales." -msgstr "" +msgstr "Cómo configurar un anticipo en la aplicación Ventas de Odoo." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:47 msgid "" @@ -6708,22 +6730,31 @@ msgid "" "product, with an invoicing policy of :guilabel:`Ordered quantities`. This " "product can be edited and modified at any time." msgstr "" +"Cuando solicita un anticipo por primera vez, se crea un nuevo producto " +"llamado :guilabel:`Anticipo`. Este producto está registrado como un producto" +" de tipo :guilabel:`Servicio` con una política de facturación de " +":guilabel:`Cantidades ordenadas` y puede editarlo y modificarlo en cualquier" +" momento." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:52 msgid "" "If :guilabel:`Delivered quantities` is chosen as the invoicing policy, an " "invoice will **not** be able to be created." msgstr "" +"Si elige :guilabel:`Cantidades entregadas` como política de facturación, " +"**no** podrá crear una factura." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:56 msgid "Request a 50% down payment" -msgstr "" +msgstr "Solicitar un anticipo del 50%" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:58 msgid "" "For the following example, the flow involves a 50% amount down payment on a " "product with :guilabel:`Ordered quantities` as the invoicing policy." msgstr "" +"En el siguiente ejemplo, el flujo implica un anticipo del 50% en un producto" +" que tiene una política de facturación de :guilabel:`Cantidades ordenadas`." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:62 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:184 @@ -6735,6 +6766,8 @@ msgid "" "When the order is confirmed (via the :guilabel:`Confirm` button), it's time " "to create/view the invoice, by clicking :guilabel:`Create Invoice`." msgstr "" +"Cuando confirma la orden (mediante el botón :guilabel:`Confirmar`), podrá " +"crear y ver la factura si hace clic en :guilabel:`Crear factura`." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:67 msgid "" @@ -6743,24 +6776,35 @@ msgid "" "Payment Amount` field. Lastly, click :guilabel:`Create and View Invoice` to " "create and view the invoice." msgstr "" +"Después, en la ventana emergente :guilabel:`Crear facturas` que aparece, " +"seleccione :guilabel:`Anticipo (porcentaje)` y escriba `50` en el campo " +":guilabel:`Importe del anticipo`, por último, haga clic en :guilabel:`Crear " +"y ver factura`." #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "Create invoices pop up window in Odoo Sales." msgstr "" +"Ventana emergente para crear facturas en la aplicación Ventas de Odoo." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:75 msgid "Doing so reveals the draft invoice, which mentions the down payment." msgstr "" +"Al hacer esto, aparecerá el borrador de la factura donde se menciona el " +"anticipo." #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "A sample draft invoice with down payment mentioned in Odoo Sales." msgstr "" +"Un borrador de factura donde se indica un anticipo en la aplicación Ventas " +"de Odoo." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:81 msgid "" "From there, the invoice can be confirmed/posted, and the payment can be " "registered. Return to the sales order, via the breadcrumbs." msgstr "" +"Desde allí puede confirmar y publicar la factura, también puede registrar el" +" pago. Regrese a la orden de venta mediante las migas de pan." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:84 msgid "" @@ -6769,10 +6813,17 @@ msgid "" ":guilabel:`Invoice` button reveals the drafted invoice. In either case, the " "down payment is mentioned on both the sales order and draft invoice." msgstr "" +"En la orden de venta, con el botón inteligente :guilabel:`Vista previa del " +"cliente` podrá visualizar lo que el cliente verá y el botón " +":guilabel:`Factura` mostrará el borrador de la factura. En ambos casos, el " +"anticipo se menciona tanto en la orden de venta como en el borrador de la " +"factura." #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "How the down payment is mentioned on the sales order in Odoo Sales." msgstr "" +"Cómo se menciona el anticipo en la orden de venta en la aplicación Ventas de" +" Odoo." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:92 msgid "" @@ -6786,6 +6837,8 @@ msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "How the register payment pop up looks in Odoo Sales." msgstr "" +"Aspecto de la ventana emergente para registrar un pago en la aplicación " +"Ventas de Odoo." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:101 msgid "" @@ -6794,12 +6847,18 @@ msgid "" "make any other modifications to the other fields, if necessary, before " "clicking :guilabel:`Create Payment`." msgstr "" +"En este formulario, seleccione el :guilabel:`diario` correspondiente y " +"confirme que el importe del anticipo es correcto en el campo " +":guilabel:`Importe`. Si es necesario, haga las modificaciones pertinentes en" +" los otros campos antes de hacer clic en :guilabel:`Crear pago`." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:105 msgid "" "Odoo returns to the invoice, which now has a green :guilabel:`In Payment` " "banner visible in the upper-right corner." msgstr "" +"Odoo regresa a la factura, esta ahora tiene una cinta verde visible en la " +"esquina superior derecha con la leyenda :guilabel:`En proceso de pago`." #: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 msgid "" @@ -6812,6 +6871,9 @@ msgid "" "another invoice must be created. To do that, return to the sales order, and " "click :guilabel:`Create Invoice`." msgstr "" +"Cuando el cliente quiera pagar la cantidad restante de la orden, deberá " +"crear otra factura. Para ello, vuelva a la orden de venta y haga clic en " +":guilabel:`Crear factura`." #: ../../content/applications/sales/sales/invoicing/down_payment.rst:115 msgid "" diff --git a/locale/fr/LC_MESSAGES/administration.po b/locale/fr/LC_MESSAGES/administration.po index 59d76d081..41fe4a1c1 100644 --- a/locale/fr/LC_MESSAGES/administration.po +++ b/locale/fr/LC_MESSAGES/administration.po @@ -758,6 +758,9 @@ msgid "" " listening on :option:`the longpolling port ` " "but the client will not connect to it." msgstr "" +"En configuration multiprocessing, un worker LiveChat dédié est " +"automatiquement lancé et écoute sur le :option:`port longpolling `, mais le client ne s'y connecter pas." #: ../../content/administration/install/deploy.rst:221 msgid "" @@ -765,6 +768,10 @@ msgid "" "``/longpolling/`` to the longpolling port. Other request should be proxied " "to the :option:`normal HTTP port `" msgstr "" +"Vous devez plutôt avoir un proxy qui redirige les requêtes dont l'URL " +"commence par ``/longpolling/`` vers le port longpolling. Les autres requêtes" +" doivent être redirigées vers le :option:`port HTTP normal `" #: ../../content/administration/install/deploy.rst:225 msgid "" @@ -972,6 +979,10 @@ msgid "" "that Odoo, this is the simplest and the longpolling URL can double up as the" " cron instance." msgstr "" +"Déployer une version threadée d'Odoo (au lieu d'une version preforking basée" +" sur les processus) et uniquement rediriger les recoupettes vers les URLs " +"commençant par ``/longpolling/`` vers ce Odoo, c'est la solution la plus " +"simple et l'URL du longpolling peut également servir d'instance cron." #: ../../content/administration/install/deploy.rst:387 msgid "" @@ -979,10 +990,13 @@ msgid "" "``/longpolling/`` to :option:`the longpolling port `." msgstr "" +"Déployer un Odoo evented via ``odoo-gevent`` et requêtes proxy commençant " +"par ``/longpolling/`` vers :option:`le port longpolling `." #: ../../content/administration/install/deploy.rst:392 msgid "Serving Static Files" -msgstr "" +msgstr "Servir des fichiers statiques" #: ../../content/administration/install/deploy.rst:394 msgid "" @@ -990,6 +1004,10 @@ msgid "" "modules. This may not be ideal when it comes to performances, and static " "files should generally be served by a static HTTP server." msgstr "" +"Pour des raisons de commodité de développement, Odoo sert directement tous " +"les fichiers statiques dans ses modules. Ce n'est peut-être pas idéal en " +"termes de performances et les fichiers statiques doivent généralement être " +"servis par un serveur HTTP statique." #: ../../content/administration/install/deploy.rst:398 msgid "" @@ -998,6 +1016,11 @@ msgid "" ":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " "in the various addons paths." msgstr "" +"Les fichiers statiques Odoo se situent dans le fichier ``static/`` de chaque" +" module, donc les fichiers statiques peuvent être servis en interceptant " +"toutes les requêtes vers :samp:`/{MODULE}/static/{FILE}`, et en recherchant " +"le bon module (et fichier) dans les différents chemins d'accès aux modules " +"complémentaires." #: ../../content/administration/install/deploy.rst:402 #: ../../content/administration/upgrade.rst:122 @@ -1010,6 +1033,10 @@ msgid "" "this, and how (e.g. possibility of mapping ir.attachment id to filestore " "hash in the database?)" msgstr "" +"tester s'il serait intéressant de service des pièces jointes stockées dans " +"des fichiers par ce biais et comment (par ex. possibilité de faire " +"correspondre l'id ir.attachment avec le hachage du dépôt de fichiers dans la" +" base de données ?)" #: ../../content/administration/install/deploy.rst:409 msgid "Security" @@ -1867,6 +1894,8 @@ msgid "" "Odoo 15 'deb' package currently supports `Debian 11 (Bullseye)`_, `Ubuntu " "20.04 (Focal)`_ or above." msgstr "" +"Le package Odoo 15 'deb' prend actuellement en charge `Debian 11 " +"(Bullseye)`_, `Ubuntu 20.04 (Focal)`_ ou les versions supérieures." #: ../../content/administration/install/install.rst:114 #: ../../content/administration/install/install.rst:187 @@ -1917,6 +1946,9 @@ msgid "" "distributions. It can be used to install *Odoo Community Edition* by " "executing the following commands **as root**:" msgstr "" +"Odoo S.A. fournit un dépôt qui peut être utilisé avec les distributions " +"Debian et Ubuntu. Il peut être utilisé pour installer l'*Édition Odoo " +"Community* en exécution les commandes suivantes **en tant que racine** :" #: ../../content/administration/install/install.rst:141 msgid "" @@ -1935,7 +1967,7 @@ msgstr "" #: ../../content/administration/install/install.rst:146 msgid "Deb Package" -msgstr "" +msgstr "Package Deb" #: ../../content/administration/install/install.rst:148 msgid "" @@ -1995,7 +2027,7 @@ msgstr "Fedora" #: ../../content/administration/install/install.rst:184 msgid "Odoo 15 'rpm' package supports Fedora 34." -msgstr "" +msgstr "Le package Odoo 15 'rpm' prend en charge Fedora 34." #: ../../content/administration/install/install.rst:189 msgid "" @@ -2042,7 +2074,7 @@ msgstr "" #: ../../content/administration/install/install.rst:237 msgid "Source Install" -msgstr "" +msgstr "Source Install" #: ../../content/administration/install/install.rst:239 msgid "" @@ -2305,6 +2337,8 @@ msgid "" "Open the **Definition** tab and enter the password (e.g. ``odoo``), then " "click **Save**." msgstr "" +"Ouvrez l'onglet **Définition** et saisissez le mot de passe (par ex. " +"``odoo``), puis cliquez sur **Enregistrer**." #: ../../content/administration/install/install.rst:356 msgid "" @@ -2392,6 +2426,9 @@ msgid "" "`rtlcss.cmd` is located (typically: " "`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." msgstr "" +"Modifiez le variable `PATH` de l'environnement système pour ajouter le " +"fichier où se trouve `rtlcss.cmd` (généralement : " +"`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." #: ../../content/administration/install/install.rst:402 #: ../../content/administration/install/install.rst:598 @@ -2467,6 +2504,9 @@ msgid "" "`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password " "and `mydb` is the name of the PostgreSQL database." msgstr "" +"Où `CommunityPath` est le chemin de l'installation Odoo Community, `dbuser` " +"est le login PostgreSQL, `dbpassword` est le mot de passe PostgreSQL et " +"`mydb` est le nom de la base de données PostgreSQL." #: ../../content/administration/install/install.rst:430 #: ../../content/administration/install/install.rst:627 @@ -2529,10 +2569,14 @@ msgid "" "Odoo uses PostgreSQL as database management system. Use your package manager" " to download and install PostgreSQL (supported version: 10.0 and later)." msgstr "" +"Odoo utilise PostgreSQL comme système de gestion de la base de données. " +"Utilisez votre gestionnaire de paquets pour télécharger et installer " +"PostgreSQL (version prise en charge : 10.0 et ultérieure)." #: ../../content/administration/install/install.rst:533 msgid "On Debian/Unbuntu, it can be achieved by executing the following:" msgstr "" +"Sur Debian/Ubuntu, il est possible d'y arriver en exécutant ce qui suit :" #: ../../content/administration/install/install.rst:547 #: ../../content/administration/install/install.rst:743 @@ -2550,12 +2594,19 @@ msgid "" "are available in `-dev` or `-devel` packages for Python, PostgreSQL, " "libxml2, libxslt1, libevent, libsasl2 and libldap2." msgstr "" +"Pour les bibliothèques utilisant du code natif, il est nécessaire " +"d'installer les outils de développement et les dépendances natives avant les" +" dépendances Python d'Odoo. Ils sont disponibles dans les paquets `-dev` ou " +"`-devel` pour Python, PostgreSQL, libxml2, libxslt1, libevent, libsasl2 et " +"libldap2." #: ../../content/administration/install/install.rst:557 msgid "" "On Debian/Unbuntu, the following command should install all the required " "libraries:" msgstr "" +"Sur Debian/Ubuntu, la commande suivante doit installer toutes les " +"bibliothèques requises :" #: ../../content/administration/install/install.rst:571 #: ../../content/administration/install/install.rst:755 @@ -2579,6 +2630,10 @@ msgid "" "defaults `_: connects over a UNIX" " socket on port `5432` with the current user and no password." msgstr "" +"Utilisateur et mot de passe PostgreSQL. Odoo n'a pas de valeurs par défaut " +"autres que celles de `psycopg2's " +"`_: se connecte sur un socket " +"UNIX sur le port `5432` avec l'utilisateur actuel et sans mot de passe." #: ../../content/administration/install/install.rst:624 #: ../../content/administration/install/install.rst:819 @@ -2586,6 +2641,8 @@ msgid "" "Where `CommunityPath` is the path of the Odoo Community installation and " "`mydb` is the name of the PostgreSQL database." msgstr "" +"Où `CommunityPath` est le chemin de l'installation Odoo Community et `mydb` " +"est le nom de la base de données PostgreSQL." #: ../../content/administration/install/install.rst:644 msgid "Mac OS" @@ -2608,6 +2665,9 @@ msgid "" "`_ to download and install PostgreSQL (supported " "version: 10.0 and later)." msgstr "" +"Odoo utilise PostgreSQL comme système de gestion de la base de données. " +"Utilisez `postgres.app `_ pour télécharger et " +"installer PostgreSQL (version prise en charge : 10.0 et ultérieure)." #: ../../content/administration/install/install.rst:731 msgid "" @@ -2656,6 +2716,9 @@ msgid "" "`current limit exceeds maximum limit`. In that case, add the following " "parameter `--limit-memory-hard 0` to avoid the problem." msgstr "" +"Certaines versions de Python sur Mac peuvent conduire au message d'erreur " +"suivant : `current limit exceeds maximum limit`. Dans ce cas, ajoutez le " +"paramètre suivant `--limit-memory-hard 0` pour éviter le problème." #: ../../content/administration/install/install.rst:844 #: ../../content/administration/maintain/update.rst:149 @@ -7031,6 +7094,15 @@ msgid "" "file. To have a concrete example, check out the `requirements.txt file of " "Odoo `_." msgstr "" +"Si votre projet nécessite des dépendances Python supplémentaires ou des " +"versions plus récentes, vous pouvez définir un fichier " +":file:`requirements.txt` dans la racine de vos branches pour les " +"répertorier. La plateforme se charge d'installer ces dépendances dans vos " +"conteneurs. La documentation relative aux `spécificateurs d'exigences pip " +"`_ peut vous aider à écrire un fichier :file:`requirements.txt`. " +"Pour avoir un exemple concret, consultez le `fichier requirements.txt d'Odoo" +" `_." #: ../../content/administration/odoo_sh/advanced/containers.rst:22 msgid "" @@ -7825,6 +7897,8 @@ msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:75 msgid "Setting payment acquirers and shipping providers in test mode." msgstr "" +"La configuration des fournisseurs de paiement et des transporteurs en mode " +"test." #: ../../content/administration/odoo_sh/getting_started/branches.rst:76 msgid "Disabling IAP services" diff --git a/locale/fr/LC_MESSAGES/finance.po b/locale/fr/LC_MESSAGES/finance.po index 33d7ca730..4b0bee0c2 100644 --- a/locale/fr/LC_MESSAGES/finance.po +++ b/locale/fr/LC_MESSAGES/finance.po @@ -45,7 +45,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:47+0000\n" "Last-Translator: Jolien De Paepe, 2023\n" "Language-Team: French (https://app.transifex.com/odoo/teams/41243/fr/)\n" @@ -696,7 +696,6 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:18 #: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:16 #: ../../content/applications/finance/accounting/reporting/budget.rst:11 -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:19 #: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 #: ../../content/applications/finance/accounting/taxes.rst:53 #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 @@ -7038,12 +7037,16 @@ msgid "" "`Odoo Tutorials: Chart of accounts `_" msgstr "" +"`Tutoriels Odoo : Plan comptable `_" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:191 msgid "" "`Odoo Tutorials: Update your chart of accounts " "`_" msgstr "" +"`Tutoriels Odoo : Mettre à jour votre plan comptable " +"`_" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:7 msgid "Accounting cheat sheet" @@ -7765,33 +7768,31 @@ msgstr "" msgid "" "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " "open the journal you want to edit, and select a currency in the field " -":guilabel:`Currency`. If left empty, all active currencies are handled " -"instead of just one." +":guilabel:`Currency`." msgstr "" "Pour ce faire, allez à :menuselection:`Comptabilité --> Configuration --> " -"Journaux`, ouvrez le journal que vous voulez modifiez et sélectionnez une " -"devise dans le champ :guilabel:`Devise`. Si le champ est vide, toutes les " -"devises actives sont prises en compte au lieu d'une seule." +"Journaux`, ouvrez le journal que vous souhaitez modifier et sélectionnez une" +" devise dans le champ :guilabel:`Devise`." #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency for the journal to handle." msgstr "Sélectionnez la devise que le journal doit prendre en compte." -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:114 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 msgid "Multi-currency accounting" msgstr "Comptabilité multidevise " -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:119 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 msgid "Invoices, bills, and other documents" msgstr "Factures clients, factures fournisseurs et autres documents" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:121 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 msgid "" "For all documents, you can select the currency and journal to use for the " -"transaction." +"transaction on the document itself." msgstr "" "Pour tous les documents, vous pouvez sélectionner la devise et le journal à " -"utiliser pour la transaction." +"utiliser pour la transaction sur le document même." #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency and journal to use." @@ -9826,7 +9827,7 @@ msgstr "Le bouton \"Payer maintenant\" sur une facture dans le Portail client" #: ../../content/applications/finance/accounting/payments/online.rst:42 msgid ":doc:`/applications/finance/payment_acquirers`" -msgstr "" +msgstr ":doc:`/applications/finance/payment_acquirers`" #: ../../content/applications/finance/accounting/payments/pay_checks.rst:3 msgid "Pay by checks" @@ -12185,43 +12186,315 @@ msgstr "Intrastat" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 msgid "" -"**Intrastat** is the system for data collection and statistic production of " -"goods traded among the EU Member States. Organizations whose annual trade " -"surpasses a certain threshold must provide data about the goods traded with " -"other EU countries." +"`Intrastat `_ is the data collection and " +"statistics production system for goods traded among EU member states. It " +"collects data on:" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:10 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:9 msgid "" -"`Eurostat Statistics Explained - Glossary: Intrastat " -"`_" +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" msgstr "" -"`Eurostat Statistics Explained - Glossaire : Intrastat " -"`_" +"Les transactions commerciales de marchandises destinées à l'utilisation, à " +"la consommation, aux investissements ou à la revente impliquant un " +"changement de propriété ;" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:14 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:11 msgid "" -"As of January 1, 2022, the reporting requirements have changed. One main " -"modification concerns the transaction codes which are now switching to a " -"2-digits format. All transactions recorded after this date have to follow " -"the new system’s rules." +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" +msgstr "" +"Les déplacements de marchandises sans changement de propriété (par ex. le " +"déplacement de stock ou des mouvements de marchandises avant ou après un " +"travail à façon et après un entretien ou une réparation) ;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:13 +msgid "Returns of goods." +msgstr "Les retours de marchandises." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:16 +msgid "" +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"`_, preferring instead " +"*intra-Union trade in goods statistics*." msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:21 -msgid "" -"Go to :menuselection:`Accounting --> Settings --> Customer Invoices`, then " -"enable **Intrastat** and *Save*. Once the Intrastat has been activated you " -"are able to choose the **Default incoterm**." -msgstr "" +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:23 +msgid "General configuration" +msgstr "Configuration générale" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:25 msgid "" -"If you created your Odoo database prior to **January 13, 2022**, please " -":ref:`upgrade ` the ``account_intrastat`` module to add the" -" new transaction codes and :ref:`install ` the " -"``account_intrastat_expiry`` module to archive the old codes." +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the **Customer Invoices** section, tick " +":guilabel:`Intrastat` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:31 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located, and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:34 +msgid "" +"If your warehouses are located in multiple regions, you can define the " +"region code for each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "Ajout de la région Intrastat à un entrepôt" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:43 +msgid "Default Incoterm" +msgstr "Incoterm par défaut" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "" +"You can set **default Incoterms** for your company by selecting an Intrastat" +" **code** in the :guilabel:`Default Incoterm` field of the **Customer " +"Invoices** section, and then clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "Product configuration" +msgstr "Configuration du produit" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:54 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" +"Tous les produits doivent être correctement configurés pour être inclus dans" +" le rapport Intrastat." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:59 +msgid "Commodity code" +msgstr "Code marchandises" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:61 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature `_." +msgstr "" +"Les codes marchandises sont des numéros de référence reconnus au niveau " +"international et sont utilisés pour classer les marchandises en fonction de " +"leur **nature**. Intrastat utilise la `Nomenclature combinée " +"`_." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:64 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" +"Pour ajouter un code marchandises, allez à :menuselection:`Comptabilité --> " +"Clients --> Produits` et sélectionnez un produit. Dans l'onglet " +":guilabel:`Comptabilité`, définissez le :guilabel:`Code marchandises` du " +"produit." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:68 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"`_" +msgstr "" +"`Banque Nationale de Belgique - Codes marchandises Intrastat " +"`_" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:74 +msgid "Country of origin" +msgstr "Pays d'origine" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:76 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" +"Pour ajouter le pays d'origine d'un produit, allez à " +":menuselection:`Comptabilité --> Clients --> Produits` et sélectionnez un " +"produit. Dans l'onglet :guilabel:`Comptabilité`, définissez le " +":guilabel:`Pays d'origine`." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:82 +msgid "Invoices and bills configuration" +msgstr "Configuration des factures clients et fournisseurs" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:84 +msgid "" +"Once products are properly configured, several settings must be enabled on " +"the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:90 +msgid "Transaction code" +msgstr "Code de transaction" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:92 +msgid "" +"Transaction codes are used to identify a transaction's nature. To set a " +"transaction code on an invoice line, create an invoice or bill, click the " +":guilabel:`⋮` button, tick :guilabel:`Intrastat`, and use the newly-added " +":guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "Ajout de la colonne Intrastat à une facture client ou fournisseur" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:101 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"`_" +msgstr "" +"`Banque Nationale de Belgique - Intrastat : Natures de transactions à partir" +" de janvier 2022 " +"`_" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:107 +msgid "Partner country" +msgstr "Pays partenaire" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:109 +msgid "" +"The partner country is the vendor's or customer's country, depending on " +"whether it is an invoice or bill. It is automatically filled in using the " +":guilabel:`Country` field in the **contact form** of the partner." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:113 +msgid "" +"To edit the partner country manually, click on the :guilabel:`Other Info` " +"tab when on an invoice or bill, and select the :guilabel:`Intrastat " +"Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "Transport code" +msgstr "Code de transport" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:121 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch). Once you have selected a :ref:`partner" +" country `, the :guilabel:`Intrastat Transport " +"Mode` becomes available." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "Value of the goods" +msgstr "Valeur des marchandises" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:130 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" +"La valeur d'une marchandise est le :guilabel:`sous-total` hors taxes (le " +":guilabel:`Prix` multiplié par la :guilabel:`Quantité`) d'une ligne de " +"facture." + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "Partner configuration" +msgstr "Configuration du partenaire" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:138 +msgid "" +"Two fields from the partner's **contact form** are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set ` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:143 +msgid "Generate the Intrastat report" +msgstr "Générer le rapport Intrastat" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:145 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration ` and the " +"information on the :ref:`products `, " +":ref:`invoices and bills `, and " +":ref:`partners `." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"Export the report as a PDF, XLSX, or XML file to submit it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:153 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" +"Chaque ligne du rapport fait référence à une seule ligne de facture et " +"contient les informations suivantes :" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:155 +msgid "Invoice or bill reference number;" +msgstr "Numéro de référence de la facture client ou fournisseur ;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:156 +msgid "" +":guilabel:`System`, which is a code automatically generated depending on " +"whether the document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:158 +msgid "" +":ref:`Country `, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" +":ref:`Pays `, c'est-à-dire le pays du fournisseur" +" pour les arrivées et le pays du client pour les expéditions ;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:160 +msgid ":ref:`Transaction Code `;" +msgstr ":ref:`Code de transaction ` ;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:161 +msgid "" +":ref:`Region Code ` (if your company is located in " +"Belgium);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:162 +msgid ":ref:`Commodity Code `;" +msgstr ":ref:`Code marchandises ` ;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:163 +msgid ":ref:`Origin Country `;" +msgstr ":ref:`Pays d'origine ` ;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:164 +msgid ":ref:`Partner VAT `;" +msgstr ":ref:`TVA partenaire ` ;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid ":ref:`Transport Code `;" +msgstr ":ref:`Code de transport ` ;" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:166 +msgid "" +":ref:`Value `, which is always expressed in EUR even if the" +" original invoice or bill used another currency." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 @@ -12308,7 +12581,7 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:35 msgid ":doc:`/developer/reference/external_api`" -msgstr "" +msgstr ":doc:`/developer/reference/external_api`" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:40 msgid "One key per database" @@ -16811,6 +17084,15 @@ msgid "" "` to " "learn more about units of measure and how to configure them." msgstr "" +"L'application *Ventes* permet de créer et de modifier les unités de mesure " +"(par ex. unités, kilomètres, nuits, etc.). Allez à l'application " +":menuselection:`Ventes --> Configuration --> Paramètres` et assurez-vous que" +" l'option `Unités de Mesure` est activée dans la section `Catélogue de " +"produits`. Cliquez sur le lien interne des :guilabel:`Unités de Mesure` pour" +" afficher, créer et modifier les unités de mesure. Consultez :doc:`ce " +"document " +"` pour en" +" apprendre plus sur les unités de mesure et la façon de les configurer." #: ../../content/applications/finance/expenses.rst:44 msgid "" @@ -16966,6 +17248,8 @@ msgid "" ":guilabel:`Total`: Enter the total amount paid for the expense in one of two" " ways:" msgstr "" +":guilabel:`Total` : Saisissez le montant total payé pour la note de frais de" +" l'une des deux manières suivantes :" #: ../../content/applications/finance/expenses.rst:96 msgid "" @@ -17141,7 +17425,7 @@ msgstr "" #: ../../content/applications/finance/expenses.rst:175 msgid "Create new expenses from a scanned receipt" -msgstr "" +msgstr "Créer de nouvelles notes de frais à partir d'un reçu numérisé" #: ../../content/applications/finance/expenses.rst:177 msgid "" @@ -17163,6 +17447,8 @@ msgid "" "Create an expense by scanning a receipt. Click Scan at the top of the Expenses dashboard\n" "view." msgstr "" +"Créez une note de frais en numérisant un reçu. Cliquez sur Numériser en haut" +" de la vue du tableau de bord des Notes de frais." #: ../../content/applications/finance/expenses.rst:190 msgid "" @@ -17193,6 +17479,10 @@ msgid "" ":menuselection:`Expenses app --> Configuration --> Settings`. Ensure " ":guilabel:`Incoming Emails` is enabled." msgstr "" +"Pour ce faire, vous devez d'abord configurer un alias d'email. Allez à " +"l'application :menuselection:`Notes de frais --> Configuration --> " +"Paramètres`. Assurez-vous que l'option :guilabel:`Emails entrants` est " +"activée." #: ../../content/applications/finance/expenses.rst-1 #: ../../content/applications/finance/expenses.rst:0 @@ -17745,6 +18035,12 @@ msgid "" "or :guilabel:`Reset to Draft`. Click :guilabel:`Post Journal Entries` to " "post the report." msgstr "" +"Pour comptabiliser un rapport individuel, cliquez sur un rapport pour voir " +"ses détails. Dans cette vue, il y a plusieurs options : " +":guilabel:`Comptabiliser les écritures`, :guilabel:`Rapporter dans la " +"prochaine fiche de paie`, :guilabel:`Refuser`, ou :guilabel:`Remettre en " +"brouillon`. Cliquez sur :guilabel:`Comptabiliser les écritures` pour " +"enregistrer le rapport." #: ../../content/applications/finance/expenses.rst:466 msgid "" @@ -18005,6 +18301,8 @@ msgid "" "After the expense report is posted to the journal entry, the sales order can be called up\n" "by clicking on the sales order number." msgstr "" +"Une fois le rapport de note de frais enregistré dans la pièce comptable, vous pouvez accéder à la commande\n" +"en cliquant sur le numéro de la commande." #: ../../content/applications/finance/expenses.rst:586 msgid "" @@ -18014,7 +18312,7 @@ msgstr "" #: ../../content/applications/finance/expenses.rst-1 msgid "See the expenses listed on the sales order after clicking into it." -msgstr "" +msgstr "Voir les dépenses listées sur la commande après avoir cliqué dessus." #: ../../content/applications/finance/expenses.rst:593 msgid "" @@ -18024,6 +18322,11 @@ msgid "" " it. Then, click :guilabel:`Create Invoice`. The customer has now been " "invoiced for the expenses." msgstr "" +"Cliquez ensuite sur :guilabel:`Créer une facture` et sélectionnez si une " +"facture est une :guilabel:`Facture normale`, un :guilabel:`Acompte " +"(pourcentage)` ou un :guilabel:`Acompte (montant fixe)` en cliquant sur le " +"bouton radio à côté. Ensuite, cliquez sur :guilabel:`Créer une facture`. Les" +" dépenses ont été facturées au client." #: ../../content/applications/finance/fiscal_localizations.rst:5 msgid "Fiscal localizations" @@ -20961,11 +21264,11 @@ msgstr "Taxes." #: ../../content/applications/finance/fiscal_localizations/chile.rst:151 #: ../../content/applications/finance/fiscal_localizations/peru.rst:70 msgid "Default Account Payable." -msgstr "Compte client par défaut." +msgstr "Compte fournisseur par défaut." #: ../../content/applications/finance/fiscal_localizations/chile.rst:152 msgid "Default Account Receivable." -msgstr "Compte fournisseur par défaut." +msgstr "Compte client par défaut." #: ../../content/applications/finance/fiscal_localizations/chile.rst:153 msgid "Transfer Accounts." @@ -25307,6 +25610,7 @@ msgid "2-digits comparison" msgstr "Comparaison à 2 chiffres" #: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:61 msgid "Template" msgstr "Modèle" @@ -32805,16 +33109,23 @@ msgid "" " This module has a dependency with *Peru - Accounting*. In case this last " "one is not installed, Odoo installs it automatically within EDI." msgstr "" +"Allez aux *Apps* et recherchez Pérou. Cliquez ensuite sur installer dans la " +"carte du module EDI pour le Pérou. Ce module a une dépendance avec *Pérou - " +"Comptabilité*. Si ce dernier module n'est pas installé, Odoo l'installe " +"automatiquement avec EDI." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "The \"Module\" filter is set on \"Peru\"" -msgstr "" +msgstr "Le filtre \"Module\" lit \"Pérou\"" #: ../../content/applications/finance/fiscal_localizations/peru.rst:39 msgid "" "When you install a database from scratch selecting Peru as country, Odoo " "automatically installs the base module: Peru - Accounting." msgstr "" +"Lorsque vous installez une base de données à partir de zéro en sélectionnant" +" le Pérou comme pays, Odoo installe automatiquement le module de base : " +"Pérou - Comptabilité." #: ../../content/applications/finance/fiscal_localizations/peru.rst:45 msgid "" @@ -32824,10 +33135,17 @@ msgid "" "by the SUNAT when companies register their RUC (Unique Contributor " "Registration):" msgstr "" +"En plus des informations de base de la Société, vous devez configurer le " +"Pérou comme Pays pour que la facturation électronique fonctionne " +"correctement. Le champ **Code de type d'adresse** représente le code " +"d'établissement assigné par le SUNAT lorsque les sociétés enregistrent leur " +"RUC (numéro d'enregistrement de contribuable unique) : " #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Company data for Peru including RUC and Address type code" msgstr "" +"Données de société pour le Pérou, y compris le RUC et le code de type " +"d'adresse" #: ../../content/applications/finance/fiscal_localizations/peru.rst:56 msgid "" @@ -32835,10 +33153,13 @@ msgid "" "value: 0000. Be aware that if an incorrect value is entered, the Electronic " "invoice validation might have errors." msgstr "" +"Si le code de type d'adresse est inconnu, vous devez le configurer sur la " +"valeur par défaut : 0000. Attention, si une valeur incorrecte est saisie, la" +" validation de la facturation électronique risque d'entraîner des erreurs." #: ../../content/applications/finance/fiscal_localizations/peru.rst:60 msgid "The NIF should be set following the RUC format." -msgstr "" +msgstr "Le NIF doit être défini selon le format RUC." #: ../../content/applications/finance/fiscal_localizations/peru.rst:64 msgid "Chart of Account" @@ -32850,10 +33171,13 @@ msgid "" "included in the localization module, the accounts are mapped automatically " "in:" msgstr "" +"Le plan comptable est installé par défaut puisqu'il fait partie de " +"l'ensemble des données incluses dans le module de localisation. Les comptes " +"sont mappés automatiquement dans :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:71 msgid "Default Account Receivable" -msgstr "" +msgstr "Compte client par défaut" #: ../../content/applications/finance/fiscal_localizations/peru.rst:73 msgid "" @@ -32861,6 +33185,9 @@ msgid "" ":abbr:`PCGE (Plan Contable General Empresarial)`, which is grouped in " "several categories and is compatible with NIIF accounting." msgstr "" +"Le plan comptable pour le Pérou est basé sur la version la plus récente du " +":abbr:`PCGE (Plan Contable General Empresarial)`, qui est regroupé en " +"plusieurs catégories et est compatible avec la comptabilité NIIF." #: ../../content/applications/finance/fiscal_localizations/peru.rst:78 msgid "Accounting Settings" @@ -32873,10 +33200,14 @@ msgid "" " this, go to :menuselection:`Accounting --> Settings --> Peruvian " "Localization`." msgstr "" +"Une fois que vous avez installé les modules et configuré les informations de" +" base de votre société, vous devez configurer les éléments requis pour la " +"facturation électronique. Allez à :menuselection:`Comptabilité --> " +"Paramètres --> Localisation péruvienne`." #: ../../content/applications/finance/fiscal_localizations/peru.rst:85 msgid "Basic Concepts" -msgstr "" +msgstr "Concepts de base" #: ../../content/applications/finance/fiscal_localizations/peru.rst:87 msgid "Here are some terms that are essential on the Peruvian localization:" @@ -32888,6 +33219,8 @@ msgid "" "**EDI**: Electronic Data Interchange, which in this refers to the Electronic" " Invoice." msgstr "" +"**EDI** : Échange de données informatisé, qui désigne ici la facture " +"électronique." #: ../../content/applications/finance/fiscal_localizations/peru.rst:90 msgid "" @@ -32901,20 +33234,25 @@ msgid "" "**OSE**: Electronic Service Operator, `OSE SUNAT's definition " "`_." msgstr "" +"**OSE** : Opérateur de services électroniques, `définition OSE SUNAT " +"`_." #: ../../content/applications/finance/fiscal_localizations/peru.rst:93 msgid "**CDR**: Receipt certificate (Constancia de Recepción)." -msgstr "" +msgstr "**CDR** : Certificat de réception (Constancia de Recepción)." #: ../../content/applications/finance/fiscal_localizations/peru.rst:94 msgid "" "**SOL Credentials**: Sunat Operaciones en Línea. User and password are " "provided by the SUNAT and grant access to Online Operations systems." msgstr "" +"**Identifiants SOL** : Opératinos en ligne SUNAT. L'utilisateur et le mot de" +" passe sont fournis par la SUNAT et donnent accès aux systèmes des " +"opérations en ligne." #: ../../content/applications/finance/fiscal_localizations/peru.rst:99 msgid "Signature Provider" -msgstr "" +msgstr "Fournisseur de signature" #: ../../content/applications/finance/fiscal_localizations/peru.rst:101 msgid "" @@ -32923,54 +33261,66 @@ msgid "" "signing process and manage the SUNAT validation response. Odoo offers three " "options:" msgstr "" +"Dans le cadre des exigences relatives à la facturation électronique au " +"Pérou, votre entreprise doit choisir un fournisseur de signature qui " +"s'occupera du processus de signature du document et gérera la réponse de " +"validation de la SUNAT. Odoo propose trois options :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:105 #: ../../content/applications/finance/fiscal_localizations/peru.rst:112 msgid "IAP (Odoo In-App Purchase)" -msgstr "" +msgstr "IAP (Achats In-App d'Odoo)" #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 #: ../../content/applications/finance/fiscal_localizations/peru.rst:106 #: ../../content/applications/finance/fiscal_localizations/peru.rst:170 msgid "Digiflow" -msgstr "" +msgstr "Digiflow" #: ../../content/applications/finance/fiscal_localizations/peru.rst:107 #: ../../content/applications/finance/fiscal_localizations/peru.rst:186 msgid "SUNAT" -msgstr "" +msgstr "SUNAT" #: ../../content/applications/finance/fiscal_localizations/peru.rst:109 msgid "" "Please refer to the sections below to check the details and considerations " "for each option." msgstr "" +"Lisez les sections suivantes pour connaître les détails et les " +"considérations de chaque option." #: ../../content/applications/finance/fiscal_localizations/peru.rst:114 msgid "" "This is the default and the suggested option, considering the digital " "ceritificate is included as part of the service." msgstr "" +"Il s'agit de l'option suggérée par défaut, étant donné que le certificat " +"numérique est inclus dans les services." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "IAP option as signature providers" -msgstr "" +msgstr "Option IAP comme fournisseurs de signature" #: ../../content/applications/finance/fiscal_localizations/peru.rst:122 msgid "What is the IAP?" -msgstr "" +msgstr "Qu'est-ce que l'IAP ?" #: ../../content/applications/finance/fiscal_localizations/peru.rst:124 msgid "" "This is a signature service offered directly by Odoo, the service takes care" " of the next process:" msgstr "" +"Il s'agit d'un service de signature proposé directement par Odoo, le service" +" prend en charge le processus suivant :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:126 msgid "" "Provides the Electronic invoice Certificate, so you do not need to acquire " "one by yourself." msgstr "" +"Fournit le certificat de facture électronique, de sorte que vous n'avez pas " +"besoin d'en acquérir un vous-même." #: ../../content/applications/finance/fiscal_localizations/peru.rst:127 msgid "Send the document to the OSE, in this case, Digiflow." @@ -32990,6 +33340,9 @@ msgid "" "Odoo provides 1000 credits for free in new databases. After these credits " "are consumed, you need to buy a Credit Package." msgstr "" +"Le service nécessite des crédits pour traiter vos documents électroniques. " +"Odoo fournit gratuitement 1.000 crédits pour les nouvelles bases de données." +" Une fois ces crédits consommés, vous devez acheter un Package de crédits." #: ../../content/applications/finance/fiscal_localizations/peru.rst:138 msgid "Credits" @@ -33017,19 +33370,19 @@ msgstr "10,000" #: ../../content/applications/finance/fiscal_localizations/peru.rst:144 msgid "220" -msgstr "" +msgstr "220" #: ../../content/applications/finance/fiscal_localizations/peru.rst:146 msgid "20,000" -msgstr "" +msgstr "20.000" #: ../../content/applications/finance/fiscal_localizations/peru.rst:146 msgid "440" -msgstr "" +msgstr "440" #: ../../content/applications/finance/fiscal_localizations/peru.rst:149 msgid "The credits are consumed per each document that is sent to the OSE." -msgstr "" +msgstr "Les crédits sont consommés par document qui est envoyé à l'OSE." #: ../../content/applications/finance/fiscal_localizations/peru.rst:152 msgid "" @@ -33038,6 +33391,10 @@ msgid "" " you verify all information is correct before sending your document to the " "OSE." msgstr "" +"Si vous avez une erreur de validation et le document doit être envoyé plus " +"d'une fois, un crédit additionnel vous sera chargé. Il est donc primordial " +"de vérifier que toutes les informations sont correctes avant d'envoyer votre" +" document à l'OSE." #: ../../content/applications/finance/fiscal_localizations/peru.rst:157 msgid "What do you need to do?" @@ -33048,6 +33405,9 @@ msgid "" "In Odoo, once your enterprise contract is activated and you start working in" " Production, you need to buy credits once the first 1000 are consumed." msgstr "" +"Dans Odoo, une fois que votre contrat d'entreprise est activé et que vous " +"commencez à travailler dans un environnement de production, vous devez " +"acheter des crédits une fois que les 1.000 premiers crédits sont consommés." #: ../../content/applications/finance/fiscal_localizations/peru.rst:161 msgid "" @@ -33056,6 +33416,11 @@ msgid "" "process. For more information, please check `OSE Affiliation guide " "`_." msgstr "" +"Puisque Digiflow est l'OSE utilisé dans l'IAP, vous devez l'affilier en tant" +" qu'OSE officiel de votre société sur le site web de la SUNAT. C'est une " +"procédure simple. Pour plus d'informations, veuillez consulter le `guide " +"d'affiliation OSE " +"`_." #: ../../content/applications/finance/fiscal_localizations/peru.rst:165 msgid "" @@ -33063,6 +33428,9 @@ msgid "" " " "`_." msgstr "" +"Enregistrez Digiflow en tant que PSE (Fournisseur de services électroniques)" +" autorisé, veuillez consulter le `guide d'affiliation PSE " +"`_." #: ../../content/applications/finance/fiscal_localizations/peru.rst:172 msgid "" @@ -33070,6 +33438,9 @@ msgid "" " you can send your document validation directly to Digiflow. In this case " "you need to consider:" msgstr "" +"Cette option peut être utilisée comme alternative. Au lieu d'utiliser les " +"services IAP, vous pouvez envoyer la validation de vos documents directement" +" à Digiflow. Dans ce cas, vous devez prendre en compte les points suivants :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:175 #: ../../content/applications/finance/fiscal_localizations/peru.rst:192 @@ -33079,16 +33450,22 @@ msgid "" "Ceritifcates " "`_." msgstr "" +"Achetez votre propre certificat numérique : Pour plus de détails relatifs à " +"la liste des fournisseurs officiels et le processus d'acquisition, veuillez " +"vous référer aux `certificats numériques de la SUNAT " +"`_." #: ../../content/applications/finance/fiscal_localizations/peru.rst:178 msgid "" "Sign a service agreement directly with `Digiflow " "`_." msgstr "" +"Signez un accord de service directement avec `Digiflow " +"`_." #: ../../content/applications/finance/fiscal_localizations/peru.rst:179 msgid "Provide your SOL credentials." -msgstr "" +msgstr "Fournissez vos identifiants SOL." #: ../../content/applications/finance/fiscal_localizations/peru.rst:188 msgid "" @@ -33096,20 +33473,27 @@ msgid "" "to select this option in your configuration. In this case you need to " "consider: - Get the SUNAT Certification process accepted." msgstr "" +"Si votre société souhaite directement signer avec la SUNAT, il est possible " +"de sélectionner cette option dans votre configuration. Dans ce cas, vous " +"devez prendre en considération les points suivants : - Faire accepter le " +"processus de certification de la SUNAT." #: ../../content/applications/finance/fiscal_localizations/peru.rst:196 msgid "Provide you SOL credentials." -msgstr "" +msgstr "Fournir vos identifiants SOL." #: ../../content/applications/finance/fiscal_localizations/peru.rst:199 msgid "" "When using direct connection with the SUNAT, the SOL User must be set with " "the Company RUT + User Id. Example: ``20121888549JOHNSMITH``" msgstr "" +"En cas de connexion directe avec la SUNAT, l'utilisateur SOL doit être " +"définir avec le RUT et l'identifiant utilisateur de la société. Par exemple " +": ``20121888549JOHNSMITH``" #: ../../content/applications/finance/fiscal_localizations/peru.rst:203 msgid "Testing environment" -msgstr "" +msgstr "Environnement de test" #: ../../content/applications/finance/fiscal_localizations/peru.rst:205 msgid "" @@ -33149,7 +33533,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "EDI Certificate wizard" -msgstr "" +msgstr "Assistant de certificat EDI" #: ../../content/applications/finance/fiscal_localizations/peru.rst:228 msgid "" @@ -33157,16 +33541,22 @@ msgid "" " Odoo can connect directly to its services and get the currency rate either " "automatically or manually." msgstr "" +"Le taux de change officiel au Pérou est fourni par la Banque du Pérou. Odoo " +"peut se connecter directement à ses services et obtenir le taux de change " +"automatiquement ou manuellement." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Bank of Peru is displayed in Multicurrency Service option" -msgstr "" +msgstr "La Banque du Pérou s'affiche dans l'option Service multi-devises." #: ../../content/applications/finance/fiscal_localizations/peru.rst:235 msgid "" "Please refer to the next section in our documentation for more information " "about :doc:`multicurrencies <../accounting/get_started/multi_currency>`." msgstr "" +"Veuillez consulter la section suivante de notre documentation pour obtenir " +"plus d'informations sur les :doc:`multi-devises " +"<../accounting/get_started/multi_currency>`." #: ../../content/applications/finance/fiscal_localizations/peru.rst:239 msgid "Configure Master data" @@ -33183,11 +33573,11 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "List of default taxes" -msgstr "" +msgstr "Liste des taxes par défaut" #: ../../content/applications/finance/fiscal_localizations/peru.rst:252 msgid "EDI Configuration" -msgstr "" +msgstr "Configuration EDI" #: ../../content/applications/finance/fiscal_localizations/peru.rst:254 msgid "" @@ -33195,10 +33585,14 @@ msgid "" "electronic invoice, the taxes created by default have this data included, " "but in case you create new taxes make sure you fill in the fields:" msgstr "" +"Dans le cadre de la configuration des taxes, il y a trois nouveaux champs " +"requis pour la facture électronique. Les taxes créées par défaut incluent " +"ces données, mais si vous créez de nouvelles taxes, assurez-vous de remplir " +"les champs suivants : " #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Taxes EDI data for Peru" -msgstr "" +msgstr "Données EDI des taxes pour le Pérou" #: ../../content/applications/finance/fiscal_localizations/peru.rst:266 msgid "" @@ -33228,6 +33622,10 @@ msgid "" "types, defined by the government fiscal authorities, in this case by the " "SUNAT." msgstr "" +"Dans certains pays d'Amérique latine, dont le Pérou, certaines transactions " +"comptables telles que les factures clients et les factures fournisseurs sont" +" classées par types de document, définis par les autorités fiscales " +"gouvernementales, en l'occurrence la SUNAT." #: ../../content/applications/finance/fiscal_localizations/peru.rst:279 msgid "" @@ -33236,28 +33634,39 @@ msgid "" "country on which the document is applicable;the data is created " "automatically when the localization module is installed." msgstr "" +"Chaque type de document se voit attribuer une séquence unique selon le " +"journal auquel il est affecté. Dans le cadre de la localisation, le type de " +"document inclut le pays sur lequel le document est applicable et les données" +" sont créées automatiquement lors de l'installation du module de " +"localisation." #: ../../content/applications/finance/fiscal_localizations/peru.rst:283 msgid "" "The information required for the document types is included by default so " "the user does not need to fill anything on this view:" msgstr "" +"Les informations requises pour les types de documents sont incluses par " +"défaut, de sorte que l'utilisateur n'a rien à compléter dans cette vue :" #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Document Type list" -msgstr "" +msgstr "Liste des types de documents" #: ../../content/applications/finance/fiscal_localizations/peru.rst:291 msgid "" "Currently the documents supported on customer invoices are: Invoice, Boleta," " Debit Note and Credit Note." msgstr "" +"Les documents actuellement pris en charge sur les factures clients sont : " +"Facture, Boleta, Note de débit et Avoir." #: ../../content/applications/finance/fiscal_localizations/peru.rst:297 msgid "" "When creating Sales Journals, the following information must be filled, in " "addition to the standard fields on the Journals:" msgstr "" +"Lors de la création des journaux de vente, les informations suivantes " +"doivent être complétées, en plus des champs standards sur les journaux :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:301 msgid "Use Documents" @@ -33270,6 +33679,10 @@ msgid "" "related to the different set of document types available in Peru. By " "default, all the sales journals created use documents." msgstr "" +"Ce champ est utilisé pour définir si le journal utilise des types de " +"documents. Il ne s'applique qu'aux journaux de vente et d'achat, qui peuvent" +" être liés aux différents types de documents disponibles au Pérou. Par " +"défaut, tous les journaux de vente créés utilisent des documents." #: ../../content/applications/finance/fiscal_localizations/peru.rst:308 msgid "Electronic Data Interchange" @@ -33280,16 +33693,20 @@ msgid "" "This section indicates which EDI workflow is used in the invoice, for Peru " "we must select “Peru UBL 2.1”." msgstr "" +"Cette section indique quel flux de travail EDI est utilisé dans la facture. " +"Pour le Pérou, vous devez sélectionner \"Peru UBL 2.1\"." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Journal EDI field" -msgstr "" +msgstr "Champ EDI journal" #: ../../content/applications/finance/fiscal_localizations/peru.rst:318 msgid "" "By default, the value Factur-X (FR) is always displayed, make sure you can " "uncheck it manually." msgstr "" +"Par défaut, la valeur Factur-X (FR) s'affiche toujours. Assurez-vous de la " +"décocher manuellement." #: ../../content/applications/finance/fiscal_localizations/peru.rst:326 msgid "" @@ -33298,10 +33715,15 @@ msgid "" "essential for most transactions either on the sender company and in the " "customer, make sure you fill in this information in your records." msgstr "" +"Dans le cadre de la localisation péruvienne, les types d'identification " +"définis par la SUNAT sont désormais disponibles sur le formulaire " +"partenaire. Ces informations sont essentielles pour la plupart des " +"transactions, tant pour la société expéditrice que pour le client. Assurez-" +"vous de remplir ces informations sur vos enregistrements." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Partner identification type" -msgstr "" +msgstr "Type d'identification du partenaire" #: ../../content/applications/finance/fiscal_localizations/peru.rst:336 msgid "Product" @@ -33313,10 +33735,13 @@ msgid "" "localization, the UNSPC Code on the product is a required value to be " "configured." msgstr "" +"En plus des informations de base de vos produits, pour la localisation " +"péruvienne, le Code UNSPC sur le produit est une valeur obligatoire à " +"configurer." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "UNSPC Code on products" -msgstr "" +msgstr "Code UNSPC sur les produits" #: ../../content/applications/finance/fiscal_localizations/peru.rst:350 msgid "Customer invoice" @@ -33324,7 +33749,7 @@ msgstr "Facture client" #: ../../content/applications/finance/fiscal_localizations/peru.rst:353 msgid "EDI Elements" -msgstr "" +msgstr "Éléments EDI" #: ../../content/applications/finance/fiscal_localizations/peru.rst:355 msgid "" @@ -33334,16 +33759,24 @@ msgid "" "<../accounting/customer_invoices/overview>`, there are a couple of fields " "required as part of the Peru EDI:" msgstr "" +"Une fois que vous avez configuré vos données de base, les factures peuvent " +"être créées à partir de votre commande ou manuellement. En plus des " +"informations de base décrites sur :doc:`notre page concernant le processus " +"de facturation <../accounting/customer_invoices/overview>`, quelques champs " +"sont requis dans le cadre de l'EDI pour le Pérou :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:360 msgid "" "**Document type**: The default value is “Factura Electronica” but you can " "manually change the document type if needed and select Boleta for example." msgstr "" +"**Type de document** : La valeur par défaut est \"Factura Electrónica\", " +"mais vous pouvez modifier manuellement le type de document si nécessaire et " +"sélectionnez Boleta par exemple." #: ../../content/applications/finance/fiscal_localizations/peru.rst:0 msgid "Invoice document type field on invoices" -msgstr "" +msgstr "Champ type de document sur une facture" #: ../../content/applications/finance/fiscal_localizations/peru.rst:367 msgid "" @@ -33352,10 +33785,14 @@ msgid "" "another value can be selected manually when needed, for example Export of " "Goods." msgstr "" +"**Type d'opération** : Cette valeur est obligatoire pour la facture " +"électronique et indique le type de transaction. La valeur par défaut est " +"\"Internal Sale\", mais une autre valeur peut être sélectionnée manuellement" +" si nécessaire, par exemple Exportation de marchandises." #: ../../content/applications/finance/fiscal_localizations/peru.rst:0 msgid "Invoice operation type field on invoices" -msgstr "" +msgstr "Champ de type d'opération sur une facture" #: ../../content/applications/finance/fiscal_localizations/peru.rst:375 msgid "" @@ -33365,10 +33802,16 @@ msgid "" "are associated with a default EDI affection reason, if needed you can " "manually select another one when creating the invoice." msgstr "" +"**Motif de l'affectation EDI** : Dans les lignes de la facture, en plus de " +"la taxe, il y a un champ \"Motif de l'affectation EDI\" qui détermine le " +"champ d'application de la taxe sur la base de la liste de la SUNAT qui est " +"affichée. Toutes les taxes chargées par défaut sont associées à un motif " +"d'affectation EDI par défaut. Si nécessaire, vous pouvez en sélectionner un " +"autre manuellement lors de la création de la facture." #: ../../content/applications/finance/fiscal_localizations/peru.rst:0 msgid "Tax affectation reason in invoice line" -msgstr "" +msgstr "Motif d'affectation de la taxe dans la ligne de facture" #: ../../content/applications/finance/fiscal_localizations/peru.rst:387 msgid "" @@ -33385,18 +33828,20 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Sending of EDI Invoice in blue" -msgstr "" +msgstr "Envoi de la facture EDI en bleu" #: ../../content/applications/finance/fiscal_localizations/peru.rst:395 msgid "" "Asynchronous means that the document is not sent automatically after the " "invoice has been posted." msgstr "" +"Asynchrone signifie que le document n'est pas envoyé automatiquement après " +"la comptabilisation de la facture." #: ../../content/applications/finance/fiscal_localizations/peru.rst:398 #: ../../content/applications/finance/fiscal_localizations/peru.rst:492 msgid "Electronic Invoice Status" -msgstr "" +msgstr "Statut de la facture électronique" #: ../../content/applications/finance/fiscal_localizations/peru.rst:400 msgid "" @@ -33405,10 +33850,14 @@ msgid "" "runs every hour, or the user can send it immediately by clicking on the " "button “Sent now”." msgstr "" +"**À envoyer** : Indique que le document est prêt à être envoyé à l'OSE, cela" +" peut être fait soit automatiquement par Odoo grâce à un *cron* qui " +"s'exécute toutes les heures, soit l'utilisateur peut l'envoyer immédiatement" +" en cliquant sur le bouton \"Envoyer maintenant\"." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Send EDI manually" -msgstr "" +msgstr "Envoyer l'EDI manuellement" #: ../../content/applications/finance/fiscal_localizations/peru.rst:408 msgid "" @@ -33416,10 +33865,14 @@ msgid "" "validated. As part of the validation a ZIP file is downloaded and a message " "is logged in the chatter indicating the correct Government validation." msgstr "" +"**Envoyé** : Indique que le document a été envoyé à l'OSE et a été validé " +"avec succès. Dans le cadre de la validation, un fichier ZIP est téléchargé " +"et un message est enregistré dans le chatter indiquant la validation " +"correcte du gouvernement." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Message on chatter when the invoice is valid" -msgstr "" +msgstr "Message sur le chatter après la validation de la facture" #: ../../content/applications/finance/fiscal_localizations/peru.rst:416 msgid "" @@ -33427,6 +33880,9 @@ msgid "" " “To be sent” so the corrections can be made and the invoice can be sent " "again." msgstr "" +"En cas d'erreur de validation, le statut de la facture électronique reste " +"sur \"À envoyer\" afin que les corrections puissent être apportées et que la" +" facture puisse être envoyées à nouveau." #: ../../content/applications/finance/fiscal_localizations/peru.rst:420 msgid "" @@ -33444,10 +33900,14 @@ msgid "" "when this happens Odoo sends a message at the top of the invoice indicating " "the error details and in the most common cases a hint to fix the issue." msgstr "" +"Il y a de multiples raisons derrière un rejet de l'OSE ou de la SUNAT. " +"Lorsque cela se produit, Odoo envoie un message en haut de la facture " +"indiquant les détails de l'erreur et, dans les cas les plus courants, un " +"conseil pour résoudre le problème." #: ../../content/applications/finance/fiscal_localizations/peru.rst:431 msgid "If a validation error is received, you have two options:" -msgstr "" +msgstr "Si une erreur de validation est reçue, vous avez deux possibilités :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:433 msgid "" @@ -33455,6 +33915,10 @@ msgid "" "taxes, you can simply apply the change on the record (example customer " "identification type) and once it is done click on the Retry button." msgstr "" +"Si l'erreur est liée aux données de base du partenaire, du client ou des " +"taxes, vous pouvez simplement appliquer la modification sur l'enregistrement" +" (par exemple, le type d'identification du client) et une fois que c'est " +"fait, cliquez sur le bouton Réessayer." #: ../../content/applications/finance/fiscal_localizations/peru.rst:436 msgid "" @@ -33463,10 +33927,15 @@ msgid "" " to reset the invoice to Draft, apply the changes, and then send the invoice" " again to the SUNAT for another validation." msgstr "" +"Si l'erreur est liée à des données enregistrées sur la facture directement " +"(type d'opération, données manquantes sur les lignes de la facture), la " +"bonne solution consiste à remettre la facture en brouillon, à appliquer les " +"modifications, puis à envoyer à nouveau la facture à la SUNAT pour une " +"nouvelle validation." #: ../../content/applications/finance/fiscal_localizations/peru.rst:0 msgid "List of common errors on invoices" -msgstr "" +msgstr "Liste des erreurs courantes sur les factures" #: ../../content/applications/finance/fiscal_localizations/peru.rst:445 msgid "" @@ -33482,6 +33951,9 @@ msgid "" "report can be printed. The report includes a QR code, indicating the invoice" " is a valid fiscal document." msgstr "" +"Après que la facture est acceptée et validée par la SUNAT, le rapport PDF de" +" la facture peut être imprimé. Le rapport inclut un code QR, indiquant que " +"la facture est un document fiscal valide." #: ../../content/applications/finance/fiscal_localizations/peru.rst:459 msgid "IAP Credits" @@ -33493,6 +33965,9 @@ msgid "" "consumed in your production database, your company must buy new credits in " "order to process your transactions." msgstr "" +"L'IAP électronique d'Odoo offre 1.000 crédits gratuitement. Une fois que ces" +" crédits sont consommés dans votre base de données de production, votre " +"société doit acheter de nouveaux crédits afin de traiter vos transactions." #: ../../content/applications/finance/fiscal_localizations/peru.rst:464 msgid "" @@ -33500,16 +33975,23 @@ msgid "" "invoice indicating that additional credits are required, you can easily buy " "them by accessing the link provided in the message." msgstr "" +"Lorsque vous n'avez plus de crédits, un libellé rouge s'affiche en haut de " +"la facture indiquant que des crédits supplémentaires sont requis. Vous " +"pouvez facilement les acheter en cliquant sur le lien fourni dans le " +"message." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Buying credits in the IAP" -msgstr "" +msgstr "Acheter des crédits dans l'IAP" #: ../../content/applications/finance/fiscal_localizations/peru.rst:472 msgid "" "In the IAP service includes packages with different pricing based on the " "number of credits. The price list in the IAP is always displayed in EUR." msgstr "" +"Les services d'IAP comprennent des packages dont les prix varient en " +"fonction du nombre de crédits. La liste des prix dans l'IAP s'exprime " +"toujours en EUR." #: ../../content/applications/finance/fiscal_localizations/peru.rst:476 msgid "Special Use cases" @@ -33518,7 +34000,7 @@ msgstr "Cas d'utilisation particuliers" #: ../../content/applications/finance/fiscal_localizations/peru.rst:479 #: ../../content/applications/finance/fiscal_localizations/peru.rst:515 msgid "Cancellation process" -msgstr "" +msgstr "Processus d'annulation" #: ../../content/applications/finance/fiscal_localizations/peru.rst:481 msgid "" @@ -33534,11 +34016,11 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Request invoice cancellation button" -msgstr "" +msgstr "Bouton de demande d'annulation sur une facture" #: ../../content/applications/finance/fiscal_localizations/peru.rst:489 msgid "In order to cancel an invoice, please provide a cancellation Reason." -msgstr "" +msgstr "Afin d'annuler une facture, indiquez un motif d'annulation." #: ../../content/applications/finance/fiscal_localizations/peru.rst:494 msgid "" @@ -33548,10 +34030,16 @@ msgid "" "button “Send now”. Once it is sent, a cancellation ticket is created, as a " "result the next message and CDR File are logged in the chatter:" msgstr "" +"**À annuler** : Indique que la demande d'annulation est prête à être envoyée" +" à l'OSE. Cela peut être fait automatiquement par Odoo avec un *cron* qui " +"s'exécute toutes les heures ou l'utilisateur peut l'envoyer immédiatement en" +" cliquant sur le bouton \"Envoyer maintenant\". Une fois qu'elle est " +"envoyée, un ticket d'annulation est créé et le message suivant et le fichier" +" CDR sont enregistrés dans le chatter :" #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Cancellation CDR sent by the SUNAT" -msgstr "" +msgstr "CDR d'annulation envoyé par la SUNAT" #: ../../content/applications/finance/fiscal_localizations/peru.rst:503 msgid "" @@ -33560,24 +34048,30 @@ msgid "" "downloaded and a message is logged in the chatter indicating the correct " "Government validation." msgstr "" +"**Annulé** : Indique que la demande d'annulation a été envoyée à l'OSE et a " +"été validée avec succès. Dans le cadre de la validation, un fichier ZIP est " +"téléchargé et un message est enregistré dans le chatter indiquant la " +"validation correcte par le gouvernement." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "nvoice after cancellation" -msgstr "" +msgstr "Facture après annulation" #: ../../content/applications/finance/fiscal_localizations/peru.rst:512 msgid "One credit is consumed on each cancellation request." -msgstr "" +msgstr "Un crédit est consommé par demande d'annulation." #: ../../content/applications/finance/fiscal_localizations/peru.rst:517 msgid "" "When creating exportation invoices, take into account the next " "considerations:" msgstr "" +"Lors de la création de factures d'exportation, tenez compte des " +"considérations suivantes :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:519 msgid "The Identification type on your customer must be Foreign ID." -msgstr "" +msgstr "Le type d'identification de votre client doit être ID Étranger." #: ../../content/applications/finance/fiscal_localizations/peru.rst:520 msgid "Operation type in your invoice must be an Exportation one." @@ -33586,27 +34080,28 @@ msgstr "Le type d'opération dans votre facture doit être Exportation." #: ../../content/applications/finance/fiscal_localizations/peru.rst:521 msgid "The taxes included in the invoice lines should be EXP taxes." msgstr "" +"Les taxes incluses dans les lignes de facture doivent être des taxes EXP." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Exportation invoices main data" -msgstr "" +msgstr "Données principales des factures d'exportation" #: ../../content/applications/finance/fiscal_localizations/peru.rst:528 msgid "Advance Payments" -msgstr "" +msgstr "Acomptes" #: ../../content/applications/finance/fiscal_localizations/peru.rst:530 msgid "Create the advance payment Invoice and apply its related payment." -msgstr "" +msgstr "Créez la facture d'acompte et appliquez le paiement correspondant." #: ../../content/applications/finance/fiscal_localizations/peru.rst:531 msgid "Create the final invoice without considering the advance payment." -msgstr "" +msgstr "Créez la facture finale sans tenir compte de l'acompte." #: ../../content/applications/finance/fiscal_localizations/peru.rst:532 msgid "" "Create a credit note for the Final invoice with the advance payment amount." -msgstr "" +msgstr "Créez un avoir pour la facture finale avec le montant de l'acompte." #: ../../content/applications/finance/fiscal_localizations/peru.rst:533 msgid "Reconcile the Credit note with the final invoice." @@ -33617,33 +34112,39 @@ msgid "" "The remaining balance on the final invoice should be paid with a regular " "payment transaction." msgstr "" +"Le solde de la facture finale doit être payé par une transaction de paiement" +" normale." #: ../../content/applications/finance/fiscal_localizations/peru.rst:537 msgid "Detraction Invoices" -msgstr "" +msgstr "Factures de rabais" #: ../../content/applications/finance/fiscal_localizations/peru.rst:539 msgid "" "When creating invoices that is subject to Detractions, take into account the" " next considerations:" msgstr "" +"Lorsque vous créez des factures soumises à des rabais, tenez compte des " +"considérations suivantes :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:541 msgid "" "All the products included in the invoice must have these fields configured:" msgstr "" +"Tous les produits inclus dans la facture doivent avoir ces champs configurés" +" :" #: ../../content/applications/finance/fiscal_localizations/peru.rst:0 msgid "Detraction fields on products" -msgstr "" +msgstr "Champs de rabais sur les produits" #: ../../content/applications/finance/fiscal_localizations/peru.rst:547 msgid "Operation type in your invoice must be ``1001``" -msgstr "" +msgstr "Le type d'opération de votre facture doit être ``1001``" #: ../../content/applications/finance/fiscal_localizations/peru.rst:0 msgid "Detraction code on invoices." -msgstr "" +msgstr "Code de rabais sur les factures." #: ../../content/applications/finance/fiscal_localizations/peru.rst:556 msgid "" @@ -33652,35 +34153,47 @@ msgid "" " a part of the Peruvian localization you need to prove a Credit Reason " "selecting one of the options in the list." msgstr "" +"Lorsqu'une correction ou un remboursement est nécessaire sur une facture " +"validée, un avoir doit être généré. Il suffit de cliquer sur le bouton " +"\"Ajouter un avoir\". Dans le cadre de la localisation péruvienne, vous " +"devez prouver un Motif de crédit en sélectionnant l'une des options de la " +"liste." #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Add Credit Note from invoice" -msgstr "" +msgstr "Ajouter un avoir à partir de la facture" #: ../../content/applications/finance/fiscal_localizations/peru.rst:565 msgid "" "When creating your first credit Note, select the Credit Method: Partial " "Refund, this allows you to define the credit note sequence." msgstr "" +"Lors de la création de votre premier avoir, sélectionnez la Méthode de " +"crédit : Remboursement partiel, ce qui vous permet de définir la séquence de" +" l'avoir." #: ../../content/applications/finance/fiscal_localizations/peru.rst:568 msgid "By default the Credit Note is set in the document type:" -msgstr "" +msgstr "Par défaut, l'avoir est défini dans le type de document :" #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Credit Note document type" -msgstr "" +msgstr "Type de document Avoir" #: ../../content/applications/finance/fiscal_localizations/peru.rst:574 msgid "" "To finish the workflow please follow the instructions on :doc:`our page " "about Credit Notes <../accounting/customer_invoices/credit_notes>`." msgstr "" +"Pour terminer le flux de travail, suivez les instructions sur :doc:`notre " +"page sur les avoirs <../accounting/customer_invoices/credit_notes>`." #: ../../content/applications/finance/fiscal_localizations/peru.rst:578 msgid "" "The EDI workflow for the Credit notes works in the same way as the invoices." msgstr "" +"Le flux de travail EDI pour les avoirs fonctionne de la même manière que " +"pour les factures." #: ../../content/applications/finance/fiscal_localizations/peru.rst:583 msgid "" @@ -33688,10 +34201,13 @@ msgid "" "existing document you can also create debit Notes. For this just use the " "button “Add Debit Note”." msgstr "" +"Dans le cadre de la localisation péruvienne, en plus de créer des avoirs à " +"partir d'un document existant, vous pouvez également créer des Notes de " +"débit. Cliquez simplement sur le bouton \"Ajouter une note de débit\"." #: ../../content/applications/finance/fiscal_localizations/peru.rst:586 msgid "By default the Debit Note is set in the document type." -msgstr "" +msgstr "Par défaut, la Note de débit est définie dans le type de document." #: ../../content/applications/finance/fiscal_localizations/spain.rst:3 msgid "Spain" @@ -33777,6 +34293,9 @@ msgid "" "from Odoo. On the customer invoices, there is a new button called *Print " "ISR*." msgstr "" +"Les BVR sont des bulletins de paiement utilisés en Suisse. Vous pouvez les " +"imprimer directement depuis Odoo. Sur les factures clients, il y a un " +"nouveau bouton intitulé *Imprimer BVR*." #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:16 msgid "" @@ -33784,6 +34303,9 @@ msgid "" "the invoice. You can use CH6309000000250097798 as bank account number and " "010391391 as CHF ISR reference." msgstr "" +"Le bouton *Imprimer BVR* s'affiche uniquement lorsqu'un compte bancaire est " +"défini sur la facture. Vous pouvez utiliser CH6309000000250097798 en tant " +"que numéro de compte bancaire et 010391391 en tant que référence BVR CHF." #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:23 msgid "Then you open a pdf with the ISR." @@ -33797,10 +34319,15 @@ msgid "" ":menuselection:`Accounting --> Configuration --> Settings --> Customer " "Invoices` and enable **Print bank on ISR**:" msgstr "" +"Il existe deux présentations pour le BVR : l'une avec et l'autre sans les " +"coordonnées bancaires. Pour choisir l'une ou l'autre, il existe une option " +"permettant d'imprimer les informations bancaires sur le BVR. Pour l'activer," +" allez à :menuselection:`Comptabilité --> Configuration --> Paramètres --> " +"Factures clients` et activez **Imprimer la banque sur le BVR** :" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:38 msgid "ISR reference on invoices" -msgstr "" +msgstr "Référence BVR sur les factures" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:40 msgid "" @@ -33819,12 +34346,21 @@ msgid "" " In the **Communication Standard** field, select *Switzerland*, and click on" " *Save*." msgstr "" +"Pour ce faire, vous devez configurer le Journal que vous utilisez " +"habituellement pour émettre des factures. Allez à " +":menuselection:`Comptabilité --> Configuration --> Journaux`, ouvrez le " +"Journal que vous souhaitez modifier (par défaut, le Journal est intitulé " +"*Factures clients*), cliquez sur *Modifier* et ouvrez l'onglet *Paramètres " +"avancés*. Dans le champ **Standard de référence**, sélectionnez la *Suisse* " +"et cliquez sur *Enregistrer*." #: ../../content/applications/finance/fiscal_localizations/switzerland.rst-1 msgid "" "Configure your Journal to display your ISR as payment reference on your " "invoices in Odoo" msgstr "" +"Configurez votre Journal pour afficher votre BVR en tant que référence de " +"paiement sur vos factures dans Odoo" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:53 msgid "Currency Rate Live Update" @@ -33837,6 +34373,10 @@ msgid "" "--> Settings`, activate the multi-currencies setting and choose the service " "you want." msgstr "" +"Vous pouvez automatiquement mettre à jour vos taux de change en fonction de " +"l'Administration fédérale des contributions de la Suisse. Pour ce faire, " +"allez à :menuselection:`Comptabilité --> Paramètres`, activez le paramètre " +"multi-devises et choisissez le service que vous souhaitez." #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:64 msgid "Updated VAT for January 2018" @@ -33856,12 +34396,14 @@ msgstr "" msgid "" "How to update your taxes in Odoo Enterprise (Odoo Online or On-premise)?" msgstr "" +"Comment mettre à jour vos taxes dans Odoo Enterprise (Odoo Online ou On-" +"premise) ?" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:73 msgid "" "If you have the V11.1 version, all the work is already been done, you don't " "have to do anything." -msgstr "" +msgstr "Si vous êtes sur la version V11.1, vous n'avez rien à faire." #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:76 msgid "" @@ -33892,6 +34434,10 @@ msgid "" "time. Instead, remember to archive them once you have encoded all your 2017 " "transactions." msgstr "" +"**Ne supprimez ou ne modifiez pas les taux existants** (8,0% ou 3,8%). Vous " +"devez les conserver, puisqu'il se peut que vous deviez utiliser les deux " +"taux pendant une courte période. Pensez plutôt à les archiver une fois que " +"vous aurez encodé toutes vos transactions de 2017." #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:92 msgid "The creation of such taxes should be done in the following manner:" @@ -33903,6 +34449,9 @@ msgid "" "**Purchase taxes**: copy the origin tax, change its name, label on invoice, " "rate and tax group (effective from v10 only)" msgstr "" +"**taxes sur les achats** : copier la taxe d'origine, copier son nom, le " +"libellé sur la facture, le taux et le groupe de taxes (uniquement en vigueur" +" à partir de la version 10)" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:97 msgid "" @@ -33910,6 +34459,11 @@ msgid "" " and tax group (effective from v10 only). Since the vat report now shows the" " details for old and new rates, you should also set the tags accordingly to" msgstr "" +"**Taxes sur les ventes** : copier la taxe d'origine, modifier son nom, le " +"libellé sur les factures, le taux et le groupe de taxes (uniquement en " +"vigueur à partir de la version 10). Puisque la déclaration de TVA affiche " +"désormais les détails pour les anciens et les nouveaux taux, vous devez " +"également définir les étiquettes en conséquence pour" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:102 msgid "" @@ -33932,6 +34486,8 @@ msgid "" "You'll find below, as examples, the correct configuration for all taxes " "included in Odoo by default" msgstr "" +"Vous trouverez ci-dessous, à titre d'exemple, la bonne configuration pour " +"toutes les taxes incluses par défaut dans Odoo." #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 msgid "**Tax Name**" @@ -34138,14 +34694,16 @@ msgid "" ":ref:`Install ` the following modules to get all the " "features of the **United Arab Emirates** localization:" msgstr "" +":ref:`Installez ` les modules suivants pour obtenir toutes " +"les fonctionnalités de la localisation des **Émirats arabes unis** :" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:19 msgid ":guilabel:`United Arab Emirates - Accounting`" -msgstr "" +msgstr ":guilabel:`Émirats arabes unis - Comptabilité`" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:20 msgid "``l10n_ae``" -msgstr "" +msgstr "``l10n_ae``" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:21 msgid "" @@ -34153,46 +34711,49 @@ msgid "" "`. Includes all accounts, taxes," " and reports." msgstr "" +":doc:`Package de localisation fiscale " +"` par défaut. Inclut les " +"comptes, les taxes et les rapports." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:23 msgid ":guilabel:`U.A.E. - Payroll`" -msgstr "" +msgstr ":guilabel:`Émirats arabes unis - Paie`" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:24 msgid "``l10n_ae_hr_payroll``" -msgstr "" +msgstr "``l10n_ae_hr_payroll``" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:25 msgid "Includes all rules, calculations, and salary structures." -msgstr "" +msgstr "Inclut les règles, les calculs et les structures salariales." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:26 msgid ":guilabel:`U.A.E. - Payroll with Accounting`" -msgstr "" +msgstr ":guilabel:`Émirats arabes unis - Paie avec Comptabilité`" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:27 msgid "``l10n_ae_hr_payroll_account``" -msgstr "" +msgstr "``l10n_ae_hr_payroll_account``" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:28 msgid "Includes all accounts related to the payroll module." -msgstr "" +msgstr "Inclut les comptes liés au module de paie." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:29 msgid ":guilabel:`United Arab Emirates - Point of Sale`" -msgstr "" +msgstr ":guilabel:`Émirats arabes unis - Point de Vente`" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:30 msgid "``l10n_ae_pos``" -msgstr "" +msgstr "``l10n_ae_pos``" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:31 msgid "Includes the UAE-compliant POS receipt." -msgstr "" +msgstr "Inclut le reçu PdV conforme aux normes des Émirats arabes unis." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 msgid "Select the modules to install." -msgstr "" +msgstr "Sélectionnez les modules à installer." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:40 msgid "" @@ -34203,12 +34764,21 @@ msgid "" ":guilabel:`Enable`/:guilabel:`Disable` reconciliation or **configure** " "specific accounts according to your needs." msgstr "" +"Allez à :menuselection:`Comptabilité --> Configuration --> Plan comptable` " +"pour afficher tous les comptes par défaut sdisponibles pour le package de " +"localisation des Émirats arabes unis. Vous pouvez filtrer par " +":guilabel:`Code` en utilisant les chiffres situés à l'extrême gauche ou en " +"cliquant sur :menuselection:`Regrouper par --> Type de compte`. Vous pouvez " +":guilabel:`activer`/:guilabel:`désactiver` le rapprochement ou " +"**configurez** des comptes spécifiques selon vos besoins." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:47 msgid "" "Always keep at least one **receivable account** and one **payable account** " "active." msgstr "" +"Gardez toujours au moins un **compte client** et un **compte fournisseur** " +"actifs." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:48 msgid "" @@ -34216,6 +34786,9 @@ msgid "" "either as transitory accounts by Odoo or are specific to the **UAE " "localization package**." msgstr "" +"Il est également conseillé de **garder les comptes suivants actifs**, car " +"ils sont utilisés comme comptes transitoires par Odoo ou sont spécifiques au" +" **package de localisation des Émirats arabes unis**." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:55 msgid "Account Name" @@ -34223,19 +34796,19 @@ msgstr "Nom du compte" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:57 msgid "102011" -msgstr "" +msgstr "102011" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:60 msgid "102012" -msgstr "" +msgstr "102012" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:61 msgid "Accounts Receivable (POS)" -msgstr "" +msgstr "Comptes clients (PdV)" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:63 msgid "201002" -msgstr "" +msgstr "201002" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:64 msgid "Payables" @@ -34243,11 +34816,11 @@ msgstr "Dettes fournisseurs" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:66 msgid "101004" -msgstr "" +msgstr "101004" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:69 msgid "105001" -msgstr "" +msgstr "105001" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:70 msgid "Cash" @@ -34255,7 +34828,7 @@ msgstr "Espèces" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:72 msgid "100001" -msgstr "" +msgstr "100001" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:73 msgid "Liquidity Transfer" @@ -34263,11 +34836,11 @@ msgstr "Transfert de liquidités" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:75 msgid "101002" -msgstr "" +msgstr "101002" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:78 msgid "101003" -msgstr "" +msgstr "101003" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:79 msgid "Outstanding Payments" @@ -34275,23 +34848,23 @@ msgstr "Paiements sortants en suspens" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:81 msgid "104041" -msgstr "" +msgstr "104041" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:82 msgid "VAT Input" -msgstr "" +msgstr "TVA en amont" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:84 msgid "100103" -msgstr "" +msgstr "100103" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:85 msgid "VAT Receivable" -msgstr "" +msgstr "TVA à percevoir" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:87 msgid "101001" -msgstr "" +msgstr "101001" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:88 msgid "Bank Suspense Account" @@ -34299,31 +34872,31 @@ msgstr "Compte d'attente de la banque" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:90 msgid "201017" -msgstr "" +msgstr "201017" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:91 msgid "VAT Output" -msgstr "" +msgstr "TVA en aval" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:93 msgid "202001" -msgstr "" +msgstr "202001" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:94 msgid "End of Service Provision" -msgstr "" +msgstr "Prestations liées à la fin du service" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:96 msgid "202003" -msgstr "" +msgstr "202003" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:97 msgid "VAT Payable" -msgstr "" +msgstr "TVA à payer" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:99 msgid "999999" -msgstr "" +msgstr "999999" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:100 msgid "Undistributed Profits/Losses" @@ -34331,7 +34904,7 @@ msgstr "Profits/pertes non distribués" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:102 msgid "400003" -msgstr "" +msgstr "400003" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:103 msgid "Basic Salary" @@ -34339,27 +34912,27 @@ msgstr "Salaire de base" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:105 msgid "400004" -msgstr "" +msgstr "400004" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:106 msgid "Housing Allowance" -msgstr "" +msgstr "Allocation de logement" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:108 msgid "400005" -msgstr "" +msgstr "400005" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:109 msgid "Transportation Allowance" -msgstr "" +msgstr "Allocation de transport" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:111 msgid "400008" -msgstr "" +msgstr "400008" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:112 msgid "End of Service Indemnity" -msgstr "" +msgstr "Indemnité de fin de service" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:118 msgid "" @@ -34373,18 +34946,29 @@ msgid "" "current account (payable)`, :guilabel:`Tax current account (receivable)`, " "and an :guilabel:`Advance Tax payment account` for the **5%** group." msgstr "" +"Pour accéder à vos taxes, allez à :menuselection:`Comptabilité --> " +"Configuration --> Taxes`. Activez/désactivez ou :doc:`configurez " +"` les taxes pertinentes pour vos " +"activités en cliquant dessus. N'oubliez pas ne configurer les comptes de " +"taxes que sur le groupe de taxes de **5%**, les autres groupes n'ayant pas " +"besoin d'être clôturés. Pour ce faire, activez le :doc:`mode développeur " +"<../../general/developer_mode>` et allez à :menuselection:`Configuration -->" +" Groupes de taxes`. Définissez ensuite un :guilabel:`Compte courant de la " +"taxe (dettes)`, un :guilabel:`Compte courant de la taxe (créances)`, et un " +":guilabel:`Compte de versement anticipé de la taxe` pour le groupe de " +"**5%**." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:127 msgid "The :abbr:`RCM (Reverse Charge Mechanism)` is supported by Odoo." -msgstr "" +msgstr "Le mécanisme d'autoliquidation est pris en charge par Odoo." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 msgid "Preview of the UAE localization package's taxes." -msgstr "" +msgstr "Aperçu des taxes du package de localisation des Émirats arabes unis." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:134 msgid "Currency exchange rates" -msgstr "" +msgstr "Taux de change" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:136 msgid "" @@ -34392,18 +34976,28 @@ msgid "" "Configuration --> Settings --> Currencies`. Click on the update button " "(:guilabel:`🗘`) found next to the :guilabel:`Next Run` field." msgstr "" +"Pour mettre à jour les taux de change, allez à :menuselection:`Comptabilité " +"--> Configuration --> Paramètres --> Devises`. Cliquez sur le bouton de mise" +" à jour (:guilabel:`🗘`) situé à côté du champ :guilabel:`Prochaine " +"exécution`." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:140 msgid "" "To launch the update automatically at set intervals, change the " ":guilabel:`Interval` from :guilabel:`Manually` to the desired frequency." msgstr "" +"Pour lancer la mise à jour automatiquement à des intervalles définis, " +"modifiez l':guilabel:`Intervalle` de :guilabel:`Manuellement` à la fréquence" +" souhaitée." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:144 msgid "" "By default, the UAE Central Bank exchange rates web service is used. Several" " other providers are available under the :guilabel:`Service` field." msgstr "" +"Par défaut, le service web des taux de change de la Banque centrale des " +"Émirats arabes unis est utilisé. Plusieurs autres fournisseurs sont " +"disponibles dans le champ :guilabel:`Service`." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:150 msgid "Payroll" @@ -34416,14 +35010,18 @@ msgid "" "salary rules are linked to the corresponding accounts in the **chart of " "accounts**." msgstr "" +"Le module :guilabel:`Émirats arabes unis - Paie` créer les **règles " +"salariales** nécessaires dans l'application Paie conformément aux règles et " +"aux réglementations des Émirats arabes unis. Les règles salariales sont " +"liées aux comptes correspondants dans le **plan comptable**." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 msgid "The UAE Employee Payroll Structure." -msgstr "" +msgstr "La structure de paie des employés des Émirats arabes unis." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:161 msgid "Salary rules" -msgstr "" +msgstr "Règles salariales" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:163 msgid "" @@ -34432,56 +35030,71 @@ msgid "" "employee's contract. In the :guilabel:`Salary Structure Type` field, select " ":guilabel:`UAE Employee`." msgstr "" +"Pour appliquer ces règles au contrat d'un employé, allez à " +":menuselection:`Paie --> Contracts --> Contrats` et sélectionnez le contrat " +"de l'employé. Dans le champ :guilabel:`Type de structure salariale`, " +"sélectionnez :guilabel:`Employé Émirats arabes unis`." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 msgid "Select the Salary Structure Type to apply to the contract." msgstr "" +"Sélectionnez le type de structure salariale pour l'appliquer au contrat." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:171 msgid "" "Under the :guilabel:`Salary Information` tab, you can find details such as " "the:" msgstr "" +"Dans l'onglet :guilabel:`Informations salariales`, vous pouvez y trouver les" +" détails suivants :" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:173 msgid ":guilabel:`Wage`;" -msgstr "" +msgstr ":guilabel:`Salaire` ;" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:174 msgid ":guilabel:`Housing Allowance`;" -msgstr "" +msgstr ":guilabel:`Allocation de logement` ;" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:175 msgid ":guilabel:`Transportation Allowance`;" -msgstr "" +msgstr ":guilabel:`Allocation de transport` ;" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:176 msgid ":guilabel:`Other Allowances`;" -msgstr "" +msgstr ":guilabel:`Autres allocations` ;" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:177 msgid "" ":guilabel:`Number of Days`: used to calculate the :ref:`end of service " "provision `." msgstr "" +":guilabel:`Nombre de jours` : utilisé pour calculer les :ref:`prestations de" +" fin de service `." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:181 msgid "" "**Leave deductions** are calculated using a salary rule linked to the " "**unpaid leave** time-off type;" msgstr "" +"Les **retenues pour congés** sont calculées à l'aide d'une règle salariale " +"liée au type de congé **congé sans solde** ; " #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:183 msgid "" "Any other deductions or reimbursements are made *manually* using other " "inputs;" msgstr "" +"Les autres déductions ou remboursement sont effectués *manuellement* à " +"l'aide d'autres entrées ;" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:184 msgid "" "**Overtimes** are added *manually* by going to :menuselection:`Work Entries " "--> Work Entries`;" msgstr "" +"Les **heures supplémentaires** sont ajoutées *manuellement* en allant à " +":menuselection:`Prestations --> Prestations` ;" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:185 msgid "" @@ -34490,6 +35103,10 @@ msgid "" "the :guilabel:`Employee` and the :guilabel:`Type (Attachment of Salary, " "Assignment of Salary, Child Support)`." msgstr "" +"Les **Saisies sur salaire** sont générées en allant aux " +":menuselection:`Contrats --> Saisies sur salaire`. :guilabel:`Créez` ensuite" +" une saisie et sélectionnez l':guilabel:`Employé` et le :guilabel:`Type " +"(Saisie sur salaire, Cession sur salaire, Pension alimentaire)`." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:190 msgid "" @@ -34498,10 +35115,15 @@ msgid "" ":guilabel:`UAE Employee Payroll Structure`, select the rule to hide, and " "uncheck :guilabel:`Appears on Payslip`." msgstr "" +"Pour empêcher qu'une règle apparaisse sur une fiche de paie, allez à " +":menuselection:`Paie --> Configuration --> Règles`. Cliquez sur " +":guilabel:`Structure de paie des employés des Émirats arabes unis`, " +"sélectionnez la règle à masquer et cliquez sur :guilabel:`Apparaît sur la " +"fiche de paie`." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:197 msgid "End of service provision" -msgstr "" +msgstr "Prestations de fin de service" #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:199 msgid "" @@ -34509,6 +35131,9 @@ msgid "" "then *multiplied* by the number of days set in the field :guilabel:`Number " "of days` at the bottom of a contract's form." msgstr "" +"La provision est définie par l'allocation mensuelle totale *divisée* par 30," +" puis *multipliée* par le nombre de jours défini dans le champ " +":guilabel:`Nombre de jours` en bas du formulaire de contrat." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:202 msgid "" @@ -34518,12 +35143,19 @@ msgid "" " to pay off the **end of service amount** by settling it with the **payables" " account**." msgstr "" +"La provision est ensuite calculée via une règle salariale associée à deux " +"comptes : l'**Indemnité de fin de service (compte de charges)** et la " +"**Provision de fin de service (compte de passifs immobilisés)**. Ce dernier " +"est utilisé pour payer le **montant de fin de service** en le réglant avec " +"le **compte créances**." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:208 msgid "" "The end of service amount is calculated based on the gross salary and the " "start and end dates of the employee’s contract." msgstr "" +"Le montant de fin de service est calculé sur la base du salaire brut et les " +"date de début et de fin du contrat de l'employé." #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:214 msgid "" @@ -34531,6 +35163,9 @@ msgid "" "Arabic, or both. The localization also includes a line to display the **VAT " "amount** per line." msgstr "" +"Le package de localisation des Émirats arabes unis permet de générer des " +"factures en anglais, en arabe ou les deux. La localisation inclut également " +"une ligne pour afficher le **montant de TVA** par ligne." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:3 msgid "United Kingdom" @@ -34542,62 +35177,71 @@ msgid "" ":guilabel:`UK - Accounting Reports` modules to get all the features of the " "UK localization." msgstr "" +":ref:`Installez ` les modules :guilabel:`Royaume-Uni - " +"Comptabilité` et :guilabel:`Royaume-Uni - Rapports comptables` pour obtenir " +"toutes les fonctionnalités de la localisation du Royaume-Uni." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:17 msgid ":guilabel:`UK - Accounting`" -msgstr "" +msgstr ":guilabel:`Royaume-Uni - Comptabilité`" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:18 msgid "`l10n_uk`" -msgstr "" +msgstr "`l10n_uk`" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:19 msgid "CT600-ready chart of accounts" -msgstr "" +msgstr "Plan comptable prêt pour le CT600" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:20 msgid "VAT100-ready tax structure" -msgstr "" +msgstr "Structure fiscale prête pour le formulaire TVA100" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:21 msgid "Infologic UK counties listing" -msgstr "" +msgstr "Liste des pays d'Infologic Royaume-Uni" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:22 msgid ":guilabel:`UK - Accounting Reports`" -msgstr "" +msgstr ":guilabel:`Royaume-Uni - Rapports comptables`" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:23 msgid "`l10n_uk_reports`" -msgstr "" +msgstr "`l10n_uk_reports`" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:24 msgid "Accounting reports for the UK" -msgstr "" +msgstr "Rapports comptables pour le Royaume-Uni" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:25 msgid "Allows sending the tax report via the MTD-VAT API to HMRC." -msgstr "" +msgstr "Permet d'envoyer la déclaration de TVA via l'API MTD-VAT au HMRC." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst-1 msgid "Odoo uk packages" -msgstr "" +msgstr "Packages du Royaume-Uni proposés par Odoo" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:32 msgid "Only UK-based companies can submit reports to HMRC." msgstr "" +"Seules les sociétés situées au Royaume-Uni peuvent soumettre des rapports au" +" HMRC." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:33 msgid "" "Installing the module :guilabel:`UK - Accounting Reports` installs all two " "modules at once." msgstr "" +"L'installation du module :guilabel:`Royaume-Uni - Rapports comptables` " +"installe les deux modules en une fois." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:36 msgid "" "`HM Revenue & Customs `_" msgstr "" +"`HM Revenue & Customs `_" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:37 msgid "" @@ -34605,6 +35249,9 @@ msgid "" "`_" msgstr "" +"`Overview of Making Tax Digital " +"`_" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:43 msgid "" @@ -34612,6 +35259,9 @@ msgid "" "module. Go to :menuselection:`Accounting --> Configuration --> Accounting: " "Chart of Accounts` to access it." msgstr "" +"Le plan comptable britannique est inclut dans le module :guilabel:`Royaume-" +"Uni - Comptabilité`. Allez à :menuselection:`Comptabilité --> Configuration " +"--> Comptabilité : Plan comptable` pour y accéder." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:46 msgid "" @@ -34620,12 +35270,19 @@ msgid "" "Import section` and choose to :guilabel:`Review Manually` or " ":guilabel:`Import (recommended)` your initial balances." msgstr "" +"Configurez votre :abbr:`CoA (plan comptable)` en allant à " +":menuselection:`Comptabilité --> Configuration --> Paramètres --> " +"Comptabilité section Import` et choisissez de :guilabel:`Réviser " +"manuellement` ou :guilabel:`Importer (recommandé)` vos soldes initiaux." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:53 msgid "" "As part of the localization module, UK taxes are created automatically with " "their related financial accounts and configuration." msgstr "" +"Dans le cadre du module de localisation, les taxes britanniques sont créées " +"automatiquement avec leurs comptes financiers et leur configuration " +"correspondants." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:56 msgid "" @@ -34633,32 +35290,45 @@ msgid "" "to update the :guilabel:`Default Taxes`, the :guilabel:`Tax Return " "Periodicity` or to :guilabel:`Configure your tax accounts`." msgstr "" +"Allez à :menuselection:`Comptabilité --> Configuration --> Paramètres --> " +"Taxes` pour mettre à jour les :guilabel:`Taxes par défaut`, la " +":guilabel:`Périodicité de la déclaration d'impôt` ou pour " +":guilabel:`Configurer vos comptes de taxes`." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:60 msgid "" "To edit existing taxes or to :guilabel:`Create` a new tax, go to " ":menuselection:`Accounting --> Configuration --> Accounting: Taxes`." msgstr "" +"Pour modifier des taxes existantes ou :guilabel:`Créer` une nouvelle taxe, " +"allez à :menuselection:`Comptabilité --> Configuration --> Comptabilité : " +"Taxes`." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:64 msgid ":doc:`taxes <../accounting/taxes>`" -msgstr "" +msgstr ":doc:`taxes <../accounting/taxes>`" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:65 msgid "" "Tutorial: `Tax report and return `_." msgstr "" +"Tutoriel : `Déclaration de TVA et d'impôt " +"`_." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:69 msgid "Making Tax Digital (MTD)" -msgstr "" +msgstr "Making Tax Digital (MTD)" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:71 msgid "" "In the UK, all VAT-registered businesses have to follow the MTD rules by " "using software to submit their VAT returns." msgstr "" +"Au Royaume-Uni, toutes les entreprises assujetties à la TVA doivent suivre " +"les règles du MTD en utilisant un logiciel pour soumettre leurs déclarations" +" de TVA." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:74 msgid "" @@ -34668,6 +35338,12 @@ msgid "" "`_." msgstr "" +"Le module **Royaume-Uni - Rapports comptables** vous permet de vous " +"conformer aux exigences du `HM Revenue & Customs " +"`_ " +"concernant `Making Tax Digital " +"`_." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:80 msgid "" @@ -34676,10 +35352,15 @@ msgid "" "the last three months. Your submission has to be done manually by contacting" " HMRC." msgstr "" +"Si votre déclaration périodique a plus de trois mois de retard, il n'est " +"plus possible de la soumettre via Odoo, puisqu'Odoo ne récupère que les " +"obligations ouvertes des trois derniers mois. Votre déclaration doit être " +"effectuée manuellement en contactant le HMRC." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:85 msgid "Register your company to HMRC before the first submission" msgstr "" +"Enregistrer votre entreprise auprès du HMRC avant la première soumission" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:87 msgid "" @@ -34687,26 +35368,35 @@ msgid "" ":guilabel:`Connect to HMRC`. Enter your company information on the HMRC " "platform. You only need to do it once." msgstr "" +"Allez à :menuselection:`Comptabilité --> Analyse --> Déclaration de TVA` et " +"cliquez sur :guilabel:`Connexion à HMRC`. Saisissez les informations " +"relatives à votre société sur la plateforme du HMRC. Vous ne devez le faire " +"qu'une seule fois." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:92 msgid "" "When entering your VAT number, do not add the GB country code. Only the 9 " "digits are required." msgstr "" +"Lorsque vous saisissez votre numéro de TVA, n'ajoutez pas le code de pays " +"GB. Seuls les 9 chiffres sont nécessaires." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:95 msgid "Periodic submission to HMRC" -msgstr "" +msgstr "Soumission périodique au HMRC" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 msgid "" "Import your obligations HMRC, filter on the period you want to submit, and " "send your tax report by clicking :guilabel:`Send to HMRC`." msgstr "" +"Importez vos obligations HMRC, filtrez sur la période que vous souhaitez " +"soumettre et envoyez votre déclaration de TVA en cliquant sur " +":guilabel:`Envoyer au HMRC`." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:101 msgid "Periodic submission to HMRC for multi-company" -msgstr "" +msgstr "Soumission périodique au HMRC pour plusieurs sociétés" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:103 msgid "" @@ -34714,10 +35404,15 @@ msgid "" " UK-based companies are on the same database, the user who submits the HMRC " "report must follow these instructions before each submission:" msgstr "" +"Une seule société et un seul utilisateur peuvent se connecter simultanément " +"au HMRC. Si plusieurs sociétés basées au Royaume-Uni se trouvent dans la " +"même base de données, l'utilisateur qui soumet le rapport HMRC doit suivre " +"ces instructions avant chaque soumission :" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:107 msgid "Log into the company for which the submission has to be done." msgstr "" +"Se connecter à la société pour laquelle la déclaration doit être soumise." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:108 msgid "" @@ -34725,6 +35420,9 @@ msgid "" "click :guilabel:`Manage Users`. Select the user who will submit the VAT " "return." msgstr "" +"Allez aux :guilabel:`Paramètres généraux` et dans la section " +":guilabel:`Utilisateurs`, cliquez sur :guilabel:`Gérer les utilisateurs`. " +"Sélectionnez l'utilisateur qui soumettra la déclaration de TVA." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:110 msgid "" @@ -34733,16 +35431,23 @@ msgid "" " button. Then click again to create new credentials. It is now possible to " "submit the tax report for this company." msgstr "" +"Allez à l'onglet :guilabel:`Intégration HMRC UK` et cliquez sur le bouton " +":guilabel:`Réinitialiser les identifiants d'authentification` ou " +":guilabel:`Supprimer les identifiants d'authentification`. Cliquez à nouveau" +" sur ce bouton pour créer de nouveaux identifiants. Il est désormais " +"possible de soumettre la déclaration de TVA pour cette société." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:113 msgid "Repeat the steps for other companies' HMRC submissions." -msgstr "" +msgstr "Répétez les étapes pour les soumissions HMRC des autres sociétés." #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:116 msgid "" "During this process, the :guilabel:`Connect to HMRC` button no longer " "appears for other UK-based companies." msgstr "" +"Pendant ce processus, le bouton :guilabel:`Connexion au HMRC` n'apparaît " +"plus pour les sociétés basées au Royaume-Uni." #: ../../content/applications/finance/payment_acquirers.rst:5 msgid "Payment acquirers (credit cards, online payments)" @@ -35174,7 +35879,7 @@ msgstr "" " d'informations." #: ../../content/applications/finance/payment_acquirers.rst:267 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:40 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:38 msgid "Configuration tab" msgstr "Onglet Configuration" @@ -35352,7 +36057,7 @@ msgstr ":ref:`payment_acquirers/add_new`" #: ../../content/applications/finance/payment_acquirers/adyen.rst:10 #: ../../content/applications/finance/payment_acquirers/adyen.rst:137 #: ../../content/applications/finance/payment_acquirers/alipay.rst:36 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:53 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:51 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:47 #: ../../content/applications/finance/payment_acquirers/mollie.rst:31 #: ../../content/applications/finance/payment_acquirers/paypal.rst:162 @@ -35761,45 +36466,328 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:31 msgid "" -"If you are trying Authorize.Net as a test, with a *sandbox account*, change " -"the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a" -" test Odoo database, rather than on your main database." +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." msgstr "" -"Si vous testez Authorize.Net, avec un *compte sandbox*, définissez le " -":guilabel:`Statut` sur :guilabel:`Mode test`. Nous vous recommandons " -"d'effectuer les tests sur une base de données de test Odoo, plutôt que sur " -"votre base de données principale." +"Pour tester Authorize.Net avec un compte *sandbox*, passer le " +":guilabel:`Statut` en :guilabel:`Mode test`. Nous vous recommandons de le " +"faire sur une base de données Odoo de test, plutôt que sur votre base de " +"données principale." -#: ../../content/applications/finance/payment_acquirers/authorize.rst:35 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:34 msgid "" -"If you set :guilabel:`Test Mode` on Odoo and use an authorize.net account " -"instead of a sandbox.authorize.net account, it results in the following " -"error: *The merchant login ID or password is invalid or the account is " -"inactive*." +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." msgstr "" -"Si vous configurez le :guilabel:`Mode test` sur Odoo et que vous utilisez un" -" compte authorize.net au lieu d'un compte sandbox.authorize.net, vous " -"obtiendrez l'erreur suivante : *L'ID de connexion marchand ou le mot de " -"passe est invalide ou le compte est inactif*." +"Si vous utilisez le :guilabel:`Mode test` avec un compte régulier, vous " +"verrez le message d'erreur suivant : *L'identifiant de connexion du marchand" +" ou le mot de passe est invalide ou le compte est inactif*." -#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:41 msgid "Place a hold on a card" msgstr "Faire une réservation sur une carte" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:45 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 msgid "" -"With Authorize.net, you can enable the :ref:`manual capture " +"With Authorize.Net, you can enable the :ref:`manual capture " "`. If enabled, the funds are " "reserved for 30 days on the customer's card, but not charged yet." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:50 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:48 msgid "" "After **30 days**, the transaction is **voided automatically** by " -"Authorize.net." +"Authorize.Net." msgstr "" -"Après **30 jours**, la transaction est **annulée automatiquement** par " -"Authorize.net." +"Après **30 jours**, la transaction est **automatiquement annulée** par " +"Authorize.Net." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:54 +msgid "Import an Authorize.Net statement" +msgstr "Importer un relevé Authorize.Net" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:57 +msgid "Export from Authorize.Net" +msgstr "Exporter depuis Authorize.Net" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:63 +msgid "" +"`Download the Excel import template " +"`_" +msgstr "" +"`Téléchargez le modèle d'importation Excel " +"`_" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:65 +msgid "To export a statement:" +msgstr "Pour exporter un relevé :" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:67 +msgid "Log in to Authorize.Net." +msgstr "Connectez-vous à Authorize.Net." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:68 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" +"Allez à :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:69 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" +"Définissez une plage d'exportation en utilisant un règlement par lot " +"d'*ouverture* et de *clôture*. Toutes les transactions comprises dans les " +"deux règlements par lot seront exportées vers Odoo." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:71 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template `." +msgstr "" +"Sélectionnez toutes les transactions dans la plage souhaitée, copiez-les et " +"collez-les dans la feuille :guilabel:`Report 1 Download` du :ref:`modèle " +"d'importation Excel `." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "Sélection des transactions Authorize.Net à importer" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "Lot de règlement d'un relevé Authorize.Net" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:84 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" +"Dans ce cas, le premier lot (01/01/2021) de l'année correspond au règlement " +"du 31/12/2020, donc le règlement d'**ouverture** date du 31/12/2020." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:87 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" +"Une fois que les données se trouvent dans la feuille :guilabel:`Report 1 " +"Download` :" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:89 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" +"Allez à l'onglet :guilabel:`Recherche de transaction` sur Authorize.Net." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:90 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" +"Dans la section :guilabel:`Date de règlement`, sélectionnez la plage de " +"dates de règlement par mot précédemment utilisée dans les champs " +":guilabel:`Du :` et :guilabel:`Au :` et cliquez sur :guilabel:`Rechercher`." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:92 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" +"Lorsque la liste a été générée, cliquez sur :guilabel:`Télécharger vers " +"fichier`." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:93 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" +"Dans la fenêtre contextuelle, sélectionnez :guilabel:`Champs élargis avec " +"réponse CAVV/séparés par des virgules`, activez :guilabel:`Inclure les en-" +"têtes de colonne` et cliquez sur :guilabel:`Soumettre`." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:95 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"`." +msgstr "" +"Ouvrez le fichier texte, sélectionnez :guilabel:`Tout`, copiez les données " +"et collez-les dans la feuille :guilabel:`Report 2 Download` du :ref:`modèle " +"d'importation Excel `." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:97 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template `. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" +"Les lignes de transit sont automatiquement complétées et mises à niveau dans" +" les feuilles :guilabel:`transit for report 1` et :guilabel:`transit for " +"report 2` du :ref:`modèle d'importation Excel `. " +"Assurez-vous que toutes les écritures s'y trouvent et **si ce n'est pas le " +"cas**, copiez la formule des lignes complétées précédemment des feuilles " +":guilabel:`transit for report 1` ou :guilabel:`2` et collez-les dans les " +"lignes vides." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:104 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" +"Pour obtenir le bon solde de clôture, **ne supprimez aucune** ligne dans les" +" feuilles Excel." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:107 +msgid "Import into Odoo" +msgstr "Importer dans Odoo" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:109 +msgid "To import the data into Odoo:" +msgstr "Pour importer les données dans Odoo :" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:111 +msgid "Open the :ref:`Excel import template `." +msgstr "" +"Ouvez le :ref:`modèle d'importation Excel `." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:112 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" +"Copiez les données de la feuille :guilabel:`transit for report 2` et " +"utilisez le *collage spécial* pour uniquement coller les valeurs dans la " +"feuille :guilabel:`Odoo Import to CSV`." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:114 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" +"Recherchez les cellules *bleues* dans la feuille :guilabel:`Odoo Import to " +"CSV`. Ce sont des écritures de rétrofacturation sans numéro de référence. " +"Étant donné qu'elles ne peuvent pas être importées en tant que telles, allez" +" à :menuselection:`Authorize.Net --> Compte --> Relevés --> Relevé de " +"règlement eCheck.Net`." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:117 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" +"Recherchez :guilabel:`Charge transaction/rétrofacturation` et cliquez " +"dessus." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:118 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" +"Copiez la description de la facture, copiez-la dans la cellule " +":guilabel:`Libellé` de la feuille :guilabel:`Odoo Import to CSV` et ajoutez " +"`Rétrofacturation /` devant la description." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:120 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template ` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" +"S'il y a plusieurs factures, ajoutez une ligne dans le :ref:`modèle " +"d'importation Excel ` pour chaque facture et " +"copiez/collez la description dans chaque ligne de :guilabel:`Libellé` " +"respective." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:125 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template ` for each invoice." +msgstr "" +"Pour les **rétrofacturations/retours combinés** dans les paiements, créez " +"une nouvelle ligne dans le :ref:`modèle d'importation Excel ` pour chaque facture." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 +msgid "Chargeback description" +msgstr "Description de la rétrofacturation" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:133 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" +"Ensuite, supprimez les lignes *transaction nulle* et *transaction annulée* " +"et modifiez le format de la colonne :guilabel:`Montant` de la feuille " +":guilabel:`Odoo Import to CSV` en *Nombre*." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:135 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" +"Retournez à :menuselection:`Relevé de règlement eCheck.Net --> Rechercher " +"une transaction` et recherchez à nouveau les dates de règlement par lot " +"précédemment utilisées." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:137 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" +"Vérifiez que les dates de règlement des lots sur eCheck.Net correspondent " +"aux dates des paiements associés trouvées dans la colonne :guilabel:`Date` " +"de la feuille :guilabel:`Odoo Import to CSV`." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:139 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" +"Si ce n'est pas le cas, remplacez la date par celle d'eCheck.Net. Triez la " +"colonne par *date* et assurez-vous que le format est `MM/DD/YYYY`." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:141 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" +"Copiez les données - y compris les en-têtes de colonne - de la feuille " +":guilabel:`Odoo Import to CSV`, collez-les dans un nouveau fichier Excel et " +"enregistrez-les en utilisant le format CSV." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:143 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" +"Ouvrez l'application Comptabilité, allez à :menuselection:`Configuration -->" +" Journaux`, cochez la case :guilabel:`Authorize.Net` et cliquez sur " +":menuselection:`Favoris --> Importer des enregistrements --> Télécharger le " +"fichier`. Sélectionnez le fichier CSV et chargez-le dans Odoo." + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:148 +msgid "" +"List of `eCheck.Net return codes " +"`_" +msgstr "" +"Liste des `codes de retour eCheck.Net " +"`_" #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:3 msgid "Buckaroo" diff --git a/locale/fr/LC_MESSAGES/inventory_and_mrp.po b/locale/fr/LC_MESSAGES/inventory_and_mrp.po index 06aedb794..8736a20be 100644 --- a/locale/fr/LC_MESSAGES/inventory_and_mrp.po +++ b/locale/fr/LC_MESSAGES/inventory_and_mrp.po @@ -15218,6 +15218,13 @@ msgid "" ":menuselection:`Manufacturing` module by selecting " ":menuselection:`Operations --> Work Orders`." msgstr "" +"Odoo *Fabrication* permet d'exécuter des ordres de travail à des postes de " +"travail spécifiques. Lorsqu'un ordre de fabrication est créé pour un " +"produit, tout ordre de travail répertorié dans l'onglet " +":guilabel:`Opérations` de la *Nomenclature* du produit sera automatiquement " +"créé et assigné au poste de travail précisé. Les ordres de travail peuvent " +"être gérés dans le module :menuselection:`Fabrication` en sélectionnant " +":menuselection:`Opérations --> Ordres de travail`." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:11 msgid "" @@ -15227,6 +15234,12 @@ msgid "" "checkbox next to :guilabel:`Work Orders`. Work centers can then be created " "and managed by selecting :menuselection:`Configuration --> Work Centers`." msgstr "" +"Pour utiliser les postes de travail, la fonctionnalité :guilabel:`Ordres de " +"travail` doit d'abord être activée. Pour ce faire, allez au module " +":menuselection:`Fabrication`, sélectionnez :menuselection:`Configuration -->" +" Paramètres` et cochez la case à côté des :guilabel:`Ordres de travail`. Les" +" postes de travail peuvent ensuite être créés et gérés en sélectionnant " +":menuselection:`Configuration --> Postes de travail`." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:17 msgid "Create a work center" @@ -15238,6 +15251,9 @@ msgid "" ":menuselection:`Configuration --> Work Centers --> Create`. The work center " "form can then be filled out as follows:" msgstr "" +"Dans le module :menuselection:`Fabrication`, sélectionnez " +":menuselection:`Configuration --> Postes de travail --> Créer`. Le " +"formulaire du poste de travail peut ensuite être complété comme suit :" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:22 msgid "" @@ -15250,6 +15266,8 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:24 msgid ":guilabel:`Tag`: assign the work center one or more user-created tags" msgstr "" +":guilabel:`Étiquette` : assignez une ou plusieurs étiquettes créées par " +"l'utilisateur au poste de travail" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:25 msgid "" @@ -15326,12 +15344,16 @@ msgid "" ":guilabel:`Setup Time`: time required to set up the work center before work " "can commence" msgstr "" +":guilabel:`Temps de configuration` : temps requis pour configurer le poste " +"de travail avant que le travaille puisse commencer" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 msgid "" ":guilabel:`Cleanup Time`: time required to clean the work center after work " "is finished" msgstr "" +":guilabel:`Temps de nettoyage` : temps requis pour nettoyer le poste de " +"travail après que le travail est terminé" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 msgid "" diff --git a/locale/fr/LC_MESSAGES/sales.po b/locale/fr/LC_MESSAGES/sales.po index 45d88504d..6c033efd6 100644 --- a/locale/fr/LC_MESSAGES/sales.po +++ b/locale/fr/LC_MESSAGES/sales.po @@ -26,7 +26,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:49+0000\n" "Last-Translator: Jolien De Paepe, 2023\n" "Language-Team: French (https://app.transifex.com/odoo/teams/41243/fr/)\n" @@ -2197,6 +2197,11 @@ msgid "" " **discount** or modify the product **price**, click respectively " ":guilabel:`Disc` or :guilabel:`Price` and enter the amounts." msgstr "" +"Cliquez sur des produits pour les ajouter au panier. Pour changer la " +"**quantité**, cliquez sur :guilabel:`Qté` et saisissez le nombre de produits" +" à l'aide du clavier. Pour ajouter une **remise** ou modifiez le **prix** du" +" produit, cliquez respectivement sur :guilabel:`Rem.` ou :guilabel:`Prix` et" +" saisissez les montants." #: ../../content/applications/sales/point_of_sale.rst:38 msgid "" @@ -2255,6 +2260,11 @@ msgid "" ":guilabel:`Create`, completing the form, and saving. Lastly, click " ":guilabel:`Set Customer` to set the selected customer." msgstr "" +"Pour accéder à la liste des clients, cliquez sur :guilabel:`Client` sur " +"l'interface du PdV. Ensuite, sélectionnez un client ou créez-en un nouveau " +"en cliquant sur :guilabel:`Créer`, en complétant le formulaire et en " +"enregistrant. Enfin, cliquez sur :guilabel:`Définir le client` pour définir " +"le client sélectionné." #: ../../content/applications/sales/point_of_sale.rst:68 msgid "Customer notes" @@ -2409,6 +2419,8 @@ msgid "" "the total of all the transactions made during the session grouped by payment" " method;" msgstr "" +"la totalité des transactions effectuées pendant la session regroupées par " +"mode de paiement ;" #: ../../content/applications/sales/point_of_sale.rst:122 msgid "the expected amounts grouped by payment method." @@ -2449,6 +2461,9 @@ msgid "" "You can let the session open by clicking :guilabel:`Keep Session Open` or " "abort and keep selling by clicking :guilabel:`Continue Selling`." msgstr "" +"Vous pouvez laisser la session ouverte en cliquant sur :guilabel:`Laisser " +"ouvert` ou l'interrompre et continuer à vendre en cliquant sur " +":guilabel:`Continuer la vente`." #: ../../content/applications/sales/point_of_sale.rst:140 msgid "" @@ -2457,6 +2472,11 @@ msgid "" " check :guilabel:`Accept payments difference and post a profit/loss journal " "entry`." msgstr "" +"En fonction de votre configuration, il se peut que vous ne soyez pas " +"autorité à clôturer une session si les recettes en espèces attendues ne " +"correspondent pas aux espèces comptées. Pour clôturer la session, cochez " +":guilabel:`Voulez-vous accepter un écart de règlement et l'enregistrer au " +"compte de résultat ?`" #: ../../content/applications/sales/point_of_sale.rst:145 msgid "" @@ -2482,6 +2502,8 @@ msgid "" "To access the general POS settings, go to :menuselection:`Point of Sale --> " "Configuration --> Settings`." msgstr "" +"Pour accéder aux paramètres généraux du point de vente, allez à " +":menuselection:`Point de Vente --> Configuration --> Paramètres`." #: ../../content/applications/sales/point_of_sale/configuration.rst:16 msgid "" @@ -2490,6 +2512,11 @@ msgid "" "Alternatively, from the Point of Sale dashboard, click the vertical ellipsis" " (:guilabel:`⋮`) button on a POS card, then on :guilabel:`Settings`." msgstr "" +"Pour accéder aux paramètres d'un point de vue spécifique, allez à " +":menuselection:`Point de Vente --> Configuration --> Point de Vente`. Sinon," +" dans le tableau de bord du point de vente, cliquez sur le bouton d'ellipse " +"verticale (:guilabel:`⋮`) sur une carte du PdV, puis sur " +":guilabel:`Paramètres`." #: ../../content/applications/sales/point_of_sale/configuration.rst:21 msgid "Make products available" @@ -2605,46 +2632,22 @@ msgid "" "<../../../productivity/iot/config/connect>` may require :doc:`the HTTPS " "protocol ` to establish a secure connection between the browser and " "the printer. However, trying to reach the printer's IP address using HTTPS " -"leads to a warning page on most web browsers." +"leads to a warning page on most web browsers. In that case, you can " +"temporarily :ref:`force the connection `, which " +"allows you to reach the page in HTTPS and use the ePOS printer in Odoo as " +"long as the browser window stays open." msgstr "" "Pour fonctionner avec Odoo, certains modèles qui peuvent être utilisés sans " "une :doc:`IoT Box <../../../productivity/iot/config/connect>` peuvent " "nécessiter :doc:`le protocole HTTPS ` pour établir une connexion " "sécurisée entre le navigateur et l'imprimante. Cependant, le fait d'essayer " "d'atteindre l'adresse IP de l'imprimante utilisant HTTPS conduit à une page " -"d'avertissement sur la plupart des navigateurs web." +"d'avertissement sur la plupart des navigateurs web. Dans ce cas, vous pouvez" +" temporairement :ref:`forcer la connexion `, ce qui " +"vous permet d'aller à la page en HTTPS et utiliser l'imprimante ePOS dans " +"Odoo tant que la fenêtre du navigateur reste ouverte." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:41 -msgid "warning page about the connection privacy on Google Chrome" -msgstr "" -"Page d'avertissement sur la confidentialité de la connexion dans Google " -"Chrome" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:41 -msgid "Warning page on Google Chrome, Windows 10" -msgstr "Page d'avertissement dans Google Chrome, Windows 10" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:43 -msgid "" -"In that case, you can temporarily force the connection by clicking " -":guilabel:`Advanced` and :guilabel:`Proceed to [IP address] (unsafe)`. Doing" -" so allows you to reach the page in HTTPS and use the ePOS printer in Odoo " -"as long as the browser window stays open." -msgstr "" -"Dans ce cas, vous pouvez temporairement forcer la connexion en cliquant sur " -":guilabel:`Avancé` et :guilabel:`Procéder à [adresse IP] (non sécurisé)`. " -"Cela vous permet d'accéder à la page en HTTPS et d'utiliser l'imprimante " -"ePOS dans Odoo tant que la fenêtre du navigateur reste ouverte." - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:48 -msgid "" -"The previous instructions apply to Google Chrome but are similar to other " -"browsers." -msgstr "" -"Les instructions précédentes s'appliquent à Google Chrome, mais sont " -"similaires pour les autres navigateurs." - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:51 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:40 msgid "" "The connection is lost after closing the browser window. Therefore, this " "method should only be used as a **workaround** or as a pre-requisite for the" @@ -2655,11 +2658,11 @@ msgstr "" "**contournement** ou comme un prérequis pour les :ref:`instructions " "suivantes `." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 msgid "Generate, export, and import self-signed certificates" msgstr "Générer, exporter et importer des certificats auto-signés" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:60 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 msgid "" "For a long-term solution, you must generate a **self-signed certificate**. " "Then, export and import it into your browser." @@ -2668,7 +2671,7 @@ msgstr "" "signé**. Ensuite, vous pouvez l'exporter et l'importer dans votre " "navigateur." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 msgid "" "**Generating** an SSL certificate should only be done **once**. If you " "create another certificate, devices using the previous one will lose HTTPS " @@ -2678,28 +2681,46 @@ msgstr "" "fois**. Si vous créez un autre certificat, les appareils utilisant le " "précédent perdront l'accès HTTPS." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:69 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 msgid "Windows 10 & Linux OS" msgstr "Windows 10 & Linux OS" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:73 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62 msgid "Generate a self-signed certificate" msgstr "Générer un certificat auto-signé" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:75 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 msgid "" -"After forcing the connection, sign in using your printer credentials to " -"access the ePOS printer settings. To sign in, enter `epson` in the " -":guilabel:`ID` field and your printer serial number in the " -":guilabel:`Password` field." +"Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force " +"the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to " +"[IP address] (unsafe)`." msgstr "" -"Après avoir forcé la connexion, ouvrez une session en utilisant les " -"identifiants de votre imprimante pour accéder aux paramètres de l'imprimante" -" ePOS. Pour ouvrir une session, saisissez `epson` dans le champ " -":guilabel:`ID` et le numéro de série de votre imprimante dans le champ " -":guilabel:`Mot de passe`." +"Allez à l'adresse IP de l'ePOS (par ex. `https://192.168.1.25`) et forcez la" +" connexion en cliquant sur :guilabel:`Avancé` et :guilabel:`Procéder à " +"[adresse IP] (non sécurisé)`." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:79 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "warning page about the connection privacy on Google Chrome" +msgstr "" +"Page d'avertissement sur la confidentialité de la connexion dans Google " +"Chrome" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72 +msgid "Warning page on Google Chrome, Windows 10" +msgstr "Page d'avertissement dans Google Chrome, Windows 10" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74 +msgid "" +"Then, sign in using your printer credentials to access the ePOS printer " +"settings. To sign in, enter `epson` in the :guilabel:`ID` field and your " +"printer serial number in the :guilabel:`Password` field." +msgstr "" +"Ensuite, connectez-vous en utilisant les identifiants de l'imprimante pour " +"accéder aux paramètres de l'imprimante ePOS. Pour vous connecter, saisissez " +"`epson` dans le champ :guilabel:`ID` et le numéro de série de votre " +"imprimante dans le champ :guilabel:`Mot de passe`." + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78 msgid "" "Click :guilabel:`Certificate List` in the :guilabel:`Authentication` " "section, and click :guilabel:`create` to generate a new **Self-Signed " @@ -2718,7 +2739,7 @@ msgstr "" ":guilabel:`Créer` et :guilabel:`Réinitialiser` ou redémarrez l'imprimante " "manuellement." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:86 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 msgid "" "The self-signed certificate is generated. Reload the page and click " ":guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure " @@ -2730,30 +2751,30 @@ msgstr "" "que le **Certificat auto-signé** est correctement sélectionné dans la " "section :guilabel:`Certificat du serveur`." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:90 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 msgid "Export a self-signed certificate" msgstr "Exporter un certificat auto-signé" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:92 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 msgid "" "The export process is heavily dependent on the :abbr:`OS (Operating System)`" " and the browser. Start by accessing your ePOS printer settings on your web " -"browser by navigating to its IP address, for example, " -"`https://192.168.1.25`. Then, force the connection as explained in the " -":ref:`introduction `." +"browser by navigating to its IP address (e.g., `https://192.168.1.25`). " +"Then, force the connection as explained in the **Generate a self-signed " +"certificate tab**." msgstr "" "La procédure d'exportation dépend fortement du système d'exploitation et du " "navigateur. Commencez par accéder aux paramètres de votre imprimante ePOS " -"sur votre navigateur web en allant à son adresse IP, par exemple, " -"`https://192.168.1.25`. Ensuite, forcez la connexion comme il est expliqué " -"dans l':ref:`introduction `." +"sur votre navigateur web en allant à son adresse IP (par ex. " +"`https://192.168.1.25`). Forcez ensuite la connexion comme il est expliqué " +"dans l'onglet **Générer un certificat autosigné**." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:97 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:160 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 msgid "If you are using **Google Chrome**," msgstr "Si vous utilisez **Google Chrome**," -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:99 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 msgid "" "click :guilabel:`Not secure` next to the search bar, and " ":guilabel:`Certificate is not valid`;" @@ -2767,12 +2788,12 @@ msgstr "" "Le bouton dans la navigateur Google Chrome signalant que la Connexion à " "l'imprimante n'est pas sécurisée." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" msgstr "" "allez à l'onglet :guilabel:`Détails` et cliquez sur :guilabel:`Exporter` ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:107 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105 msgid "" "add `.crt` at the end of the file name to ensure it has the correct " "extension;" @@ -2780,7 +2801,7 @@ msgstr "" "ajoutez `.crt` à la fin du nom de fichier pour vous assurer qu'il a " "l'extension correcte ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 msgid "" "select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom " "of the pop-up window;" @@ -2788,12 +2809,12 @@ msgstr "" "sélectionnez :guilabel:`ASCII encodé en Base64, certificat unique`, en bas " "de la fenêtre contextuelle ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:110 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:128 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125 msgid "save, and the certificate is exported." msgstr "enregistrez et le certificat est exporté." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:113 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 msgid "" "Make sure that the certificate ends with the extension `.crt`. Otherwise, " "some browsers might not see the file during the import process." @@ -2802,17 +2823,17 @@ msgstr "" "certains navigateurs risquent de ne pas voir le fichier pendant la procédure" " d'importation." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:172 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 msgid "If you are using **Mozilla Firefox**," msgstr "Si vous utilisez **Mozilla Firefox**," -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:118 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 msgid "click the **lock-shaped** icon on the left of the address bar;" msgstr "" "cliquez sur l'icône en forme de **cadenas** à gauche de la barre d'adresse ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:119 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 msgid "" "go to :menuselection:`Connection not secure --> More information --> " "Security tab --> View certificate`;" @@ -2826,20 +2847,20 @@ msgstr "" "Le bouton dans le navigateur Mozilla Firefox signalant que la connexion " "n'est pas sécurisée." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:126 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123 msgid "scroll down to the :guilabel:`Miscellaneous` section;" msgstr "descendez jusqu'à la section :guilabel:`Divers` ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124 msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" msgstr "" "cliquez sur :guilabel:`PEM (cert)` dans la section :guilabel:`Télécharger` ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:130 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 msgid "Import a self-signed certificate" msgstr "Importer un certificat auto-signé" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:132 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 msgid "" "The import process is heavily dependent on the :abbr:`OS (Operating System)`" " and the browser." @@ -2847,11 +2868,11 @@ msgstr "" "La procédure d'importation dépend fortement du système d'exploitation et du " "navigateur." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:137 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 msgid "Windows 10" msgstr "Windows 10" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 msgid "" "Windows 10 manages certificates, which means that self-signed certificates " "must be imported from the certification file rather than the browser. To do " @@ -2861,14 +2882,14 @@ msgstr "" "signés doivent être importés depuis le fichier de certification plutôt que " "depuis le navigateur. Procédez comme suit :" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 msgid "" "open the Windows File Explorer and locate the downloaded certification file;" msgstr "" "ouvrez l'explorateur de fichiers de Windows et localisez le fichier de " "certification téléchargé ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:143 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 msgid "" "right-click on the certification file and click :guilabel:`Install " "Certificate`;" @@ -2876,7 +2897,7 @@ msgstr "" "cliquez droit sur le fichier de certification et cliquez sur " ":guilabel:`Installer le certificat` ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 msgid "" "select where to install the certificate and for whom - either for the " ":guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, " @@ -2886,7 +2907,7 @@ msgstr "" "l':guilabel:`utilisateur actuel`, soit pour tous les utilisateurs " "(:guilabel:`Ordinateur local`). Cliquez ensuite sur :guilabel:`Suivant` ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:148 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 msgid "" "on the `Certificate Store` screen, tick :guilabel:`Place all certificates in" " the following store`, click :guilabel:`Browse...`, and select " @@ -2897,27 +2918,27 @@ msgstr "" "et sélectionnez :guilabel:`Autorités de certification racines de confiance` " ";" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:155 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:151 msgid "click :guilabel:`Finish`, accept the pop-up security window;" msgstr "" "cliquez sur :guilabel:`Terminer`, acceptez la fenêtre contextuelle de " "sécurité ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 msgid "restart the computer to make sure that the changes are applied." msgstr "" "redémarrez l'ordinateur pour vous assurer que tous les changements sont " "appliqués." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 msgid "Linux" msgstr "Linux" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:162 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 msgid "open Chrome;" msgstr "ouvrez Chrome ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 msgid "" "go to :menuselection:`Settings --> Privacy and security --> Security --> " "Manage certificates`;" @@ -2925,7 +2946,7 @@ msgstr "" "allez à :menuselection:`Paramètres --> Confidentialité et sécurité --> " "Sécurité --> Gérer les certificats` ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 msgid "" "go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select " "the exported certification file;" @@ -2933,24 +2954,24 @@ msgstr "" "allez à l'onglet :guilabel:`Autorités`, cliquez sur :guilabel:`Importer` et " "sélectionnez le fichier de certification importé ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:167 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 msgid "accept all warnings;" msgstr "acceptez tous les avertissements ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:164 msgid "click :guilabel:`ok`;" msgstr "cliquez sur :guilabel:`ok` ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:169 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 msgid "restart your browser." msgstr "redémarrez votre navigateur." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:170 msgid "open Firefox;" msgstr "ouvrez Firefox ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:171 msgid "" "go to :menuselection:`Settings --> Privacy & Security --> Security --> View " "Certificates... --> Import`;" @@ -2958,23 +2979,23 @@ msgstr "" "allez à :menuselection:`Paramètres --> Confidentialité & Sécurité --> " "Sécurité --> Afficher les certificats... --> Importer` ; " -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:173 msgid "select the exported certification file;" msgstr "sélectionnez le fichier de certification exporté ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:178 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 msgid "tick the checkboxes and validate;" msgstr "cochez les cases à cocher et validez ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 msgid "Mac OS" msgstr "Mac OS" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:183 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 msgid "To secure the connection on a Mac:" msgstr "Pour sécuriser la connexion sur un Mac :" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:185 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 msgid "" "open Safari and navigate to your printer's IP address. Doing so leads to a " "warning page;" @@ -2982,7 +3003,7 @@ msgstr "" "ouvrez Safari et allez à l'adresse IP de votre imprimante. Une page " "d'avertissement s'affiche ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 msgid "" "on the warning page, go to :menuselection:`Show Details --> visit this " "website --> Visit Website`, validate;" @@ -2990,17 +3011,17 @@ msgstr "" "sur la page d'avertissement, allez à :menuselection:`Afficher les détails " "--> visiter ce site web --> Visiter le site web`, validez ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:184 msgid "reboot the printer so you can use it with any other browser." msgstr "" "redémarrez l'imprimante pour pouvoir l'utiliser avec n'importe quel autre " "navigateur." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:190 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 msgid "Android OS" msgstr "Android OS" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188 msgid "" "To import an SSL certificate into an Android device, first create and export" " it from a computer. Next, transfer the `.crt` file to the device using " @@ -3011,22 +3032,22 @@ msgstr "" " `.crt` vers l'appareil par email, Bluetooth ou USB. Une fois le fichier sur" " l'appareil," -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:196 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192 msgid "open the settings and search for `certificate`;" msgstr "ouvrez les paramètres et recherchez le `certificat` ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 msgid "click :guilabel:`Certificate AC` (Install from device storage);" msgstr "" "cliquez sur :guilabel:`Certificate AC` (Installer à partir du stockage de " "l'appareil) ;" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:198 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:194 msgid "select the certificate file to install it on the device." msgstr "" "sélectionnez le fichier de certificat pour l'installer sur l'appareil." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197 msgid "" "The specific steps for installing a certificate may vary depending on the " "version of Android and the device manufacturer." @@ -3034,7 +3055,7 @@ msgstr "" "Les étapes spécifiques pour l'installation d'un certificat peuvent dépendre " "fortement de la version d'Android et du fabriquant de l'appareil." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:206 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:202 msgid "" "If you need to export SSL certificates from an operating system or web " "browser that has not been mentioned, search for `export SSL certificate` + " @@ -3046,7 +3067,7 @@ msgstr "" "`exporter certificat SSL` + `le nom de votre navigateur ou système " "d'exploitation` dans votre moteur de recherche préféré." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:209 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:205 msgid "" "Similarly, to import SSL certificates from an unmentioned OS or browser, " "search for `import SSL certificate root authority` + `the name of your " @@ -3057,11 +3078,11 @@ msgstr "" "autorité racine` + `le nom de votre navigateur ou système d'opération` dans " "votre moteur de recherche préféré." -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:210 msgid "Check if the certificate was imported correctly" msgstr "Vérifiez si le certificat est correctement importé" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:216 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:212 msgid "" "To confirm your printer's connection is secure, connect to its IP address " "using HTTPS. For example, navigate to `https://192.168.1.25` in your " @@ -4965,12 +4986,17 @@ msgid "" "Configuration --> Point of Sale`, select your POS, and click " ":menuselection:`Edit --> Is a Bar/Restaurant --> Save`." msgstr "" +"Pour activer les fonctionnalités, allez à :menuselection:`Point de Vente -->" +" Configuration --> Point de Vente`, sélectionnez votre PdV et cliquez sur " +":menuselection:`Modifier --> Est un Bar/Restaurant --> Sauvegarder`." #: ../../content/applications/sales/point_of_sale/restaurant.rst:26 msgid "" "These specific features can be identified by the cutlery-shaped icon located" " to the right of the feature name." msgstr "" +"Ces fonctionnalités spécifiques peuvent être identifiées par l'icône en " +"forme de couverts à droite du nom de la fonctionnalité." #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3 msgid "Bills" @@ -4996,6 +5022,11 @@ msgid "" "select your POS. Then, scroll down to the :guilabel:`Bills & Receipts` " "section and enable :guilabel:`Bill Printing` and :guilabel:`Bill Splitting`." msgstr "" +"Pour activer les fonctionnalités d'impression de la facture et de partage " +"d'addition, allez à :menuselection:`Point de Vente --> Configuration --> " +"Point de Vente` et sélectionnez votre PdV. Faites ensuite défiler jusqu'à la" +" section :guilabel:`Factures & Reçus` et activez :guilabel:`Impression de la" +" facture` et :guilabel:`Partage d'addition`." #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst-1 msgid "" @@ -6644,7 +6675,7 @@ msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:76 msgid "Add an unsupported marketplace" -msgstr "" +msgstr "Ajouter un marketplace non pris en charge" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:78 msgid "" @@ -6654,6 +6685,12 @@ msgid "" "wish to use them. See :ref:`here ` for the " "exhaustive list of natively supported marketplaces." msgstr "" +"Certains marketplaces Amazon, telles qu'Amazon Brésil, ne sont pas créées " +"par défaut, car elles ne sont pas officiellement prises en charge par Odoo. " +"Elles peuvent toutefois être compatibles avec votre compte vendeur. Ces " +"marketplaces peuvent être ajoutées manuellement si vous voulez les utiliser." +" Consultez :ref:`ici ` la liste exhaustive " +"des marketplaces prises en charge nativement." #: ../../content/applications/sales/sales/amazon_connector/setup.rst:84 msgid "" @@ -6662,18 +6699,27 @@ msgid "" "shipping/docs/seller-central-urls>`_. The marketplace must belong to the " "same region as that of your seller account." msgstr "" +"Pour savoir si une marketplace est éventuellement compatible, consultez la " +"`documentation d'Amazon `_. La marketplace doit appartenir à la " +"même région que celle de votre compte vendeur." #: ../../content/applications/sales/sales/amazon_connector/setup.rst:88 msgid "" "To add a new marketplace, activate the :ref:`developer mode `." msgstr "" +"Pour ajouter une nouvelle marketplace, activez le :ref:`mode développeur " +"`." #: ../../content/applications/sales/sales/amazon_connector/setup.rst:90 msgid "" "Once that is done, go to :menuselection:`Sales --> Configuration --> " "Settings --> Connectors --> Amazon Sync --> Amazon Marketplaces`." msgstr "" +"Une fois cela fait, allez à :menuselection:`Ventes --> Configuration --> " +"Paramètres --> Connecteurs --> Synchronisation Amazon --> Marketplaces " +"Amazon`." #: ../../content/applications/sales/sales/amazon_connector/setup.rst:93 msgid "" @@ -6684,6 +6730,14 @@ msgid "" " the `Amazon Documentation for seller central URLs `_." msgstr "" +"De là, créez une nouvelle marketplace. Saisissez l'Identifiant de la " +"marketplace et sélectionnez la Région d'Amazon de votre marketplace, comme " +"il est décrit dans la `Documentation d'Amazon relative aux identifiants de " +"marketplace `_, et l'URL Seller Central comme il est " +"décrit dans la `Documentation d'Amazon relative aux URL Seller Central " +"`_." #: ../../content/applications/sales/sales/amazon_connector/setup.rst:99 msgid "" @@ -6693,6 +6747,12 @@ msgid "" "respectively hold the *MarketplaceId*, the selected Amazon region and the " "*Seller Central URL* values from the Amazon Documentation." msgstr "" +"Définissez le nom de l’enregistrement sur ``Amazon.`` pour " +"facilement le retrouver (par ex. ``Amazon.se``). Les champs " +":guilabel:`Identifiant API`, :guilabel:`Région` et :guilabel:`URL Seller " +"Central` doivent respectivement contenir les valeurs *MarketplaceId*, la " +"région Amazon sélectionnée et l'*URL Seller Central* de la documentation " +"d'Amazon." #: ../../content/applications/sales/sales/amazon_connector/setup.rst:104 msgid "" @@ -6723,10 +6783,15 @@ msgid "" "is no guarantee that adding one as described above will work, nor can this " "be considered as a bug when contacting Odoo Support." msgstr "" +"Étant donné que les marketplaces ajoutées manuellement ne sont pas " +"officiellement prises en charge par Odoo, il n'y a aucune garantie que " +"l'ajout d'une marketplace comme il est décrit ci-dessus fonctionnera et cela" +" ne peut pas être considéré comme un bug lorsque vous contactez Odoo " +"Assistance." #: ../../content/applications/sales/sales/amazon_connector/update.rst:3 msgid "Install the Amazon Selling Partner API Update" -msgstr "" +msgstr "Installer la mise à jour Amazon Selling Partner API" #: ../../content/applications/sales/sales/amazon_connector/update.rst:5 msgid "" @@ -6734,6 +6799,10 @@ msgid "" "needs to be updated to continue to exchange information with Amazon. This " "also makes it easier for you to set up the Connector." msgstr "" +"À partir de juillet 2022, en raison d'un changement dans l'API d'Amazon, le " +"Connecteur Amazon doit être mis à jour pour qu'il continue à échanger des " +"informations avec Amazon. Cette mise à jour facilite également la " +"configuration du Connecteur." #: ../../content/applications/sales/sales/amazon_connector/update.rst:10 msgid "" @@ -6745,6 +6814,13 @@ msgid "" "and you can proceed with the :doc:`setup ` step of the Amazon " "Connector." msgstr "" +"Si votre base de données Odoo a été créée après la publication de la mise à " +"jour, le module de mise à jour est installé automatiquement. Pour vérifier " +"si ce module est déjà installé, allez aux :guilabel:`Apps`, supprimez le " +"filtre ``Apps`` et recherchez ``Amazon``. Si le module :guilabel:`Patch " +"Amazon/Selling Partner API` s'y trouve et est marqué comme installé, votre " +"base de données Odoo est déjà à jour et vous pouvez passer à l'étape de " +":doc:`configuration ` du Connecteur Amazon." #: ../../content/applications/sales/sales/amazon_connector/update.rst:17 msgid "Update Odoo to the latest release" @@ -6756,6 +6832,9 @@ msgid "" "module; to be able to install it, you must make sure that your Odoo source " "code is up-to-date." msgstr "" +"Le nouveau mécanisme d'authentification est accessible via un nouveau module" +" Odoo ; pour pouvoir l'installer, vous devez d'abord vous assurer que votre " +"code source Odoo est à jour." #: ../../content/applications/sales/sales/amazon_connector/update.rst:22 msgid "" @@ -6772,6 +6851,11 @@ msgid "" "` or by contacting your integrating " "partner." msgstr "" +"Si vous utilisez Odoo par le biais d'une installation sur vos serveurs ou " +"par le biais d'un partenaire, vous devez mettre à jour votre installation " +"comme il est expliqué dans :doc:`cette page de documentation " +"` ou en contactant votre partenaire " +"d'intégration." #: ../../content/applications/sales/sales/amazon_connector/update.rst:31 msgid "Update the list of available modules" @@ -6797,7 +6881,7 @@ msgstr "" #: ../../content/applications/sales/sales/amazon_connector/update.rst:40 msgid "Install the Amazon/Selling Partner API Patch" -msgstr "" +msgstr "Installer le Patch Amazon/Selling Partner API" #: ../../content/applications/sales/sales/amazon_connector/update.rst:43 msgid "" @@ -6828,12 +6912,20 @@ msgid "" " available modules, it means your Odoo source code is not up-to-date; refer " "to step one of this page." msgstr "" +"Le module devrait maintenant être disponible dans votre menu " +":guilabel:`Apps`. Supprimez le filtre ``Apps`` et recherchez ``Amazon`` ; le" +" module :guilabel:`Amazon/Selling Partner API Patch` devrait être disponible" +" pour l'installation. Si vous ne trouvez pas le module après avoir mis à " +"jour la liste des modules disponibles, cela signifie que votre code source " +"Odoo n'est pas à jour ; reprenez la première étape de cette page." #: ../../content/applications/sales/sales/amazon_connector/update.rst:54 msgid "" "Once the module is installed, link your Amazon account by following the " "instructions on the :doc:`setup ` page." msgstr "" +"Une fois le module installé, liez votre compte Amazon en suivant les " +"instructions sur la page de :doc:`configuration `." #: ../../content/applications/sales/sales/ebay_connector.rst:5 msgid "eBay Connector" @@ -10013,6 +10105,14 @@ msgid "" ":doc:`/applications/finance/payment_acquirers/authorize`, and others in the " ":doc:`/applications/finance/payment_acquirers` documentation." msgstr "" +"Vous y aurez directement accès à la page des **Fournisseurs de paiement** où" +" vous pouvez sélectionner et configurer les fournisseurs de votre choix. " +"Avant de créer ou de modifier un fournisseur de paiement, lisez notre " +"documentation sur la manière de recevoir des paiements par le biais de " +"fournisseurs de paiement tels que " +":doc:`/applications/finance/payment_acquirers/paypal`, " +":doc:`/applications/finance/payment_acquirers/authorize`, et autres dans la " +"documentation :doc:`/applications/finance/payment_acquirers`." #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:30 msgid "" @@ -10050,15 +10150,15 @@ msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:51 msgid ":doc:`/applications/finance/payment_acquirers`" -msgstr "" +msgstr ":doc:`/applications/finance/payment_acquirers`" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:52 msgid ":doc:`/applications/finance/payment_acquirers/paypal`" -msgstr "" +msgstr ":doc:`/applications/finance/payment_acquirers/paypal`" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:53 msgid ":doc:`/applications/finance/payment_acquirers/authorize`" -msgstr "" +msgstr ":doc:`/applications/finance/payment_acquirers/authorize`" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:3 msgid "Get a signature to confirm an order" diff --git a/locale/fr/LC_MESSAGES/services.po b/locale/fr/LC_MESSAGES/services.po index e25220590..330536868 100644 --- a/locale/fr/LC_MESSAGES/services.po +++ b/locale/fr/LC_MESSAGES/services.po @@ -1107,6 +1107,9 @@ msgid "" "Click on your helpdesk team's name - for the example below: *Customer Care* " "- and :doc:`set up your channel `." msgstr "" +"Cliquez sur le nom de votre équipe d'assistance - pour l'exemple ci-dessous " +": *Customer Care* - et :doc:`configurez votre canal " +"`." #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 msgid "" @@ -1122,6 +1125,9 @@ msgid "" "` */helpdesk " "(subject_of_ticket)*." msgstr "" +"Désormais, vos opérateurs peuvent créer des tickets en utilisant la " +":doc:`commande ` */helpdesk " +"(subject_of_ticket)*." #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:72 msgid "Prioritize tickets" diff --git a/locale/fr/LC_MESSAGES/websites.po b/locale/fr/LC_MESSAGES/websites.po index 07c4309ac..9890619ca 100644 --- a/locale/fr/LC_MESSAGES/websites.po +++ b/locale/fr/LC_MESSAGES/websites.po @@ -194,7 +194,7 @@ msgstr ":doc:`../maximizing_revenue/pricing`" #: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:30 msgid ":doc:`../../website/pages/seo`" -msgstr "" +msgstr ":doc:`../../website/pages/seo`" #: ../../content/applications/websites/ecommerce/managing_products.rst:5 msgid "Manage my products" @@ -328,7 +328,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 msgid "ecommerce product variants values" -msgstr "" +msgstr "Valeurs variantes produit eCommerce" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:39 msgid "Edit variants" @@ -344,7 +344,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 msgid "ecommerce product variants smart button" -msgstr "" +msgstr "Bouton intelligent variantes produit eCommerce" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:48 msgid "" @@ -404,7 +404,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 msgid "ecommerce product variants configure variants" -msgstr "" +msgstr "Configurer des variantes variantes produit eCommerce" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:72 msgid "" @@ -427,7 +427,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 msgid "ecommerce value price extra" -msgstr "" +msgstr "Prix supplémentaire valeur eCommerce" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:82 msgid "This is how the *Value Price Extra* looks on your website:" @@ -436,7 +436,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 msgid "ecommerce value price extra on the frontend" -msgstr "" +msgstr "Prix supplémentaire dans le frontend valeur eCommerce" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:89 msgid "" @@ -465,7 +465,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 msgid "ecommerce product variants archive" -msgstr "" +msgstr "Archiver variantes produit eCommerce" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:103 msgid "" @@ -477,7 +477,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 msgid "ecommerce product variants archive search" -msgstr "" +msgstr "Rechercher archive variantes produit eCommerce" #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:110 msgid ":doc:`../../../sales/sales/products_prices/products/variants`" @@ -557,7 +557,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst-1 msgid "Add an accessory product to product form." -msgstr "" +msgstr "Ajoutez un produit accessoire à la fiche du produit." #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:32 msgid "" @@ -570,7 +570,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst-1 msgid "See of payment view and accessory product suggestion." -msgstr "" +msgstr "Vue de paiement et suggestion de produits accessoires." #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:40 msgid "" @@ -613,7 +613,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst-1 msgid "Add an optional product to product form." -msgstr "" +msgstr "Ajoutez un produit optionnel à la fiche du produit." #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:60 msgid "" @@ -625,7 +625,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst-1 msgid "Pop-up with optional products appears." -msgstr "" +msgstr "Fenêtre contextuelle avec produits optionnels" #: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:68 msgid ":doc:`upselling`" @@ -2398,6 +2398,9 @@ msgid "" ":guilabel:`Newsletter Popup` snippets on the website are now protected by " "reCAPTCHA." msgstr "" +"Toutes les pages utilisant les snippets :guilabel:`Formulaire`, " +":guilabel:`Bloc newsletter` et :guilabel:`Fenêtre contextuelle Newsletter` " +"sur le site web sont désormais protégées par reCAPTCHA." #: ../../content/applications/websites/website/configuration/recaptcha.rst:65 msgid "" diff --git a/locale/nl/LC_MESSAGES/finance.po b/locale/nl/LC_MESSAGES/finance.po index 62ece53b2..b6abf44bc 100644 --- a/locale/nl/LC_MESSAGES/finance.po +++ b/locale/nl/LC_MESSAGES/finance.po @@ -11,20 +11,20 @@ # Cas Vissers , 2022 # Guido Leenders, 2023 # Dylan Kiss, 2023 -# Yenthe Van Ginneken , 2023 # Martin Trigaux, 2023 -# Jolien De Paepe, 2023 -# Erwin van der Ploeg , 2023 # Gunther Clauwaert , 2023 +# Yenthe Van Ginneken , 2023 +# Erwin van der Ploeg , 2023 +# Jolien De Paepe, 2023 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:47+0000\n" -"Last-Translator: Gunther Clauwaert , 2023\n" +"Last-Translator: Jolien De Paepe, 2023\n" "Language-Team: Dutch (https://app.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -549,7 +549,6 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:18 #: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:16 #: ../../content/applications/finance/accounting/reporting/budget.rst:11 -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:19 #: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 #: ../../content/applications/finance/accounting/taxes.rst:53 #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 @@ -6311,26 +6310,25 @@ msgstr "" msgid "" "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " "open the journal you want to edit, and select a currency in the field " -":guilabel:`Currency`. If left empty, all active currencies are handled " -"instead of just one." +":guilabel:`Currency`." msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency for the journal to handle." msgstr "" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:114 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 msgid "Multi-currency accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:119 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 msgid "Invoices, bills, and other documents" msgstr "" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:121 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 msgid "" "For all documents, you can select the currency and journal to use for the " -"transaction." +"transaction on the document itself." msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 @@ -9747,40 +9745,281 @@ msgstr "Intrastat" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 msgid "" -"**Intrastat** is the system for data collection and statistic production of " -"goods traded among the EU Member States. Organizations whose annual trade " -"surpasses a certain threshold must provide data about the goods traded with " -"other EU countries." +"`Intrastat `_ is the data collection and " +"statistics production system for goods traded among EU member states. It " +"collects data on:" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:10 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:9 msgid "" -"`Eurostat Statistics Explained - Glossary: Intrastat " -"`_" +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:14 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:11 msgid "" -"As of January 1, 2022, the reporting requirements have changed. One main " -"modification concerns the transaction codes which are now switching to a " -"2-digits format. All transactions recorded after this date have to follow " -"the new system’s rules." +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:21 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:13 +msgid "Returns of goods." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:16 msgid "" -"Go to :menuselection:`Accounting --> Settings --> Customer Invoices`, then " -"enable **Intrastat** and *Save*. Once the Intrastat has been activated you " -"are able to choose the **Default incoterm**." +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"`_, preferring instead " +"*intra-Union trade in goods statistics*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:23 +msgid "General configuration" msgstr "" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:25 msgid "" -"If you created your Odoo database prior to **January 13, 2022**, please " -":ref:`upgrade ` the ``account_intrastat`` module to add the" -" new transaction codes and :ref:`install ` the " -"``account_intrastat_expiry`` module to archive the old codes." +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the **Customer Invoices** section, tick " +":guilabel:`Intrastat` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:31 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located, and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:34 +msgid "" +"If your warehouses are located in multiple regions, you can define the " +"region code for each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:43 +msgid "Default Incoterm" +msgstr "Standaard incoterm" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "" +"You can set **default Incoterms** for your company by selecting an Intrastat" +" **code** in the :guilabel:`Default Incoterm` field of the **Customer " +"Invoices** section, and then clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "Product configuration" +msgstr "Product configuratie" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:54 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:59 +msgid "Commodity code" +msgstr "Goederencode" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:61 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature `_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:64 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:68 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:74 +msgid "Country of origin" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:76 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:82 +msgid "Invoices and bills configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:84 +msgid "" +"Once products are properly configured, several settings must be enabled on " +"the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:90 +msgid "Transaction code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:92 +msgid "" +"Transaction codes are used to identify a transaction's nature. To set a " +"transaction code on an invoice line, create an invoice or bill, click the " +":guilabel:`⋮` button, tick :guilabel:`Intrastat`, and use the newly-added " +":guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:101 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:107 +msgid "Partner country" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:109 +msgid "" +"The partner country is the vendor's or customer's country, depending on " +"whether it is an invoice or bill. It is automatically filled in using the " +":guilabel:`Country` field in the **contact form** of the partner." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:113 +msgid "" +"To edit the partner country manually, click on the :guilabel:`Other Info` " +"tab when on an invoice or bill, and select the :guilabel:`Intrastat " +"Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "Transport code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:121 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch). Once you have selected a :ref:`partner" +" country `, the :guilabel:`Intrastat Transport " +"Mode` becomes available." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "Value of the goods" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:130 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "Partner configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:138 +msgid "" +"Two fields from the partner's **contact form** are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set ` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:143 +msgid "Generate the Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:145 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration ` and the " +"information on the :ref:`products `, " +":ref:`invoices and bills `, and " +":ref:`partners `." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"Export the report as a PDF, XLSX, or XML file to submit it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:153 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:155 +msgid "Invoice or bill reference number;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:156 +msgid "" +":guilabel:`System`, which is a code automatically generated depending on " +"whether the document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:158 +msgid "" +":ref:`Country `, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:160 +msgid ":ref:`Transaction Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:161 +msgid "" +":ref:`Region Code ` (if your company is located in " +"Belgium);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:162 +msgid ":ref:`Commodity Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:163 +msgid ":ref:`Origin Country `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:164 +msgid ":ref:`Partner VAT `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid ":ref:`Transport Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:166 +msgid "" +":ref:`Value `, which is always expressed in EUR even if the" +" original invoice or bill used another currency." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 @@ -20093,6 +20332,7 @@ msgid "2-digits comparison" msgstr "" #: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:61 msgid "Template" msgstr "Sjabloon" @@ -28069,7 +28309,7 @@ msgid "" msgstr "" #: ../../content/applications/finance/payment_acquirers.rst:267 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:40 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:38 msgid "Configuration tab" msgstr "" @@ -28218,7 +28458,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/adyen.rst:10 #: ../../content/applications/finance/payment_acquirers/adyen.rst:137 #: ../../content/applications/finance/payment_acquirers/alipay.rst:36 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:53 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:51 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:47 #: ../../content/applications/finance/payment_acquirers/mollie.rst:31 #: ../../content/applications/finance/payment_acquirers/paypal.rst:162 @@ -28542,34 +28782,241 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:31 msgid "" -"If you are trying Authorize.Net as a test, with a *sandbox account*, change " -"the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a" -" test Odoo database, rather than on your main database." +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:35 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:34 msgid "" -"If you set :guilabel:`Test Mode` on Odoo and use an authorize.net account " -"instead of a sandbox.authorize.net account, it results in the following " -"error: *The merchant login ID or password is invalid or the account is " -"inactive*." +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:41 msgid "Place a hold on a card" msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:45 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 msgid "" -"With Authorize.net, you can enable the :ref:`manual capture " +"With Authorize.Net, you can enable the :ref:`manual capture " "`. If enabled, the funds are " "reserved for 30 days on the customer's card, but not charged yet." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:50 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:48 msgid "" "After **30 days**, the transaction is **voided automatically** by " -"Authorize.net." +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:54 +msgid "Import an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:57 +msgid "Export from Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:63 +msgid "" +"`Download the Excel import template " +"`_" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:65 +msgid "To export a statement:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:67 +msgid "Log in to Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:68 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:69 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:71 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:84 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:87 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:89 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:90 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:92 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:93 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:95 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:97 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template `. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:104 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:107 +msgid "Import into Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:109 +msgid "To import the data into Odoo:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:111 +msgid "Open the :ref:`Excel import template `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:112 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:114 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:117 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:118 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:120 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template ` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:125 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template ` for each invoice." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 +msgid "Chargeback description" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:133 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:135 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:137 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:139 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:141 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:143 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:148 +msgid "" +"List of `eCheck.Net return codes " +"`_" msgstr "" #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:3 diff --git a/locale/nl/LC_MESSAGES/settings.po b/locale/nl/LC_MESSAGES/settings.po index 138bc5099..6e0fb0dfe 100644 --- a/locale/nl/LC_MESSAGES/settings.po +++ b/locale/nl/LC_MESSAGES/settings.po @@ -6,6 +6,7 @@ # Translators: # Martin Trigaux, 2022 # Yenthe Van Ginneken , 2022 +# Jolien De Paepe, 2023 # #, fuzzy msgid "" @@ -14,7 +15,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-05-18 07:12+0200\n" "PO-Revision-Date: 2022-03-18 15:03+0000\n" -"Last-Translator: Yenthe Van Ginneken , 2022\n" +"Last-Translator: Jolien De Paepe, 2023\n" "Language-Team: Dutch (https://app.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -48,6 +49,11 @@ msgid "" "subscription amount significantly (or switch you from a free account to a " "paying one on our online platform)." msgstr "" +"Odoo is veel dingen (ERP, CMS, CRM-applicatie, e-Commerce back-end, enz.), " +"maar het is *geen* smartphone. Je moet voorzichtig zijn met het " +"toevoegen/verwijderen van functies (vooral Apps) op je database, omdat dit " +"het bedrag van je abonnement aanzienlijk kan beïnvloeden (of je kan overgaan" +" van een gratis account naar een betalend account op ons online platform)." #: ../../content/applications/settings/users_and_features.rst:18 msgid "" @@ -56,6 +62,10 @@ msgid "" "to test them on a duplicate of your database first. That way, if something " "goes wrong, your day-to-day business is not impacted." msgstr "" +"Deze pagina bevat informatie over hoe je je Odoo-instanties kan beheren. " +"Voordat je deze procedures uitvoert, raden we **sterk** aan om ze eerst te " +"testen op een duplicaat van je database. Op die manier, als er iets mis " +"gaat, hebben je dagelijkse activiteiten er geen last van." #: ../../content/applications/settings/users_and_features.rst:23 msgid "" diff --git a/locale/pl/LC_MESSAGES/administration.po b/locale/pl/LC_MESSAGES/administration.po new file mode 100644 index 000000000..a8eb7c9bd --- /dev/null +++ b/locale/pl/LC_MESSAGES/administration.po @@ -0,0 +1,9669 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"PO-Revision-Date: 2022-03-18 14:59+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/administration.rst:8 +msgid "Install and Maintain" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid "" +":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration/install.rst:5 +msgid "Install" +msgstr "" + +#: ../../content/administration/install/cdn.rst:3 +msgid "Set up a content delivery network (CDN)" +msgstr "" + +#: ../../content/administration/install/cdn.rst:8 +msgid "Deploying with KeyCDN" +msgstr "" + +#: ../../content/administration/install/cdn.rst:10 +msgid "" +"A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, " +"is a geographically distributed network of servers that provides high speed " +"internet content. The :abbr:`CDN (Content Delivery Network)` provides quick," +" high-quality content delivery for content-heavy websites." +msgstr "" + +#: ../../content/administration/install/cdn.rst:14 +msgid "" +"This document will guide you through the setup of a KeyCDN_ account with an " +"Odoo powered website." +msgstr "" + +#: ../../content/administration/install/cdn.rst:17 +msgid "Create a pull zone in the KeyCDN dashboard" +msgstr "" + +#: ../../content/administration/install/cdn.rst:19 +msgid "" +"On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` " +"menu item on the left. On the form, give a value to the :guilabel:`Zone " +"Name`, which will appear as part of the :abbr:`CDN (Content Delivery " +"Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the " +":guilabel:`Zone Status` to :guilabel:`active` to engage the zone. For the " +":guilabel:`Zone Type` set the value to :guilabel:`Pull`, and then, finally, " +"under the :guilabel:`Pull Settings`, enter the :guilabel:`Origin URL`— this " +"address should be the full Odoo database :abbr:`URL (Uniform Resource " +"Locator)`." +msgstr "" + +#: ../../content/administration/install/cdn.rst:28 +msgid "" +"Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* " +"subdomain prefix with the actual name of the database. A custom :abbr:`URL " +"(Uniform Resource Locator)` can be used, as well, in place of the Odoo " +"subdomain that was provided to the database." +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "KeyCDN's Zone configuration page." +msgstr "" + +#: ../../content/administration/install/cdn.rst:36 +msgid "" +"Under the :guilabel:`General Settings` heading below the zone form, click " +"the :guilabel:`Show all settings` button to expand the zone options. This " +"should be the last option on the page. After expanding the " +":guilabel:`General Settings` ensure that the :guilabel:`CORS` option is " +":guilabel:`enabled`." +msgstr "" + +#: ../../content/administration/install/cdn.rst:41 +msgid "" +"Next, scroll to the bottom of the zone configuration page and " +":guilabel:`Save` the changes. KeyCDN will indicate that the new zone will be" +" deployed. This can take about 10 minutes." +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "KeyCDN deploying the new Zone." +msgstr "" + +#: ../../content/administration/install/cdn.rst:49 +msgid "" +"A new :guilabel:`Zone URL` has been generated for your Zone, in this example" +" it is ``pulltest-xxxxx.kxcdn.com``. This value will differ for each " +"database." +msgstr "" + +#: ../../content/administration/install/cdn.rst:52 +msgid "" +"Copy this :guilabel:`Zone URL` to a text editor for later, as it will be " +"used in the next steps." +msgstr "" + +#: ../../content/administration/install/cdn.rst:55 +msgid "Configure the Odoo instance with the new zone" +msgstr "" + +#: ../../content/administration/install/cdn.rst:57 +msgid "" +"In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and" +" then activate the :guilabel:`Content Delivery Network (CDN)` setting and " +"copy/paste the :guilabel:`Zone URL` value from the earlier step into the " +":guilabel:`CDN Base URL` field. This field is only visible and configurable " +"when :doc:`Developer Mode <../../applications/general/developer_mode>` is " +"activated." +msgstr "" + +#: ../../content/administration/install/cdn.rst:63 +msgid "" +"Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN" +" Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`." +msgstr "" + +#: ../../content/administration/install/cdn.rst:66 +msgid ":guilabel:`Save` the settings when complete." +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "Activate the CDN setting in Odoo." +msgstr "" + +#: ../../content/administration/install/cdn.rst:72 +msgid "" +"Now the website is using the CDN for the resources matching the " +":guilabel:`CDN filters` regular expressions." +msgstr "" + +#: ../../content/administration/install/cdn.rst:75 +msgid "" +"In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` " +"integration is evidenced as working properly by checking the :abbr:`URL " +"(Uniform Resource Locators)` of images. The *CDN Base URL* value can be seen" +" by using your web browser's :guilabel:`Inspect` feature on the Odoo " +"website. Look for it's record by searching within the :guilabel:`Network` " +"tab inside of devtools." +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "" +"The CDN Base URL can be seen using the inspect function on the Odoo website." +msgstr "" + +#: ../../content/administration/install/cdn.rst:85 +msgid "" +"Prevent security issues by activating cross-origin resource sharing (CORS)" +msgstr "" + +#: ../../content/administration/install/cdn.rst:87 +msgid "" +"A security restriction in some browsers (such as Mozilla Firefox and Google " +"Chrome) prevents a remotely linked CSS file to fetch relative resources on " +"this same external server." +msgstr "" + +#: ../../content/administration/install/cdn.rst:90 +msgid "" +"If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in " +"the :guilabel:`CDN Zone`, the more obvious resulting problem on a standard " +"Odoo website will be the lack of *Font Awesome* icons because the font file " +"declared in the *Font Awesome* CSS won't be loaded from the remote server." +msgstr "" + +#: ../../content/administration/install/cdn.rst:95 +msgid "" +"When these cross-origin resource issues occur, a security error message " +"similar to the output below will appear in the web browser's developer " +"console:" +msgstr "" + +#: ../../content/administration/install/cdn.rst:98 +msgid "" +"``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from " +"loading /shop:1 by Cross-Origin Resource Sharing policy: No 'Access-Control-" +"Allow-Origin' header is present on the requested resource. Origin " +"'http://yourdatabase.odoo.com' is therefore not allowed access.``" +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "Error message populated in the browser console." +msgstr "" + +#: ../../content/administration/install/cdn.rst:106 +msgid "" +"Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the " +":abbr:`CDN (Content Delivery Network)` settings fixes this issue." +msgstr "" + +#: ../../content/administration/install/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/install/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :ref:`installation `, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/install/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/install/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/install/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/install/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/install/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/install/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/install/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/install/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/install/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/install/deploy.rst:46 +#: ../../content/administration/install/deploy.rst:58 +#: ../../content/administration/install/deploy.rst:153 +#: ../../content/administration/install/deploy.rst:276 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/install/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/install/deploy.rst:76 +#: ../../content/administration/install/install.rst:339 +#: ../../content/administration/install/install.rst:528 +#: ../../content/administration/install/install.rst:725 +msgid "PostgreSQL" +msgstr "PostgreSQL" + +#: ../../content/administration/install/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/install/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/install/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/install/deploy.rst:95 +#: ../../content/administration/install/deploy.rst:145 +#: ../../content/administration/install/deploy.rst:231 +#: ../../content/administration/install/deploy.rst:271 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/install/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/install/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/install/deploy.rst:100 +msgid "in ``/etc/postgresql/9.5/main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:108 +msgid "in ``/etc/postgresql/9.5/main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/install/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/install/deploy.rst:126 +msgid "" +"The :ref:`packaged installers ` will automatically " +"create a new user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/install/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/install/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/install/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/install/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/install/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/install/deploy.rst:148 +msgid "port 5432" +msgstr "port 5432" + +#: ../../content/administration/install/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/install/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/install/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/install/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/install/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/install/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/install/deploy.rst:180 +msgid "Builtin server" +msgstr "Wbudowany serwer" + +#: ../../content/administration/install/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP servers, using either multithreading or " +"multiprocessing." +msgstr "" + +#: ../../content/administration/install/deploy.rst:185 +msgid "" +"For production use, it is recommended to use the multiprocessing server as " +"it increases stability, makes somewhat better use of computing resources and" +" can be better monitored and resource-restricted." +msgstr "" + +#: ../../content/administration/install/deploy.rst:189 +msgid "" +"Multiprocessing is enabled by configuring :option:`a non-zero number of " +"worker processes `, the number of workers should be " +"based on the number of cores in the machine (possibly with some room for " +"cron workers depending on how much cron work is predicted)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:193 +msgid "" +"Worker limits can be configured based on the hardware configuration to avoid" +" resources exhaustion" +msgstr "" + +#: ../../content/administration/install/deploy.rst:196 +msgid "multiprocessing mode currently isn't available on Windows" +msgstr "" + +#: ../../content/administration/install/deploy.rst:199 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/install/deploy.rst:201 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/install/deploy.rst:202 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/install/deploy.rst:203 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/install/deploy.rst:206 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/install/deploy.rst:208 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/install/deploy.rst:209 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/install/deploy.rst:210 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/install/deploy.rst:212 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/install/deploy.rst:215 +#: ../../content/administration/install/deploy.rst:369 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/install/deploy.rst:217 +msgid "" +"In multiprocessing, a dedicated LiveChat worker is automatically started and" +" listening on :option:`the longpolling port ` " +"but the client will not connect to it." +msgstr "" + +#: ../../content/administration/install/deploy.rst:221 +msgid "" +"Instead you must have a proxy redirecting requests whose URL starts with " +"``/longpolling/`` to the longpolling port. Other request should be proxied " +"to the :option:`normal HTTP port `" +msgstr "" + +#: ../../content/administration/install/deploy.rst:225 +msgid "" +"To achieve such a thing, you'll need to deploy a reverse proxy in front of " +"Odoo, like nginx or apache. When doing so, you'll need to forward some more " +"http Headers to Odoo, and activate the proxy_mode in Odoo configuration to " +"have Odoo read those headers." +msgstr "" + +#: ../../content/administration/install/deploy.rst:233 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/install/deploy.rst:234 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/install/deploy.rst:236 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/install/deploy.rst:237 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/install/deploy.rst:238 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/install/deploy.rst:239 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" +msgstr "" + +#: ../../content/administration/install/deploy.rst:241 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:257 +msgid "HTTPS" +msgstr "HTTPS" + +#: ../../content/administration/install/deploy.rst:259 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:264 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/install/deploy.rst:265 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:266 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:267 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/install/deploy.rst:273 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/install/deploy.rst:274 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/install/deploy.rst:282 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:343 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/install/deploy.rst:345 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/install/deploy.rst:351 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/install/deploy.rst:356 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/install/deploy.rst:358 +msgid "To run cron jobs for an Odoo deployment as a WSGI application requires" +msgstr "" + +#: ../../content/administration/install/deploy.rst:360 +msgid "A classical Odoo (run via ``odoo-bin``)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:361 +msgid "" +"Connected to the database in which cron jobs have to be run (via " +":option:`odoo-bin -d`)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:363 +msgid "" +"Which should not be exposed to the network. To ensure cron runners are not " +"network-accessible, it is possible to disable the built-in HTTP server " +"entirely with :option:`odoo-bin --no-http` or setting ``http_enable = " +"False`` in the configuration file" +msgstr "" + +#: ../../content/administration/install/deploy.rst:371 +msgid "" +"The second problematic subsystem for WSGI deployments is the LiveChat: where" +" most HTTP connections are relatively short and quickly free up their worker" +" process for the next request, LiveChat require a long-lived connection for " +"each client in order to implement near-real-time notifications." +msgstr "" + +#: ../../content/administration/install/deploy.rst:376 +msgid "" +"This is in conflict with the process-based worker model, as it will tie up " +"worker processes and prevent new users from accessing the system. However, " +"those long-lived connections do very little and mostly stay parked waiting " +"for notifications." +msgstr "" + +#: ../../content/administration/install/deploy.rst:381 +msgid "" +"The solutions to support livechat/motifications in a WSGI application are:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:383 +msgid "" +"Deploy a threaded version of Odoo (instead of a process-based preforking " +"one) and redirect only requests to URLs starting with ``/longpolling/`` to " +"that Odoo, this is the simplest and the longpolling URL can double up as the" +" cron instance." +msgstr "" + +#: ../../content/administration/install/deploy.rst:387 +msgid "" +"Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting with " +"``/longpolling/`` to :option:`the longpolling port `." +msgstr "" + +#: ../../content/administration/install/deploy.rst:392 +msgid "Serving Static Files" +msgstr "" + +#: ../../content/administration/install/deploy.rst:394 +msgid "" +"For development convenience, Odoo directly serves all static files in its " +"modules. This may not be ideal when it comes to performances, and static " +"files should generally be served by a static HTTP server." +msgstr "" + +#: ../../content/administration/install/deploy.rst:398 +msgid "" +"Odoo static files live in each module's ``static/`` folder, so static files " +"can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/install/deploy.rst:402 +#: ../../content/administration/upgrade.rst:122 +msgid "Todo" +msgstr "" + +#: ../../content/administration/install/deploy.rst:402 +msgid "" +"test whether it would be interesting to serve filestored attachments via " +"this, and how (e.g. possibility of mapping ir.attachment id to filestore " +"hash in the database?)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:409 +msgid "Security" +msgstr "" + +#: ../../content/administration/install/deploy.rst:411 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/install/deploy.rst:415 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/install/deploy.rst:421 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:424 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:427 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/install/deploy.rst:432 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/install/deploy.rst:436 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`db_filter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/install/deploy.rst:443 +msgid "" +"Once your ``db_name`` and ``db_filter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:449 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:454 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/install/deploy.rst:458 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:461 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:468 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/install/deploy.rst:474 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/install/deploy.rst:478 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/install/deploy.rst:482 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/install/deploy.rst:486 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/install/deploy.rst:497 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/install/deploy.rst:508 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/install/deploy.rst:511 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/install/deploy.rst:518 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/install/deploy.rst:520 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/install/deploy.rst:524 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/install/deploy.rst:526 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/install/deploy.rst:530 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/install/deploy.rst:535 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:537 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/install/deploy.rst:544 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/install/deploy.rst:546 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/install/deploy.rst:560 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/install/deploy.rst:562 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/install/deploy.rst:564 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/install/deploy.rst:567 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/install/deploy.rst:573 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/install/deploy.rst:579 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/install/deploy.rst:582 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``db_filter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/install/deploy.rst:587 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/install/deploy.rst:591 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/install/deploy.rst:595 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/install/deploy.rst:601 +msgid "which will generate a 32 characters pseudorandom printable string." +msgstr "" + +#: ../../content/administration/install/deploy.rst:604 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/install/deploy.rst:606 +msgid "" +"Odoo supports all the major desktop and mobile browsers available on the " +"market, as long as they are supported by their publishers." +msgstr "" + +#: ../../content/administration/install/deploy.rst:609 +msgid "Here are the supported browsers:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:611 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/install/deploy.rst:612 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/install/deploy.rst:613 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/install/deploy.rst:614 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/install/deploy.rst:616 +msgid "" +"Please make sure your browser is up-to-date and still supported by its " +"publisher before filing a bug report." +msgstr "" + +#: ../../content/administration/install/deploy.rst:621 +msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." +msgstr "" + +#: ../../content/administration/install/deploy.rst:624 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/install/deploy.rst:627 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/install/deploy.rst:631 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:30 +#: ../../content/administration/install/email_gateway.rst:45 +msgid "Resources" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:38 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:47 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:50 +msgid "" +"If you don't have access/manage your email server, use :ref:`inbound " +"messages `." +msgstr "" + +#: ../../content/administration/install/install.rst:6 +msgid "Installing Odoo" +msgstr "" + +#: ../../content/administration/install/install.rst:8 +msgid "" +"There are multiple ways to install Odoo, or not install it at all, depending" +" on the intended use case." +msgstr "" + +#: ../../content/administration/install/install.rst:11 +msgid "This documents attempts to describe most of the installation options." +msgstr "" + +#: ../../content/administration/install/install.rst:14 +msgid ":ref:`setup/install/online`" +msgstr "" + +#: ../../content/administration/install/install.rst:14 +msgid "The easiest way to use Odoo in production or to try it." +msgstr "" + +#: ../../content/administration/install/install.rst:18 +msgid ":ref:`setup/install/packaged`" +msgstr "" + +#: ../../content/administration/install/install.rst:17 +msgid "" +"Suitable for testing Odoo, developing modules and can be used for long-term " +"production use with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration/install/install.rst:23 +msgid ":ref:`setup/install/source`" +msgstr "" + +#: ../../content/administration/install/install.rst:21 +msgid "" +"Provides greater flexibility: e.g. allow multiple running Odoo versions on " +"the same system. Good for developing modules, can be used as base for " +"production deployment." +msgstr "" + +#: ../../content/administration/install/install.rst:28 +msgid ":ref:`setup/install/docker`" +msgstr "" + +#: ../../content/administration/install/install.rst:26 +msgid "" +"If you usually use docker_ for development or deployment, an official " +"docker_ base image is available." +msgstr "" + +#: ../../content/administration/install/install.rst:33 +msgid "Editions" +msgstr "" + +#: ../../content/administration/install/install.rst:35 +msgid "" +"There are two different Editions_ of Odoo: the Community and Enterprise " +"versions. Using the Enterprise version is possible on `Odoo Online`_ and " +"accessing the code is restricted to Enterprise customers and partners. The " +"Community version is freely available to anyone." +msgstr "" + +#: ../../content/administration/install/install.rst:40 +msgid "" +"If you already use the Community version and wish to upgrade to Enterprise, " +"please refer to :ref:`setup/enterprise` (except for " +":ref:`setup/install/source`)." +msgstr "" + +#: ../../content/administration/install/install.rst:47 +msgid "Online" +msgstr "" + +#: ../../content/administration/install/install.rst:50 +msgid "Demo" +msgstr "" + +#: ../../content/administration/install/install.rst:52 +msgid "" +"To simply get a quick idea of Odoo, demo_ instances are available. They are " +"shared instances which only live for a few hours, and can be used to browse " +"around and try things out with no commitment." +msgstr "" + +#: ../../content/administration/install/install.rst:56 +msgid "Demo_ instances require no local installation, just a web browser." +msgstr "" + +#: ../../content/administration/install/install.rst:59 +#: ../../content/administration/maintain/domain_names.rst:166 +#: ../../content/administration/maintain/domain_names.rst:236 +#: ../../content/administration/maintain/supported_versions.rst:31 +#: ../../content/administration/upgrade/odoo_online.rst:3 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/install/install.rst:61 +msgid "" +"Trivial to start with, fully managed and migrated by Odoo S.A., `Odoo " +"Online`_ provides private instances and starts out free. It can be used to " +"discover and test Odoo and do non-code customizations (i.e. incompatible " +"with custom modules or the Odoo Apps Store) without having to install it " +"locally." +msgstr "" + +#: ../../content/administration/install/install.rst:66 +msgid "Can be used for both testing Odoo and long-term production use." +msgstr "" + +#: ../../content/administration/install/install.rst:68 +msgid "" +"Like demo_ instances, `Odoo Online`_ instances require no local " +"installation, a web browser is sufficient." +msgstr "" + +#: ../../content/administration/install/install.rst:75 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/install/install.rst:77 +msgid "" +"Odoo provides packaged installers for Windows, deb-based distributions " +"(Debian, Ubuntu, …) and RPM-based distributions (Fedora, CentOS, RHEL, …) " +"for both the Community and Enterprise versions." +msgstr "" + +#: ../../content/administration/install/install.rst:81 +msgid "" +"These packages automatically set up all dependencies (for the Community " +"version), but may be difficult to keep up-to-date." +msgstr "" + +#: ../../content/administration/install/install.rst:84 +msgid "" +"Official Community packages with all relevant dependency requirements are " +"available on our nightly_ server. Both Communtiy and Enterprise packages can" +" be downloaded from our download_ page (you must to be logged in as a paying" +" customer or partner to download the Enterprise packages)." +msgstr "" + +#: ../../content/administration/install/install.rst:90 +#: ../../content/administration/install/install.rst:255 +msgid "Windows" +msgstr "" + +#: ../../content/administration/install/install.rst:92 +msgid "" +"Download the installer from our nightly_ server (Community only) or the " +"Windows installer from the download_ page (any edition)." +msgstr "" + +#: ../../content/administration/install/install.rst:94 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/install/install.rst:0 +msgid "" +"On Windows 8 and later you may see a warning titled \"Windows protected your" +" PC\"." +msgstr "" + +#: ../../content/administration/install/install.rst:0 +msgid "Click on **More Info** and then on **Run anyway**." +msgstr "" + +#: ../../content/administration/install/install.rst:99 +msgid "Accept the UAC_ prompt." +msgstr "" + +#: ../../content/administration/install/install.rst:100 +msgid "Go through the various installation steps." +msgstr "" + +#: ../../content/administration/install/install.rst:102 +msgid "Odoo will automatically be started at the end of the installation." +msgstr "" + +#: ../../content/administration/install/install.rst:105 +#: ../../content/administration/install/install.rst:447 +msgid "Linux" +msgstr "" + +#: ../../content/administration/install/install.rst:108 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/install/install.rst:110 +msgid "" +"Odoo 15 'deb' package currently supports `Debian 11 (Bullseye)`_, `Ubuntu " +"20.04 (Focal)`_ or above." +msgstr "" + +#: ../../content/administration/install/install.rst:114 +#: ../../content/administration/install/install.rst:187 +#: ../../content/administration/install/install.rst:314 +#: ../../content/administration/install/install.rst:506 +#: ../../content/administration/install/install.rst:703 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/install/install.rst:116 +msgid "" +"Odoo needs a `PostgreSQL`_ server to run properly. The default configuration" +" for the Odoo 'deb' package is to use the PostgreSQL server on the same host" +" as your Odoo instance. Execute the following command in order to install " +"the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/install/install.rst:124 +#: ../../content/administration/install/install.rst:200 +#: ../../content/administration/install/install.rst:381 +#: ../../content/administration/install/install.rst:580 +#: ../../content/administration/install/install.rst:775 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in version `0.12.5 `_ for it to " +"support headers and footers. See our `wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/install/install.rst:130 +#: ../../content/administration/install/install.rst:206 +msgid "Repository" +msgstr "" + +#: ../../content/administration/install/install.rst:132 +msgid "" +"Odoo S.A. provides a repository that can be used with Debian and Ubuntu " +"distributions. It can be used to install *Odoo Community Edition* by " +"executing the following commands **as root**:" +msgstr "" + +#: ../../content/administration/install/install.rst:141 +msgid "" +"You can then use the usual `apt-get upgrade` command to keep your " +"installation up-to-date." +msgstr "" + +#: ../../content/administration/install/install.rst:143 +msgid "" +"At this moment, there is no nightly repository for the Enterprise Edition." +msgstr "" + +#: ../../content/administration/install/install.rst:146 +msgid "Deb Package" +msgstr "" + +#: ../../content/administration/install/install.rst:148 +msgid "" +"Instead of using the repository as described above, the 'deb' packages for " +"both the *Community* and *Enterprise* editions can be downloaded from the " +"`official download page `_." +msgstr "" + +#: ../../content/administration/install/install.rst:151 +msgid "Next, execute the following commands **as root**:" +msgstr "" + +#: ../../content/administration/install/install.rst:159 +msgid "" +"This will install Odoo as a service, create the necessary PostgreSQL_ user " +"and automatically start the server." +msgstr "" + +#: ../../content/administration/install/install.rst:162 +msgid "" +"The `python3-xlwt` Debian package does not exists in Debian Buster nor " +"Ubuntu 18.04. This python module is needed to export into xls format." +msgstr "" + +#: ../../content/administration/install/install.rst:165 +msgid "If you need the feature, you can install it manually with:" +msgstr "" + +#: ../../content/administration/install/install.rst:171 +msgid "" +"The `num2words` python package does not exists in Debian Buster nor Ubuntu " +"18.04. Textual amounts will not be rendered by Odoo and this could cause " +"problems with the `l10n_mx_edi` module." +msgstr "" + +#: ../../content/administration/install/install.rst:175 +msgid "If you need this feature, you can install manually with:" +msgstr "" + +#: ../../content/administration/install/install.rst:182 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/install/install.rst:184 +msgid "Odoo 15 'rpm' package supports Fedora 34." +msgstr "" + +#: ../../content/administration/install/install.rst:189 +msgid "" +"Odoo needs a `PostgreSQL`_ server to run properly. Make sure that the `sudo`" +" command is available and well configured and, only then, execute the " +"following command in order to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/install/install.rst:208 +msgid "" +"Odoo S.A. provides a repository that can be used with the Fedora " +"distributions. It can be used to install *Odoo Community Edition* by " +"executing the following commands:" +msgstr "" + +#: ../../content/administration/install/install.rst:220 +msgid "RPM package" +msgstr "" + +#: ../../content/administration/install/install.rst:222 +msgid "" +"Instead of using the repository as described above, the 'rpm' packages for " +"both the *Community* and *Enterprise* editions can be downloaded from the " +"`official download page `_." +msgstr "" + +#: ../../content/administration/install/install.rst:225 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/install/install.rst:237 +msgid "Source Install" +msgstr "" + +#: ../../content/administration/install/install.rst:239 +msgid "" +"The source \"installation\" is really about not installing Odoo, and running" +" it directly from source instead." +msgstr "" + +#: ../../content/administration/install/install.rst:242 +msgid "" +"It can be more convenient for module developers as the Odoo source is more " +"easily accessible than using packaged installation." +msgstr "" + +#: ../../content/administration/install/install.rst:245 +msgid "" +"It also makes starting and stopping Odoo more flexible and explicit than the" +" services set up by the packaged installations, and allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/install/install.rst:249 +msgid "" +"Finally it provides greater control over the system's set up, and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/install/install.rst:258 +#: ../../content/administration/install/install.rst:450 +#: ../../content/administration/install/install.rst:647 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/install/install.rst:260 +#: ../../content/administration/install/install.rst:452 +#: ../../content/administration/install/install.rst:649 +msgid "" +"There are two ways to obtain the source code of Odoo: as a zip **archive** " +"or through **git**." +msgstr "" + +#: ../../content/administration/install/install.rst:263 +#: ../../content/administration/install/install.rst:455 +#: ../../content/administration/install/install.rst:652 +msgid "Archive" +msgstr "" + +#: ../../content/administration/install/install.rst:265 +#: ../../content/administration/install/install.rst:457 +#: ../../content/administration/install/install.rst:654 +msgid "Community Edition:" +msgstr "" + +#: ../../content/administration/install/install.rst:267 +#: ../../content/administration/install/install.rst:273 +#: ../../content/administration/install/install.rst:459 +#: ../../content/administration/install/install.rst:465 +#: ../../content/administration/install/install.rst:656 +#: ../../content/administration/install/install.rst:662 +msgid "`Official download page `_" +msgstr "" + +#: ../../content/administration/install/install.rst:268 +#: ../../content/administration/install/install.rst:460 +#: ../../content/administration/install/install.rst:657 +msgid "`GitHub repository `_" +msgstr "" + +#: ../../content/administration/install/install.rst:269 +#: ../../content/administration/install/install.rst:461 +#: ../../content/administration/install/install.rst:658 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/install/install.rst:271 +#: ../../content/administration/install/install.rst:463 +#: ../../content/administration/install/install.rst:660 +msgid "Enterprise Edition:" +msgstr "" + +#: ../../content/administration/install/install.rst:274 +#: ../../content/administration/install/install.rst:466 +#: ../../content/administration/install/install.rst:663 +msgid "`GitHub repository `_" +msgstr "" + +#: ../../content/administration/install/install.rst:279 +#: ../../content/administration/install/install.rst:471 +#: ../../content/administration/install/install.rst:668 +msgid "Git" +msgstr "" + +#: ../../content/administration/install/install.rst:281 +#: ../../content/administration/install/install.rst:473 +#: ../../content/administration/install/install.rst:670 +msgid "" +"The following requires `Git `_ to be installed on your machine and " +"that you have basic knowledge of Git commands. To clone a Git repository, " +"you must choose between cloning with HTTPS or SSH. If you do not know the " +"difference between the two, the best option is most likely HTTPS. If you are" +" following the :doc:`Getting started `" +" developer tutorial, or plan on contributing to Odoo source code, choose " +"SSH." +msgstr "" + +#: ../../content/administration/install/install.rst:288 +#: ../../content/administration/install/install.rst:480 +#: ../../content/administration/install/install.rst:677 +msgid "" +"**The Enterprise Git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community version. Running the Enterprise version actually means " +"running the server from the Community version with the addons-path option " +"set to the folder with the Enterprise version. You need to clone both the " +"Community and Enterprise repository to have a working Odoo Enterprise " +"installation. See :ref:`setup/install/editions` to get access to the " +"Enterprise repository." +msgstr "" + +#: ../../content/administration/install/install.rst:297 +#: ../../content/administration/install/install.rst:489 +#: ../../content/administration/install/install.rst:686 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/install/install.rst:304 +#: ../../content/administration/install/install.rst:496 +#: ../../content/administration/install/install.rst:693 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/install/install.rst:317 +#: ../../content/administration/install/install.rst:509 +#: ../../content/administration/install/install.rst:706 +msgid "Python" +msgstr "" + +#: ../../content/administration/install/install.rst:319 +msgid "" +"Odoo requires Python 3.7 or later to run. Visit `Python's download page " +"`_ to download and install the " +"latest version of Python 3 on your machine." +msgstr "" + +#: ../../content/administration/install/install.rst:322 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/install/install.rst:325 +#: ../../content/administration/install/install.rst:514 +#: ../../content/administration/install/install.rst:711 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.7 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/install/install.rst:332 +#: ../../content/administration/install/install.rst:521 +#: ../../content/administration/install/install.rst:718 +msgid "Verify also that pip_ is installed for this version." +msgstr "" + +#: ../../content/administration/install/install.rst:341 +msgid "" +"Odoo uses PostgreSQL as database management system. `Download and install " +"PostgreSQL `_ (supported " +"version: 10.0 and later)." +msgstr "" + +#: ../../content/administration/install/install.rst:344 +#: ../../content/administration/install/install.rst:539 +#: ../../content/administration/install/install.rst:735 +msgid "" +"By default, the only user is `postgres` but Odoo forbids connecting as " +"`postgres`, so you need to create a new PostgreSQL user:" +msgstr "" + +#: ../../content/administration/install/install.rst:347 +msgid "" +"Add PostgreSQL's `bin` directory (by default: `C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to your `PATH`." +msgstr "" + +#: ../../content/administration/install/install.rst:349 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/install/install.rst:351 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/install/install.rst:352 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/install/install.rst:353 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/install/install.rst:354 +msgid "Enter the username in the **Role Name** field (e.g. `odoo`)." +msgstr "" + +#: ../../content/administration/install/install.rst:355 +msgid "" +"Open the **Definition** tab and enter the password (e.g. ``odoo``), then " +"click **Save**." +msgstr "" + +#: ../../content/administration/install/install.rst:356 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/install/install.rst:360 +#: ../../content/administration/install/install.rst:551 +#: ../../content/administration/install/install.rst:747 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/install/install.rst:362 +msgid "" +"Before installing the dependencies, you must download and install the `Build" +" Tools for Visual Studio " +"`_. When prompted, select **C++ build tools** in the " +"**Workloads** tab and install them." +msgstr "" + +#: ../../content/administration/install/install.rst:366 +#: ../../content/administration/install/install.rst:565 +#: ../../content/administration/install/install.rst:749 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo community directory." +msgstr "" + +#: ../../content/administration/install/install.rst:369 +#: ../../content/administration/install/install.rst:568 +#: ../../content/administration/install/install.rst:752 +msgid "" +"It can be preferable to not mix python modules packages between different " +"instances of Odoo or with your system. You can use virtualenv_ to create " +"isolated Python environments." +msgstr "" + +#: ../../content/administration/install/install.rst:372 +msgid "" +"Navigate to the path of your Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/install/install.rst:386 +#: ../../content/administration/install/install.rst:585 +#: ../../content/administration/install/install.rst:780 +msgid "" +"For languages with right-to-left interface (such as Arabic or Hebrew), the " +"package `rtlcss` is needed:" +msgstr "" + +#: ../../content/administration/install/install.rst:389 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/install/install.rst:390 +#: ../../content/administration/install/install.rst:589 +#: ../../content/administration/install/install.rst:784 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/install/install.rst:396 +msgid "" +"Edit the System Environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +"`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/install/install.rst:402 +#: ../../content/administration/install/install.rst:598 +#: ../../content/administration/install/install.rst:793 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/install/install.rst:404 +#: ../../content/administration/install/install.rst:600 +#: ../../content/administration/install/install.rst:795 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/install/install.rst:407 +#: ../../content/administration/install/install.rst:603 +#: ../../content/administration/install/install.rst:798 +msgid "" +"To configure the server, you can either specify :ref:`command-line arguments" +" ` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/install/install.rst:410 +#: ../../content/administration/install/install.rst:606 +#: ../../content/administration/install/install.rst:801 +msgid "" +"For the Enterprise edition, you must add the path to the `enterprise` addons" +" to the `addons-path` argument. Note that it must come before the other " +"paths in `addons-path` for addons to be loaded correctly." +msgstr "" + +#: ../../content/administration/install/install.rst:414 +#: ../../content/administration/install/install.rst:610 +#: ../../content/administration/install/install.rst:805 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/install/install.rst:416 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/install/install.rst:417 +#: ../../content/administration/install/install.rst:615 +#: ../../content/administration/install/install.rst:810 +msgid "Custom addon paths beyond the defaults, to load your own modules." +msgstr "" + +#: ../../content/administration/install/install.rst:419 +#: ../../content/administration/install/install.rst:617 +#: ../../content/administration/install/install.rst:812 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/install/install.rst:426 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/install/install.rst:430 +#: ../../content/administration/install/install.rst:627 +#: ../../content/administration/install/install.rst:827 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in your web browser and log" +" in with the base administrator account: Use `admin` for the " +":guilabel:`Email` and, again, `admin` for the :guilabel:`Password`. That's " +"it, you just logged into your own Odoo database!" +msgstr "" + +#: ../../content/administration/install/install.rst:436 +#: ../../content/administration/install/install.rst:633 +#: ../../content/administration/install/install.rst:833 +msgid "" +"From there, you can create and manage new :doc:`users " +"`." +msgstr "" + +#: ../../content/administration/install/install.rst:438 +#: ../../content/administration/install/install.rst:635 +#: ../../content/administration/install/install.rst:835 +msgid "" +"The user account you use to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/install/install.rst:442 +#: ../../content/administration/install/install.rst:639 +#: ../../content/administration/install/install.rst:839 +msgid "" +":doc:`The exhaustive list of CLI arguments for odoo-bin " +"`." +msgstr "" + +#: ../../content/administration/install/install.rst:511 +msgid "" +"Odoo requires Python 3.7 or later to run. Use your package manager to " +"download and install Python 3 on your machine if it is not already done." +msgstr "" + +#: ../../content/administration/install/install.rst:530 +msgid "" +"Odoo uses PostgreSQL as database management system. Use your package manager" +" to download and install PostgreSQL (supported version: 10.0 and later)." +msgstr "" + +#: ../../content/administration/install/install.rst:533 +msgid "On Debian/Unbuntu, it can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/install/install.rst:547 +#: ../../content/administration/install/install.rst:743 +msgid "" +"Because your PostgreSQL user has the same name as your Unix login, you will " +"be able to connect to the database without password." +msgstr "" + +#: ../../content/administration/install/install.rst:553 +msgid "" +"For libraries using native code, it is necessary to install development " +"tools and native dependencies before the Python dependencies of Odoo. They " +"are available in `-dev` or `-devel` packages for Python, PostgreSQL, " +"libxml2, libxslt1, libevent, libsasl2 and libldap2." +msgstr "" + +#: ../../content/administration/install/install.rst:557 +msgid "" +"On Debian/Unbuntu, the following command should install all the required " +"libraries:" +msgstr "" + +#: ../../content/administration/install/install.rst:571 +#: ../../content/administration/install/install.rst:755 +msgid "" +"Navigate to the path of your Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/install/install.rst:588 +msgid "Download and install **nodejs** and **npm** with your package manager." +msgstr "" + +#: ../../content/administration/install/install.rst:612 +#: ../../content/administration/install/install.rst:807 +msgid "" +"PostgreSQL user and password. Odoo has no defaults beyond `psycopg2's " +"defaults `_: connects over a UNIX" +" socket on port `5432` with the current user and no password." +msgstr "" + +#: ../../content/administration/install/install.rst:624 +#: ../../content/administration/install/install.rst:819 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/install/install.rst:644 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/install/install.rst:708 +msgid "" +"Odoo requires Python 3.7 or later to run. Use your preferred package manager" +" (homebrew_, macports_) to download and install Python 3 on your machine if " +"it is not already done." +msgstr "" + +#: ../../content/administration/install/install.rst:727 +msgid "" +"Odoo uses PostgreSQL as database management system. Use `postgres.app " +"`_ to download and install PostgreSQL (supported " +"version: 10.0 and later)." +msgstr "" + +#: ../../content/administration/install/install.rst:731 +msgid "" +"To make the command line tools bundled with `postgres.app` available, make " +"sure to setup your `$PATH` variable by following the `Postgres.app CLI Tools" +" Instructions `_." +msgstr "" + +#: ../../content/administration/install/install.rst:764 +msgid "Non-Python dependencies need to be installed with a package manager:" +msgstr "" + +#: ../../content/administration/install/install.rst:766 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/install/install.rst:772 +msgid "" +"Download and install the package manager of your choice (homebrew_, " +"macports_)." +msgstr "" + +#: ../../content/administration/install/install.rst:773 +msgid "Install non-python dependencies." +msgstr "" + +#: ../../content/administration/install/install.rst:783 +msgid "" +"Download and install **nodejs** with your preferred package manager " +"(homebrew_, macports_)." +msgstr "" + +#: ../../content/administration/install/install.rst:823 +msgid "" +"Some versions of python on Mac might lead to the following error message: " +"`current limit exceeds maximum limit`. In that case, add the following " +"parameter `--limit-memory-hard 0` to avoid the problem." +msgstr "" + +#: ../../content/administration/install/install.rst:844 +#: ../../content/administration/maintain/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/install/install.rst:846 +msgid "" +"The full documentation on how to use Odoo with Docker can be found on the " +"official Odoo `docker image `_ page." +msgstr "" + +#: ../../content/administration/maintain.rst:5 +msgid "Maintain" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:3 +msgid "Connect Microsoft Outlook 365 to Odoo using Azure OAuth" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:5 +msgid "" +"Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order " +"to send and receive secure emails from a custom domain, all that is required" +" is to configure a few settings on the Azure platform and on the back end of" +" the Odoo database. This configuration works with either a personal email " +"address or an address created by a custom domain." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:11 +msgid "" +"`Microsoft Learn: Register an application with the Microsoft identity " +"platform `_" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:15 +msgid ":doc:`/applications/general/auth/azure`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:16 +msgid ":doc:`/applications/productivity/calendar/outlook`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:19 +msgid "Setup in Microsoft Azure Portal" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:22 +msgid "Create a new application" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:24 +msgid "" +"To get started, go to `Microsoft's Azure Portal " +"`_. Log in with the :guilabel:`Microsoft Outlook " +"Office 365` account if there is one, otherwise log in with the personal " +":guilabel:`Microsoft account`. A user with administrative access to the " +"Azure Settings will need to connect and perform the following configuration." +" Next, navigate to the section labeled :guilabel:`Manage Azure Active " +"Directory`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:30 +msgid "" +"Now, click on :guilabel:`Add (+)`, located in the top menu, and then select " +":guilabel:`App registration`. On the :guilabel:`Register an application` " +"screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. " +"Under the :guilabel:`Supported account types` section select " +":guilabel:`Accounts in any organizational directory (Any Azure AD directory " +"- Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:36 +msgid "" +"Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the " +"platform, and then input `https:///microsoft_outlook/confirm`" +" in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at " +"which your Odoo instance can be reached in the URL field." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:41 +msgid "" +"*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the " +"database's subdomain, assuming it's hosted on Odoo.com" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:44 +msgid "" +"After the URL has been added to the field, :guilabel:`Register` the " +"application so it is created." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:47 +msgid "API permissions" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:49 +msgid "" +"The :guilabel:`API permissions` should be set next. Odoo will need specific " +"API permissions to be able to read (IMAP) and send (SMTP) emails in the " +"Microsoft 365 setup. First, click the :guilabel:`API permissions` link, " +"located in the left menu bar. Next, click on the :guilabel:`(+) Add a " +"Permission` button and select :guilabel:`Microsoft Graph` under " +":guilabel:`Commonly Used Microsoft APIs`. After, select the " +":guilabel:`Delegated Permissions` option." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:55 +msgid "" +"In the search bar, search for the following :guilabel:`Deregulated " +"permissions` and click :guilabel:`Add permissions` for each one:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:58 +msgid ":guilabel:`SMTP.Send`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:59 +msgid ":guilabel:`IMAP.AccessAsUser.All`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:62 +msgid "The :guilabel:`User.Read` permission will be added by default." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "" +"API permissions needed for Odoo integration are listed under the Microsoft " +"Graph." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:69 +msgid "Assign users and groups" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:71 +msgid "" +"After adding the API permissions, navigate back to the :guilabel:`Overview` " +"of the :guilabel:`Application` in the top of the left sidebar menu." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:74 +msgid "" +"Now, add users to this application. Under the :guilabel:`Essentials` " +"overview table, click on the link labeled :guilabel:`Managed Application in " +"Local Directory`, or the last option on the bottom right-hand side of the " +"table." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "" +"Add users/groups by clicking the Managed application in local directory link for the\n" +"created application." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:83 +msgid "" +"In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click " +"on :guilabel:`(+) Add User/Group`. Depending on the account, either a " +":guilabel:`Group` and a :guilabel:`User` can be added, or only " +":guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` " +"to be added." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:88 +msgid "" +"Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None " +"Selected` and add the users or group of users that will be sending emails " +"from the :guilabel:`Microsoft account` in Odoo. :guilabel:`Add` the " +"users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to " +"the application." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:94 +msgid "Create credentials" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:96 +msgid "" +"Now that the Microsoft Azure app is set up, credentials need to be created " +"for the Odoo setup. These include the :guilabel:`Client ID` and " +":guilabel:`Client Secret`. To start, the :guilabel:`Client ID` can be copied" +" from the :guilabel:`Overview` page of the app. The :guilabel:`Client ID` or" +" :guilabel:`Application ID` is located under the :guilabel:`Display Name` in" +" the :guilabel:`Essentials` overview of the app." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Application/Client ID located in the Overview of the app." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:106 +msgid "" +"Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this" +" value, click on :guilabel:`Certificates & Secrets` in the left sidebar " +"menu. Then, a :guilabel:`Client Secret` needs to be produced. In order to do" +" this, click on the :guilabel:`(+) New Client Secret` button." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:110 +msgid "" +"A window on the right will populate with a button labeled :guilabel:`Add a " +"client secret`. Under :guilabel:`Description`, type in `Odoo Fetchmail` or " +"something recognizable, and then set the :guilabel:`expiration date`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:115 +msgid "" +"A new :guilabel:`Client Secret` will need to be produced and configured if " +"the first one expires. In this event, there could be an interruption of " +"service, so the expiration date should be noted and set to the furthest " +"possible date." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:119 +msgid "" +"Next, click on :guilabel:`Add` when these two values are entered. A " +":guilabel:`Client Secret Value` and :guilabel:`Secret ID` will be created. " +"It is important to copy the :guilabel:`Value` or :guilabel:`Client Secret " +"Value` into a notepad as it will become encrypted after leaving this page. " +"The :guilabel:`Secret ID` is not needed." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Client Secret Value or Value in the app's credentials." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:128 +msgid "" +"After these steps, the following items should be ready to be set up in Odoo:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:130 +msgid "A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:131 +msgid "A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:133 +msgid "" +"This completes the setup on the :guilabel:`Microsoft Azure Portal` side." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:136 +#: ../../content/administration/maintain/google_oauth.rst:111 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:139 +msgid "Enter Microsoft Outlook credentials" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:141 +msgid "" +"First, open the Odoo database and navigate to the :guilabel:`Apps` module. " +"Then, remove the :guilabel:`Apps` filter from the search bar and type in " +"`Outlook`. After that, install the module called :guilabel:`Microsoft " +"Outlook`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:145 +msgid "" +"Next, navigate to :menuselection:`Settings --> General Settings`, and under " +"the :guilabel:`Discuss` section, ensure that the checkbox for " +":guilabel:`Custom Email Servers` is checked. This populates a new option for" +" :guilabel:`Outlook Credentials`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:149 +msgid ":guilabel:`Save` the progress." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:151 +msgid "" +"Then, copy and paste the :guilabel:`Client ID` (Application ID) and " +":guilabel:`Client Secret (Client Secret Value)` into the respective fields " +"and :guilabel:`Save` the settings." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Outlook Credentials in Odoo General Settings." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:159 +#: ../../content/administration/maintain/google_oauth.rst:127 +msgid "Configure outgoing email server" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:161 +msgid "" +"On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email " +"Servers` setting, click the :guilabel:`Outgoing Email Servers` link to " +"configure the Microsoft account." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:164 +msgid "" +"Then, create a new email server and check the box for :guilabel:`Outlook`. " +"Next, fill in the :guilabel:`Name` (it can be anything) and the Microsoft " +"Outlook email :guilabel:`Username`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:167 +msgid "" +"If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain " +"or email address `." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:170 +msgid "Then, click on :guilabel:`Connect your Outlook account`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:172 +msgid "" +"A new window from Microsoft opens to complete the :guilabel:`authorization " +"process`. Select the appropriate email address that is being configured in " +"Odoo." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Permission page to grant access between newly created app and Odoo." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:179 +msgid "" +"Then, allow Odoo to access the Microsoft account by clicking on " +":guilabel:`Yes`. After this, the page will navigate back to the newly " +"configured :guilabel:`Outgoing Mail Server` in Odoo. The configuration " +"automatically loads the :guilabel:`token` in Odoo, and a tag stating " +":guilabel:`Outlook Token Valid` appears in green." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Valid Outlook Token indicator." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:188 +msgid "" +"Finally, click :guilabel:`Test Connection`. A confirmation message should " +"appear. The Odoo database can now send safe, secure emails through Microsoft" +" Outlook using OAuth authentication." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:192 +msgid "Multiple user configuration" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:194 +msgid "" +"Each user should have a separate server set up. The :guilabel:`from-filter` " +"should be set so that only the user's email is sent from that server. In " +"other words, only a user with an email address that matches the set " +":guilabel:`from-filter` is able to use this server." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:198 +msgid "" +"After setting the :guilabel:`from-filter`, set up a fallback email account " +"to allow for the sending of :guilabel:`notifications`. The fallback email " +"must be configured as a :guilabel:`general transactional server`. The " +":guilabel:`mail.default.from` system parameter must be set to the " +":guilabel:`username` of the general transactional server account. For more " +"information see :ref:`Use a default email address " +"`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:205 +#: ../../content/administration/maintain/mailjet_api.rst:213 +msgid "" +"The :guilabel:`System Parameters` can be accessed by activating " +":doc:`../../applications/general/developer_mode` in the " +":menuselection:`Settings --> Technical --> Parameters --> System Parameters`" +" menu." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:210 +msgid "Configure incoming email server" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:212 +msgid "" +"The incoming account should be configured in a similar way to the outgoing " +"email account. Navigate to the :guilabel:`Incoming Mail Servers` in the " +":guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check" +" or Select the button next to :guilabel:`Outlook Oauth Authentication` and " +"enter the :guilabel:`Microsoft Outlook username`. Click on " +":guilabel:`Connect your Outlook account`. Odoo will state: " +":guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the " +"account. The account should be ready to receive email to the Odoo database." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:220 +msgid ":doc:`../../applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:3 +#: ../../content/administration/maintain/odoo_online.rst:70 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:5 +msgid "" +"A **domain name** works as an address for your website. It makes the " +"Internet much more accessible as it allows users to type a meaningful web " +"address, such as ``www.odoo.com``, rather than its server's IP address with " +"a series of numbers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:9 +msgid "" +"You can use a custom domain name to access your Odoo database and websites:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:11 +msgid "" +"By :ref:`registering a free domain name with Odoo ` (for Odoo Online databases)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:13 +msgid "" +"By :ref:`configuring a custom domain that you already own `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:16 +msgid "" +"Odoo Online and Odoo.sh databases, including their websites, use by default " +"a subdomain of ``odoo.com`` for both the URL and the emails (e.g., " +"``https://example.odoo.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:20 +msgid "" +"Odoo offers a :ref:`free custom domain name ` to " +"all Odoo Online databases for one year. Visitors can then access your " +"website with an address such as ``www.example.com`` rather than the default " +"``example.odoo.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:25 +msgid "" +"`Odoo Tutorials: Register a Free Domain Name " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:27 +msgid "" +"`Odoo Quick Tips: Get a free domain name! " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:32 +msgid "About domain names" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:34 +msgid "" +"Having a **good domain name** is as important to your branding as the name " +"of your business or organization as it is the first thing your visitors will" +" notice. We recommend you keep them *simple, short, easy to remember and " +"spell*." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:38 +msgid "" +"A **subdomain** is a domain that is a part of another domain. It often " +"refers to the additional part that comes before the main domain name. " +"Traditionally, most websites use the ``www.`` subdomain, but any string of " +"letters can be used as well. You can use subdomains to direct your visitors " +"to other websites than your main website or to specific pages (e.g., " +"``experience.odoo.com`` points to a specific page.)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:44 +msgid "" +"All domain names are referenced in the **Domain Name System**, or **DNS**, " +"which works as a giant directory for the Internet. There are many DNS " +"servers, so any modification to the DNS can take up to 72 hours to propagate" +" worldwide on all servers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:51 +msgid "Indexing of domain names by search engines" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:53 +msgid "" +"Search engines, such as Google and Bing, rely on web crawlers (:dfn:`robots " +"that explore and analyze the web`) to index all websites and their related " +"domain names. These crawlers discover new URLs thanks to links on known web " +"pages. As a result, search engines should index domain names automatically " +"after a while, as long as their URLs are mentioned elsewhere on the " +"Internet." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:58 +msgid "" +"Improving the appearance and positioning of web pages on search engines is a" +" practice named \"Search Engine Optimization\" (SEO)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:62 +msgid "" +"Adding relevant content, optimizing metadata, and building high-quality " +"backlinks can all help improve a website's search engine visibility." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:65 +msgid "" +"Some search engines provide tools for web admins, such as `Google Search " +"Console `_ and `Bing Webmaster " +"Tools `_, to help you analyze and improve " +"your page ranking. To use these services, you must prove that you are the " +"owner of your domain name. One way to verify the ownership of your domain " +"name is by adding a DNS record. You can do this for :ref:`domain names " +"registered with Odoo ` and for domain names managed" +" by other providers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:74 +msgid ":doc:`/applications/websites/website/pages/seo`" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:75 +msgid "" +"`Google Search Console Help - Verify your site ownership " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:76 +msgid "" +"`Bing Webmaster Tools - Add and Verify site " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:81 +msgid "Register a free domain name with Odoo" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:83 +msgid "" +"You can register a domain name for your Odoo Online database directly from " +"Odoo Website or your database manager." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:87 +msgid "" +"Your domain name is **free for one year** if you register it with Odoo!" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:88 +msgid "" +"The domain name is registered with `Gandi `_, the " +"domain name registrar." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:90 +msgid "" +"You are the owner of the domain name and can use it for other purposes." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:91 +msgid "Odoo manages payment and technical support for you." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:92 +msgid "" +"This offer doesn't include any mailbox. However, you can :ref:`configure " +"your MX records ` to use your own email server or " +"solution such as Google Workspace." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:95 +msgid "" +"To do so, go to :menuselection:`Website --> Go to website --> Promote --> " +"Domain Name`. Alternatively, open your `database manager " +"`_, click on the :guilabel:`settings` " +"button next to your database, then on :guilabel:`Domain names`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "Clicking on Domain Names from an Odoo website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:103 +msgid "" +"Search for the domain name of your choice to check its availability, then " +"select the one you want to register for your website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "" +"The search of the domain name example.com shows which associated domains are" +" available." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:110 +msgid "" +"Next, fill in the form with your information to become the domain name " +"owner." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:112 +msgid "" +"Your domain name is directly linked to your database, but you still have to " +":ref:`map your domain name with your website `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:116 +msgid "" +"Free domain names are also available for free Odoo Online databases (if you " +"installed one app only, for example). In this case, Odoo reviews your " +"request and your website to avoid abuse. This process may take up to three " +"days." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:119 +msgid "This is not available for Odoo.sh databases yet." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:124 +msgid "Manage your domain name registered with Odoo" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:126 +msgid "" +"To manage the DNS records of your domain name registered with Odoo or to " +"visualize the contacts associated with it, open your `database manager " +"`_, click on the :guilabel:`settings` " +"button next to your database, on :guilabel:`Domain names`, and then on " +":guilabel:`Contacts` or :guilabel:`DNS`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "Management of the domain names linked to an Odoo database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:136 +msgid "" +"Please `submit a support ticket `_ if you need " +"further assistance to manage your domain name." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:142 +msgid "Configure your existing domain name" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:144 +msgid "" +"If you already own a domain name, you can use it to point to your website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:146 +msgid "" +"To avoid any issue with the :ref:`SSL certificate validation `, we highly recommend that you proceed with the following actions " +"in this order:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:149 +msgid "" +":ref:`Add a CNAME record ` on your domain name's DNS " +"zone." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:150 +msgid "" +":ref:`Map your domain name with your Odoo database `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:151 +msgid "" +":ref:`Map your domain name with your Odoo website `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:156 +msgid "Add a CNAME record" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:158 +msgid "" +"A **CNAME record** is a type of DNS record that points to the domain of " +"another website rather than directly to an IP address." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:161 +msgid "" +"You need a CNAME record that points to your Odoo database. The requirements " +"are detailed in your database manager." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:168 +msgid "" +"The target address is the current address of your database, as defined at " +"its creation (e.g., ``example.odoo.com``)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:171 +#: ../../content/administration/maintain/domain_names.rst:250 +#: ../../content/administration/maintain/supported_versions.rst:32 +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/upgrade/odoo_sh.rst:3 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:173 +msgid "" +"Your project's main address is defined in :menuselection:`Settings --> " +"Project Name`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:175 +msgid "" +"If you want to target a specific branch (production, staging or " +"development), go to :menuselection:`Branches --> select your branch --> " +"Settings --> Custom domains`, and click on :guilabel:`How to set up my " +"domain?`. A message indicates which address your CNAME record should target." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:180 +#: ../../content/administration/maintain/domain_names.rst:222 +msgid "Open your domain name's manager dashboard." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:181 +msgid "" +"Open the **DNS zone** management page for the domain name you want to " +"configure." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:182 +msgid "Create a **CNAME record** pointing to the address of your database." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:184 +msgid "" +"While Odoo suggests creating a CNAME record for your ``www.`` subdomain " +"(``www.example.com``), you can of course use any domain name of your choice," +" with any subdomain (e.g., ``anything.example.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:189 +msgid "" +"You own the domain name ``example.com``, and you have an Odoo Online " +"database at the address ``example.odoo.com``. You want to access your Odoo " +"database primarily with the domain ``www.example.com`` but also with the " +":ref:`naked domain ` ``example.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:194 +msgid "" +"To do so, you create a CNAME record for the ``www`` subdomain, with " +"``example.odoo.com`` as the target. The DNS zone manager generates the " +"following rule and adds it to your DNS zone: ``www IN CNAME " +"example.odoo.com.``" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:198 +msgid "" +"You also create a redirection from ``example.com`` to ``wwww.example.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:200 +msgid "Your new DNS records are propagated to all DNS servers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:203 +msgid "Here are some specific guidelines to create a CNAME record:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:205 +msgid "`GoDaddy `_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:206 +msgid "" +"`Namecheap " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:207 +msgid "" +"`OVH " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:208 +msgid "" +"`CloudFlare `_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:209 +msgid "" +"`Google Domains `_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:214 +msgid "Naked domain" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:216 +msgid "" +"A **naked domain** is a domain name that doesn't have any subdomain at the " +"beginning of the address (e.g., ``odoo.com`` instead of ``www.odoo.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:219 +msgid "" +"You may want your naked domain to redirect to your website as some visitors " +"may not type the full domain name to access your website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:223 +msgid "" +"Create a **redirection** from the naked domain (``example.com``) to your " +"main domain name (``www.example.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:227 +msgid "" +"Depending on your domain name registrar, this redirection may be already " +"pre-configured." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:232 +msgid "Map your domain name with your Odoo database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:238 +msgid "" +"Open your `database manager `_, click on " +"the :guilabel:`settings` button next to your database, on :guilabel:`Domain " +"names`, and then on :guilabel:`Use my own domain` at the bottom of the right" +" column." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:242 +msgid "" +"Type the domain name you want to add to this database, then click on " +":guilabel:`Verify` to check if the CNAME record is correctly configured. " +"Once done, click on :guilabel:`I confirm, it's done`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:0 +msgid "" +"Verification of the CNAME records of a domain name before mapping it with a " +"database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:252 +msgid "" +"Go to :menuselection:`Branches --> select your branch --> Settings --> " +"Custom domains`, type the domain name you want to add to this database, then" +" click on :guilabel:`Add domain`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:0 +msgid "Mapping a domain name with an Odoo.sh branch" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:260 +msgid "" +":ref:`Odoo.sh branches: settings tab `" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:263 +msgid "" +"Make sure to :ref:`add a CNAME record ` to your domain " +"name's DNS **before** mapping your domain name with your Odoo database." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:266 +msgid "" +"Failing to do so may impede the validation of the :ref:`SSL certificate " +"` and would result in a *certificate name mismatch* error. " +"This is often displayed by web browsers as a warning such as *\"Your " +"connection is not private\"*." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:270 +msgid "" +"If this is the case and you have added the domain name to your database's " +"settings less than five days ago, wait 24 hours as the validation may still " +"happen. Otherwise, please `submit a support ticket " +"`_ including screenshots of your CNAME records." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:277 +msgid "SSL encryption (HTTPS protocol)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:279 +msgid "" +"**SSL encryption** is an encryption-based Internet security protocol. It " +"allows your visitors to navigate your website through a secure connection, " +"which appears as an ``https://`` protocol at the beginning of your web " +"address, rather than a non-secure ``http://`` protocol." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:283 +msgid "" +"Odoo generates a separate SSL certificate for each domain :ref:`mapped in " +"the database manager `, using integration with `Let's " +"Encrypt Certificate Authority and ACME protocol " +"`_." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:288 +msgid "The certificate generation may take up to 24h." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:289 +msgid "" +"Several attempts to validate your certificate are made during the five days " +"following the moment you add your domain name in your database's settings." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:291 +msgid "" +"If you already use another service, you can keep using it or simply change " +"for Odoo." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:296 +msgid "Web base URL of a database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:299 +msgid "" +"If you have Odoo Website, you can disregard this part and directly :ref:`map" +" your domain name with your website `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:302 +msgid "" +"The **web base URL** of a database, or **root URL** affects your main " +"website address and all the links sent to your customers (e.g., quotations, " +"portal links, etc.)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:305 +msgid "" +"To configure it, access your Odoo database with your custom address, then " +"log in as an administrator of your database (any user in the *Settings* " +"group) from the login screen." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:309 +msgid "" +"Connecting to your database with the original Odoo subdomain address (e.g., " +"``example.odoo.com`` also updates the web base URL of your database. See " +"below to prevent these automatic updates." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:312 +msgid "" +"Alternatively, you can do it manually. To do so, activate the " +":ref:`developer mode `, then go to :menuselection:`Settings " +"--> Technical --> System Parameters`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:315 +msgid "" +"Find the key called ``web.base.url`` (or create it if it does not exist) and" +" enter the full address of your website as value, such as " +"``https://www.example.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:319 +msgid "" +"The URL must include the protocol ``https://`` (or ``http://``) and must not" +" end with a slash (``/``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:322 +msgid "" +"To prevent the automatic update of the web base URL when an administrator " +"logs in the database, you can create the following System Parameter:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:325 +msgid "key: ``web.base.url.freeze``" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:326 +msgid "value: ``True``" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:331 +msgid "Map your domain name with your website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:333 +msgid "" +"Mapping your domain name to your website isn't the same as mapping it with " +"your database:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:335 +msgid "" +"It defines your domain name as the main one for your website, helping search" +" engines to index your website properly." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:337 +msgid "" +"It defines your domain name as the base URL for your database, including the" +" portal links sent by email to your customers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:339 +msgid "" +"If you have multiple websites, it maps your domain name with the appropriate" +" website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:341 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Settings --> Website " +"Info`. If you have multiple websites, select the one you want to configure." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:344 +msgid "" +"In the :guilabel:`Domain` field, fill in the web address of your website " +"(e.g., ``https://www.example.com``) and click on :guilabel:`Save`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "Configuring https://www.example.com as the Domain of the website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:352 +msgid "" +"Mapping your domain name with your Odoo website prevents Google from " +"indexing both your custom domain name ``www.example.com`` and your original " +"odoo database address ``example.odoo.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:355 +msgid "" +"If both addresses are already indexed, it may take some time before Google " +"removes the indexation of the second address. You may also try using the " +"`Google Search Console `_ to fix " +"this." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:360 +msgid "" +"If you have multiple websites and companies on your database, make sure that" +" you select the right :guilabel:`Company` in the website settings, next to " +"the :guilabel:`Domain` settings. Doing so indicates Odoo which URL to use as" +" the :ref:`base URL ` according to the company in " +"use." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:366 +msgid ":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:12 +#: ../../content/administration/maintain/enterprise.rst:31 +#: ../../content/administration/maintain/enterprise.rst:63 +#: ../../content/administration/maintain/enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:17 +#: ../../content/administration/maintain/enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":ref:`setup/install/source`)" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:3 +msgid "Connect Gmail to Odoo using Google OAuth" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:5 +msgid "" +"Odoo is compatible with Google's OAuth for Gmail. In order to send secure " +"emails from a custom domain, all that is required is to configure a few " +"settings on Google's *Workspace* platform, as well as on the back end of the" +" Odoo database. This configuration works by using either a personal email " +"address or an address created by a custom domain." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:11 +msgid "" +"For more information, visit `Google's documentation " +"`_ on setting up OAuth." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:15 +msgid ":doc:`/applications/general/auth/google`" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:16 +msgid ":doc:`/applications/productivity/calendar/google`" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:19 +msgid "Setup in Google" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:22 +msgid "Create a new project" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:24 +msgid "" +"To get started, go to the `Google API Console " +"`_. Log in with your *Google " +"Workspace* account if you have one, otherwise log in with your personal " +"Gmail account (this should match the email address you want to configure in " +"Odoo)." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:28 +msgid "" +"After that, click on :guilabel:`Create Project`, located on the far right of" +" the :guilabel:`OAuth consent screen`. If a project has already been created" +" in this account, then the :guilabel:`New Project` option will be located on" +" the top right under the :guilabel:`Select a project` drop-down menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:33 +msgid "" +"On the :menuselection:`New Project` screen, rename the :guilabel:`Project " +"name` to `Odoo` and browse for the :guilabel:`Location`. Set the " +":guilabel:`Location` as the *Google Workspace organization*. If you are " +"using a personal Gmail account, then leave the :guilabel:`Location` as " +":guilabel:`No Organization`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Project Name and Location for Google OAuth." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:42 +msgid "Click on :guilabel:`Create` to finish this step." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:45 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:47 +msgid "" +"If the page doesn't redirect to the :menuselection:`User Type` options, " +"click on :guilabel:`OAuth consent screen` in the left menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:50 +msgid "" +"Under :guilabel:`User Type` options, select the appropriate :guilabel:`User " +"Type`, and then click on :guilabel:`Create` again, which will finally " +"navigate to the :menuselection:`Edit app registration` page." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:55 +msgid "" +"*Personal* Gmail Accounts are only allowed to be **External** User Type, " +"which means Google may require an approval, or for *Scopes* to be added on. " +"However, using a *Google WorkSpace* account allows for **Internal** User " +"Type to be used." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:59 +msgid "" +"Note, as well, that while the API connection is in the *External* testing " +"mode, then no approval is necessary from Google. User limits in this testing" +" mode is set to 100 users." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:63 +msgid "Edit app registration" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:65 +msgid "Next we will configure the app registration of the project." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:67 +msgid "" +"On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App " +"information` section, enter `Odoo` in the :guilabel:`App name` field. Select" +" the organization's email address under the :guilabel:`User support` email " +"field." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:71 +msgid "" +"Next, under :menuselection:`App Domain --> Authorized domains`, click on " +":guilabel:`Add Domain` and enter `odoo.com`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:74 +msgid "" +"After that, under the :guilabel:`Developer contact information` section, " +"enter the organization's email address. Google uses this email address to " +"notify the organization about any changes to your project." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:78 +msgid "" +"Next, click on the :guilabel:`Save and Continue` button. Then, skip the " +":menuselection:`Scopes` page by scrolling to the bottom and clicking on " +":guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:81 +msgid "" +"If continuing in testing mode (External), add the email addresses being " +"configured under the :guilabel:`Test users` step, by clicking on " +":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " +"summary of the app registration appears." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:85 +msgid "" +"Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to " +"finish setting up the project." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:89 +msgid "Create Credentials" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:91 +msgid "" +"Now that the project is set up, credentials should be created, which " +"includes the *Client ID* and *Client Secret*. First, click on " +":guilabel:`Credentials` in the left sidebar menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:94 +msgid "" +"Then, click on :guilabel:`Create Credentials` in the top menu and select " +":guilabel:`OAuth client ID` from the dropdown menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:97 +msgid "" +"Under :guilabel:`Application Type`, select :guilabel:`Web Application` from " +"the dropdown menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:98 +msgid "In the :guilabel:`Name` field, enter `Odoo`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:99 +msgid "" +"Under the :guilabel:`Authorized redirect URIs` label, click the button " +":guilabel:`ADD URI`, and then input " +"`https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1`" +" field. Be sure to replace the *yourdbname* part of the URL with the actual " +"Odoo database name." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:102 +msgid "" +"Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID`" +" and :guilabel:`Client Secret`. Finally, copy each generated value for later" +" use when configuring in Odoo, and then navigate to the Odoo database." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Client ID and Client Secret for Google OAuth." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:114 +msgid "Enter Google Credentials" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:116 +msgid "" +"First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove " +"the :guilabel:`Apps` filter from the search bar and type in `Google`. " +"Install the module called :guilabel:`Google Gmail`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:120 +msgid "" +"Next, navigate to :menuselection:`Settings --> General Settings`, and under " +"the :guilabel:`Discuss` section, ensure that the checkbox for " +":guilabel:`Custom Email Servers` or :guilabel:`External Email Servers` is " +"checked. This populates a new option for :guilabel:`Gmail Credentials` or " +":guilabel:`Use a Gmail Sever`. Then, copy and paste the respective values " +"into the :guilabel:`Client ID` and :guilabel:`Client Secret` fields and " +":guilabel:`Save` the settings." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:129 +msgid "" +"To configure the external Gmail account, return to the top of the " +":guilabel:`Custom Email Servers` setting and then click the " +":guilabel:`Outgoing Email Servers` link." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Configure Outgoing Email Servers in Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:136 +msgid "" +"Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email " +"server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the " +"email :guilabel:`Username` (if required)." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:139 +msgid "" +"Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` " +"(under the :guilabel:`Authenticate with` or :guilabel:`Connection` section)." +" Finally, click on :guilabel:`Connect your Gmail Account`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:143 +msgid "" +"A new window labeled :guilabel:`Google` opens to complete the authorization " +"process. Select the appropriate email address that is being configured in " +"Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:146 +msgid "" +"If the email address is a personal account, then an extra step pops up, so " +"click :guilabel:`Continue` to allow the verification and connect the Gmail " +"account to Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:149 +msgid "" +"Then, allow Odoo to access the Google account by clicking on " +":guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates " +"back to the newly configured outgoing email server in Odoo. The " +"configuration automatically loads the token in Odoo, and a tag stating " +":guilabel:`Gmail Token Valid` appears in green." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:158 +msgid "" +"Finally, :guilabel:`Test the Connection`. A confirmation message should " +"appear. The Odoo database can now send safe, secure emails through Google " +"using OAuth authentication." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:162 +msgid "Google OAuth FAQ" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:165 +msgid "Production VS Testing Publishing Status" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:167 +msgid "" +"Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` " +"(instead of :guilabel:`Testing`) will display the following warning message:" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "OAuth is Limited to 100 Sensitive Scope Logins." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:174 +msgid "" +"To correct this warning, navigate to the `Google API Platform " +"`_. If the " +":guilabel:`Publishing status` is :guilabel:`In Production`, click " +":guilabel:`Back to Testing` to correct the issue." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:179 +msgid "No Test Users Added" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:181 +msgid "" +"If no test users are added to the OAuth consent screen, then a 403 access " +"denied error will populate." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "403 Access Denied Error." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:188 +msgid "" +"To correct this error, return to the :guilabel:`OAuth consent screen` under " +":guilabel:`APIs & Services` and add test user(s) to the app. Add the email " +"that you are configuring in Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:192 +msgid "Gmail Module not updated" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:194 +msgid "" +"If the *Google Gmail* module in Odoo has not been updated to the latest " +"version, then a :guilabel:`Forbidden` error message populates." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "" +"Forbidden you don't have the permission to access the requested resource." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:201 +msgid "" +"To correct this error, go to the :menuselection:`Apps` module and clear out " +"the search terms. Then, search for `Gmail` or `Google` and upgrade the " +":guilabel:`Google Gmail` module. Finally, click on the three dots on the " +"upper right of the module and select :guilabel:`Upgrade`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:206 +msgid "Application Type" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:208 +msgid "" +"When creating the credentials (OAuth *Client ID* and *Client Secret*), if " +":guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an" +" :guilabel:`Authorization Error` appears." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Error 400 Redirect URI Mismatch." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:215 +msgid "" +"To correct this error, delete the credentials already created and create new" +" credentials, selecting :guilabel:`Web Application` for the " +":guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect " +"URIs`, click :guilabel:`ADD URI` and type: " +"`https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure " +"to replace *yourdbname* in the URL with the Odoo database name." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:6 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:8 +msgid "" +"You may want to move your Odoo database from one hosting solution to " +"another. Depending on the platforms, you have to do it by yourself or " +"contact our support team first." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:12 +msgid "From on-premises to Odoo Online" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:14 +msgid "" +"Create a :ref:`duplicate ` of your database: in this " +"duplicate, uninstall all the **non-standard apps**." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:15 +msgid "" +"Grab a \"dump with filestore\" of your database by using the Database " +"Manager." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:16 +msgid "" +"**If you have time constraints, contact us earlier to schedule the " +"transfer.**" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:17 +msgid "" +"`Create a support ticket `_ and attach the dump " +"(if the file is too large, use any file transfer service and attach the link" +" to your ticket). Also include your subscription number and the URL you want" +" to use for your database (e.g.: my-company.odoo.com)." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:18 +#: ../../content/administration/maintain/hosting_changes.rst:66 +msgid "" +"We will make sure your database is compatible and upload it to our cloud. In" +" case of technical issues, we will get in touch with you." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:19 +msgid "It's done!" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:22 +#: ../../content/administration/maintain/hosting_changes.rst:71 +msgid "Odoo Online is not compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:23 +msgid "" +"The database you are moving to Odoo Online must be in a :doc:`supported " +"version `." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:27 +msgid "From on-premises to Odoo.sh" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:29 +#: ../../content/administration/maintain/hosting_changes.rst:46 +msgid "" +"Follow the :ref:`Import your database section of the Odoo.sh documentation " +"`." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:30 +msgid "...and voilà!" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:33 +msgid "From Odoo Online to on-premises" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:35 +#: ../../content/administration/maintain/hosting_changes.rst:43 +msgid "" +"Log into `your Odoo Online user portal " +"`_ and look for the version " +"number of your database." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:36 +msgid "" +"If your database does not run a :ref:`major version ` of" +" Odoo, you cannot host it on-premises yet, you have to upgrade it first to a" +" new major version. (*e.g.: If your database runs Odoo 12.3 which is not a " +"major version, you have to upgrade it first to Odoo 13.0 or 14.0.*)" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:37 +#: ../../content/administration/maintain/hosting_changes.rst:45 +msgid "" +"Download a backup of your database by clicking on the \"Gear\" icon next to " +"your database name then :menuselection:`Download` (if the download fails due" +" to your backup file being too large, contact `our support " +"`_)" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:38 +#: ../../content/administration/maintain/hosting_changes.rst:87 +msgid "Restore it from the database manager on your local server." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:41 +msgid "From Odoo Online to Odoo.sh" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:44 +msgid "" +"If your database does not run a :ref:`major version ` of" +" Odoo, you cannot host it on Odoo.sh yet, you have to upgrade it first to a " +"new major version. (*e.g.: If your database runs Odoo 12.3 which is not a " +"major version, you have to upgrade it first to Odoo 13.0 or 14.0.*)" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:49 +msgid "From Odoo.sh to Odoo Online" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:51 +msgid "Uninstall all the **non-standard apps**." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:52 +msgid "" +"`Create a support ticket `_ and include the " +"following:" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:54 +msgid "Your subscription number" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:55 +msgid "The URL you want to use for your database (e.g., `example.odoo.com`)" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:56 +msgid "Which branch you want to migrate" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:57 +msgid "In which region you want to be hosted:" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:59 +msgid "Americas" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:60 +msgid "Europe" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:61 +msgid "Asia" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:63 +msgid "Which user(s) will be the administrator(s)" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:64 +msgid "" +"When (and in which timezone) you want the database to be up and running" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:68 +msgid "All done!" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:72 +msgid "" +"Make sure to uninstall all the **non-standard apps** in a staging build " +"before doing it in your production build." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:76 +msgid "" +"Make sure you select the **region** that is closest to your users to reduce " +"latency." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:77 +msgid "The future **administrator(s)** must have an odoo.com account." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:78 +msgid "" +"The specific **date and time** at which you want the database to be up and " +"running are mainly helpful to organize the switch from the odoo.sh server to" +" the Odoo Online servers." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:80 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:81 +msgid "" +"**If you have time constraints, contact us earlier to schedule the " +"transfer**." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:84 +msgid "From Odoo.sh to on-premises" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:86 +msgid "" +"Grab a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:3 +msgid "Mailjet API" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:5 +msgid "" +"Odoo is compatible with Mailjet's :abbr:`API (Application Programming " +"Interface)` for mass mailing. Set up a dedicated mass mailing server through" +" Mailjet by configuring settings in the Mailjet account and the Odoo " +"database. In some circumstances, settings need to be configured on the " +"custom domain's :abbr:`DNS (Domain Name System)` settings as well." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:11 +msgid "Set up in Mailjet" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:14 +msgid "Create API credentials" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:16 +msgid "" +"To get started, sign in to the `Mailjet Account Information " +"`_ page. Next, navigate to the " +":guilabel:`Senders & Domains` section and click on :guilabel:`SMTP and SEND " +"API Settings`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "" +"SMTP and Send API Settings link in the Senders & Domains section of Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:24 +msgid "" +"Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration " +"settings onto a notepad. They can be found under the " +":guilabel:`Configuration (SMTP only)` section. The :abbr:`SMTP (Simple Mail " +"Transfer Protocol)` configuration settings include the server address, the " +"security option needed (Use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS " +"(Transport Layer Security)`), and the port number. The settings are needed " +"to configure Mailjet in Odoo, which is covered in the :ref:`last section " +"`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:32 +msgid "" +"`Mailjet: How can I configure my SMTP parameters? " +"`_" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:36 +msgid "" +"Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See " +"reference here `." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "SMTP configuration from Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:43 +msgid "" +"Next, click on the button labeled :guilabel:`Retrieve your API credentials` " +"to retrieve the Mailjet API credentials." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:46 +msgid "" +"Then, click on the eye icon to reveal the :guilabel:`API key`. Copy this key" +" to a notepad, as this serves as the :guilabel:`Username` in the Odoo " +"configuration. Next, click on the :guilabel:`Generate Secret Key` button to " +"generate the :guilabel:`Secret Key`. Copy this key to a notepad, as this " +"serves as the :guilabel:`Password` in the Odoo configuration." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:52 +msgid "Add verified sender address(es)" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:54 +msgid "" +"The next step is to add a sender address or a domain to the Mailjet account " +"settings so that the email address or domain is approved to send emails " +"using Mailjet's servers. First, navigate to the `Mailjet Account Information" +" `_ page. Next, click on the :guilabel:`Add" +" a Sender Domain or Address` link under the :guilabel:`Senders & Domains` " +"section." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Add a sender domain or address in the Mailjet interface." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:63 +msgid "" +"Determine if a sender's email address or the entire domain needs to be added" +" to the Mailjet settings. It may be easier to configure the domain as a " +"whole if :abbr:`DNS (Domain Name System)` access is available. Jump to the " +":ref:`Add a domain ` section for steps on " +"adding the domain." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:69 +msgid "" +"Either all email addresses of the Odoo database users who are sending emails" +" using Mailjet's servers need to be configured or the domain(s) of the " +"users' email addresses can be configured." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:72 +msgid "" +"By default, the email address originally set up in the Mailjet account is " +"added as a trusted sender. To add another email address, click on the button" +" labeled :guilabel:`Add a sender address`. Then, add the email address that " +"is configured to send from the custom domain." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:76 +msgid "" +"At minimum the following email addresses should be set up in the provider " +"and verified in Mailjet:" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:78 +msgid "notifications\\@yourdomain.com" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:79 +msgid "bounce\\@yourdomain.com" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:80 +msgid "catchall\\@yourdomain.com" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:83 +msgid "" +"Replace `yourdomain` with the custom domain for the Odoo database. If there " +"isn't one, then use the :guilabel:`mail.catchall.domain` system parameter." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:86 +msgid "" +"After that, fill out the :guilabel:`Email Information` form, making sure to " +"select the appropriate email type: transactional email or mass emails. After" +" completing the form, an activation email is sent to the email address and " +"the trusted sender can be activated." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:90 +msgid "" +"It is recommended to set up the :abbr:`SPF (Sender Policy " +"Framework)`/:abbr:`DKIM (DomainKeys Identified Mail)`/:abbr:`DMARC (Domain-" +"based Message Authentication, Reporting, and Conformance)` settings on the " +"domain of the sender." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:95 +#: ../../content/administration/maintain/mailjet_api.rst:162 +msgid "" +"`Mailjet's SPF/DKIM/DMARC documentation " +"`_" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:99 +msgid "" +"If the database is not using a custom domain, then in order to verify the " +"sender's address, a temporary alias (of the three email addresses mentioned " +"above) should be set up in Odoo CRM to create a lead. Then, the database is " +"able to receive the verification email and verify the accounts." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:107 +msgid "Add a domain" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:109 +msgid "" +"By adding an entire domain to the Mailjet account, all the sender addresses " +"related to that domain are automatically validated for sending emails using " +"Mailjet servers. First, navigate to the `Mailjet Account Information " +"`_ page. Next, click on :guilabel:`Add a " +"Sender Domain or Address` link under the :guilabel:`Senders & Domains` " +"section. Then, click on :guilabel:`Add domain` to add the custom domain." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:116 +msgid "" +"The domain needs to be added to the Mailjet account and then validated " +"through the :abbr:`DNS (Domain Name System)`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:119 +msgid "" +"After that, fill out the :guilabel:`Add a new Domain` page on Mailjet and " +"click :guilabel:`Continue`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:122 +msgid "" +"After adding the domain, a validation page will populate. Unless the Odoo " +"database is on-premise (in which case, choose :guilabel:`Option 1`), choose " +":guilabel:`Option 2: Create a DNS Record`. Copy the TXT record information " +"to a notepad and then navigate to the domain's :abbr:`DNS (Domain Name " +"System)` provider to complete validation." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "The TXT record information to input on the domain's DNS." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:132 +msgid "Setup in the domain's DNS" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:134 +msgid "" +"After getting the TXT record information from the Mailjet account, add a TXT" +" record to the domain's :abbr:`DNS (Domain Name System)`. This process " +"varies depending on the :abbr:`DNS (Domain Name System)` provider. Consult " +"the provider for specific configuration processes. The TXT record " +"information consists of the :guilabel:`Host` and :guilabel:`Value`. Paste " +"these into the corresponding fields in the TXT record." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:141 +msgid "Return to Mailjet account information" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:143 +msgid "" +"After adding the TXT record to the domain's :abbr:`DNS (Domain Name " +"System)`, navigate back to the Mailjet account. Then, navigate to " +":menuselection:`Account Information --> Add a Sender Domain or Address`, " +"click the gear icon next to :guilabel:`Domain`, and select " +":guilabel:`Validate`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:147 +msgid "" +"This action can also be done by going to the `Sender domains & addresses " +"`_ page on the Mailjet account " +"information and clicking on :guilabel:`Manage`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:150 +msgid "" +"Next, click :guilabel:`Check Now` to validate the TXT record that was added " +"on the domain. A success screen will appear if the domain is configured " +"correctly." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Check DNS record in Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:157 +msgid "" +"After successfully setting up the domain, there is an option to " +":guilabel:`Authenticate this domain (SPF/DKIM)`. This button populates " +":abbr:`SPF (Sender Policy Framework)` & :abbr:`DKIM (DomainKeys Identified " +"Mail) records to input into the :abbr:`DNS (Domain Name System)` provider." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Authenticate the domain with SPF/DKIM records in Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:172 +msgid "Set up in Odoo" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:174 +msgid "" +"To complete the setup, navigate to the Odoo database and go to the " +":guilabel:`Settings`. With :ref:`developer-mode` turned on, go to the " +":menuselection:`Technical Menu --> Email --> Outgoing Mail Servers`. Then, " +"create a new outgoing server configuration by clicking on the " +":guilabel:`Create` button." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:179 +msgid "" +"Next, input the `SMTP server` (in-v3.mailjet.com), `port number` (587 or " +"465), and `Security (SSL/TLS)` that was copied earlier from the Mailjet " +"account. They can also be found `here " +"`_. It is recommended to use " +":abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)` " +"even though Mailjet may not require it." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:184 +msgid "" +"For the :guilabel:`Username`, input the :guilabel:`API KEY`. For the " +":guilabel:`Password`, input the :guilabel:`SECRET KEY` that was copied from " +"the Mailjet account to the notepad earlier. These settings can be found on " +":menuselection:`Mailjet --> Account Settings --> SMTP and SEND API " +"Settings`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:189 +msgid "" +"Then, if the Mailjet server is used for mass emailing, set the " +":guilabel:`Priority` value higher than that of any transactional email " +"server(s). Finally, save the settings and :guilabel:`Test the Connection`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Odoo outgoing email server settings." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:198 +msgid "" +"In order for the notifications feature to work using Mailjet, there are " +"three settings that need to be set in Odoo." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:201 +msgid "" +"The :guilabel:`From Filter` needs to be set on the server configuration. It " +"is recommended to set it as a domain and not a full email address. It should" +" match the domain in the two proceeding steps. More information can be " +"referenced :ref:`here `." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:205 +msgid "" +"The :guilabel:`mail.default.from` system parameter must have the value " +"`notifications\\@yourdomain.com`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:207 +msgid "" +"The :guilabel:`mail.default.from_filter` system parameter must have the " +"value `yourdomain.com`. Replace `yourdomain` with the custom domain for the " +"Odoo database. If there isn't one, then use the " +":guilabel:`mail.catchall.domain` system parameter." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:211 +msgid "" +"For more information see :ref:`Using a default email address " +"`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:217 +msgid "" +"Once the setup is complete, the Odoo database is ready to use the Mailjet " +"email server for mass mailing or transactional emails!" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:3 +msgid "Odoo Online database management" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:5 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:8 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:15 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:16 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:17 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:18 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:19 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:20 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:21 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:22 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:23 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:28 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:77 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/upgrade.rst:10 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:30 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:33 +msgid "" +"For more information about the upgrade process, check out the :doc:`Odoo " +"Online upgrade documentation <../upgrade/odoo_online>`." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:39 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:41 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:45 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:47 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:52 +msgid "Rename" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:54 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:59 +msgid "Download" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:61 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:64 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:72 +msgid "" +"Use a custom :doc:`domain name ` to access the database via " +"another URL." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:75 +msgid "" +"You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:80 +msgid "Tags" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:82 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:85 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:90 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:92 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:95 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:98 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:105 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:106 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:107 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:113 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:115 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:121 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:123 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:129 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:132 +msgid ":doc:`../../applications/general/users/manage_users`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:133 +msgid ":doc:`../../applications/general/users/delete_account`" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:3 +msgid "On-premise database management" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:6 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:8 +msgid "" +"To register your database, you just need to enter your Subscription Code in " +"the banner in the App Switcher. Make sure you do not add extra spaces before" +" or after your subscription code. If the registration is successful, it will" +" turn green and will provide you with the Expiration Date of your freshly-" +"registered database. You can check this Expiration Date in the About menu " +"(Odoo 9) or in the Settings Dashboard (Odoo 10)." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:16 +msgid "Registration Error Message" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:18 +msgid "" +"If you are unable to register your database, you will likely encounter this " +"message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst-1 +msgid "" +"Something went wrong while registering your database, you can try again or contact Odoo\n" +"Help" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:27 +#: ../../content/administration/maintain/on_premise.rst:100 +#: ../../content/administration/maintain/on_premise.rst:127 +msgid "Solutions" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:29 +msgid "Do you have a valid Enterprise subscription?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:31 +msgid "" +"Check if your subscription details get the tag \"In Progress\" on your `Odoo" +" Account `__ or with your Account" +" Manager" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:35 +msgid "Have you already linked a database with your subscription reference?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:37 +msgid "" +"You can link only one database per subscription. (Need a test or a " +"development database? `Find a partner `__)" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:41 +msgid "" +"You can unlink the old database yourself on your `Odoo Contract " +"`__ with the button \"Unlink " +"database\"" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:47 +msgid "" +"A confirmation message will appear; make sure this is the correct database " +"as it will be deactivated shortly:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:53 +msgid "Do you have the updated version of Odoo 9?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:55 +#: ../../content/administration/maintain/on_premise.rst:159 +msgid "" +"From July 2016 onward, Odoo 9 now automatically change the uuid of a " +"duplicated database; a manual operation is no longer required." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:58 +msgid "" +"If it's not the case, you may have multiple databases sharing the same UUID." +" Please check on your `Odoo Contract " +"`__, a short message will appear " +"specifying which database is problematic:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:66 +msgid "" +"In this case, you need to change the UUID on your test databases to solve " +"this issue. You will find more information about this in :ref:`this section " +"`." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:69 +msgid "" +"For your information, we identify database with UUID. Therefore, each " +"database should have a distinct UUID to ensure that registration and " +"invoicing proceed effortlessly for your and for us." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:73 +msgid "Check your network and firewall settings" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:75 +msgid "" +"The Update notification must be able to reach Odoo's subscription validation" +" servers. In other words, make sure that the Odoo server is able to open " +"outgoing connections towards:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:79 +msgid "services.odoo.com on port 443 (or 80)" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:80 +msgid "services.openerp.com on port 443 (or 80) for older deployments" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:82 +msgid "" +"Once you activated your database, you must keep these ports open, as the " +"Update notification runs once a week." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:86 +msgid "Error message due to too many users" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:88 +msgid "" +"If you have more users in your local database than provisionned in your Odoo" +" Enterprise subscription, you may encounter this message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst-1 +msgid "" +"This database will expire in X days, you have more users than your " +"subscription allows" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:96 +msgid "" +"When the message appears you have 30 days before the expiration. The " +"countdown is updated everyday." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:102 +msgid "" +"**Add more users** on your subscription: follow the link and Validate the " +"upsell quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:104 +msgid "" +"**Deactivate users** as explained in this `documentation " +"`_ and **Reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:107 +msgid "" +"Once your database has the correct number of users, the expiration message " +"will disappear automatically after a few days, when the next verification " +"occurs. We understand that it can be a bit frightening to see the countdown," +" so you can :ref:`force an Update Notification ` to make the " +"message disappear right away." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:114 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:116 +msgid "" +"If your database reaches its expiration date before your renew your " +"subscription, you will encounter this message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst-1 +msgid "This database has expired." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:123 +msgid "" +"This **blocking** message appears after a non-blocking message that lasts 30" +" days. If you fail to take action before the end of the countdown, the " +"database is expired." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:131 +msgid "" +"Renew your subscription: follow the link and renew your subscription - note " +"that" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:130 +msgid "" +"if you wish to pay by Wire Transfer, your subscription will effectively be " +"renewed only when the payment arrives, which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:133 +msgid "Contact our `Support `__" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:135 +msgid "" +"None of those solutions worked for you? Please contact our `Support " +"`__" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:143 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:145 +msgid "" +"You can duplicate your database by accessing the database manager on your " +"server (/web/database/manager). In this page, you can easily " +"duplicate your database (among other things)." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:152 +msgid "" +"When you duplicate a local database, it is **strongly** advised to change " +"the duplicated database's uuid (Unniversally Unique Identifier), since this " +"uuid is how your database identifies itself with our servers. Having two " +"databases with the same uuid could result in invoicing problems or " +"registration problems down the line." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:162 +msgid "" +"The database uuid is currently accessible from the menu " +":menuselection:`Settings --> Technical --> System Parameters`, we advise you" +" to use a `uuid generator `_ or to use the unix " +"command ``uuidgen`` to generate a new uuid. You can then simply replace it " +"like any other record by clicking on it and using the edit button." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:6 +#: ../../content/administration/upgrade.rst:208 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:8 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:11 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:15 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` " +"them regularly." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:16 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:17 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:20 +msgid "What's the support status of my Odoo?" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:22 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:24 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:33 +#: ../../content/administration/upgrade/on_premise.rst:3 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:34 +msgid "Release date" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:35 +msgid "End of support" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:36 +msgid "Odoo saas~16.3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:37 +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:55 +#: ../../content/administration/maintain/supported_versions.rst:56 +#: ../../content/administration/maintain/supported_versions.rst:57 +#: ../../content/administration/maintain/supported_versions.rst:73 +#: ../../content/administration/maintain/supported_versions.rst:74 +#: ../../content/administration/maintain/supported_versions.rst:75 +#: ../../content/administration/maintain/supported_versions.rst:79 +#: ../../content/administration/maintain/supported_versions.rst:80 +#: ../../content/administration/maintain/supported_versions.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:62 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:67 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:82 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:99 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:107 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:119 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:122 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:127 +msgid "|green|" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:38 +#: ../../content/administration/maintain/supported_versions.rst:39 +#: ../../content/administration/maintain/supported_versions.rst:44 +#: ../../content/administration/maintain/supported_versions.rst:45 +#: ../../content/administration/maintain/supported_versions.rst:50 +#: ../../content/administration/maintain/supported_versions.rst:51 +#: ../../content/administration/maintain/supported_versions.rst:62 +#: ../../content/administration/maintain/supported_versions.rst:63 +#: ../../content/administration/maintain/supported_versions.rst:68 +#: ../../content/administration/maintain/supported_versions.rst:69 +#: ../../content/administration/maintain/supported_versions.rst:92 +#: ../../content/administration/maintain/supported_versions.rst:93 +#: ../../content/administration/maintain/supported_versions.rst:104 +#: ../../content/administration/maintain/supported_versions.rst:105 +#: ../../content/administration/maintain/supported_versions.rst:116 +#: ../../content/administration/maintain/supported_versions.rst:117 +#: ../../content/administration/maintain/supported_versions.rst:122 +#: ../../content/administration/maintain/supported_versions.rst:123 +#: ../../content/administration/maintain/supported_versions.rst:134 +#: ../../content/administration/maintain/supported_versions.rst:135 +#: ../../content/administration/maintain/supported_versions.rst:140 +#: ../../content/administration/maintain/supported_versions.rst:146 +#: ../../content/administration/maintain/supported_versions.rst:147 +#: ../../content/administration/maintain/supported_versions.rst:152 +msgid "N/A" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:40 +msgid "June 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:41 +msgid "September 2023 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:42 +msgid "Odoo saas~16.2" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:46 +msgid "March 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:47 +msgid "July 2023 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:48 +msgid "Odoo saas~16.1" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:49 +#: ../../content/administration/maintain/supported_versions.rst:61 +#: ../../content/administration/maintain/supported_versions.rst:67 +#: ../../content/administration/maintain/supported_versions.rst:85 +#: ../../content/administration/maintain/supported_versions.rst:86 +#: ../../content/administration/maintain/supported_versions.rst:87 +#: ../../content/administration/maintain/supported_versions.rst:91 +#: ../../content/administration/maintain/supported_versions.rst:97 +#: ../../content/administration/maintain/supported_versions.rst:98 +#: ../../content/administration/maintain/supported_versions.rst:99 +#: ../../content/administration/maintain/supported_versions.rst:103 +#: ../../content/administration/maintain/supported_versions.rst:109 +#: ../../content/administration/maintain/supported_versions.rst:110 +#: ../../content/administration/maintain/supported_versions.rst:111 +#: ../../content/administration/maintain/supported_versions.rst:115 +#: ../../content/administration/maintain/supported_versions.rst:121 +#: ../../content/administration/maintain/supported_versions.rst:127 +#: ../../content/administration/maintain/supported_versions.rst:128 +#: ../../content/administration/maintain/supported_versions.rst:129 +#: ../../content/administration/maintain/supported_versions.rst:133 +#: ../../content/administration/maintain/supported_versions.rst:139 +#: ../../content/administration/maintain/supported_versions.rst:141 +#: ../../content/administration/maintain/supported_versions.rst:145 +#: ../../content/administration/maintain/supported_versions.rst:151 +#: ../../content/administration/maintain/supported_versions.rst:153 +msgid "|red|" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:52 +msgid "February 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:53 +msgid "April 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:54 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../content/administration/maintain/supported_versions.rst:89 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:59 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:60 +msgid "Odoo saas~15.2" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:64 +msgid "March 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:65 +msgid "January 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:66 +msgid "Odoo saas~15.1" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:70 +msgid "February 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:71 +msgid "July 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:72 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:76 +#: ../../content/administration/maintain/supported_versions.rst:101 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:77 +msgid "October 2024 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:78 +msgid "**Odoo 14.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:82 +#: ../../content/administration/maintain/supported_versions.rst:113 +msgid "October 2020" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:83 +msgid "October 2023 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:84 +msgid "**Odoo 13.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:88 +#: ../../content/administration/maintain/supported_versions.rst:131 +msgid "October 2019" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:90 +msgid "Odoo saas~12.3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:94 +msgid "August 2019" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:96 +msgid "**Odoo 12.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:100 +#: ../../content/administration/maintain/supported_versions.rst:143 +msgid "October 2018" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:102 +msgid "Odoo saas~11.3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:106 +msgid "April 2018" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:108 +msgid "**Odoo 11.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:112 +#: ../../content/administration/maintain/supported_versions.rst:155 +msgid "October 2017" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:114 +msgid "Odoo 10.saas~15" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:118 +msgid "March 2017" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:120 +msgid "Odoo 10.saas~14" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:124 +msgid "January 2017" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:126 +msgid "**Odoo 10.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:130 +msgid "October 2016" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:132 +msgid "Odoo 9.saas~11" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:136 +msgid "May 2016" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:138 +msgid "**Odoo 9.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:142 +msgid "October 2015" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:144 +msgid "Odoo 8.saas~6" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:148 +msgid "February 2015" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:150 +msgid "**Odoo 8.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:154 +msgid "September 2014" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:159 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:161 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:163 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:165 +msgid "🏁 Future version, not released yet" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:176 +msgid "I run an older version of Odoo/OpenERP/TinyERP" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:178 +msgid "" +"OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:180 +msgid "" +"TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:182 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/maintain/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/maintain/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/maintain/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/maintain/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/maintain/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/maintain/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/maintain/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/maintain/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/maintain/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/maintain/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/maintain/update.rst:49 +msgid "" +"The main reference for updating is logically our :ref:`installation guide " +"`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/maintain/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/maintain/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/maintain/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/maintain/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/maintain/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/maintain/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/maintain/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/maintain/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/maintain/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/maintain/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/maintain/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/maintain/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/maintain/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/maintain/update.rst:113 +msgid "" +"You will get a folder labelled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/maintain/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/maintain/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/maintain/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/maintain/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/maintain/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/maintain/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +#: ../../content/administration/upgrade/odoo_sh.rst:8 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:170 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment acquirers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as often is the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:109 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade - Odoo.sh <../../upgrade/odoo_sh>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:117 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:124 +msgid "Settings" +msgstr "Ustawienia" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF " +"` and :ref:`DKIM " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of " +"Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../maintain/on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :ref:`installation of Odoo " +"`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/getting_started` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are two levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid "Admin: has access to all features of Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:39 +msgid "" +"User: does not have access to the project settings nor to the production and" +" staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:41 +msgid "" +"The user group is meant for developers who can make modifications in your " +"code but are not allowed to access the production data. Users of this group " +"cannot connect to the production and staging databases using the *1-click " +"connect* feature, but they can of course use their regular account on these " +"databases if they have one, using their regular credentials." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:46 +msgid "" +"In addition, they cannot use the webshell nor have access to the server " +"logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "User" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:97 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +msgid "Production & Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +msgid "|green|\\*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:120 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +msgid "\\* Only in staging branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:145 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:147 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:152 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to connect to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:155 +msgid "" +"In addition, visitors have access to the logs, shell and mails of your " +"development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:157 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:162 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:164 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:172 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:183 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:188 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:190 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:192 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:193 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:196 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:198 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:200 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:202 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:203 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:204 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:205 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:208 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:210 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:215 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:217 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:219 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:222 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:225 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:231 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:239 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:245 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:247 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:254 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:256 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/upgrade.rst:20 +msgid "" +"An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo " +"15.0)." +msgstr "" + +#: ../../content/administration/upgrade.rst:22 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"Changing :ref:`editions ` (i.e., Community to " +"Enterprise edition)" +msgstr "" + +#: ../../content/administration/upgrade.rst:25 +msgid "" +"Switching :ref:`hosting type ` (i.e., On-" +"Premise to Odoo Online or Odoo.sh)" +msgstr "" + +#: ../../content/administration/upgrade.rst:27 +msgid "Migration from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:29 +#: ../../content/administration/upgrade.rst:148 +#: ../../content/administration/upgrade.rst:259 +#: ../../content/administration/upgrade/faq.rst:81 +#: ../../content/administration/upgrade/faq.rst:92 +#: ../../content/administration/upgrade/faq.rst:119 +msgid "|assistance-contact|" +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid ":ref:`upgrade/sla`" +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "Process workflow" +msgstr "" + +#: ../../content/administration/upgrade.rst:39 +msgid "The upgrade process in a nutshell:" +msgstr "" + +#: ../../content/administration/upgrade.rst:41 +msgid "You create a test upgrade request." +msgstr "" + +#: ../../content/administration/upgrade.rst:42 +msgid "" +"Odoo processes the request automatically by running the database through an " +"upgrade script, which takes between 20 and 120 minutes." +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "Odoo delivers a test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:45 +msgid "" +"You test your database for possible discrepancies (see :ref:`upgrade/test-" +"guidance`)." +msgstr "" + +#: ../../content/administration/upgrade.rst:46 +msgid "" +"If there are any discrepancies, you report them to the Upgrade support team " +"via the help portal (see :ref:`upgrade/test-assistance`)." +msgstr "" + +#: ../../content/administration/upgrade.rst:48 +msgid "We fix the issues and send you a new test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"Once you have completed the testing and are happy with the result, you " +"decide on a date and time when you stop users from accessing Odoo, freeze " +"all data entries, and create an upgrade request for the production upgrade." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "Odoo delivers the production database through the automated process." +msgstr "" + +#: ../../content/administration/upgrade.rst:53 +msgid "" +"You restore it in your Production environment a few short hours later and " +"continue working on the newly upgraded database (this is done automatically " +"on Odoo Online)." +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid ":doc:`Upgrade process for Odoo Online `" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid ":doc:`Upgrade process for Odoo.sh `" +msgstr "" + +#: ../../content/administration/upgrade.rst:59 +msgid ":doc:`Upgrade process for On-Premise `" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +msgid "Testing" +msgstr "" + +#: ../../content/administration/upgrade.rst:66 +msgid "" +"This phase allows you to review an upgraded version of your database without" +" affecting your production database in any way. We suggest that you run the " +"test upgrade process at least once, but you can do it as many times as you " +"need (one at a time)." +msgstr "" + +#: ../../content/administration/upgrade.rst:70 +msgid "" +"Once you receive your upgraded test database, check that all data, " +"processes, and functionality are still correct and working as expected." +msgstr "" + +#: ../../content/administration/upgrade.rst:73 +msgid "" +"If you do find discrepancies, :ref:`report your issues ` and :ref:`request a new test database ` when the reported issues are fixed in the upgrade script." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +msgid "" +"If you do not find any discrepancies, you can move on to the upgrade of your" +" production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:80 +msgid "" +"A test database is only intended for testing and remains completely " +"unrelated to your present or future production database. Any data you add, " +"or changes you make, will not be reflected in your upgraded production " +"database." +msgstr "" + +#: ../../content/administration/upgrade.rst:85 +msgid "" +"Test databases are neutered and features are disabled to prevent them from " +"having an impact on the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:88 +msgid "" +"The serial number of the database is modified (to prevent it from sending " +"information as if it was the production database)." +msgstr "" + +#: ../../content/administration/upgrade.rst:90 +msgid "" +"The :ref:`base URL of the database ` is reset to " +"``http://localhost:8069`` and the email domain to ``localhost``." +msgstr "" + +#: ../../content/administration/upgrade.rst:92 +msgid "" +"Scheduled actions are disabled (the calendar synchronization, the bank " +"statement synchronization, the planned automated actions, the fetching of " +"incoming mail servers, etc.)." +msgstr "" + +#: ../../content/administration/upgrade.rst:94 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake/non-working one." +msgstr "" + +#: ../../content/administration/upgrade.rst:96 +msgid "Payment providers and delivery carriers are reset to test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +msgid "" +"Accounting localization Electronic Data Interchange (EDI) services are " +"disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:98 +msgid "A system parameter is set to tell the database has been neutered." +msgstr "" + +#: ../../content/administration/upgrade.rst:103 +msgid "Request a test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:105 +msgid "" +"Follow the instructions available per hosting type on the `website form " +"`_ and select *Testing* purpose." +msgstr "" + +#: ../../content/administration/upgrade.rst-1 +msgid "Selection of the \"Testing\" purpose in the upgrade form on Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:115 +msgid "Test guidance" +msgstr "" + +#: ../../content/administration/upgrade.rst:117 +msgid "" +"Every business and organization has its own operational needs and has to " +"test its specific Odoo database individually. We recommend you look at `the " +"test scenario " +"`_" +" for further information." +msgstr "" + +#: ../../content/administration/upgrade.rst:122 +msgid "change link \"test scenario\" once the related doc is published" +msgstr "" + +#: ../../content/administration/upgrade.rst:127 +#: ../../content/administration/upgrade.rst:172 +msgid "Assistance" +msgstr "" + +#: ../../content/administration/upgrade.rst:129 +msgid "" +"If you encounter an issue in the **test database**, please get in touch with" +" Odoo Upgrade Support via the `Odoo Support page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:132 +msgid "" +"Under the *Ticket Description* section, select *An issue related to my " +"upgrade* ticket type." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"Selection of \"An issue related to my upgrade\" as Ticket Type in the " +"support form on Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:139 +msgid "" +"If you choose another *Ticket Description* type, the request will be " +"redirected to another team. This will slow down the processing and response " +"time." +msgstr "" + +#: ../../content/administration/upgrade.rst:142 +#: ../../content/administration/upgrade.rst:185 +msgid "" +"Please provide as much detail as you can (i.e., videos and screenshots to " +"illustrate your issue). This will avoid clarifying questions and speed up " +"the resolution process significantly." +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The purpose of the test phase is not to correct existing data or " +"configurations in your database." +msgstr "" + +#: ../../content/administration/upgrade.rst:153 +msgid "The production launch" +msgstr "" + +#: ../../content/administration/upgrade.rst:155 +msgid "" +"The production upgrade request is when you decide to upgrade your current " +"database with all your production data (invoices, VAT returns, inventories, " +"current orders) to a new version of your choice." +msgstr "" + +#: ../../content/administration/upgrade.rst:159 +msgid "" +"After your :ref:`tests ` are completed to your " +"satisfaction, submit the request to upgrade your production database via our" +" `website form `_. Select *Production* purpose." +msgstr "" + +#: ../../content/administration/upgrade.rst:164 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:166 +msgid "" +"business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:167 +msgid "" +"poor customer experiences (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:174 +msgid "" +"If you encounter issues or problems in the **production database**, please " +"get in touch with **Odoo Support**:" +msgstr "" + +#: ../../content/administration/upgrade.rst:177 +msgid "Connect to our `Odoo Support page `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"Under the *Ticket Description* section, select the appropriate type related " +"to your issue but **do not select** the option *An issue related to my " +"upgrade*." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"After upgrading to production, the support will be provided by the Support " +"team instead of the Upgrade team." +msgstr "" + +#: ../../content/administration/upgrade.rst:189 +msgid "" +"If you choose *An issue related to my upgrade* as ticket type, the request " +"will be redirected to another team than the support one and will slow down " +"the processing and response time." +msgstr "" + +#: ../../content/administration/upgrade.rst:195 +msgid "Help" +msgstr "" + +#: ../../content/administration/upgrade.rst:200 +msgid "Contact our upgrade service support" +msgstr "" + +#: ../../content/administration/upgrade.rst:202 +msgid "" +"Should you have any more questions about the upgrade, do not hesitate to " +"send a message to `Odoo Upgrade Team `_. We will be" +" happy to answer it as soon as possible." +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "" +"Please note that Odoo provides support and bug fixing only for the three " +"last major versions of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:213 +msgid "" +"This is a factor to take into consideration before upgrading. If you are on " +"an older version, we suggest you to prefer the most recent version to " +"benefit from longer support (before having to upgrade again)." +msgstr "" + +#: ../../content/administration/upgrade.rst:218 +msgid ":doc:`maintain/supported_versions`" +msgstr "" + +#: ../../content/administration/upgrade.rst:223 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:225 +msgid "" +"With Odoo Enterprise, upgrading a database to the most recent version of " +"Odoo is **free**, including any support required to rectify potential " +"discrepancies in the upgraded database." +msgstr "" + +#: ../../content/administration/upgrade.rst:228 +msgid "" +"Information about the upgrade services included in the Enterprise Licence is" +" available in the :ref:`Odoo Enterprise Subscription Agreement `. " +"However, this section clarifies what upgrade services you can expect." +msgstr "" + +#: ../../content/administration/upgrade.rst:233 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:235 +msgid "" +"Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or " +"self-hosted (On-Premise) can benefit from upgrade services at all times for:" +msgstr "" + +#: ../../content/administration/upgrade.rst:238 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "" +"the upgrade of all **customizations created with the Studio app**, as long " +"as Studio is still installed and the respective subscription is still " +"active; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:244 +msgid "" +"Upgrade services are limited to the technical conversion and adaptation of a" +" database (standard modules and data) to make it compatible with the version" +" targeted by the upgrade." +msgstr "" + +#: ../../content/administration/upgrade.rst:248 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "" +"the upgrade of **custom modules created in-house or by third parties**, " +"including Odoo partners;" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "" +"lines of **code added to standard modules**, i.e., customizations created " +"outside the Studio app, code entered manually, and :ref:`automated actions " +"using Python code `; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:262 +msgid ":doc:`Upgrade FAQ `" +msgstr "" + +#: ../../content/administration/upgrade.rst:263 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +msgid ":doc:`Supported Odoo versions `" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:8 +msgid "FAQ" +msgstr "FAQ" + +#: ../../content/administration/upgrade/faq.rst:13 +msgid "Why upgrade" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:15 +msgid "" +"You benefit from the latest features of the :ref:`new major version " +"` released by Odoo." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:17 +msgid "" +"If you are in an :ref:`unsupported version `, " +"you get a new version with support." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:23 +msgid "When to upgrade" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:25 +msgid "" +"Whenever you want. You can make your upgrade request as soon as a new " +"version is released or when your version turns unsupported, and you still " +"wish to enjoy support." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:31 +msgid "Availability of the new version" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:33 +msgid "" +"As soon as Odoo announces the release of a new major version, you can create" +" a test upgrade request to try the latest version. Please note that at this " +"point, the upgrade scripts will only have been tested with demo data. Please" +" report any issue you might encounter while testing via the `Odoo Support " +"page `_ and make sure to be happy with your test " +"version before requesting the upgrade of your database in production." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:42 +msgid "Duration of the upgrade" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:44 +msgid "It is impossible to give time estimates for every upgrade request." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:46 +msgid "" +"In general, the \"smaller\" the database, the quickest the upgrade request " +"is completed. A single-user database that uses only CRM will be processed " +"faster than a multi-company, multi-user database that uses Accounting, " +"Sales, Purchase, and Manufacturing." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:50 +msgid "" +"You can expect the time it takes for the platform to upgrade the test " +"database to be similar to the production upgrade." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:56 +msgid "Duration of the upgrade project" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:58 +msgid "" +"It depends on the user involvement (the time spent on testing, reporting " +"problems, etc.) and the issues encountered that might need to be addressed " +"by our technical team." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:61 +msgid "So, in a nutshell, what can impact your upgrade lead time?" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:63 +msgid "Source & targeted versions" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:64 +msgid "Installed apps" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:65 +msgid "Volume of data" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:66 +msgid "" +"Amount of customization (models, fields, methods, workflows, reports, " +"website, etc.)" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:67 +msgid "" +"Installation of new apps or configuration changes after the start of the " +"test phase" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:68 +msgid "User commitment" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:73 +msgid "Upgrade of the custom modules" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:75 +msgid "" +"As stated in our :doc:`/legal/terms/enterprise`, section " +":ref:`charges_standard`, this optional service is subject to additional " +"fees." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:78 +msgid "" +"Depending on your situation, the custom code could be upgraded by our " +"services, by one of our partners, or you can do it yourself." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:86 +msgid "Upgrade or Migration" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:88 +msgid "" +"An upgrade is switching to a newer version of Odoo, while a migration " +"reflects the change of :ref:`editions ` or " +"change of :ref:`hosting type `." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:97 +msgid "Editions change (from Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:99 +msgid "" +"The upgrade always returns an Enterprise edition of Odoo, whether the " +"database you sent was a community or enterprise edition. It is required to " +"have an enterprise subscription to upgrade." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:103 +msgid "" +"If you need assistance on this matter, please contact us via the `Odoo " +"Support page `_." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:107 +msgid "`Editions `_" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:112 +msgid "Switching the hosting types (On-premise vs. Odoo Online vs. Odoo.sh)" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:114 +msgid "" +"An upgrade does not cover a change of `Hosting types " +"`_." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:116 +msgid "" +"Open the following link to get :doc:`more information about how to change " +"your hosting type <../maintain/hosting_changes>`." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:124 +msgid "The Upgrade Report" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:126 +msgid "" +"When an upgrade request completes successfully (test or production), you " +"receive an email notification about it that includes an 'Upgrade Report'. " +"This report is also sent to you via the Discuss app. It contains valuable " +"information regarding changes that occurred during the upgrade. While it " +"serves as a guide to possible issues to look out for, it is not an " +"exhaustive list. It remains imperative that you test the upgraded database " +"thoroughly and report any discrepancies you might find, before you decide to" +" upgrade your production database." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:136 +msgid "Custom views" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:138 +msgid "" +"During the upgrade, some custom views might get disabled for technical " +"reasons. Therefore they might have to be fixed after the upgrade. The " +":ref:`Upgrade Report ` that is generated after " +"the upgrade is available in the Discuss app, and lists all the custom views " +"that might be impacted by this." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:146 +msgid "Release Notes by version" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:148 +msgid "" +"Open our `Release Note `_ page to " +"get a summary of the new features and improvements made in each version." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:152 +msgid "How long is my test available for" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:154 +msgid "" +"An Odoo Online test database is available for one month by default. We can " +"extend this trial period upon request. For Odoo.sh or on-premise, there is " +"no restriction." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:158 +msgid "How many tests to perform before upgrading to production?" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:160 +msgid "" +"As many as needed. When you are comfortable with the database, run a last " +"test upgrade 48 hours before requesting your production upgrade and test " +"your workflows one last time." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:164 +msgid "How to/Where to report upgrade issues?" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:166 +msgid "" +"If you encounter issues during the upgrade process, please contact the Odoo " +"Support through the `Odoo Support page `_." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:169 +msgid "" +"To report an issue discovered during the testing phase, please select **An " +"issue related to my upgrade (test phase)**." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:171 +msgid "" +"To report an issue discovered post-upgrade, please select **An issue related" +" to my upgrade (production)**." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:175 +msgid "Upgrading to production" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:177 +msgid "" +"Once you have completed testing and are happy with the result, you decide on" +" a date and time when you stop users from accessing Odoo, freeze all data " +"entries, and create an upgrade request for the production upgrade." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:182 +msgid "How is my data handled in the Upgrade Platform?" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:184 +msgid "" +"The Odoo Upgrade platform uses the same Privacy Policy as the rest of " +"Odoo.com services." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:186 +msgid "" +"Your data is hosted on servers that follow our security guidelines, namely:" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:188 +msgid "" +"SSL - All web connections to client instances are protected with 256-bit SSL" +" encryption (HTTPS with a 2048-bit modulus SSL certificate), and running " +"behind Grade A SSL stacks. All our certificate chains are using SHA-2 " +"already." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:191 +msgid "" +"Safe System - Our servers are running recent Linux distribution with up-to-" +"date security patches, with firewall and intrusion countermeasures (not " +"disclosed for obvious reasons)." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:194 +msgid "" +"Servers are located at the same locations as our Cloud providers with the " +"following services:" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:196 +msgid "" +"Restricted perimeter, physically accessed by authorized data center " +"employees only" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:197 +msgid "Physical access control with security badges or biometrical security" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:198 +msgid "Security cameras monitoring the data center locations 24/7" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:199 +msgid "Security personnel on-site 24/7" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:201 +msgid "" +"The uploaded and migrated databases uploaded to the Upgrade platform are " +"kept for up to 3 months and are permanently deleted following that period." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:204 +msgid "" +"You can learn more about privacy and data handling at Odoo by visiting our " +"`General Data Protection Regulation page `_." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:208 +msgid "Rolling Release (applicable to Odoo Online databases)" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:210 +msgid "" +"This feature allows customers to upgrade their database directly from a " +"message prompt sent to the database administrator as soon as the new version" +" is released. Odoo first tests the upgrade to the next version. The rolling " +"release upgrade option is displayed if the automated tests are successful. " +"The message offers two options:" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:215 +msgid "" +"To 'Upgrade Now', which immediately triggers the upgrade of your live " +"production database." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:217 +msgid "" +"To take you to your `database manager `_" +" where you can `request an upgraded test database " +"`_ and check the upgraded test database " +"for any discrepancies." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:221 +msgid "" +"When you choose to proceed with the production upgrade directly, make sure " +"all users have saved their work and are logged out. The upgrade takes " +"approximately 15 minutes. During this time your database is unreachable. If " +"you notice any problem after the upgrade, please report it via the `Odoo " +"Support page `_." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:227 +msgid "" +"If you are using the Website or Studio app, we recommend you always do a " +"test upgrade before upgrading your production instance." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:5 +msgid "" +"Odoo databases can be manually upgraded directly from the main Odoo website." +" To upgrade an Odoo database, navigate to the `database manager " +"`_ page and sign in." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:8 +msgid "" +"The database manager page displays all of the Odoo databases associated with" +" the user's account. Any databases that are not already on the most recent " +"version of Odoo display an **arrow in a circle** icon next to the database " +"name, indicating that the database can be upgraded." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst-1 +msgid "" +"The database manager page with an upgrade button next to the name of a " +"database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:17 +msgid "" +"If the database's version is **lower** than the latest major release: the " +"database must be upgraded within two months. After these two months, an " +"automatic upgrade is initiated." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:19 +msgid "" +"If the database's version is **equal** to or **higher** than the latest " +"major release: you can disregard the invitation to upgrade, as the database " +"probably would not benefit from new features every two months." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:23 +msgid "" +"If a database is *not* on the latest online version, its administrator " +"should receive an invitation to upgrade on the database's dashboard, " +"displayed as an **arrow in a circle**." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst-1 +msgid "Invitation to upgrade on the database dashboard." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:30 +msgid "" +"Versions that are not supported anymore become deprecated and must be " +"updated to avoid security issues. It is recommended to initiate the upgrade " +"yourself and not wait for the automatic upgrade, as the former method allows" +" you to request a test upgrade of the database to check for any " +"discrepancies." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:36 +msgid "Test database" +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:38 +msgid "" +"Click on the **arrow in a circle** icon to start the upgrade process. On the" +" :guilabel:`Upgrade your database` pop-up, select the version of Odoo that " +"the platform will be upgraded to. In the :guilabel:`Email to notify` field, " +"enter an email address that will receive email notifications about the " +"database upgrade." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:43 +msgid "" +"There is also a :guilabel:`Purpose` section on the pop-up that is used to " +"specify the reason for the upgrade. However, at this stage of the process, " +"the only selectable option is :guilabel:`Test`, as Odoo requires users to " +"create a test copy of the upgraded database before converting the actual " +"database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst-1 +msgid "The \"Upgrade your database\" pop-up." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:52 +msgid "" +"After filling out the form, click the :guilabel:`Upgrade` button. The pop-up" +" disappears and the database being upgraded shows a red :guilabel:`Upgrade " +"in progress` tag next to its name. An email confirming that the upgrade is " +"in progress is also sent to the email address specified on the pop-up." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst-1 +msgid "The \"Upgrade in progress\" tag next to the database name." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:61 +msgid "" +"Once the upgrade is complete, a new test database appears on the `database " +"manager `_ page. To access the test " +"database, click the drop-down arrow (:guilabel:`⯆`) to the left of the main " +"database's name. Doing so makes the test version appear below it. Finally, " +"click the green :guilabel:`Connect` button on the right side of the test " +"version's row to go to the database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst-1 +msgid "A test database on the database manager page." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:71 +msgid "" +"Except for being on the newer version of Odoo, the test database is an exact" +" copy of the one being upgraded. It is important to do extensive testing in " +"this database to ensure that the upgrade has not altered or corrupted any " +"data, and that all workflows still proceed as expected." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:76 +msgid "Production database" +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:78 +msgid "" +"After confirming the integrity of the new version, return to the `database " +"manager `_ page. Once again, click on the" +" **arrow in a circle** icon next to the database being upgraded. The " +":guilabel:`Upgrade your database` pop-up appears as before, except that " +"there is now a :guilabel:`Production` option under the :guilabel:`Purpose` " +"section." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:83 +msgid "" +"Select the :guilabel:`Production` option and then click :guilabel:`Upgrade` " +"to begin the upgrade process. As before, a notification email is sent to the" +" email address provided and a red :guilabel:`Upgrade in progress` tag " +"appears next to the name of the database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:87 +msgid "" +"The production database is then taken offline and will be upgraded " +"automatically. The time it takes to upgrade the production database should " +"be similar to the time that was necessary to upgrade the test database. Make" +" sure to inform database users of the scheduled downtime." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:91 +msgid "" +"After the upgrade is finished, the :guilabel:`Upgrade in progress` tag " +"disappears and the database is upgraded to the version specified." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:10 +msgid "" +"Odoo.sh is integrated with the upgrade platform to make the upgrade process " +"easier." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:13 +msgid "" +"The :guilabel:`Upgrade` tab is available in the branches view. It is only " +"available for valid projects with a valid production build." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst-1 +msgid "Click on the upgrade menu" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:20 +msgid "The suggested upgrade steps on Odoo.sh are:" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:22 +msgid "" +"On a :guilabel:`Development` branch, upgrade your custom modules to keep " +"them compatible with the new version and thoroughly **test them**." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:24 +msgid "" +"Switch that branch to the :guilabel:`Staging` branch, **upgrade** the last " +"daily production backup and **test it**. Write upgrade scripts if necessary." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:26 +msgid "" +"Trigger the production upgrade from your :guilabel:`Production` branch and " +"sit tight." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:29 +msgid ":doc:`../../administration/upgrade`" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:30 +msgid ":doc:`Upgrade FAQ <../upgrade/faq>`" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:31 +msgid ":doc:`Introduction to Odoo.sh <../odoo_sh/overview/introduction>`" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:36 +msgid "Upgrade your custom modules" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:38 +msgid "" +"The first step is to upgrade your custom modules to keep them compatible " +"with the new version. Fork your :guilabel:`Production` branch in the " +":guilabel:`Development` stage, then go to the settings of your " +":guilabel:`Development` branch and select the Odoo version you target. If " +"needed, modify your code to be compatible with the new version. Make sure to" +" **test** your features are still working correctly." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:45 +msgid "" +"Depending on your contract, the upgrade of your custom modules can be done " +"by yourself, by your Partner or by Odoo (if you hold a subscription " +"including maintenance of customizations)." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:51 +msgid "Upgrade your database on a staging branch" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:53 +msgid "" +"Take the upgraded development branch and drag & drop it to " +":guilabel:`Staging`." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:55 +msgid "" +"Go to the :guilabel:`Upgrade` tab and select the :guilabel:`target version`." +" Then, click on :guilabel:`Test Upgrade`." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst-1 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:62 +msgid "" +"The **latest production daily automatic backup** is sent to the `upgrade " +"platform `_ to start the upgrade test process." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:66 +msgid "" +"You can follow the upgrade process by going to the :guilabel:`Upgrade` menu " +"of your :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:69 +msgid "" +"When the upgraded backup is ready on the `upgrade platform " +"`_, it is automatically downloaded back to " +"your project." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:72 +msgid "" +"The branch is now in a **special mode**: each time a **commit is pushed** on" +" the branch, a **restore operation** of the upgraded backup occurs, and an " +"**update of all the custom modules** happens. This allows you to quickly " +"iterate on your custom modules upgrade scripts. The log file of the upgrade " +"process can be found at :file:`~/logs/upgrade.log` in your newly upgraded " +"staging build." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:78 +msgid "The **special upgrade mode** is automatically closed after 30 days." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:79 +#: ../../content/administration/upgrade/odoo_sh.rst:128 +msgid "" +"It may happen that custom modules are no longer needed after an upgrade. " +"Custom modules in the upgraded database are set to be updated. If the " +"modules are missing in the code, the update fails, thus failing the whole " +"process. An empty module with a manifest and possibly some custom upgrade " +"script are necessary to clean up the database. The complete removal of the " +"module has to be handled afterwards." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:86 +msgid "Functionally test your upgraded database" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:88 +msgid "" +"Now that the test upgraded database is available on your staging branch, " +"**thoroughly test it** and make sure everything runs as it's supposed to. " +"Once you are satisfied with the result, you are ready to upgrade your " +"production database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:93 +msgid "Production upgrade" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:95 +msgid "" +"Once you are happy with your testing, you can start the process on the " +":guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:98 +msgid "" +"On your :guilabel:`Production` branch, go to the :guilabel:`Upgrade` tab, " +"select the :guilabel:`targeted version` and click on the :guilabel:`start " +"Upgrade` button." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst-1 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:105 +msgid "" +"The actual process is **triggered as soon as you push a new commit** in your" +" branch. Make sure you are pushing code that is compatible with the new " +"version. For example by merging the code from your upgraded staging branch." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:110 +msgid "" +"You can see the progress of the upgrade by going to the :guilabel:`Upgrade` " +"tab of the main branch." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst-1 +msgid "View showing the progress of the upgrade" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:118 +msgid "Your database is unavailable throughout the process." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:121 +msgid "" +"If anything goes wrong, the platform automatically reverts the upgrade, the " +"same as it would be for a regular update. In case of success, a backup is " +"always made." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:124 +msgid "" +"The update of your custom modules must be successful to complete the entire " +"upgrade process. Make sure the status of your staging upgrade is " +":guilabel:`successful` before trying it in production." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:6 +msgid "Test upgrade request" +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:8 +msgid "There are two ways to create your upgrade request." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:11 +msgid "Upgrade request via command line" +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:13 +msgid "" +"For technically-advanced users and partners, the upgrade process can be " +"initiated via the following command line on the server where the database is" +" hosted:" +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:16 +msgid "" +":command:`python <(curl -s https://upgrade.odoo.com/upgrade) test -d -t `" +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:19 +msgid "" +"The above command creates the database dump, sends it to the upgrade " +"platform, and initiates the automated upgrade process. During the upgrade, " +"you can follow the live logs on your screen. Once the upgrade process is " +"completed successfully, the upgraded database is restored onto the server " +"(as a duplicate test database)." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:25 +msgid "Upgrade request via the Odoo Upgrade Portal" +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:27 +msgid "" +"Download a recent copy of your database and select the option " +":guilabel:`pg_dump custom format (without filestore)`." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:29 +msgid "" +"Upload this dump file at https://upgrade.odoo.com and select *Testing* as " +"the aim. Odoo performs the automated upgrade process. Once it is completed, " +"you receive an email with a link to download the upgrade database dump file." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:32 +msgid "" +"Import the upgraded database into your on-premise environment and manually " +"test all processes and workflows." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:36 +msgid "" +"For security reasons, only the person who submitted the upgrade request is " +"able to download it." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:37 +msgid "" +"Any problem found during testing should be reported via the `helpdesk " +"`_." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:41 +msgid "Upgrade your production database" +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:43 +msgid "" +"Once you have completed the testing successfully, you can proceed to upgrade" +" your live database in production. Download your upgraded database from the " +"link in the email and import it onto your live environment." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:48 +msgid "Custom modules (if applicable)" +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:50 +msgid "" +"The upgrade of a database that contains custom modules is a two-step " +"process." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:52 +msgid "The standard upgrade is done when your upgrade request is completed." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:53 +msgid "" +"Your custom modules also need to be upgraded to keep them compatible with " +"the new version." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:55 +msgid "" +"Depending on your contract, the upgrade of your custom modules can be done" +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:57 +msgid "by yourself." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:58 +msgid "by your Partner." +msgstr "" + +#: ../../content/administration/upgrade/on_premise.rst:59 +msgid "" +"by Odoo (if you hold a subscription to 'Maintenance of Customizations')." +msgstr "" diff --git a/locale/pl/LC_MESSAGES/applications.po b/locale/pl/LC_MESSAGES/applications.po new file mode 100644 index 000000000..970255960 --- /dev/null +++ b/locale/pl/LC_MESSAGES/applications.po @@ -0,0 +1,26 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-11-02 08:37+0000\n" +"PO-Revision-Date: 2021-11-02 08:46+0000\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications.rst:9 +msgid "User Docs" +msgstr "" + +#: ../../content/applications.rst:11 +msgid "Discover our user guides and configuration tutorials per application." +msgstr "" diff --git a/locale/pl/LC_MESSAGES/finance.po b/locale/pl/LC_MESSAGES/finance.po new file mode 100644 index 000000000..b7b79e455 --- /dev/null +++ b/locale/pl/LC_MESSAGES/finance.po @@ -0,0 +1,29971 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" +"PO-Revision-Date: 2021-11-02 08:47+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications/finance.rst:5 +msgid "Finance" +msgstr "Finanse" + +#: ../../content/applications/finance/accounting.rst:5 +msgid "Accounting and Invoicing" +msgstr "Księgowość i fakturowanie" + +#: ../../content/applications/finance/accounting.rst:7 +msgid "" +"**Odoo Invoicing** is a standalone invoicing app to create invoices, send " +"them to your customers, and manage payments." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:10 +msgid "" +"**Odoo Accounting** is a full featured accounting app. Accountant " +"productivity is at the core of its development with features such as AI-" +"powered invoice recognition, synchronization with your bank accounts, smart " +"matching suggestions, etc." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:15 +msgid "" +"`Odoo Tutorials: Accounting `_" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:56 +msgid "Double-entry bookkeeping" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:58 +msgid "" +"Odoo automatically creates all the underlying journal entries for all " +"accounting transactions (e.g., customer invoices, vendor bills, point-of-" +"sales orders, expenses, inventory valuations, etc.)." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:61 +msgid "" +"Odoo uses the double-entry bookkeeping system, whereby every entry needs a " +"corresponding and opposite counterpart in a different account, with one " +"account debited and the other credited. It ensures that all transactions are" +" recorded accurately and consistently and that the accounts always balance." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:67 +#: ../../content/applications/finance/accounting.rst:217 +msgid ":doc:`Accounting Cheat Sheet `" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:70 +msgid "Accrual and cash basis" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:72 +msgid "" +"Both accrual and cash basis accounting are supported in Odoo. This allows " +"reporting income and expense either when the transaction occurs (accrual " +"basis) or when the payment is made or received (cash basis)." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:77 +msgid ":doc:`Cash basis `" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:80 +msgid "Multi-company" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:82 +msgid "" +"Several companies can be managed within the same database. Each company has " +"its :doc:`chart of accounts `, " +"which is also useful to generate consolidation reports. Users can access " +"several companies but can only work on a single company's accounting at a " +"time." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:88 +msgid "Multi-currency environment" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:90 +msgid "" +"A :doc:`multi-currency ` environment " +"with an automated exchange rate to ease international transactions is " +"available in Odoo. Every transaction is recorded in the company's default " +"currency; for transactions occurring in another currency, Odoo stores both " +"the value in the company's currency and the transactions' currency value. " +"Odoo generates currency gains and losses after reconciling the journal " +"items." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:97 +msgid "" +":doc:`Manage a bank in a foreign currency " +"`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:100 +msgid "International standards" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:102 +msgid "" +"Odoo Accounting supports more than 70 countries. It provides the central " +"standards and mechanisms common to all nations, and thanks to country-" +"specific modules, local requirements are fulfilled. Fiscal positions exist " +"to address regional specificities like the chart of accounts, taxes, or any " +"other requirements." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:108 +msgid ":doc:`Fiscal localization packages `" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:111 +msgid "Accounts receivable and payable" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:113 +msgid "" +"By default, there is a single account for the account receivable entries and" +" one for the account payable entries. As transactions are linked to your " +"**contacts**, you can run a report per customer, vendor, or supplier." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:117 +msgid "" +"The **Partner Ledger** report displays the balance of your customers and " +"suppliers. It is available by going to :menuselection:`Accounting --> " +"Reporting --> Partner Ledger`." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:121 +#: ../../content/applications/finance/accounting/reporting.rst:5 +#: ../../content/applications/finance/accounting/vendor_bills.rst:120 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:123 +msgid "" +"The following financial :doc:`reports ` are available " +"and updated in real-time:" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:127 +msgid "Financial reports" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:129 +msgid "Statement" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:129 +#: ../../content/applications/finance/accounting/customer_invoices.rst:214 +msgid "Balance sheet" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:131 +#: ../../content/applications/finance/accounting/customer_invoices.rst:204 +msgid "Profit and loss" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:133 +msgid "Cash flow statement" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:135 +#: ../../content/applications/finance/accounting.rst:174 +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:77 +msgid "Tax report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:137 +msgid "ES sales list" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:139 +msgid "Audit" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:139 +msgid "General ledger" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:141 +msgid "Trial balance" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:143 +msgid "Journal report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:145 +msgid "Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:147 +msgid "Check register" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:149 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:135 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:161 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:89 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:321 +msgid "Partner" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:149 +msgid "Partner ledger" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:151 +msgid "Aged receivable" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:153 +msgid "Aged payable" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:155 +msgid "Management" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:155 +msgid "Invoice analysis" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:157 +msgid "Unrealized currency gains/losses" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:159 +msgid "Depreciation schedule" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:161 +msgid "Disallowed expenses" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:163 +msgid "Budget analysis" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:165 +msgid "Product margins" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:167 +msgid "1099 report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:171 +msgid "" +":doc:`Create and customize reports ` with " +"Odoo's report engine." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:176 +msgid "" +"Odoo computes all accounting transactions for the specific tax period and " +"uses these totals to calculate the tax obligation." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:180 +msgid "" +"Once the tax report has been generated for a period, Odoo locks it and " +"prevents the creation of new journal entries involving VAT. Any correction " +"to customer invoices or vendor bills has to be recorded in the next period." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:185 +msgid "" +"Depending on the country's localization, an XML version of the tax report " +"can be generated to be uploaded to the VAT platform of the relevant taxation" +" authority." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:189 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:5 +msgid "Bank synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:191 +msgid "" +"The bank synchronization system directly connects with your bank institution" +" to automatically import all transactions into your database. It gives an " +"overview of your cash flow without logging into an online banking system or " +"waiting for paper bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:196 +msgid ":doc:`Bank synchronization `" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:199 +msgid "Inventory valuation" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:201 +msgid "" +"Both periodic (manual) and perpetual (automated) inventory valuations are " +"supported in Odoo. The available methods are standard price, average price, " +":abbr:`LIFO (Last-In, First-Out)` and :abbr:`FIFO (First-In, First-Out).`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:206 +msgid "" +":doc:`View the impact of the valuation methods on transactions " +"<../inventory_and_mrp/inventory/management/reporting/inventory_valuation_config>`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:210 +msgid "Retained earnings" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:212 +msgid "" +"Retained earnings are the portion of income retained by a business. Odoo " +"calculates current year earnings in real-time, so no year-end journal or " +"rollover is required. The profit and loss balance is automatically reported " +"on the balance sheet report." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:220 +msgid "Fiduciaries" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:222 +msgid "" +"The :guilabel:`Accounting Firms` mode can be activated by going to " +":menuselection:`Accounting --> Configuration --> Settings --> Accounting " +"Firms mode`. When enabled:" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:225 +msgid "The document's sequence becomes editable on all documents;" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:226 +msgid "" +"The :guilabel:`Total (tax incl.)` field appears to speed up and control the " +"encoding by automating line creation with the right account and tax;" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:228 +msgid "" +":guilabel:`Invoice Date` and :guilabel:`Bill Date` are pre-filled when " +"encoding a transaction." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:229 +msgid "" +"A :guilabel:`Quick encoding` option is available for customer invoices and " +"vendor bills." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:5 +msgid "Bank and cash accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:7 +msgid "" +"You can manage as many bank or cash accounts as needed on your database. " +"Configuring them well allows you to have all your banking data up-to-date " +"and ready for :doc:`reconciliation ` with your journal " +"entries." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:11 +msgid "" +"In Odoo Accounting, each bank account has a dedicated journal set to post " +"all entries in a dedicated account. Both the journal and the account are " +"automatically created and configured whenever you add a bank account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:16 +msgid "Cash journals and accounts must be configured manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:18 +msgid "" +"Bank journals are displayed by default on the :guilabel:`Accounting " +"Dashboard` in the form of cards which include action buttons." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "" +"Bank journals are displayed on the Accounting Dashboard and contain action " +"buttons" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:27 +msgid "Manage your bank and cash accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:30 +msgid "Connect your bank for automatic synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:32 +msgid "" +"To connect your bank account to your database, go to " +":menuselection:`Accounting --> Configuration --> Banks: Add a Bank Account`," +" select your bank in the list, click on :guilabel:`Connect`, and follow the " +"instructions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:37 +#: ../../content/applications/finance/accounting/bank.rst:133 +#: ../../content/applications/finance/accounting/get_started.rst:188 +msgid ":doc:`bank/bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:40 +msgid "Create a bank account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:42 +msgid "" +"If your banking institution is not available in Odoo, or if you don't want " +"to connect your bank account to your database, you can configure your bank " +"account manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:45 +msgid "" +"To manually add a bank account, go to :menuselection:`Accounting --> " +"Configuration --> Banks: Add a Bank Account`, click on :guilabel:`Create it`" +" (at the bottom right), and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:49 +msgid "" +"Odoo automatically detects the bank account type (e.g., IBAN) and enables " +"some features accordingly." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:51 +msgid "" +"A default bank journal is available and can be used to configure your bank " +"account by going to :menuselection:`Accounting --> Configuration --> " +"Accounting: Journals --> Bank`. Open it and edit the different fields to " +"match your bank account information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:56 +msgid "Create a cash journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:58 +msgid "" +"To create a new cash journal, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals`, click on :guilabel:`Create` and " +"select :guilabel:`Cash` in the :guilabel:`Type` field." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:61 +msgid "" +"For more information on the accounting information fields, read the " +":ref:`bank_accounts/configuration` section of this page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:65 +msgid "" +"A default cash journal is available and can be used straight away. You can " +"review it by going to :menuselection:`Accounting --> Configuration --> " +"Accounting: Journals --> Cash`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:69 +msgid "Edit an existing bank or cash journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:71 +msgid "" +"To edit an existing bank journal, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals` and select the journal you want to " +"modify." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:77 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:28 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:21 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:24 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:22 +#: ../../content/applications/finance/accounting/bank/cash_register.rst:9 +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:16 +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:16 +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:67 +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:14 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:59 +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:21 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:46 +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:12 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:15 +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:22 +#: ../../content/applications/finance/accounting/payments/batch.rst:15 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:20 +#: ../../content/applications/finance/accounting/payments/follow_up.rst:14 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:9 +#: ../../content/applications/finance/accounting/payments/online.rst:14 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:10 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:45 +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:18 +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:16 +#: ../../content/applications/finance/accounting/reporting/budget.rst:11 +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 +#: ../../content/applications/finance/accounting/taxes.rst:53 +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:14 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:17 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:27 +#: ../../content/applications/finance/accounting/taxes/retention.rst:23 +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:13 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:22 +#: ../../content/applications/finance/fiscal_localizations.rst:21 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:14 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:18 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:104 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:29 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:290 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:332 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:32 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:58 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:8 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:8 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:6 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:78 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:25 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:6 +#: ../../content/applications/finance/payment_acquirers.rst:226 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:17 +#: ../../content/applications/finance/payment_acquirers/alipay.rst:9 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:9 +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:9 +#: ../../content/applications/finance/payment_acquirers/mollie.rst:8 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:141 +#: ../../content/applications/finance/payment_acquirers/sips.rst:9 +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:30 +msgid "Configuration" +msgstr "Konfiguracja" + +#: ../../content/applications/finance/accounting/bank.rst:79 +msgid "" +"You can edit the accounting information and bank account number according to" +" your needs." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "Manually configure your bank information" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:85 +#: ../../content/applications/finance/accounting/bank.rst:107 +msgid ":doc:`get_started/multi_currency`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:86 +#: ../../content/applications/finance/accounting/bank.rst:134 +msgid ":doc:`bank/bank_statements`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:89 +msgid "Suspense account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:91 +msgid "" +"Bank statement transactions are posted on the :guilabel:`Suspense Account` " +"until the final reconciliation allows finding the right account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:95 +msgid "Profit and loss accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:97 +msgid "" +"The :guilabel:`Profit Account` is used to register a profit when the ending " +"balance of a cash register differs from what the system computes, while the " +":guilabel:`Loss Account` is used to register a loss when the ending balance " +"of a cash register differs from what the system computes." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:102 +msgid "Currency" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:104 +msgid "You can edit the currency used to enter the statements." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:110 +msgid "Account number" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:112 +msgid "" +"If you need to **edit your bank account details**, click on the external " +"link arrow next to your :guilabel:`Account Number`. On the new page, click " +"on the external link arrow next to your :guilabel:`Bank` and update your " +"bank information accordingly. These details are used when registering " +"payments." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "Edit your bank information" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:121 +msgid "Bank feeds" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:123 +msgid "" +":guilabel:`Bank Feeds` defines how the bank statements are registered. Three" +" options are available:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:125 +msgid "" +":guilabel:`Undefined yet`, which should be selected when you don’t know yet " +"if you will synchronize your bank account with your database or not." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:127 +msgid "" +":guilabel:`Import (CAMT, CODA, CSV, OFX, QIF)`, which should be selected if " +"you want to import your bank statement using a different format." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:129 +msgid "" +":guilabel:`Automated Bank Synchronization`, which should be selected if your" +" bank is synchronized with your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:139 +msgid "Outstanding accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:141 +msgid "" +"By default, payments are registered through transitory accounts named " +"**outstanding accounts**, before being recorded in your bank account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:144 +msgid "" +"An **outstanding payments account** is where outgoing payments are posted " +"until they are linked with a withdrawal from your bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:146 +msgid "" +"An **outstanding receipts account** is where incoming payments are posted " +"until they are linked with a deposit from your bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:149 +msgid "" +"These accounts should be of :ref:`type ` " +":guilabel:`Current Assets`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:152 +msgid "" +"The movement from an outstanding account to a bank account is done " +"automatically when you reconcile the bank account with a bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:156 +msgid "Default accounts configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:158 +msgid "" +"The outstanding accounts are defined by default. If necessary, you can " +"update them by going to :menuselection:`Accounting --> Configuration --> " +"Settings --> Default Accounts` and update your :guilabel:`Outstanding " +"Receipts Account` and :guilabel:`Outstanding Payments Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:163 +msgid "Bank and cash journals configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:165 +msgid "" +"You can also set specific outstanding accounts for any journal with the " +":ref:`type ` :guilabel:`Bank` or :guilabel:`Cash`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:168 +msgid "" +"From your :guilabel:`Accounting Dashboard`, click on the menu selection ⋮ of" +" the journal you want to configure, and click on :guilabel:`Configuration`, " +"then open the :guilabel:`Incoming/Outgoing Payments` tab. To display the " +"outstanding accounts column, click on the toggle button and check the " +":guilabel:`Outstanding Receipts/Payments accounts`, then update the account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "Select the toggle button and click on outstanding Accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:178 +msgid "" +"If you do not specify an outstanding payments account or an outstanding " +"receipts account for a specific journal, Odoo uses the default outstanding " +"accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:180 +msgid "" +"If your main bank account is added as an outstanding receipts account or " +"outstanding payments account, when a payment is registered, the invoice or " +"bill's status is directly set to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:3 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:143 +msgid "Bank statements" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:5 +msgid "" +"Importing your bank statements allows you to keep track of your bank account" +" transactions and reconcile them with the ones recorded in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:8 +msgid "" +"We recommend using :doc:`the bank synchronization feature " +"` for more efficiency. However, if you do not want to " +"use it or if your bank is not yet supported, other options exist:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:12 +msgid "Import the bank statement files delivered by your bank;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:13 +msgid "Register the bank statements manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:16 +msgid "Import bank statements files" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:18 +msgid "Odoo supports multiple file formats to import bank statements:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:20 +msgid "SEPA recommended Cash Management format (CAMT.053);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:21 +msgid "Comma-separated values (.CSV);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:22 +msgid "Open Financial Exchange (.OFX);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:23 +msgid "Quicken Interchange Format (.QIF);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:24 +msgid "Belgium: Coded Statement of Account (.CODA)." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:26 +msgid "" +"To import a file, go to the Accounting dashboard and click on " +":guilabel:`Import (Statements)` under the :guilabel:`Bank` window, or click " +"on the drop-down menu (:guilabel:`⋮`) button and then on :guilabel:`Import " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst-1 +msgid "Import a bank statement file in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:34 +msgid "" +"Next, select the file you want to import and click on :guilabel:`Upload`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:36 +msgid "" +"Once the file uploaded, the **import widget** helps you set formatting " +"options and **map** the different columns you want to import. You also can " +":guilabel:`test` the bank statement file before importing it to your " +"database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst-1 +msgid "Register bank statements manually in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:45 +msgid "Register bank statements manually" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:47 +msgid "" +"If needed, you can also record your bank statements manually. To do so, go " +"to the :guilabel:`Accounting dashboard` and click on the :guilabel:`Create " +"Statements` under the :guilabel:`Bank` window. Alternatively, you can click " +"the drop-down menu (:guilabel:`⋮`) button, and then :guilabel:`New " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:52 +msgid "" +"To ease the reconciliation process, make sure to fill out the " +":guilabel:`Partner` field. You can also type in the payments’ references in " +"the :guilabel:`Label` field. Add a new line for each transaction written on " +"the original bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_statements.rst:61 +msgid "" +"The **Ending Balance** and the **Computed Balance** should have the same " +"amount. If this is not the case, make sure there are no mistakes in the " +"transactions’ amounts." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:7 +msgid "" +"Odoo can synchronize directly with your bank institution to get all bank " +"statements imported automatically into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:10 +msgid "" +"To check if your bank is compatible with Odoo, go to `Odoo Accounting " +"Features `_, and click on " +":guilabel:`See list of supported institutions`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:14 +msgid "Odoo supports more than 25,000 institutions around the world." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:16 +msgid "To connect to the banks, Odoo uses multiple web-services:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:18 +msgid "**Plaid**: United States of America and Canada" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:19 +msgid "**Yodlee**: Worldwide" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:20 +msgid ":doc:`Salt Edge `: Worldwide" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:21 +msgid ":doc:`Ponto `: Europe" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:22 +msgid "" +":doc:`Enable Banking `: Scandinavian " +"countries" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:25 +msgid ":doc:`bank_statements`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:31 +msgid "On-Premise users" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:33 +msgid "" +"To be able to use this service, you need to have a valid Odoo Enterprise " +"subscription. So make sure that your database is registered with your Odoo " +"Enterprise contract. We also use a proxy between your database and the third" +" party provider so, in case of a connection error, please check that you " +"don't have a firewall or a proxy blocking the following address:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:39 +msgid "https://production.odoofin.com/" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:42 +msgid "First synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:44 +msgid "" +"You can start synchronization either by going to the Accounting app and " +":menuselection:`Accounting Dashboard --> Configuration --> Banks: Add a Bank" +" Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:47 +msgid "" +"Now you can search for your bank institution. Select it and follow the steps" +" to synchronize with it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:50 +msgid "" +"If you have any issues during your first synchronization, please verify that" +" your web browser doesn't block pop-ups and that your ad-blocker is " +"disabled." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:54 +msgid "" +"When choosing the date for the first bank statement synchronization, pick " +"the date when you start recording accounting transaction on your Odoo " +"accounting database. For example, if you import your closing balance in Odoo" +" on the 31/12/2022 and you start recording accounting transactions on the " +"01/01/2023, your synchronization date should be 01/01/2023." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:59 +msgid "" +"You must provide a phone number during your first synchronization to secure " +"your account. We ask for such information because we don't want your data " +"falling into the wrong hands. Therefore, if we detect suspicious activities " +"on your account, we block all requests coming from your account, and you " +"need to reactivate it using that phone number." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:64 +msgid "" +"The third-party provider may request more information in order to connect " +"with your bank institution. This information is not stored on Odoo's " +"servers." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:68 +msgid "" +"By default, transactions fetched from an online source are grouped inside " +"the same statement, and one bank statement is created per month. You can " +"change the bank statement creation periodicity in your journal settings." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:72 +msgid "" +"You can find all your synchronizations by going to " +":menuselection:`Accounting Dashboard --> Configuration --> Accounting: " +"Online Synchronization`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:76 +msgid "Synchronize manually" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:78 +msgid "" +"After your first synchronization, the created journals are synchronized by " +"default every 12 hours. If you wish, you can synchronize manually by " +"clicking on the :guilabel:`Synchronize Now` button on the dashboard." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:82 +msgid "" +"Or you can go to :menuselection:`Accounting Dashboard --> Configuration --> " +"Accounting: Online Synchronization`, select your institution and then click " +"on the :guilabel:`fetch transactions` button." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:87 +msgid "" +"Some institutions do not allow transactions to be fetched automatically. For" +" such institutions, during the automatic synchronization of the account, you" +" receive an error message asking you to disable the automatic " +"synchronization. This message can be found in the chatter of your online " +"synchronizations. In this case, make sure to perform manual " +"synchronizations." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:93 +msgid "Issues" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:96 +msgid "Synchronization in error" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:98 +msgid "" +"To report a connection error to the `Odoo support " +"`_, go to :menuselection:`Accounting Dashboard-->" +" Configuration --> Accounting: Online Synchronization`, select the " +"connection that failed, and copy the error description and the reference." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:103 +msgid "Synchronization disconnected" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:105 +msgid "" +"If your connection with the proxy is disconnected, you can reconnect with " +"the proxy using the :guilabel:`Fetch Account` button." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:109 +msgid "" +"This disconnection can be caused by the Odoo support. In this case, please " +"contact the `support `_ directly with your client" +" id or the reference of the error listed in the chatter." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:116 +msgid "Migration process for users having installed Odoo before December 2020" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:118 +msgid "" +"If you are on-premise, please first make sure that your source is up-to-date" +" with the latest version of Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:121 +msgid "" +"Users who have created a database before December 2020 need to install the " +"new module manually to use the new functionalities." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:124 +msgid "" +"To do so, go to :menuselection:`Apps --> Update Apps List`, remove the " +"default filter in the search bar and type `account_online_synchronization`. " +"You can then click on :guilabel:`Install`. Finally, make sure all your users" +" refresh their Odoo page by pressing CTRL+F5." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:130 +msgid "" +"All previous synchronizations are disconnected during the installation and " +"won't work anymore." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:131 +msgid "" +"You can find them directly in the synchronization menu " +"(:menuselection:`Accounting Dashboard --> Configuration --> Accounting: " +"Online Synchronization`). It is not possible to resynchronize these " +"connections; you have to make new ones." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:135 +msgid "" +"Do not uninstall `account_online_sync`, which is the previous module for " +"online synchronization. The new one overrides it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:137 +msgid "" +"By default, `account_online_synchronization` is installed automatically with" +" Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:140 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:95 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:81 +msgid "FAQ" +msgstr "FAQ" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:143 +msgid "The synchronization is not working in real-time. Is that normal?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:145 +msgid "" +"The process is not intended to work in real-time as third party providers " +"synchronize your accounts at different intervals. To force the " +"synchronization and fetch the statements, go to your :guilabel:`Accounting " +"Dashboard`, and click on the :guilabel:`Synchronize Now` button. You can " +"also synchronize and fetch transactions through :menuselection:`Accounting " +"Dashboard --> Configuration --> Accounting: Online Synchronization`. Some " +"providers only allow one refresh per day, so it is possible that clicking on" +" :guilabel:`Synchronize Now` does not get your latest transactions if you " +"already performed such action earlier in the day." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:153 +msgid "" +"A transaction can be visible on your bank account but not be fetched if it " +"has the status :guilabel:`Pending`. Only transactions with the " +":guilabel:`Posted` status will be retrieved. If the transaction is not " +"**Posted** yet, you will have to wait until the status changes." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:158 +msgid "Is the Online Bank Synchronization feature included in my contract?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:160 +msgid "" +"**Community Version**: No, this feature is not included in the Community " +"Version." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:161 +msgid "" +"**Online Version**: Yes, even if you benefit from the One App Free contract." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:162 +msgid "" +"**Enterprise Version**: Yes, if you have a valid enterprise contract linked " +"to your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:165 +msgid "Some banks have a status \"Beta.\" What does this mean?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:167 +msgid "" +"This means that banking institutions are not yet fully supported by our " +"Third Party Provider. Bugs or other problems may arise. Odoo does not " +"support technical problems that occur with banks in the Beta phase, but the " +"user may still choose to connect. Connecting with these banks contributes to" +" the development process since the Provider will have real data and feedback" +" from the connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:173 +msgid "Why do my transactions only synchronize when I refresh manually?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:175 +msgid "" +"Some banks have additional security measures and require extra steps, such " +"as an SMS/email authentication code or another type of MFA. Because of this," +" the integrator cannot pull transactions until the security code is " +"provided." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:180 +msgid "Not all of my past transactions are in Odoo, why?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:182 +msgid "" +"For some institutions, transactions can only be fetched up to 3 months in " +"the past." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:185 +msgid "Why don't I see any transactions?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:187 +msgid "" +"During your first synchronization, you selected the bank accounts you " +"decided to synchronize with Odoo. If you didn't synchronize any of your " +"accounts, you can go to :menuselection:`Accounting Dashboard --> " +"Configuration --> Accounting: Online Synchronization` to click on the " +":guilabel:`Fetch Account` button on the connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:192 +msgid "There may also be no new transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:194 +msgid "" +"If your bank account is properly linked to a journal and posted transactions" +" are not visible in your database, please `submit a support ticket " +"`_." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:198 +msgid "How can I update my bank credentials?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:200 +msgid "" +"You can update your credentials by going to :menuselection:`Accounting " +"Dashboard --> Configuration --> Accounting: Online Synchronization`,open the" +" connection you want to update your credentials and click on the " +":guilabel:`Update Credentials` button." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:3 +msgid "Enable Banking" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:5 +msgid "" +"**Enable Banking** is a third-party provider aggregating banking information" +" from bank accounts all in one place. It offers non-intrusive connectivity " +"to ASPSPs' official APIs across Europe without storing data." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst-1 +msgid "Enable Banking logo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:13 +msgid "" +"**Odoo** synchronizes directly with banks to get access to all bank " +"transactions and automatically import them into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:17 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:20 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:18 +msgid ":doc:`../bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:18 +msgid "`Enable Banking website `_" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:24 +msgid "Link bank accounts with Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:26 +msgid "" +"Start synchronization by clicking on :menuselection:`Accounting --> " +"Configuration --> Add a Bank Account`;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:28 +msgid "Select your bank;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:29 +msgid "" +"Make sure you give your consent to share your account information with Odoo " +"by clicking :guilabel:`Continue authentication`;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:0 +msgid "Enable Banking authentication page" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:36 +msgid "Finally, you are redirected to your bank's login page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:3 +msgid "Ponto" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:5 +msgid "" +"**Ponto** is a service that allows companies and professionals to aggregate " +"their accounts in one place and directly see all their transactions within " +"one app. It is a third-party solution that is continuously expanding the " +"number of bank institutions that can be synchronized with Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst-1 +msgid "Logo of the Ponto brand" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:13 +msgid "" +"**Odoo** can synchronize directly with your bank to get all bank statements " +"imported automatically into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:16 +msgid "" +"Ponto is a paid third-party provider that can handle the synchronization " +"between your bank accounts and Odoo. `Its pricing is 4€/month per " +"account/integration `_." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:21 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:19 +msgid ":doc:`../bank_statements`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:27 +msgid "Link your bank accounts with Ponto" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:29 +msgid "Go to `Ponto's website (https://myponto.com) `_." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:30 +msgid "Create an account if you don't have one yet." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:31 +msgid "Once you are logged in, create an *organization*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Fill out the form to add an organization in Ponto." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Go to :menuselection:`Accounts --> Live`, and click on *Add account*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "You might have to add your **Billing Information** first." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:39 +msgid "" +"Select your country, your bank institutions, give your consent to Ponto, and" +" follow the steps on-screen to link your bank account with your Ponto " +"account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Add bank accounts to your Ponto account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:46 +msgid "" +"Make sure to add all bank accounts you want to synchronize with your Odoo " +"database before moving on to the next steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:50 +msgid "Link your Ponto account with your Odoo database" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:52 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Add a Bank Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:53 +msgid "" +"Search your institution, make sure to select the right institution. By " +"selecting the institution, you can verify that the third party provider is " +"Ponto." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:55 +msgid "Click on *Connect* and follow the steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:56 +msgid "" +"At some point, you will have to authorize the accounts you want to access in" +" Odoo. Please select **all the accounts** you want to synchronize. Even the " +"ones coming from other banking institutions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Selection of the accounts you wish to synchronize with Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:64 +msgid "Finish the flow." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:67 +msgid "" +"You have to authorize all the accounts you want to access in Odoo, but Odoo " +"will filter the accounts based on the institution you selected in the second" +" step." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:71 +msgid "Update your synchronization credentials" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:73 +msgid "" +"You might have to update your Ponto credentials or modify the " +"synchronization settings." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:75 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:87 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Online " +"Synchronization` and select the institution you want to fetch the other " +"accounts. Click on *Fetch Accounts* button to start the flow." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:79 +msgid "" +"During the update, select **all the accounts** you want to synchronize, even" +" the ones coming from other banking institutions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:83 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:69 +msgid "Fetch new accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:85 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:71 +msgid "You might want to add new online accounts to your connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:91 +msgid "" +"Don't forget to keep authorization for existing accounts (for all " +"institutions that you have synchronized with Ponto)." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:98 +msgid "After my synchronization, no account appears" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:100 +msgid "" +"You selected an institution from the list and did not authorize any accounts" +" from this institution." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:103 +msgid "I have an error about that my authorization has expired" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:105 +msgid "" +"Every **3 months** (90 days) you must re-authorize the connection between " +"your bank account and Ponto. This must be done from the `Ponto website " +"`_. If you do not do this, the synchronization will " +"stop for these accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:110 +msgid "I have some errors with my beta institution" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:112 +msgid "" +"Ponto provides institutions in *beta*, these institutions are not directly " +"supported by Odoo and we advise you to contact Ponto directly." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:116 +msgid "" +"Using an institution in beta is beneficial for Ponto, it allows them to have" +" real feedback on the connection with the institution." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:3 +msgid "Salt Edge" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:5 +msgid "" +"**Salt Edge** is a third-party provider that aggregates banking information " +"from your bank accounts. It supports ~5000 institutions in more than 50 " +"countries." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst-1 +msgid "Salt Edge Logo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:14 +msgid "" +"Odoo can synchronize directly with your bank to get all bank statements " +"imported automatically into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:25 +msgid "Link your bank accounts with Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:27 +msgid "" +"Start synchronization by clicking on :menuselection:`Accounting --> " +"Configuration --> Add a Bank Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:29 +msgid "" +"Select the institution you want to synchronize. You can see if Salt Edge is " +"the third party provider of the institution by selecting it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:31 +msgid "" +"After giving your phone number, you are asked for an email address. This " +"email address is used to create your Salt Edge account. Please make sure you" +" enter a valid email address, as otherwise, you will not be able to access " +"your Salt Edge account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 +msgid "" +"Email address to provide to Salt Edge for the creation of your account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:40 +msgid "" +"After entering your email address, you are redirected to Salt Edge to " +"continue the synchronization process." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 +msgid "Salt Edge Login page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:47 +msgid "Make sure you give your consent by checking the consent checkbox." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 +msgid "Salt Edge give consent page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:53 +msgid "Complete the synchronization by following the steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:57 +msgid "Update your credentials" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:59 +msgid "" +"You might have to update your Salt Edge credentials or modify the " +"synchronization settings." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:61 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Online " +"Synchronization` and select the institution you want to update credentials. " +"Click on the *Update Credentials* button to start the flow and follow the " +"steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:65 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:77 +msgid "" +"Don't forget to check the consent checkbox. Otherwise, Odoo may not be able " +"to access your information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:73 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Online " +"Synchronization` and select the institution to fetch the new accounts. Click" +" on the *Fetch Accounts* button to start the flow and follow the steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:84 +msgid "I have an error when I try to delete my synchronization within Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:86 +msgid "" +"Odoo can't permanently delete the connection you have created with the " +"banking institution. However, it can revoke the consent you gave so that " +"Odoo won't be able to access your account anymore. The error you are seeing " +"is probably a message telling you that the consent was revoked, but the " +"record could not be deleted as it still exists within Salt edge. If you want" +" to remove the connection completely, please connect to your `Salt Edge " +"account `_ and manually delete your " +"synchronization. Once this is done, you can go back to Odoo to delete the " +"record." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:95 +msgid "I have an error saying that I have already synchronized this account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:97 +msgid "" +"You have probably already synchronized your bank account with Salt Edge, " +"please check on your `dashboard `_ that " +"you don't already have a connection with the same credentials." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:101 +msgid "" +"In case you already have a synchronization with the same credentials present" +" on your Salt Edge dashboard and this synchronization has not been created " +"with Odoo, please delete it and create it from your Odoo database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:105 +msgid "" +"In case you already have a connection with the same credentials present on " +"your Salt Edge dashboard and this synchronization was created with Odoo, you" +" will normally be able to find it by going to :menuselection:`Accounting -->" +" Configuration --> Online Synchronization`. Please make sure to do an " +"*Update Credentials* to reactivate the connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:3 +msgid "Cash register" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/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 "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:14 +msgid "" +"Configure the Cash journal in :menuselection:`Accounting --> Configuration " +"--> Journals`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/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 "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:21 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:262 +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:34 +msgid "Usage" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:24 +msgid "How to register cash payments?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:26 +msgid "" +"To register a cash payment specific to another customer, you should follow " +"these steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:29 +msgid "" +"Go to :menuselection:`Accounting --> Dashboard --> Cash --> Register " +"Transactions`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:32 +msgid "Fill in the start and ending balance" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:34 +msgid "" +"Register the transactions, specifying the customers linked to the " +"transaction" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:37 +msgid "Put money in" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:39 +msgid "" +"Put money in is used to placed your cash manually before starting your " +"transactions. From the Register Transactions window, go to " +":menuselection:`More --> Put money in`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:47 +msgid "Take money out" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:49 +msgid "" +"Take money out is used to collect/get yor your cash manually after ending " +"all your transactions. From the Register Transaction windows, go to " +":menuselection:`More --> Take money out`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:56 +msgid "" +"The transactions will be added to the current cash payment registration." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:3 +msgid "Manage a bank account in a foreign currency" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:5 +msgid "" +"In Odoo, every transaction is recorded in the default currency of the " +"company, and reports are all based on that default currency. When you have a" +" bank account in a foreign currency, for every transaction, Odoo stores two " +"values:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:9 +msgid "The debit/credit in the currency of the *company*;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:10 +msgid "The debit/credit in the currency of the *bank account*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:12 +msgid "" +"Currency rates are updated automatically using the web services of a banking" +" institution. By default, Odoo uses the European Central Bank's web services" +" but other options are available." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:19 +msgid "Activate multi-currencies" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:21 +msgid "" +"To work with multiple currencies, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies` and tick :guilabel:`Multi-" +"Currencies`. Under :guilabel:`Post Exchange difference entries in:`, provide" +" a :guilabel:`Journal`, a :guilabel:`Gain Account`, a :guilabel:`Loss " +"Account`, and then click on :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:27 +msgid "Configure currencies" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:29 +msgid "" +"Once Odoo is configured to support multiple currencies, they are all created" +" by default, but not necessarily active. To activate the new currencies, " +"click on :guilabel:`Activate Other Currencies` under the :guilabel:`Multi-" +"Currencies` setting or go to :menuselection:`Accounting --> Configuration " +"--> Accounting: Currencies`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:34 +msgid "" +"When the currencies are activated, you can choose to **automate** the " +"currency rate update, or leave it on **manual**. To configure the rate " +"update, go back to :menuselection:`Accounting --> Configuration --> Settings" +" --> Currencies`, check :guilabel:`Automatic Currency Rates`, set " +":guilabel:`Interval` to your desired frequency, and then click on " +":guilabel:`Save`. You also have the option to choose the :guilabel:`Service`" +" you wish to obtain currency rates from." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:40 +msgid "" +"Click on the Update now button (:guilabel:`🗘`) besides the :guilabel:`Next " +"Run` field to update the currency rates manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:44 +msgid "Create a new bank account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:46 +msgid "" +"In the accounting application, go to :menuselection:`Accounting --> " +"Configuration --> Journals` and create a new one. Enter a :guilabel:`Journal" +" Name` and set the :guilabel:`Type` to `Bank`. In the :guilabel:`Journal " +"Entries` tab, enter a **short code**, a **currency**, and then finally click" +" on the :guilabel:`Bank Account` field to create a new account. In the pop-" +"up window of the account creation, enter a name, a code (ex.: 550007), set " +"its type to `Bank and Cash`, set a currency type, and save. When you are " +"back on the **journal**, click on the :guilabel:`Account Number` field, and " +"in the pop-up window, fill out the :guilabel:`Account Number`, " +":guilabel:`Bank` of your account, and save." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Example of a created bank journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:59 +msgid "" +"Upon creation of the journal, Odoo automatically links the bank account to " +"the journal. It can be found under :menuselection:`Accounting --> " +"Configuration --> Accounting: Chart of Accounts`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:63 +msgid "Vendor bill in a foreign currency" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:65 +msgid "" +"To pay a bill in a foreign currency, simply select the currency next to the " +":guilabel:`Journal` field and register the payment. Odoo automatically " +"creates and posts the foreign **exchange gain or loss** as a new journal " +"entry." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "How to set a bill currency." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:74 +msgid "" +"Note that you can pay a foreign bill with another currency. In that case, " +"Odoo automatically converts between the two currencies." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:78 +msgid "Unrealized Currency Gains/Losses Report" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:80 +msgid "" +"This report gives an overview of all unrealized amounts in a foreign " +"currency on your balance sheet, and allows you to adjust an entry or " +"manually set an exchange rate. To access this report, go to " +":menuselection:`Reporting --> Management: Unrealized Currency Gains/Losses`." +" From here, you have access to all open entries in your **balance sheet**." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "View of the Unrealized Gains/Losses journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:89 +msgid "" +"If you wish to use a different currency rate than the one set in " +":menuselection:`Accounting --> Configuration --> Settings --> Currencies`, " +"click the :guilabel:`Exchange Rates` button and change the rate of the " +"foreign currencies in the report." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Menu to manually change exchange rates." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:97 +msgid "" +"When manually changing **exchange rates**, a yellow banner appears allowing " +"you to reset back to Odoo's rate. To do so, simply click on :guilabel:`Reset" +" to Odoo's Rate`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Banner to reset back to Odoo's rates." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:104 +msgid "" +"In order to update your **balance sheet** with the amount of the " +":guilabel:`adjustment` column, click on the :guilabel:`Adjustment Entry` " +"button. In the pop-up window, select a :guilabel:`Journal`, " +":guilabel:`Expense Account` and :guilabel:`Income Account` to calculate and " +"process the **unrealized gains and losses**." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:109 +msgid "" +"You can set the date of the report in the :guilabel:`Date` field. Odoo " +"automatically reverses the booking entry to the date set in " +":guilabel:`Reversal Date`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:112 +msgid "" +"Once posted, the :guilabel:`adjustment` column should indicate `0.00`, " +"meaning all **unrealized gains/losses** have been adjusted." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Unrealized Currency Gains/Losses report once adjusted." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:3 +msgid "Bank reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:6 +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:6 +#: ../../content/applications/finance/accounting/reporting/customize.rst:6 +msgid "Overview" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:8 +msgid "" +"Matching your bank statements with your accounting records can be a tedious " +"task. You need to find the corresponding invoices, compare the amounts and " +"partners' details with those in the bank statement. These steps can take a " +"lot of time. Luckily, with Odoo you can very easily match your invoices or " +"any other payment document with your bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:10 +msgid "Two options of the reconciliation process exist in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:12 +msgid "We can directly specify the payment on the invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:13 +msgid "We can reconcile open invoices with bank statements" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:18 +msgid "" +"No special configuration is necessary to record invoices. All we need to do " +"is to install the accounting app." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:24 +msgid "Use cases" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:27 +msgid "Case 1: Payments registration" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:29 +msgid "" +"We received the proof of payment of our invoice in the amount of 2100 euros " +"issued to Smith & Co." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:32 +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 bank statements at the end of week, so we have to mark this " +"invoice as paid immediately in order to indicate that we can start rendering" +" services to our customer." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:38 +msgid "" +"Our customer send us a payment confirmation. We can thus register a payment " +"and mark the invoice as paid." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:43 +msgid "" +"By clicking on **register payment,** we are telling Odoo that our customer " +"has paid the Invoice. We thus have to specify the amount and the payment " +"method." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:49 +msgid "" +"Now we can always find the payment details in the Invoice by clicking on the" +" :menuselection:`Info --> Open Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:54 +msgid "" +"The invoice has been paid and **the reconciliation has been done " +"automatically.**" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:58 +msgid "Case 2: Bank statements reconciliations" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:60 +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 "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:65 +msgid "" +"We receive our bank statement and find that not only the invoice issued to " +"Smith & Co has been paid, but the one to Buzz of 92 euros as well." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:68 +msgid "" +"**Import** or **Create** the bank statements. Please refer to the documents " +"from the Bank Feeds section." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:73 +msgid "On the dashboard, click on **Reconcile # Items**" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:77 +msgid "" +"If everything was right (correct partner name, right amount) odoo will do " +"the reconciliations **automatically**." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:82 +msgid "If some issues are found, you will need to take **manual actions**." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:84 +msgid "" +"For example, if the partner is missing from your bank statement, just fill " +"it in :" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:89 +msgid "" +"If the payment is done with a down payment, just check if it is all right " +"and validate all related payments :" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:95 +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:125 +msgid ":doc:`bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:3 +msgid "Cash reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:5 +msgid "" +"By default in Odoo, payments registered in the **cash journal** are " +"automatically reconciled with an **outstanding account** and their related " +"invoices or bills marked as *In Payment* until they are reconciled with a " +"bank statement. It is possible to :ref:`bypass `" +" the *In Payment* status for cash transactions, therefore removing the need " +"to reconcile with a bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst-1 +msgid "In Payment status of invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:16 +msgid "Cash logs" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:18 +msgid "" +"At the start of each day, create a **cash log**. To do so, go to your " +":guilabel:`Accounting Dashboard` and click :guilabel:`New Transaction` in " +"the :guilabel:`Cash` journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst-1 +msgid "Create a new cash log." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:25 +msgid "" +"Enter the :guilabel:`Starting Balance` of your cash float and save, but do " +"*not* post the entry yet. Create your invoice by going to " +":menuselection:`Accounting dashboard --> Customers --> Invoices` and confirm" +" it. Click :guilabel:`Register Payment` and select the cash " +":guilabel:`Journal`. Repeat the process for each invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst-1 +msgid "Select Cash journal upon payment registration." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:34 +msgid "" +"Go back to your :guilabel:`Accounting Dashboard`, and click again on " +":guilabel:`New transactions`. Click on the :guilabel:`Add a line` button in " +"the :guilabel:`Transactions` tab, and enter the total of cash earned during " +"the day. Add a label name according to your needs. Input the amount " +"displayed under :guilabel:`Computed Balance` in the :guilabel:`Ending " +"Balance` field, and make sure it matches your end cash float." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:40 +msgid "" +"Once certain the **computed balance** is correct, click :guilabel:`Save`, " +":guilabel:`Post`, and then :guilabel:`Reconcile`. This will take you to the " +"**bank reconciliation** page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:44 +msgid "Cash payments reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:46 +msgid "" +"On the **bank reconciliation** page, search through the list for the **cash " +"log** transaction you created earlier. To be able to match all cash " +"payments, make sure no **partner** is selected in the :guilabel:`Select " +"Partner` field. If a **partner** is selected, click in the field and delete " +"the partner. Then, pair (or match) each cash payment with your cash log by " +"clicking on the payment in the :guilabel:`Customer/Vendor Matching`, and " +":guilabel:`validate`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst-1 +msgid "Cash payments reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:57 +msgid "" +"If your ending cash balance is **over** or **under** the computed balance, " +"add another :guilabel:`Transaction` line corresponding to the **over** or " +"**under** amount in order to match it later during reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:62 +msgid "Cash reconciliation bypass" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:67 +msgid "" +"Bypassing the cash journal is recommended **only for organizations** that do" +" not need a cash report or do not wish to reconcile cash." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:70 +msgid "" +"To bypass the *In Payment* status, go to :menuselection:`Accounting app --> " +"Configuration --> Accounting: Journals` and select the :guilabel:`Cash` " +"journal. Click on the :guilabel:`Payments Configuration` tab and set a " +"`Cash` account in both the :guilabel:`Outstanding Receipts Account` and " +":guilabel:`Outstanding Payments Account` fields, then save. Payments " +"registered in the **cash** journal now bypass the *In Payment* status." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst-1 +msgid "Configuration tab of the cash journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_cash.rst:81 +msgid "" +"In case you use cash to pay expenses, advance employees, are required to " +"keep records of cash flows, or use anything resembling a cash box, you can " +"benefit from creating a second **cash journal** that *does* use the " +"**outstanding accounts**. This way, you can both generate *and* reconcile " +"bank statements when closing your POS session or your books at the end of " +"the day." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:3 +msgid "Reconciliation models" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:5 +msgid "" +"Once the bank statements are correctly imported, it is essential to " +"reconcile the records properly and ensure all **journal entries** are " +"balanced and in agreement. To ease and speed up the reconciliation process, " +"you can configure **reconciliation models**, which are particularly useful " +"with **recurrent entries** such as bank fees." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:11 +msgid "" +"Reconciliation models are also useful when handling *Cash Discounts*. Please" +" refer to :doc:`the cash discounts <../customer_invoices/cash_discounts>` " +"for more information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:18 +msgid "Types of reconciliation models" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:20 +msgid "There are three types of reconciliation models:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:22 +msgid ":ref:`Write-off button `" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:23 +msgid "" +":ref:`Suggestion of counterpart values `" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:24 +msgid ":ref:`Match existing invoices/bills `" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:29 +msgid "Manually create a write-off on clicked button" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:31 +msgid "" +"When reconciling an entry with an *open balance*, you can use the buttons " +"available under the :guilabel:`Manual Operations` tab to pre-fill all the " +"values automatically before validating the reconciliation. Each button " +"corresponds to a reconciliation model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Example of a reconciliation model with a write-off button in Odoo " +"Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:42 +msgid "Suggest counterpart values" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:44 +msgid "" +"This type of reconciliation model immediately suggests counterpart values " +"when selecting an entry, which then only needs to be validated. This " +"automation is based on a set of rules defined in the reconciliation model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Example of a reconciliation model that suggests counterpart values in Odoo " +"Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:55 +msgid "Match existing invoices/bills" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:57 +msgid "" +"This type of reconciliation model automatically selects the right customer " +"invoice or vendor bill that matches the payment. All that is left to do is " +"to validate the entry. This automation is based on a set of rules defined in" +" the reconciliation model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Example of a reconciliation model that matches existing invoices and bills automatically\n" +"in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:69 +msgid "" +"To manage or create new **reconciliation models**, go to " +":menuselection:`Accounting app --> Configuration --> Banks: Reconciliation " +"Models`. Alternatively, you can also open this menu from " +":menuselection:`Accounting app --> Bank --> Drop-down menu (⋮) --> " +"Reconciliation Models`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Open the reconciliation model menu from the overview dashboard in Odoo " +"Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:78 +msgid "" +"The first entry, :guilabel:`Invoices Matching Rule`, is responsible for the " +"current matching of invoices and bills. Therefore, it is advised to leave it" +" at the top of the list and not delete it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:82 +msgid "" +"Open the model you want to modify or click on :guilabel:`Create` to create a" +" new one, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:86 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:52 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:56 +msgid "Type" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:88 +msgid "" +"See :ref:`types of reconciliation models ` for " +"an explanation about the different types of reconciliation models." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:92 +msgid "" +"If the *Documents* application is installed on your database, an additional " +":guilabel:`Activity type` field appears when :guilabel:`To Check` is ticked." +" Selecting the value :guilabel:`Reconciliation request` implies that " +"whenever you use this model, a :guilabel:`Request Document` window pops up " +"to request a document from the user." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:98 +msgid "Conditions on bank statement line" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:100 +msgid "" +"Define here all the conditions that should be fulfilled for the " +"reconciliation model to be applied. Depending on the :guilabel:`Type` of " +"model you choose, different options are available." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:104 +msgid "" +"If a record matches with several reconciliation models, the first one in the" +" list is applied. Models can be rearranged by dragging and dropping the " +"handle next to their name." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Conditions for the reconciliation model to be applied in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:112 +msgid "Counterpart values" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:114 +msgid "" +"This section comprises the values that are applied by the reconciliation " +"model. If the value to reconcile needs to be written-off in two separate " +"accounts, click on :guilabel:`Add a second line` a second time." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "Counterparts values of a reconciliation model in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:124 +msgid ":doc:`reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:126 +msgid ":doc:`../customer_invoices/cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:5 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:86 +msgid "Customer invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:8 +msgid "From Customer Invoice to Payments Collection" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:10 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:17 +msgid "From Draft Invoice to Profit and Loss" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:19 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:26 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:35 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:177 +msgid "Invoice creation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:37 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:41 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:47 +msgid "Draft invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:49 +msgid "" +"The system generates invoice which are initially set to the Draft state. " +"While these invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:52 +msgid "" +"remain unvalidated, they have no accounting impact within the system. There " +"is nothing to stop users from creating their own draft invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:55 +msgid "Let's create a customer invoice with following information:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:57 +msgid "Customer: Agrolait" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:58 +msgid "Product: iMac" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:59 +msgid "Quantity: 1" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:60 +msgid "Unit Price: 100" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:61 +msgid "Taxes: Tax 15%" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:67 +msgid "The document is composed of three parts:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:69 +msgid "the top of the invoice, with customer information," +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:70 +msgid "the main body of the invoice, with detailed invoice lines," +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:71 +msgid "the bottom of the page, with detail about the taxes, and the totals." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:74 +msgid "Open or Pro-forma invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:76 +msgid "" +"An invoice will usually include the quantity and the price of goods and/or " +"services, the date, any parties involved, the unique invoice number, and any" +" tax information." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:80 +msgid "" +"\"Validate\" the invoice when you are ready to approve it. The invoice then " +"moves from the Draft state to the Open state." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:83 +msgid "" +"When you have validated an invoice, Odoo gives it a unique number from a " +"defined, and modifiable, sequence." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:88 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:96 +msgid "Send the invoice to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:98 +msgid "" +"After validating the customer invoice, you can directly send it to the " +"customer via the 'Send by email' functionality." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:103 +msgid "" +"A typical journal entry generated from a validated invoice will look like as" +" follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:52 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:69 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:119 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:139 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:69 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:160 +msgid "**Account**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +msgid "**Partner**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +msgid "**Due date**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:53 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:70 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:120 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:140 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:69 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:160 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:82 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:99 +msgid "**Debit**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:54 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:71 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:121 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:141 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:69 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:160 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:82 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:99 +msgid "**Credit**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:168 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:58 +msgid "Accounts Receivable" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +msgid "Agrolait" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +msgid "01/07/2015" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +msgid "115" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/accounting/taxes.rst:5 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:164 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:198 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:123 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:69 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:242 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:116 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:51 +msgid "Taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +msgid "15" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:113 +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:16 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:265 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "Sales" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:113 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +#: ../../content/applications/finance/accounting/taxes.rst:127 +msgid "100" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:117 +msgid "Payment" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:124 +msgid "" +"A typical journal entry generated from a payment will look like as follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +#: ../../content/applications/finance/accounting/payments/checks.rst:108 +#: ../../content/applications/finance/accounting/payments/checks.rst:127 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:67 +msgid "Bank" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:136 +msgid "Receive a partial payment through the bank statement" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:142 +msgid "" +"Create a bank statement from the accounting dashboard with the related " +"journal and enter an amount of $100 ." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:148 +msgid "Reconcile" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:150 +msgid "Now let's reconcile!" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:154 +msgid "" +"You can now go through every transaction and reconcile them or you can mass " +"reconcile with instructions at the bottom." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:156 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:164 +msgid "" +"Apply the payment. Below, you can see that the payment has been added to the" +" invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:170 +msgid "Payment Followup" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:172 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:176 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:184 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:192 +msgid "Customer aging report:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:194 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:198 +msgid "" +"Use the aging report to determine which customers are overdue and begin your" +" collection efforts." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:206 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:216 +msgid "" +"The balance sheet summarizes your company's liabilities, assets and equity " +"at a specific moment in time." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:223 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:3 +msgid "Cash discounts" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:5 +msgid "" +"Cash discounts are incentives you can offer to customers to motivate them to" +" pay within a specific time frame. For instance, you offer a 2% discount if " +"the customer pays you within the first 5 days of the invoice, when it is due" +" in 30 days. This approach can greatly improve your average collection " +"period." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:12 +msgid "Set up a cash discount" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:14 +msgid "" +"To set up a cash discount, go to :menuselection:`Accounting --> " +"Configuration --> Management --> Payment Terms` and click on *Create*. Add a" +" *Percent* type of term with a corresponding value (e.g. 98% of the total " +"price for a 2% discount) and the number of days during which the offer is " +"valid. You can also change the default balance term if needed." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:25 +msgid "Start offering the cash discount" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:27 +msgid "" +"Now, you can create a customer invoice and select the cash discount payment " +"term you added. Once the invoice is validated, Odoo will automatically split" +" the account receivables part of the journal entry into two installments " +"having different due dates. Since the discounted price is already " +"calculated, your payment controls will be simplified." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:37 +msgid "Grant the cash discount" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:39 +msgid "" +"The customer fulfilled the payment terms and therefore benefits from the " +"cash discount. When you process the bank statement, match the payment with " +"the related journal entry. Then, select the remaining cash discount and " +"click on *Create Write-off* to reconcile it." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:48 +msgid "" +"You can also create a dedicated reconciliation model to make the process " +"easier. In this case, you should add a tax to the model based on the taxes " +"applied to your invoices. This means that if you handle multiple tax rates, " +"you need to create several reconciliation models. Note that depending on " +"your localisation, you might already have a Cash Discount model available by" +" default." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:56 +msgid "Register the full payment" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:58 +msgid "" +"In this case, the customer has not fulfilled the payment term and cannot " +"benefit from the cash discount. When you process the bank statement, match " +"the payment with the two related journal entries." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:67 +msgid ":doc:`payment_terms`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:68 +msgid ":doc:`../bank/reconciliation_models`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:3 +msgid "Cash rounding" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:5 +msgid "" +"**Cash rounding** is required when the lowest physical denomination of " +"currency, or the smallest coin, is higher than the minimum unit of account." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:9 +msgid "" +"For example, some countries require their companies to round up or down the " +"total amount of an invoice to the nearest five cents, when the payment is " +"made in cash." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:16 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and enable " +"*Cash Rounding*, then click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:22 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Cash Roundings`, and " +"click on *Create*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:25 +msgid "" +"Define here your *Rounding Precision*, *Rounding Strategy*, and *Rounding " +"Method*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:28 +msgid "Odoo supports two **rounding strategies**:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:30 +msgid "" +"**Add a rounding line**: a *rounding* line is added on the invoice. You have" +" to define which account records the cash roundings." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:33 +msgid "**Modify tax amount**: the rounding is applied in the taxes section." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:36 +msgid "Apply roundings" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:38 +msgid "" +"When editing a draft invoice, open the *Other Info* tab, go to the " +"*Accounting Information* section, and select the appropriate *Cash Rounding " +"Method*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:3 +msgid "Credit notes and refunds" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:5 +msgid "" +"A **credit note**, or **credit memo**, is a document issued to a customer " +"that notifies them that they have been credited a certain amount." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:12 +msgid "There are several reasons that can lead to a credit note, such as:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:10 +msgid "a mistake in the invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:11 +msgid "a return of the goods, or a rejection of the services" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:12 +msgid "the goods delivered are damaged" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:15 +msgid "" +"Issuing a credit note is the only legal way to cancel, refund or modify a " +"validated invoice. Don’t forget to *register the payment* afterward if you " +"need to send money back to your customer." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:21 +msgid "Issue a Credit Note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:23 +msgid "" +"You can create a credit note from scratch by going to " +":menuselection:`Accounting --> Customers --> Credit Notes`, and by clicking " +"on *Create*. Filling the Credit Note’s form works the same way as the " +"Invoice’s form." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:28 +msgid "" +"However, most of the time, credit notes are generated directly from the " +"invoices they are related to." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:31 +msgid "To do so, open the *Customer Invoice*, and click on *Add Credit Note*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:39 +msgid "You can choose between three options:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:37 +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:46 +msgid "Partial Refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:38 +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:58 +msgid "Full Refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:39 +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:70 +msgid "Full refund and new draft invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:42 +msgid "" +"Credit Notes’ numbers start with “R” and are followed by the number of the " +"document they are related to (e.g., RINV/2019/0004)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:48 +msgid "" +"Odoo creates a draft credit note already prefilled with all the necessary " +"information from the original invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:51 +msgid "" +"This is the option to choose to do a partial refund, or if you want to " +"modify any detail on the credit note." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:55 +msgid "" +"This is the only option available for invoices that are already marked as " +"*Paid*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:60 +msgid "" +"Odoo creates a credit note, automatically validates it, and reconciles the " +"original invoice with it." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:66 +msgid "" +"This is the option to choose to do a full refund or cancel a validated " +"invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:72 +msgid "" +"Odoo creates a credit note, automatically validates it, reconciles the " +"original invoice with it, and open a new draft invoice prefilled with the " +"same details from the original invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:76 +msgid "" +"This is the option to choose to modify the content of a validated invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:79 +msgid "Record a Vendor Refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:81 +msgid "" +"**Vendor Refunds** are recorded the same way you would do with invoices’ " +"credit notes:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:83 +msgid "" +"You can either create a credit note from scratch by going to " +":menuselection:`Accounting --> Vendors --> Refund`, and by clicking on " +"*Create*, or by opening the validated *Vendor Bill*, and clicking on *Add " +"Credit Note*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:89 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:94 +msgid "Journal Entries" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:91 +msgid "" +"Issuing a credit note from an invoice creates a **reverse entry** that " +"zeroes out the journal items generated by the original invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:94 +msgid "Here is an example of an invoice’s journal entry:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:99 +msgid "" +"And here is the credit note’s journal entry generated to reverse the " +"original invoice above:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:3 +msgid "Deferred revenues" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:5 +msgid "" +"**Deferred revenues**, or **unearned revenue**, are payments made in advance" +" by customers for products yet to deliver or services yet to render." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:8 +msgid "" +"Such payments are a **liability** for the company that receives them since " +"it still owes its customers these products or services. The company cannot " +"report them on the current **Profit and Loss statement**, or *Income " +"Statement*, since the payments will be effectively earned in the future." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:12 +msgid "" +"These future revenues must be deferred on the company's balance sheet until " +"the moment in time they can be **recognized**, at once or over a defined " +"period, on the Profit and Loss statement." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:15 +msgid "" +"For example, let's say we sell a five-year extended warranty for $ 350. We " +"already receive the money now but haven't earned it yet. Therefore, we post " +"this new income in a deferred revenue account and decide to recognize it on " +"a yearly basis. Each year, for the next 5 years, $ 70 will be recognized as " +"revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:20 +msgid "" +"Odoo Accounting handles deferred revenues by spreading them in multiple " +"entries that are automatically created in *draft mode* and then posted " +"periodically." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:24 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:28 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:25 +msgid "" +"The server checks once a day if an entry must be posted. It might then take " +"up to 24 hours before you see a change from *draft* to *posted*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:28 +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:20 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:32 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:29 +msgid "Prerequisites" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:30 +msgid "" +"Such transactions must be posted on a **Deferred Revenue Account** rather " +"than on the default income account." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:34 +msgid "Configure a Deferred Revenue Account" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:36 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:40 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:37 +msgid "" +"To configure your account in the **Chart of Accounts**, go to " +":menuselection:`Accounting --> Configuration --> Chart of Accounts`, click " +"on *Create*, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +msgid "Configuration of a Deferred Revenue Account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:44 +msgid "" +"This account's type must be either *Current Liabilities* or *Non-current " +"Liabilities*" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:47 +msgid "Post an income to the right account" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:50 +msgid "Select the account on a draft invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:52 +msgid "" +"On a draft invoice, select the right account for all the products of which " +"the incomes must be deferred." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +msgid "" +"Selection of a Deferred Revenue Account on a draft invoice in Odoo " +"Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:60 +msgid "Choose a different Income Account for specific products" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:62 +msgid "" +"Start editing the product, go to the *Accounting* tab, select the right " +"**Income Account**, and save." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +msgid "Change of the Income Account for a product in Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:70 +msgid "" +"It is possible to automate the creation of revenue entries for these " +"products (see: `Automate the Deferred Revenues`_)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:74 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:81 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:75 +msgid "Change the account of a posted journal item" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:76 +msgid "" +"To do so, open your Sales Journal by going to :menuselection:`Accounting -->" +" Accounting --> Sales`, select the journal item you want to modify, click on" +" the account, and select the right one." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Modification of a posted journal item's account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:85 +msgid "Deferred Revenues entries" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:88 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:97 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:89 +msgid "Create a new entry" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:90 +msgid "" +"A **Deferred Revenues entry** automatically generates all journal entries in" +" *draft mode*. They are then posted one by one at the right time until the " +"full amount of the income is recognized." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:93 +msgid "" +"To create a new entry, go to :menuselection:`Accounting --> Accounting --> " +"Deferred Revenues`, click on *Create*, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:96 +msgid "" +"Click on **select related purchases** to link an existing journal item to " +"this new entry. Some fields are then automatically filled out, and the " +"journal item is now listed under the **Related Sales** tab." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +msgid "Deferred Revenue entry in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:104 +msgid "" +"Once done, you can click on *Compute Revenue* (next to the *Confirm* button)" +" to generate all the values of the **Revenue Board**. This board shows you " +"all the entries that Odoo will post to recognize your revenue, and at which " +"date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +msgid "Revenue Board in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:113 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:122 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:114 +msgid "What does \"Prorata Temporis\" mean?" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:115 +msgid "" +"The **Prorata Temporis** feature is useful to recognize your revenue the " +"most accurately possible." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:117 +msgid "" +"With this feature, the first entry on the Revenue Board is computed based on" +" the time left between the *Prorata Date* and the *First Recognition Date* " +"rather than the default amount of time between recognitions." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:121 +msgid "" +"For example, the Revenue Board above has its first revenue with an amount of" +" $ 4.22 rather than $ 70.00. Consequently, the last entry is also lower and " +"has an amount of $ 65.78." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:125 +msgid "Deferred Entry from the Sales Journal" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:127 +msgid "" +"You can create a deferred entry from a specific journal item in your **Sales" +" Journal**." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:129 +msgid "" +"To do so, open your Sales Journal by going to :menuselection:`Accounting -->" +" Accounting --> Sales`, and select the journal item you want to defer. Make " +"sure that it is posted in the right account (see: `Change the account of a " +"posted journal item`_)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:134 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:134 +msgid "" +"Then, click on *Action*, select **Create Deferred Entry**, and fill out the " +"form the same way you would do to `create a new entry`_." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Create Deferred Entry from a journal item in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:142 +msgid "Deferred Revenue Models" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:144 +msgid "" +"You can create **Deferred Revenue Models** to create your Deferred Revenue " +"entries faster." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:146 +msgid "" +"To create a model, go to :menuselection:`Accounting --> Configuration --> " +"Deferred Revenue Models`, click on *Create*, and fill out the form the same " +"way you would do to create a new entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:150 +msgid "" +"You can also convert a *confirmed Deferred Revenue entry* into a model by " +"opening it from :menuselection:`Accounting --> Accounting --> Deferred " +"Revenues` and then, by clicking on the button *Save Model*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:155 +msgid "Apply a Deferred Revenue Model to a new entry" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:157 +msgid "" +"When you create a new Deferred Revenue entry, fill out the **Deferred " +"Revenue Account** with the right recognition account." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:160 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:222 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:160 +msgid "" +"New buttons with all the models linked to that account appear at the top of " +"the form. Clicking on a model button fills out the form according to that " +"model." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +msgid "Deferred Revenue model button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:170 +msgid "Automate the Deferred Revenues" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:172 +msgid "" +"When you create or edit an account of which the type is either *Current " +"Liabilities* or *Non-current Liabilities*, you can configure it to defer the" +" revenues that are credited on it automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:175 +msgid "You have three choices for the **Automate Deferred Revenue** field:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:177 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:240 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:177 +msgid "**No:** this is the default value. Nothing happens." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:178 +msgid "" +"**Create in draft:** whenever a transaction is posted on the account, a " +"draft *Deferred Revenues entry* is created, but not validated. You must " +"first fill out the form in :menuselection:`Accounting --> Accounting --> " +"Deferred Revenues`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:181 +msgid "" +"**Create and validate:** you must also select a Deferred Revenue Model (see:" +" `Deferred Revenue Models`_). Whenever a transaction is posted on the " +"account, a *Deferred Revenues entry* is created and immediately validated." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +msgid "Automate Deferred Revenue on an account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:190 +msgid "" +"You can, for example, select this account as the default **Income Account** " +"of a product to fully automate its sale. (see: `Choose a different Income " +"Account for specific products`_)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:194 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:256 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:195 +msgid ":doc:`../get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:195 +msgid "" +"`Odoo Academy: Deferred Revenues (Recognition) " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:3 +msgid "Electronic invoicing (:abbr:`EDI (electronic data interchange)`)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:5 +msgid "" +"EDI, or electronic data interchange, is the inter-company communication of " +"business documents, such as purchase orders and invoices, in a standard " +"format. Sending documents according to an EDI standard ensures that the " +"machine receiving the message can interpret the information correctly. " +"Various EDI file formats exist and are available depending on your company's" +" country." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:10 +msgid "" +"EDI feature enables automating the administration between companies and " +"might also be required by some governments for fiscal control or to " +"facilitate the administration." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:13 +msgid "" +"Electronic invoicing of your documents such as customer invoices, credit " +"notes or vendor bills is one of the application of EDI." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:16 +msgid "Odoo supports, among others, the following formats." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:21 +msgid "Format Name" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:22 +msgid "Applicability" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:23 +msgid "Factur-X (CII)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:24 +msgid "Default format on Odoo (enabled by default)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:25 +msgid "Peppol BIS Billing 3.0 (UBL)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:26 +msgid "" +"For companies whose countries are part of the `EAS list " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:28 +msgid "E-FFF" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:29 +msgid "For Belgian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:30 +msgid "XRechnung (UBL)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:31 +msgid "For German companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:32 +msgid "Fattura PA (IT)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:33 +msgid "For Italian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:34 +msgid "CFDI (4.0)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:35 +msgid "For Mexican companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:36 +msgid "Peru UBL 2.1" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:37 +msgid "For Peruvian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:38 +msgid "SII IVA Llevanza de libros registro (ES)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:39 +msgid "For Spanish companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:40 +msgid "UBL 2.1 (Columbia)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:41 +msgid "For Colombian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:42 +msgid "Egyptian Tax Authority" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:43 +msgid "For Egyptian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:44 +msgid "E-Invoice (IN)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:45 +msgid "For Indian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:46 +msgid "NLCIUS (Netherlands)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:47 +msgid "For Dutch companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:48 +msgid "EHF 3.0" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:49 +msgid "For Norwegian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:50 +msgid "SG BIS Billing 3.0" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:51 +msgid "For Singaporean companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:54 +msgid ":ref:`fiscal_localizations/packages`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:61 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Journals --> Customer" +" Invoices --> Advanced Settings --> Electronic Invoicing` and enable the " +"formats you need for this journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Select the EDI format you need" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:68 +msgid "" +"Once an electronic invoicing format is enabled, XML documents are generated " +"when clicking on :guilabel:`Confirm` in documents such as invoices, credit " +"notes, etc. These documents are either visible in the attachment section, or" +" embedded in the PDF." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:73 +msgid "" +"For E-FFF, the xml file only appears after having generated the PDF " +"(:guilabel:`Print` or :guilabel:`Send & Print` button), since the PDF needs " +"to be embedded inside the xml." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:75 +msgid "" +"By default, the :guilabel:`Factur-X` option is enabled. It means that an XML" +" file is automatically included in the PDF document that is sent." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:77 +msgid "" +"The formats available depend on the country registered in your company's " +":guilabel:`General Information`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:79 +msgid "" +"Odoo supports the **Peppol BIS Billing 3.0** format that can be used via " +"existing access points." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:83 +msgid "Add new formats to a database created before July 2022" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:85 +msgid "" +"If your database was created before July 2022 and you wish to use one of the" +" formats available from July 2022, you have to :ref:`install " +"` the module :guilabel:`Import/Export electronic invoices " +"with UBL/CII` (module’s technical name: `account_edi_ubl_cii`) and your " +"country-specific module." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:91 +msgid "" +"If you want to use the Belgian format E-FFF in a database created prior to " +"July 2022, you need to :ref:`install `:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:97 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:26 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/india.rst:16 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:17 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:34 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:14 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:14 +msgid "Name" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:98 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:27 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 +#: ../../content/applications/finance/fiscal_localizations/india.rst:17 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:18 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:17 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:35 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:15 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:17 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:15 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:99 +msgid "Belgium - E-Invoicing (UBL 2.0, e-fff)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:100 +msgid "`l10n_be_edi`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:101 +msgid "Import/Export electronic invoices with UBL/CII" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:102 +msgid "`account_edi_ubl_cii`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:105 +msgid "" +"Once the new module is installed, UBL 2.0 and UBL 2.1 formats no longer " +"appear in the journal since UBL BIS Billing 3.0 is available and more widely" +" supported." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:3 +msgid "EPC QR codes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:5 +msgid "" +"European Payments Council quick response codes, or **EPC QR codes**, are " +"two-dimensional barcodes that customers can scan with their **mobile banking" +" applications** to initiate a **SEPA credit transfer (SCT)** and pay their " +"invoices instantly." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:9 +msgid "" +"In addition to bringing ease of use and speed, it greatly reduces typing " +"errors that would potentially make for payment issues." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:13 +msgid "" +"This feature is only available for companies in several European countries " +"such as Austria, Belgium, Finland, Germany, and the Netherlands." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:17 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:122 +msgid ":doc:`../bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:18 +msgid "" +"`Odoo Academy: QR Code on Invoices for European Customers " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:23 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and " +"activate the :guilabel:`QR Codes` feature in the :guilabel:`Customer " +"Payments` section." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:27 +msgid "Configure your bank account's journal" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:29 +msgid "" +"Make sure that your :guilabel:`Bank Account` is correctly configured in Odoo" +" with your IBAN and BIC." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:31 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open your bank journal, then fill out the :guilabel:`Account Number` and " +":guilabel:`Bank` under the :guilabel:`Bank Account Number` column." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst-1 +msgid "Bank account number column in the bank journal" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:39 +msgid "Issue invoices with EPC QR codes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:41 +msgid "" +"EPC QR codes are added automatically to your invoices. Customers whose bank " +"supports making payments via EPC QR codes will be able to scan the code and " +"pay the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:44 +msgid "" +"Go to :menuselection:`Accounting --> Customers --> Invoices`, and create a " +"new invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:46 +msgid "" +"Before posting it, open the :guilabel:`Other Info` tab. Odoo automatically " +"fills out the :guilabel:`Recipient Bank` field with your IBAN." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:50 +msgid "" +"In the :guilabel:`Other Info` tab, the account indicated in the " +":guilabel:`Recipient Bank` field is used to receive your customer's payment." +" Odoo automatically populates this field with your IBAN by default and uses " +"it to generate the EPC QR code." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:54 +msgid "" +"When the invoice is printed or previewed, the QR code is included at the " +"bottom." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst-1 +msgid "QR code on a customer invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:60 +msgid "" +"If you want to issue an invoice without an EPC QR code, remove the IBAN " +"indicated in the :guilabel:`Recipient Bank` field, under the " +":guilabel:`Other Info` tab of the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:3 +msgid "Invoicing processes" +msgstr "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:12 +msgid "" +"Depending on your business, you may opt for one of the following way to " +"create draft invoices:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:19 +msgid "Sales Order ‣ Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:25 +msgid "" +"Invoice manually: use a button on the sale order to trigger the draft " +"invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:28 +msgid "" +"Invoice before delivery: invoice the full order before triggering the " +"delivery order" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:31 +msgid "Invoice based on delivery order: see next section" +msgstr "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:42 +msgid "This process is good for both services and physical products." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:45 +msgid ":doc:`/applications/sales/sales/invoicing/proforma`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:48 +msgid "Sales Order ‣ Delivery Order ‣ Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:50 +msgid "" +"Retailers and eCommerce usually invoice based on delivery orders, instead of" +" sales order. This approach is suitable for businesses where the quantities " +"you deliver may differs from the ordered quantities: foods (invoice based on" +" actual Kg)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:55 +msgid "" +"This way, if you deliver a partial order, you only invoice for what you " +"really delivered. If you do back orders (deliver partially and the rest " +"later), the customer will receive two invoices, one for each delivery order." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:61 +msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:64 +msgid "eCommerce Order ‣ Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:66 +msgid "" +"An eCommerce order will also trigger the creation of the order when it is " +"fully paid. If you allow paying orders by check or wire transfer, Odoo only " +"creates an order and the invoice will be triggered once the payment is " +"received." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:72 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:75 +msgid "Regular Contracts ‣ Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:77 +msgid "" +"If you use contracts, you can trigger invoice based on time and material " +"spent, expenses or fixed lines of services/products. Every month, the " +"salesperson will trigger invoice based on activities on the contract." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:81 +msgid "Activities can be:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:83 +msgid "" +"fixed products/services, coming from a sale order linked to this contract" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:84 +msgid "materials purchased (that you will re-invoice)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:85 +msgid "time and material based on timesheets or purchases (subcontracting)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:86 +msgid "" +"expenses like travel and accommodation that you re-invoice to the customer" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:88 +msgid "" +"You can invoice at the end of the contract or trigger intermediate invoices." +" This approach is used by services companies that invoice mostly based on " +"time and material. For services companies that invoice on fix price, they " +"use a regular sales order." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:94 +msgid ":doc:`/applications/sales/sales/invoicing/time_materials`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:95 +msgid ":doc:`/applications/sales/sales/invoicing/expense`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:96 +msgid ":doc:`/applications/sales/sales/invoicing/milestone`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:99 +msgid "Recurring Contracts ‣ Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:106 +msgid ":doc:`/applications/sales/sales/invoicing/subscriptions`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:109 +msgid "Others" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:112 +msgid "Creating an invoice manually" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:114 +msgid "" +"Users can also create invoices manually without using contracts or a sales " +"order. It's a recommended approach if you do not need to manage the sales " +"process (quotations), or the delivery of the products or services." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:119 +msgid "" +"Even if you generate the invoice from a sales order, you may need to create " +"invoices manually in exceptional use cases:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:122 +msgid "if you need to create a refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:124 +msgid "If you need to give a discount" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:126 +msgid "if you need to change an invoice created from a sales order" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:128 +msgid "if you need to invoice something not related to your core business" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:131 +msgid "Specific modules" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:133 +msgid "Some specific modules are also able to generate draft invoices:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:135 +msgid "**membership**: invoice your members every year" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:137 +msgid "**repairs**: invoice your after-sale services" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:140 +msgid "Resequencing of the invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:142 +msgid "" +"It remains possible to resequence the invoices but with some restrictions:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:144 +msgid "The feature does not work when entries are previous to a lock date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:145 +msgid "" +"The feature does not work if the sequence is inconsistent with the month of " +"the entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:146 +msgid "It does not work if the sequence leads to a duplicate." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:147 +msgid "The order of the invoice remains unchanged." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:148 +msgid "" +"It is useful for people who use a numbering from another software and who " +"want to continue the current year without starting over from the beginning." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:152 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:3 +msgid "Invoice digitization with optical character recognition (OCR)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:154 +msgid "" +"**Invoice digitization** is the process of automatically encoding " +"traditional paper invoices into invoices forms in your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:157 +msgid "" +"Odoo uses OCR and artificial intelligence technologies to recognize the " +"content of the documents. Vendor bills and customer invoices forms are " +"automatically created and populated based on scanned invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:162 +msgid "" +":doc:`/applications/finance/accounting/vendor_bills/invoice_digitization`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:3 +msgid "Payment terms and installment plans" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:5 +msgid "" +"**Payment Terms** specify all the conditions under which a sale is paid, " +"mostly to ensure customers pay their invoices correctly and on time." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:8 +msgid "" +"Payment Terms can be applied to sales orders, customer invoices, supplier " +"bills, and contacts. These conditions cover:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:11 +msgid "The due date" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:12 +msgid "Some discounts" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:13 +msgid "Any other condition on the payment" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:15 +msgid "" +"Defining Payment Terms automatically calculates the payments' due dates. " +"This is particularly helpful for managing installment plans." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:18 +msgid "" +"An **installment plan** allows the customers to pay an invoice in parts, " +"with the amounts and payment dates defined beforehand by the seller." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:21 +msgid "**Examples of Payment Terms:**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "**Immediate Payment**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "The full payment is due on the day of the invoice's issuance." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "**15 Days** (or **Net 15**)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "The full payment is due 15 days after the invoice date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "**21 MFI**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "" +"The full payment is due by the 21st of the month following the invoice date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "**2% 10, Net 30 EOM**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "" +"2% :doc:`cash discount ` if the payment is received within " +"ten days. Otherwise, the full payment is due at the end of the month " +"following the invoice date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:34 +msgid "" +"Payment terms are not to be confused with down payment invoices. If, for a " +"specific order, you issue several invoices to your customer, that is neither" +" a payment term nor an installment plan, but an invoicing policy." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:39 +msgid "" +"This document is about the *Payment Terms* feature, not *Terms & " +"Conditions*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:42 +msgid ":doc:`cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:43 +msgid "" +"`Odoo Tutorials: Payment Terms `_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:48 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Payment Terms` and " +"click on *Create*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:50 +msgid "" +"The **Description on the Invoice** is the text displayed on the document " +"(sale order, invoice, etc.)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:53 +msgid "" +"In the **Terms** section, you can add a set of rules, called *terms*, to " +"define what needs to be paid and by which due date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:56 +msgid "" +"To add a term, click on *Add a line*, and define its *Type*, *Value*, and " +"*Due Date Computation*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:59 +msgid "Terms are computed in the order they are set up." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:60 +msgid "The **balance** should always be used for the last line." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:62 +msgid "" +"In the following example, 30% is due on the day of issuance, and the balance" +" is due at the end of the following month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst-1 +msgid "" +"Example of Payment Terms. The last line is the balance due on the 31st of the following\n" +"month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:71 +msgid "Using Payment Terms" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:73 +msgid "" +"Payment Terms can be defined in the **Due Date** field, with the **Terms** " +"drop-down list, on:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "**Quotations**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "" +"To set specific payment terms automatically on all invoices generated from a" +" quotation." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "**Customer Invoices**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "To set specific payment terms on an invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "**Vendor Bills**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "" +"To set specific payment terms on a bill. This is mostly useful when you need" +" to manage vendor terms with several installments. Otherwise, setting the " +"*Due Date* is enough." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:84 +msgid "" +"You can also define a **Due Date** manually. If Payment Terms are already " +"defined, empty the field so you can select a date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:87 +msgid "Payment Terms can be defined with the **Payment Terms** field on:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "**Contacts**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "" +"To set specific payment terms automatically on new sales orders, invoices, " +"and bills of a contact. This can be modified in the contact’s *Form View*, " +"under the *Sales & Purchase* tab." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:96 +msgid "" +"Invoices with specific Payment Terms generate different *Journal Entries*, " +"with one *Journal Item* for every computed *Due Date*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:99 +msgid "" +"This makes for easier *Follow-ups* and *Reconciliation* since Odoo takes " +"each due date into account, rather than just the balance due date. It also " +"helps to get an accurate *Aged Receivable report*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst-1 +msgid "" +"The amount debited on the Account Receivable is split into two Journal Items with distinct\n" +"Due Dates" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:107 +msgid "" +"In this example, an invoice of $1000 has been issued with the following " +"payment terms: *30% is due on the day of issuance, and the balance is due at" +" the end of the following month.*" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:111 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +msgid "Account" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:111 +msgid "Due date" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:111 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:168 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +msgid "Debit" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:111 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:168 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +msgid "Credit" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:113 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:115 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/payments/checks.rst:95 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +msgid "Account Receivable" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:113 +msgid "February 21" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:113 +msgid "300" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:115 +msgid "March 31" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:115 +msgid "700" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:117 +msgid "Product Sales" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:117 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:140 +msgid "1000" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:120 +msgid "" +"The $1000 debited on the Account Receivable is split into two distinct " +"*Journal Items*. Both of them have their own **Due Date**." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:5 +msgid "Snailmail" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:7 +msgid "" +"Sending direct mail can be an effective strategy for grabbing people's " +"attention, especially when their email inboxes are overflowing. With Odoo, " +"you have the ability to send invoices and follow-up reports through postal " +"mail worldwide, all from within your database." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:14 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Customer" +" invoices` section to activate :guilabel:`Snailmail`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:17 +msgid "" +"To make it a by-default feature, select :guilabel:`Send by Post` in the " +":guilabel:`Default Sending Options` section." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst-1 +msgid "Under settings enable the snailmail feature in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:25 +msgid "Send invoices by post" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:27 +msgid "" +"Open your invoice, click on :guilabel:`Send & Print` and select " +":guilabel:`Send by Post`. Make sure your customer’s address is set " +"correctly, including the country, before sending the letter." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:31 +msgid "" +"Your document must respect the following rules to pass the validation before" +" being sent:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:33 +msgid "" +"Margins must be **5 mm** on all sides. As Odoo forces the outer margins by " +"filling them with white before sending the snailmail, it can results in the " +"user's custom being cut off if it protrudes into the margins. To check the " +"margins, activate the :ref:`developer mode `, go to " +":menuselection:`General Settings --> Technical --> Reporting section: Paper " +"Format`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:38 +msgid "" +"A square of **15mm by 15mm** on the bottom left corner has to stay clear." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:39 +msgid "" +"The postage area has to stay clear (click :download:`here " +"` to get more info about the area)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:41 +msgid "" +"Pingen (Odoo Snailmail service provider) scans the area to process the " +"address, so if something gets written outside the area, it is not counted as" +" part of the address." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:45 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:65 +msgid "Pricing" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:47 +msgid "" +"Snailmail is an :doc:`/applications/general/in_app_purchase` service that " +"requires prepaid stamps (=credits) to work. Sending one document consumes " +"one stamp." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:50 +msgid "" +"To buy stamps, go to :menuselection:`Accounting --> Configuration --> " +"Settings --> Customer invoices: Snailmail`, click on :guilabel:`Buy " +"credits`, or go to :menuselection:`Settings --> In-App Purchases: Odoo IAP`," +" and click on :guilabel:`View my Services`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:55 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:74 +msgid "" +"If you are on Odoo Online and have the Enterprise version, you benefit from " +"free trial credits to test the feature." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:57 +msgid "" +"Click `here `_ to know about our " +"*Privacy Policy*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:7 +msgid "" +"When you first open your Odoo Accounting app, the *Accounting Overview* page" +" welcomes you with a step-by-step onboarding banner, a wizard that helps you" +" get started. This onboarding banner is displayed until you choose to close " +"it." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:11 +msgid "" +"The settings visible in the onboarding banner can still be modified later by" +" going to :menuselection:`Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:15 +msgid "" +"Odoo Accounting automatically installs the appropriate **Fiscal Localization" +" Package** for your company, according to the country selected at the " +"creation of the database. This way, the right accounts, reports, and taxes " +"are ready-to-go. :ref:`Click here ` for more " +"information about Fiscal Localization Packages." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:21 +msgid "Accounting onboarding banner" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:23 +msgid "" +"The step-by-step Accounting onboarding banner is composed of four steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Step-by-step onboarding banner in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:28 +msgid ":ref:`accounting-setup-company`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:29 +msgid ":ref:`accounting-setup-bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:30 +msgid ":ref:`accounting-setup-periods`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:31 +msgid ":ref:`accounting-setup-chart`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:36 +#: ../../content/applications/finance/accounting/get_started.rst:137 +msgid "Company Data" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:38 +msgid "" +"This menu allows you to add your company’s details such as the name, " +"address, logo, website, phone number, email address, and Tax ID, or VAT " +"number. These details are then displayed on your documents, such as on " +"invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Add your company's details in Odoo Accounting and Odoo Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:46 +msgid "" +"You can also change these settings by going to :menuselection:`Settings --> " +"General Settings --> Settings --> Companies` and clicking on **Update " +"Info**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:52 +msgid "Bank Account" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:54 +msgid "" +"Connect your bank account to your database and have your bank statements " +"synced automatically. To do so, find your bank in the list, click on " +"*Connect*, and follow the instructions on-screen." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:58 +msgid "" +":doc:`Click here ` for more information about " +"this feature." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:60 +msgid "" +"If your Bank Institution can’t be synchronized automatically, or if you " +"prefer not to sync it with your database, you may also configure your bank " +"account manually by clicking on *Create it*, and filling out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:64 +msgid "**Name**: the bank account's name, as displayed on Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:65 +msgid "**Account Number**: your bank account number (IBAN in Europe)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:66 +msgid "" +"**Bank**: click on *Create and Edit* to configure the bank's details. Add " +"the bank institution's name and its Identifier Code (BIC or SWIFT)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:68 +msgid "" +"**Code**: this code is your Journal's *Short Code*, as displayed on Odoo. By" +" default, Odoo creates a new Journal with this Short Code." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:70 +msgid "" +"**Journal**: This field is displayed if you have an existing Bank Journal " +"that is not linked yet to a bank account. If so, then select the *Journal* " +"you want to use to record the financial transactions linked to this bank " +"account or create a new one by clicking on *Create and Edit*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:75 +msgid "" +"You can add as many bank accounts as needed with this tool by going to " +":menuselection:`Accounting --> Configuration`, and clicking on *Add a Bank " +"Account*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:77 +msgid ":doc:`Click here ` for more information about Bank Accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:83 +msgid "Accounting Periods" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:85 +msgid "" +"Define here your **Fiscal Years**’ opening and closing dates, which are used" +" to generate reports automatically, and your **Tax Return Periodicity**, " +"along with a reminder to never miss a tax return deadline." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:89 +msgid "" +"By default, the opening date is set on the 1st of January and the closing " +"date on the 31st of December, as this is the most common use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:93 +msgid "" +"You can also change these settings by going to :menuselection:`Accounting " +"--> Configuration --> Settings --> Fiscal Periods` and updating the values." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:99 +msgid "Chart of Accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:101 +msgid "" +"With this menu, you can add accounts to your **Chart of Accounts** and " +"indicate their initial opening balances." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:104 +msgid "" +"Basic settings are displayed on this page to help you review your Chart of " +"Accounts. To access all the settings of an account, click on the *double " +"arrow button* at the end of the line." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "" +"Setup of the Chart of Accounts and their opening balances in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:111 +msgid "" +":doc:`Click here ` for more information on " +"how to configure your Chart of Accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:115 +msgid "Invoicing onboarding banner" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:117 +msgid "" +"There is another step-by-step onboarding banner that helps you take " +"advantage of your Odoo Invoicing and Accounting apps. The *Invoicing " +"onboarding banner* is the one that welcomes you if you use the Invoicing app" +" rather than the Accounting app." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:121 +msgid "" +"If you have Odoo Accounting installed on your database, you can reach it by " +"going to :menuselection:`Accounting --> Customers --> Invoices`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:124 +msgid "The Invoicing onboarding banner is composed of four main steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Step-by-step onboarding banner in Odoo Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:129 +msgid ":ref:`invoicing-setup-company`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:130 +msgid ":ref:`invoicing-setup-layout`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:131 +msgid ":ref:`invoicing-setup-payment`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:132 +msgid ":ref:`invoicing-setup-sample`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:139 +msgid "" +"This form is the same as :ref:`the one presented in the Accounting " +"onboarding banner `." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:145 +msgid "Invoice Layout" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:147 +msgid "" +"With this tool, you can design the appearance of your documents by selecting" +" which layout template, paper format, colors, font, and logo you want to " +"use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:150 +msgid "" +"You can also add your *Company Tagline* and the content of the documents’ " +"*footer*. Note that Odoo automatically adds the company's phone number, " +"email, website URL, and Tax ID (or VAT number) to the footer, according to " +"the values you previously configured in the :ref:`Company Data `." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Document layout configuration in Odoo Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:159 +msgid "" +"Add your **bank account number** and a link to your **General Terms & " +"Condition** in the footer. This way, your contacts can find the full content" +" of your GT&C online without having to print them on the invoices you issue." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:164 +msgid "" +"These settings can also be modified by going to :menuselection:`Settings -->" +" General Settings`, under the *Business Documents* section." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:170 +msgid "Payment Method" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:172 +msgid "" +"This menu helps you configure the payment methods with which your customers " +"can pay you." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:175 +msgid "" +"Configuring a *Payment Acquirer* with this tool also activates the *Invoice " +"Online Payment* option automatically. With this, users can directly pay " +"online, from their Customer Portal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:181 +msgid "Sample Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:183 +msgid "" +"Send yourself a sample invoice by email to make sure everything is correctly" +" configured." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:186 +msgid ":doc:`bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:187 +msgid ":doc:`get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:189 +msgid ":doc:`../fiscal_localizations`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:190 +msgid "`Odoo Tutorials: Accounting Basics `_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:3 +msgid "Inventory average price valuation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:5 +msgid "" +"As stated in the :doc:`inventory valuation page " +"`," +" one of the possible costing method you can use in perpetual stock " +"valuation, is the average cost." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:18 +msgid "Definition of average cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:24 +msgid "" +"The weighted average cost per unit is calculated using the following " +"formula:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:27 +msgid "" +"When new products arrive in a warehouse, the new average cost is recomputed " +"as:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:33 +msgid "" +"When products leave the warehouse: the average cost **does not** change" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:36 +msgid "Defining the purchase price" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:45 +msgid "Average cost example" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +msgid "Operation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +msgid "Delta Value" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +msgid "Inventory Value" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +msgid "Qty On Hand" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +msgid "Avg Cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:50 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +msgid "$0" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:50 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 +#: ../../content/applications/finance/fiscal_localizations/france.rst:240 +msgid "0" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +msgid "Receive 8 Products at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 +msgid "+8\\*$10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +msgid "$80" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +msgid "8" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +msgid "$10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 +msgid "Receive 4 Products at $16" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 +msgid "+4\\*$16" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +msgid "$144" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +msgid "$12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 +msgid "Deliver 10 Products" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +msgid "-10\\*$12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 +msgid "$24" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 +msgid "2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:73 +msgid "Purchase return use case" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:79 +msgid "Which means that the above table will be updated as follow:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +msgid "Return of 1 Product initially bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 +msgid "-1\\*$12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +msgid "1" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:90 +msgid "Explanation: counter example" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 +msgid "Customer Shipping 1 product" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 +msgid "-1\\*$10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +msgid "**$2**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 +msgid "**0**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:113 +msgid "" +"The correct scenario should be to return the goods at the current average " +"cost:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 +msgid "**$0**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:130 +msgid "Further thoughts on anglo saxon mode" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +msgid "stock input" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +msgid "price diff" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +msgid "($80)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +msgid "Receive vendor bill $80" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 +msgid "($64)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +msgid "Receive vendor bill $64" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +msgid "**$10**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +msgid "**$12**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +msgid "Receive vendor refund $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +msgid "$2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/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 "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:3 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:79 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:145 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:41 +msgid "Chart of accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:5 +msgid "" +"The **chart of accounts (COA)** is the list of all the accounts used to " +"record financial transactions in the general ledger of an organization." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:8 +msgid "" +"The accounts are usually listed in the order of appearance in the financial " +"reports. Most of the time, they are listed as follows :" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:11 +msgid "Balance Sheet accounts:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:13 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 +msgid "Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:14 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:79 +msgid "Liabilities" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:15 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:87 +msgid "Equity" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:17 +msgid "Profit & Loss:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:19 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:91 +msgid "Income" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:20 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:95 +msgid "Expense" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:22 +msgid "" +"When browsing your chart of accounts, you can filter the accounts by number," +" in the left column, and also group them by :guilabel:`Account Type`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Group the accounts by type in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:30 +msgid "Configuration of an account" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:32 +msgid "" +"The country you select at the creation of your database (or additional " +"company on your database) determines which **fiscal localization package** " +"is installed by default. This package includes a standard chart of accounts " +"already configured according to the country's regulations. You can use it " +"directly or set it according to your company's needs." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:38 +msgid "" +"It is not possible to modify the **fiscal localization** of a company once a" +" journal entry has been posted." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:41 +msgid "" +"To create a new account, go to :menuselection:`Accounting --> Configuration " +"--> Chart of Accounts`, click on :guilabel:`Create`, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:45 +msgid "Code and name" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 +msgid "" +"Each account is identified by its **code** and **name**, which also " +"indicates the account's purpose." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 +msgid "" +"Correctly configuring the **account type** is critical as it serves multiple" +" purposes:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +msgid "Information on the account's purpose and behavior" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:57 +msgid "Generate country-specific legal and financial reports" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +msgid "Set the rules to close a fiscal year" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:59 +msgid "Generate opening entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:61 +msgid "" +"To configure an account type, open the :guilabel:`Type` field's drop-down " +"selector and select the right type among the following list:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 +msgid "Report" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 +msgid "Category" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 +msgid "Account Types" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 +#: ../../content/applications/finance/accounting/reporting.rst:34 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:23 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:27 +msgid "Balance Sheet" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:59 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:62 +msgid "Receivable" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:69 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:71 +msgid "Bank and Cash" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:71 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:74 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:77 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:80 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:83 +msgid "Current Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:73 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:86 +msgid "Non-current Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:75 +msgid "Prepayments" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:77 +msgid "Fixed Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:79 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:65 +msgid "Payable" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:81 +msgid "Credit Card" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:83 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:89 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:92 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:95 +msgid "Current Liabilities" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:85 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:98 +msgid "Non-current Liabilities" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:89 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:101 +msgid "Current Year Earnings" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:91 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:24 +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:20 +msgid "Profit & Loss" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:93 +msgid "Other Income" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:97 +msgid "Depreciation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:99 +msgid "Cost of Revenue" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:101 +msgid "Other" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:101 +msgid "Off-Balance Sheet" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:105 +msgid "Assets, deferred expenses, and deferred revenues automation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:107 +msgid "" +"Some **account types** display a new field **to automate** the creation of " +":ref:`assets ` entries, :ref:`deferred expenses " +"` entries, and :ref:`deferred revenues " +"` entries." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:111 +msgid "You have three choices for the :guilabel:`Automation` field:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:113 +msgid ":guilabel:`No`: this is the default value. Nothing happens." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:114 +msgid "" +":guilabel:`Create in draft`: whenever a transaction is posted on the " +"account, a draft entry is created, but not validated. You must first fill " +"out the corresponding form." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:116 +msgid "" +":guilabel:`Create and validate`: you must also select a **model**. Whenever " +"a transaction is posted on the account, an entry is created and immediately " +"validated." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:120 +#: ../../content/applications/finance/accounting/taxes.rst:14 +msgid "Default taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:122 +msgid "" +"Select a **default tax** that will be applied when this account is chosen " +"for a product sale or purchase." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:126 +msgid "Tags" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:128 +msgid "" +"Some accounting reports require **tags** to be set on the relevant accounts." +" By default, you can choose among the tags that are used by the *Cash Flow " +"Statement*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:132 +msgid "Account groups" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:134 +msgid "" +"**Account groups** are useful to list multiple accounts as *sub-accounts* of" +" a bigger account and thus consolidate reports such as the **Trial " +"Balance**. By default, groups are handled automatically based on the code of" +" the group. For example, a new account `131200` is going to be part of the " +"group `131000`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:140 +msgid "Create account groups manually" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:143 +msgid "" +"Regular users should not need to create account groups manually. The " +"following section is only intended for rare and advanced use cases." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:146 +msgid "" +"To create a new account group, :ref:`developer mode ` and " +"head to :menuselection:`Accounting app --> Configuration --> Account " +"Groups`. Here, create a new group and enter the :guilabel:`name, code " +"prefix, and company` to which that group account should be available. Note " +"that you must enter the same code prefix in both :guilabel:`From` and " +":guilabel:`to` fields." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Account groups creation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:156 +msgid "" +"To display your **Trial Balance** report with your account groups, go to " +":menuselection:`Accounting app-->Reporting-->Trial Balance`, then open the " +":guilabel:`Options` menu and select :guilabel:`Hierarchy and Subtotals`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Account Groups in the Trial Balance in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:165 +msgid "Allow reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:167 +msgid "" +"Some accounts, such as accounts made to record the transactions of a payment" +" method, can be used for the reconciliation of journal entries." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:170 +msgid "" +"For example, an invoice paid with a credit card can be marked as " +":guilabel:`paid` if reconciled with its payment. Therefore, the account used" +" to record credit card payments needs to be configured as **allowing " +"reconciliation**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:174 +msgid "" +"To do so, check the :guilabel:`Allow Reconciliation` box in the account's " +"settings, and save." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:177 +msgid "Deprecated" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:179 +msgid "" +"It is not possible to delete an account once a transaction has been recorded" +" on it. You can make them unusable by using the **Deprecated** feature." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 +msgid "" +"To do so, check the :guilabel:`Deprecated` box in the account's settings, " +"and save." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:185 +msgid ":doc:`cheat_sheet`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:186 +msgid ":doc:`../vendor_bills/assets`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:187 +msgid ":doc:`../vendor_bills/deferred_expenses`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:188 +msgid ":doc:`../customer_invoices/deferred_revenues`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:189 +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:123 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:38 +msgid ":doc:`../../fiscal_localizations`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:190 +msgid "" +"`Odoo Tutorials: Chart of accounts `_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:191 +msgid "" +"`Odoo Tutorials: Update your chart of accounts " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:7 +msgid "Accounting cheat sheet" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:13 +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 "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:18 +msgid "" +"**Assets** represent the company's wealth and the goods it owns. Fixed " +"assets include buildings and offices, while current assets include bank " +"accounts and cash. The money owed by a client is an asset. An employee is " +"not an asset." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:24 +msgid "" +"**Liabilities** are obligations from past events that the company will have " +"to pay in the future (utility bills, debts, unpaid suppliers). Liabilities " +"could also be defined as a source of financing which is provided to the " +"company, also called *leverage*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:30 +msgid "" +"**Equity** is the amount of the funds contributed by the owners of the " +"company (founders or shareholders) plus previously retained earnings (or " +"losses). Each year, net profits (or losses) may be reported as retained " +"earnings or distributed to the shareholders (as a dividend)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:34 +msgid "" +"What is owned (an asset) has been financed through debts to reimburse " +"(liabilities) or equity (profits, capital)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:42 +msgid "A difference is made between **assets** and **expenses**:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:38 +msgid "" +"An **asset** is a resource with economic value that an individual, " +"corporation, or country owns or controls with the expectation that it will " +"provide a future benefit. Assets are reported on a company's balance sheet. " +"They are bought or created to increase a firm's value or benefit its " +"operations." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:42 +msgid "" +"An **expense** is the costs of operations a company bears to generate " +"revenues." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:48 +msgid "" +"The **profit and loss** (P&L) report shows the company's performance over a " +"specific period of time, usually a quarter or a fiscal year." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:53 +msgid "" +"The **revenue** refers to the money earned by the company by selling goods " +"and/or services." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:57 +msgid "" +"The **cost of goods sold** (COGS, or also known as \"Cost of Sale\") refers " +"to the sale of goods' costs (e.g., the cost of the materials and labor used " +"to create the goods)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:62 +msgid "" +"The **Gross profit** equals the revenues from sales minus the cost of goods " +"sold." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:66 +msgid "" +"**Operating expenses** (OPEX) include administration, sales and R&D " +"salaries, rent and utilities, miscellaneous costs, insurances, and anything " +"beyond the costs of products sold or the cost of sale." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:76 +msgid "Assets = Liabilities + Equity" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:81 +msgid "" +"The **chart of accounts** lists all the company's accounts: both Balance " +"sheet accounts and P&L accounts. Every transaction is recorded by debiting " +"and crediting multiple accounts in a journal entry. In a way, a chart of " +"accounts is like a company's DNA!" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:85 +msgid "" +"Every account listed in the chart of accounts belongs to a specific " +"category. In Odoo, each account has a unique code and belongs to one of " +"these categories:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:92 +msgid "**Equity and subordinated debts**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:89 +msgid "" +"**Equity** is the amount of money invested by a company's shareholders to " +"finance the company's activities." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:91 +msgid "" +"**Subordinated debts** are the amount of money lent by a third party to a " +"company to finance its activities. In the event of the dissolution of a " +"company, these third parties are reimbursed before the shareholders." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:94 +msgid "" +"**Fixed assets** are tangible (i.e., physical) items or properties that a " +"company purchases and uses to produce its goods and services. Fixed assets " +"are long-term assets. This means the assets have a useful life of more than " +"one year. They also include properties, plants, and equipments (also known " +"as \"PP&E\") and are recorded on the balance sheet with that classification." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:103 +msgid "**Current assets and liabilities**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:99 +msgid "" +"The **current assets** account is a balance sheet line item listed under the" +" Assets section, which accounts for all company-owned assets that can be " +"converted to cash within one year. Current assets include cash, cash " +"equivalents, accounts receivable, stock inventory, marketable securities, " +"prepaid liabilities, and other liquid assets." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:103 +msgid "" +"**Current liabilities** are a company's short-term financial obligations due" +" within one year. An example of a current liability is money owed to " +"suppliers in the form of accounts payable." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:108 +msgid "**Bank and cash accounts**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:106 +msgid "" +"A **bank account** is a financial account maintained by a bank or other " +"financial institution in which the financial transactions between the bank " +"and a customer are recorded." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:108 +msgid "" +"A **cash account**, or cash book, may refer to a ledger in which all cash " +"transactions are recorded. The cash account includes both the cash receipts " +"and the cash payment journals." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:115 +msgid "**Expenses and income**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:111 +msgid "" +"An **expense** is the costs of operations a company bears to generate " +"revenues. It is simply defined as the cost one is required to spend on " +"obtaining something. Common expenses include supplier payments, employee " +"wages, factory leases, and equipment depreciation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:114 +msgid "" +"The term \"**income**\" generally refers to the amount of money, property, " +"and other transfers of value received over a set period of time in exchange " +"for services or products." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:118 +msgid "Example" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:122 +msgid "" +"\\*: Customer Refund and Customer Payment boxes cannot be simultaneously " +"selected as they are contradictory." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:126 +msgid "Balance = Debit - Credit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:133 +#: ../../content/applications/finance/accounting/payments/checks.rst:84 +msgid "Journal entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:135 +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 "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:138 +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 "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:143 +msgid "" +"examples of accounting entries for various transactions. (see entries.js)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:148 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +msgid "Reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:150 +msgid "" +":doc:`Reconciliation <../../accounting/bank/reconciliation>` is the process " +"of linking journal items of a specific account and matching credits and " +"debits." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:153 +msgid "" +"Its primary purpose is to link payments to their related invoices to mark " +"them as paid. This is done by doing a reconciliation on the accounts " +"receivable account and/or the accounts payable account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:156 +msgid "Reconciliation is performed automatically by the system when:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:158 +msgid "the payment is registered directly on the invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:159 +msgid "" +"the links between the payments and the invoices are detected at the bank " +"matching process" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:0 +msgid "Customer Statement Example" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +msgid "Invoice 1" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 +msgid "Partial payment 1/2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 +msgid "70" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 +msgid "Invoice 2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 +msgid "65" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 +msgid "Partial payment 2/2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 +msgid "30" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 +msgid "Payment 2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 +msgid "Invoice 3" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:184 +msgid "50" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:184 +msgid "Total to pay" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:188 +#: ../../content/applications/finance/accounting/payments/batch.rst:80 +#: ../../content/applications/finance/accounting/reporting.rst:141 +msgid "Bank Reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:190 +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 "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:194 +msgid "" +"**matched with a previously recorded payment**: a payment is registered when" +" a check is received from a customer, then matched when checking the bank " +"statement." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:196 +msgid "" +"**recorded as a new payment**: the payment's journal entry is created and " +"reconciled with the related invoice when processing the bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:198 +msgid "" +"**recorded as another transaction**: bank transfer, direct charge, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:200 +msgid "" +"Odoo should automatically reconcile most transactions; only a few 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 "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:207 +msgid "Checks Handling" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:209 +msgid "" +"There are two approaches to managing checks and internal wire transfers:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:211 +msgid "Two journal entries and a reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:212 +msgid "One journal entry and a bank reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:216 +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 "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +msgid "Invoice ABC" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +msgid "Undeposited funds" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +msgid "Check 0123" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:241 +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 "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 +msgid "Bank Statement" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +msgid "Statement XYZ" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:3 +msgid "Multi-currency system" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:5 +msgid "" +"Odoo allows you to issue invoices, receive bills, and record transactions in" +" currencies other than the main currency configured for your company. You " +"can also set up bank accounts in other currencies and run reports on your " +"foreign currency activities." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:10 +msgid ":doc:`../bank/foreign_currency`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:20 +msgid "Main currency" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:22 +msgid "" +"The **main currency** is defined by default according to the company's " +"country. You can change it by going to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies` and changing the currency in the " +":guilabel:`Main Currency` setting." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:29 +msgid "Enable foreign currencies" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:31 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Currencies`, and " +"enable the currencies you wish to use by toggling the :guilabel:`Active` " +"button." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Enable the currencies you wish to use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:41 +msgid "Currency rates" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:44 +msgid "Manual update" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:46 +msgid "" +"To manually create and set a currency rate, go to :menuselection:`Accounting" +" --> Configuration --> Currencies`, click on the currency you wish to change" +" the rate of, and under the :guilabel:`Rates` tab, click :guilabel:`Add a " +"line` to create a new rate." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Create or modify the currency rate." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:55 +msgid "Automatic update" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:57 +msgid "" +"When you activate a second currency for the first time, :guilabel:`Automatic" +" Currency Rates` appears under :menuselection:`Accounting Dashboard --> " +"Configuration --> Settings --> Currencies`. By default, you have to click on" +" the **Update now** button (:guilabel:`🗘`) to update the rates." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:61 +msgid "" +"Odoo can update the rates at regular intervals. To do so, change the " +":guilabel:`Interval` from :guilabel:`Manually` to :guilabel:`Daily`, " +":guilabel:`Weekly`, or :guilabel:`Monthly`. You can also select the web " +"service from which you want to retrieve the latest currency rates by " +"clicking on the :guilabel:`Service` field." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:69 +msgid "Exchange difference entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:71 +msgid "" +"Odoo automatically records exchange differences entries on dedicated " +"accounts, in a dedicated journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:74 +msgid "" +"You can define which journal and accounts to use to **post exchange " +"difference entries** by going to :menuselection:`Accounting --> " +"Configuration --> Settings --> Default Accounts` and editing the " +":guilabel:`Journal`, :guilabel:`Gain Account`, and :guilabel:`Loss Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:79 +msgid "" +"If you receive a payment for a customer invoice one month after it was " +"issued, the exchange rate has likely changed since. Therefore, this " +"fluctuation implies some profit or loss due to the exchange difference, " +"which Odoo automatically records in the default **Exchange Difference** " +"journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:89 +msgid "" +"Each account can have a set currency. By doing so, all moves relevant to the" +" account are forced to have that account's currency." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:92 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Charts of " +"Accounts` and select a currency in the field :guilabel:`Account Currency`. " +"If left empty, all active currencies are handled instead of just one." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:99 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:249 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:259 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:140 +#: ../../content/applications/finance/fiscal_localizations/france.rst:194 +#: ../../content/applications/finance/fiscal_localizations/india.rst:102 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:295 +msgid "Journals" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:101 +msgid "" +"If a currency is set on a **journal**, that journal only handles " +"transactions in that currency." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:103 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open the journal you want to edit, and select a currency in the field " +":guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Select the currency for the journal to handle." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 +msgid "Multi-currency accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 +msgid "Invoices, bills, and other documents" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 +msgid "" +"For all documents, you can select the currency and journal to use for the " +"transaction on the document itself." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Select the currency and journal to use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:130 +#: ../../content/applications/finance/accounting/payments/checks.rst:58 +msgid "Payment registration" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:132 +msgid "" +"To register a payment in a currency other than your company's main currency," +" click on the :guilabel:`Register Payment` payment button of your document " +"and, in the pop-up window, select a **currency** in the :guilabel:`Amount` " +"field." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Select the currency and journal to use before registering the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:145 +msgid "" +"When creating or importing bank statements, the amount is in the company's " +"main currency. To see additional fields related to foreign currencies, click" +" on the **columns dropdown button** (:guilabel:`⋮`) next to " +":guilabel:`Amount`, and check :guilabel:`Amount Currency` and " +":guilabel:`Foreign Currency`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "The extra fields related to foreign currencies." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:154 +msgid "" +"When reconciling, Odoo displays both the foreign currency amount and the " +"equivalent amount in your company's main currency." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:160 +msgid "Exchange rate journal entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:162 +msgid "" +"To see **exchange difference journal entries**, go to " +":menuselection:`Accounting Dashboard --> Accounting --> Journals: " +"Miscellaneous`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Exchange rate journal entry." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:3 +msgid "VAT units" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:6 +msgid "This is only applicable to multi-company environments." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:8 +msgid "" +"A **VAT unit** is a group of VAT-taxable enterprises that are legally " +"independent of each other but are closely linked financially, " +"organizationally, and economically and therefore considered the same VAT-" +"taxable enterprise. **VAT units** are not mandatory, but if created, " +"constituent companies of the unit must belong to the same **country**, use " +"the same **currency**, and one company must be designated as the " +"**representative** company of the **VAT unit**. **VAT units** receive a " +"specific **tax ID** intended only for **tax returns**. **Constituent** " +"companies keep their **tax ID** used for **commercial purposes**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:17 +msgid "" +"Enterprise **A** owes €300.000,00 of VAT taxes and enterprise **B** can " +"recover €280.000,00 of VAT taxes. They form up as a **VAT unit** so that the" +" two amounts balance out and must conjointly only pay €20.000,00 of VAT " +"taxes." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:24 +msgid "" +"To configure a **VAT unit**, go to :menuselection:`Settings --> General " +"Settings`, scroll down to the :guilabel:`Companies` section, and click " +":guilabel:`Manage Companies`. Select the company to serve the " +"**representative** role, and in the :guilabel:`General Information` tab, " +"fill in the mandatory fields for the .XML export when exporting the **tax " +"report**: :guilabel:`Company Name`, :guilabel:`Address`, :guilabel:`VAT`, " +":guilabel:`Currency`, :guilabel:`Phone`, and :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst-1 +msgid "General information tab" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:35 +msgid "" +"Then, click on the :guilabel:`VAT Units` tab, :guilabel:`Add a line`, and " +"either select an existing **VAT unit**, or create a new one. Enter a " +"**name** for the unit, :guilabel:`Country` of the constituent companies and " +"tax report, the :guilabel:`Companies`, the :guilabel:`Main Company` that " +"serves the **representative** role, and the :guilabel:`Tax ID` of the **VAT " +"unit**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst-1 +msgid "VAT units tab" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:45 +msgid "Fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:47 +msgid "" +"As transactions between constituents of the same **VAT unit** are not " +"subject to VAT, it is possible to create a :doc:`tax mapping (fiscal " +"position) <../taxes/fiscal_positions>` to avoid the application of VAT on " +"inter-constituent transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:51 +msgid "" +"Be sure a constituent company has been selected before, then go to " +":menuselection:`Accounting --> Configuration --> Fiscal Positions`, and " +":guilabel:`Create` a new **fiscal position**. Click the :guilabel:`Tax " +"Mapping` tab, select the :guilabel:`Tax on Product` usually applied for " +"**non-constituent** transactions, and in :guilabel:`Tax to Apply`, select " +"the 0% tax to apply for **constituent** transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:57 +msgid "" +"Do the same for the :guilabel:`Account Mapping` tab if required, and repeat " +"this process for **each** constituent company on your database." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:61 +msgid "" +"Depending on your :doc:`localization package " +"`, taxes may vary from the " +"screenshot displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:0 +msgid "Tax mapping of fiscal position for VAT unit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:68 +msgid "" +"Then, assign the fiscal position by opening the **Contacts** app. Search for" +" a **constituent** company, and open the contact's **card**. Click the " +":guilabel:`Sales & Purchase` tab, and in the :guilabel:`Fiscal Position` " +"field, input the **fiscal position** created for the **VAT unit**. Repeat " +"the process for each **constituent** company card form, on each company " +"database." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:74 +msgid ":doc:`../taxes/fiscal_positions`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:79 +msgid "" +"The **representative** company can access the aggregated tax report of the " +"**VAT unit** by going to :menuselection:`Accounting --> Reporting --> Tax " +"Report`, and selecting the **VAT unit** in :guilabel:`Tax Unit`. This report" +" contains the aggregated transactions of all **constituents** and the .XML " +"export contains the name and VAT number of the **main** company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst-1 +msgid "VAT unit tax report" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:5 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:498 +msgid "Payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:7 +msgid "" +"In Odoo, payments can either be linked automatically to an invoice or bill " +"or be stand-alone records for use at a later date." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:10 +msgid "" +"If a payment is **linked to an invoice or bill**, it reduces the amount due " +"of the invoice. You can have multiple payments related to the same invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:13 +msgid "" +"If a payment is **not linked to an invoice or bill**, the customer has an " +"outstanding credit with your company, or your company has an outstanding " +"debit with a vendor. You can use those outstanding amounts to reduce unpaid " +"invoices/bills." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:18 +msgid ":doc:`Internal transfers `" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:19 +#: ../../content/applications/finance/accounting/payments.rst:54 +#: ../../content/applications/finance/accounting/payments.rst:78 +#: ../../content/applications/finance/accounting/payments.rst:127 +msgid ":doc:`bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:20 +msgid "" +"`Odoo Tutorials: Bank Configuration `_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:24 +msgid "Registering payment from an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:26 +msgid "" +"When clicking on :guilabel:`Register payment` in a customer invoice or " +"vendor bill, it generates a new journal entry and changes the amount due " +"according to the amount of the payment. The counterpart is reflected in an " +"outstanding receipts or payments account. At this point, the customer " +"invoice or vendor bill is marked as :guilabel:`In payment`. Then, when the " +"outstanding account is reconciled with a bank statement line, the invoice or" +" vendor bill changes to the :guilabel:`Paid` status." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:32 +msgid "" +"The information icon near the payment line displays more information about " +"the payment. You can access additional information, such as the related " +"journal, by clicking on :guilabel:`View`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "See detailed information of a payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:39 +msgid "" +"The customer invoice or vendor bill should be in the status " +":guilabel:`Posted` to register the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:41 +msgid "" +"When clicking on :guilabel:`Register payment`, you can select the amount to " +"pay and make a partial or full payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:43 +msgid "" +"If your main bank account is set as :ref:`outstanding account " +"`, and the payment is made in Odoo (not related " +"to a bank statement), invoices and bills are directly registered in the " +"status :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:46 +msgid "" +"If you unreconciled a payment, it still appears in your books but is no " +"longer linked to the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:48 +msgid "" +"If you (un)reconcile a payment in a different currency, a journal entry is " +"automatically created to post the currency exchange gains/losses (reversal) " +"amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:50 +msgid "" +"If you (un)reconcile a payment and an invoice having cash basis taxes, a " +"journal entry is automatically created to post the cash basis tax (reversal)" +" amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:57 +msgid "Registering payments not tied to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:59 +msgid "" +"When a new payment is registered via the menu :menuselection:`Customers / " +"Vendors --> Payments`, it is not directly linked to an invoice or bill. " +"Instead, the account receivable or the account payable are matched with the " +"outstanding account until they are manually matched with their related " +"invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:65 +msgid "Matching invoices and bills with payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:67 +msgid "" +"A blue banner appears when you validate a new invoice or bill and there is " +"an outstanding payment for this specific customer or vendor. It can easily " +"be matched from the invoice or the bill by clicking on :guilabel:`ADD` under" +" :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "Shows the ADD option to reconcile an invoice or a bill with a payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:74 +msgid "" +"The invoice or bill is now marked as :guilabel:`In payment` until it is " +"reconciled with the bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:81 +msgid "Batch payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:83 +msgid "" +"Batch payments allow you to group different payments to ease " +":doc:`reconciliation `. They are also useful when you " +"deposit checks to the bank or for SEPA Payments. To do so, go to " +":menuselection:`Accounting --> Customers --> Batch Payments` or " +":menuselection:`Accounting --> Vendors --> Batch Payments`. In the list view" +" of payments, you can select several payments and group them in a batch by " +"clicking on :menuselection:`Action --> Create Batch Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:91 +msgid ":doc:`payments/batch`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:92 +msgid ":doc:`payments/batch_sdd`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:95 +msgid "Payments matching" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:97 +msgid "" +"The :guilabel:`Payments matching` tool opens all unreconciled customer " +"invoices or vendor bills and gives you the opportunity to process them all " +"one by one, doing the matching of all their payments and invoices at once. " +"You can reach this tool from the :menuselection:`Accounting Dashboard --> " +"Customer Invoices / Vendor Bills`, and click on :guilabel:`⋮` and select " +":guilabel:`Payments Matching`, or by going to :menuselection:`Accounting -->" +" Reconciliation`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:104 +msgid "" +"During the :doc:`reconciliation `, if the sum of the " +"debits and credits does not match, there is a remaining balance. This either" +" needs to be reconciled at a later date or needs to be written off directly." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:109 +msgid "Batch payments matching" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:111 +msgid "" +"To reconcile several outstanding payments or invoices at once, for a " +"specific customer or vendor, the batch reconciliation feature can be used. " +"Go to :menuselection:`Accounting --> Reporting --> Aged Receivable / Aged " +"Payable`. You now see all transactions that have not been reconciled yet, " +"and when you select a customer or vendor, the :guilabel:`Reconcile` option " +"is displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "See the reconcile option" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:120 +msgid "Reconciling payments with bank statements" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:122 +msgid "" +"Once a payment has been registered, the status of the invoice or bill is " +":guilabel:`In payment`. The next step is to reconcile it with the related " +"bank statement line to have the transaction finalized and the invoice or " +"bill marked as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:3 +msgid "Batch payments: Batch deposits (checks, cash etc.)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:5 +msgid "" +"A **Batch Deposit** groups multiple payments in a single batch. This allows " +"you to deposit several payments into your bank account with a single " +"transaction. This is particularly useful to deposit cash and checks." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:9 +msgid "" +"This feature allows you to list several customer payments and print a " +"**deposit slip**. This ticket contains the details of the transactions and a" +" reference to the batch deposit. You can then select this reference during a" +" bank reconciliation to match the single bank statement line with all the " +"transactions listed in the batch deposit." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:17 +msgid "" +"To activate the feature, go to :menuselection:`Accounting --> Configuration " +"--> Settings --> Customer Payments`, activate **Batch Payments**, and click " +"on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:21 +msgid "Payment Method Types" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:23 +msgid "" +"To record new payments as part of a Batch Deposit, you have to configure " +"first the Journal on which you record them." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:26 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open the Journal you want to edit, click on *Edit*, and open the *Advanced " +"Settings* tab. In the *Payment Method Types* section, enable **Batch " +"Deposit**, and click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Payment Method Types in a journal's advanced settings" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:35 +msgid "" +"Your main bank accounts are automatically configured to process batch " +"payments when you activate the feature." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:39 +msgid "Deposit multiple payments in batch" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:42 +msgid "Record payments to deposit in batch" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:44 +msgid "" +":doc:`Register the payments <../payments>` on the bank account on which you " +"plan to deposit them by opening the *Customer Invoice* for which you " +"received a payment, and clicking on *Register Payment*. There, select the " +"appropriate Journal linked to your bank account and select *Batch Deposit* " +"as Payment Method." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "" +"Registering a customer payment as part of a Batch Deposit in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:53 +msgid "Do this step for all checks or payments you want to process in batch." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:56 +msgid "Make sure to write the payment reference in the **Memo** field." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:59 +msgid "Add payments to a Batch Deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:61 +msgid "" +"To add the payments to a Batch Deposit, go to :menuselection:`Accounting -->" +" Customers --> Batch Payments`, and click on *Create*. Next, select the Bank" +" and Payment Method, then click on *Add a line*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Filling out a new Inbound Batch Payment form on Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:69 +msgid "" +"Select all payments to include in the current Batch Deposit and click on " +"*Select*. You can also record a new payment and add it to the list by " +"clicking on *Create*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Selection of all payments to include in the Batch Deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:76 +msgid "" +"Once done, click on *Validate* to finalize your Batch Deposit. You can then " +"click on *Print* to download a PDF file to include with the deposit slip " +"that the bank usually requires to fill out." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:82 +msgid "" +"Once the bank statements are on your database, you can reconcile the bank " +"statement line with the *Batch Payment* reference. To do so, start your " +"**Bank Reconciliation** by going to your Accounting dashboard and clicking " +"on *Reconcile Items* on the related bank account. At the bank statement " +"line, click on *Choose counterpart or Create Write-off* to display more " +"options, open the *Batch Payments* tab, and select your Batch Payment. All " +"related payments are automatically added." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:89 +msgid "" +"The *Batch Payments* tab won't appear if a Partner is selected for this bank" +" statement line." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Reconciliation of the Batch Payment with all its transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:95 +msgid "" +"If a check, or a payment, couldn't be processed by the bank and is missing, " +"remove the related payment before validating the bank reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:99 +msgid ":doc:`../payments`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:100 +msgid ":doc:`batch_sdd`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:3 +msgid "Batch payments: SEPA Direct Debit (SDD)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:5 +msgid "" +"SEPA, the Single Euro Payments Area, is a payment-integration initiative of " +"the European Union for simplification of bank transfers denominated in " +"euros. With **SEPA Direct Debit** (SDD), your customers can sign a mandate " +"that authorizes you to collect future payments from their bank accounts. " +"This is particularly useful for recurring payments based on a subscription." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:10 +msgid "" +"You can record customer mandates in Odoo, and generate `.xml` files " +"containing pending payments made with an SDD mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:0 +msgid "" +"SDD is supported by all SEPA countries, which includes the 27 member states " +"of the European Union as well as additional countries." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:0 +msgid "" +"`List of all SEPA countries " +"`_." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:22 +msgid "" +"Go to :menuselection:`Accounting app --> Configuration --> Settings`, " +"activate :guilabel:`SEPA Direct Debit (SDD)`, and click on :guilabel:`Save`." +" Enter your company's :guilabel:`Creditor Identifier`. This number is " +"provided by your bank institution, or the authority responsible for " +"delivering them." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst-1 +msgid "Add a SEPA Creditor Identifier to Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:32 +msgid "SEPA Direct Debit Mandates" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:35 +msgid "Create a mandate" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:37 +msgid "" +"The :abbr:`SDD (sepa direct debit)` Mandate is the document that your " +"customers sign to authorize you to collect money directly from their bank " +"accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:40 +msgid "" +"To create a new mandate, go to :menuselection:`Accounting app --> Customers " +"--> Direct Debit Mandates`, on :guilabel:`Create`, and fill out the form. " +"Export the PDF file by clicking on :guilabel:`Print`. It is then up to your " +"customer to sign this document. Once done, upload the signed file and click " +"on :guilabel:`Validate` to start running the mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:46 +msgid "" +"Make sure that the **IBAN bank accounts details** are correctly recorded on " +"the debtor’s contact form, under the :guilabel:`Accounting` tab, and in your" +" own :doc:`Bank Account <../bank>` settings." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:50 +msgid "SEPA Direct Debit as a payment method" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:52 +msgid "" +"SDD can be used as a payment method both on your **eCommerce** or on the " +"**Customer Portal** by activating SDD as a **Payment Acquirer**. With this " +"method, your customers can create and sign their mandates themselves." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:56 +msgid "" +"To do so, go to :menuselection:`Accounting app --> Configuration --> Payment" +" Acquirers`, click on :guilabel:`SEPA Direct Debit`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:60 +msgid "" +"Make sure to change the :guilabel:`State` field to :guilabel:`Enabled`, and " +"to check :guilabel:`Online Signature`, as this is necessary to let your " +"customers sign their mandates." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:63 +msgid "" +"Customers using SDD as payment method get prompted to add their IBAN, email " +"address, and to sign their SDD mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:67 +msgid "Close or revoke a mandate" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:69 +msgid "" +"Direct debit mandates are closed automatically after their :guilabel:`End " +"Date`. If this field is left blank, the mandate keeps being **Active** until" +" it is **Closed** or **Revoked**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:72 +msgid "" +"Clicking on :guilabel:`Close` updates the mandate’s end day to the current " +"day. This means that invoices issued after the present day will not be " +"processed with an SDD payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:75 +msgid "" +"Clicking on :guilabel:`Revoke` disables the mandate immediately. No SDD " +"payment can be registered anymore, regardless of the invoice’s date. " +"However, payments that have already been registered are still included in " +"the next SDD `.xml` file." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:80 +msgid "" +"Once a mandate has been :guilabel:`closed` or :guilabel:`revoked`, it cannot" +" be reactivated." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:83 +msgid "Get paid with SEPA Direct Debit batch payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:88 +msgid "" +"You can register SDD payments for invoices issued to customers who have an " +"active SDD mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:90 +msgid "" +"To do so, open the invoice, click on :guilabel:`Register Payment`, and " +"choose :guilabel:`SEPA Direct Debit` as payment method." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:94 +msgid "Generate SEPA Direct Debit `.XML` files to submit payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:96 +msgid "" +"`.xml` files with all SDD payment instructions can be uploaded to your " +"online banking interface to process all payments at once." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:100 +msgid "" +"The files generated by Odoo follow the SEPA Direct Debit **PAIN.008.001.02**" +" specifications, as required by the SEPA customer-to-bank `implementation " +"guidelines `_, which ensures compatibility with the banks." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:105 +msgid "" +"To generate your `.xml` file of multiple pending SDD payments, you can " +"create a batch payment. To do so, go to :menuselection:`Accounting app --> " +"Customers --> Payments`, select the needed payments, then click on " +":guilabel:`Action`, and finally :guilabel:`Create a batch Payment`. Once you" +" click on :guilabel:`Validate`, the `.xml` file is directly available for " +"download." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst-1 +msgid "Generate an .XML file for your SDD payments in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:114 +msgid "" +"Finally, upload this file to your online banking interface to process the " +"payments." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:117 +msgid "" +"You can retrieve all the generated SDD `.xml` files by going to " +":menuselection:`Accounting app --> Customers --> Batch Payments`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:121 +msgid ":doc:`batch`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:123 +msgid "" +"`List of all SEPA countries " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:125 +msgid "" +"`Sepa guidelines `_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:3 +msgid "Checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:5 +msgid "" +"There are two ways to handle payments received by checks in Odoo, either by " +"using :ref:`outstanding accounts ` or by " +":ref:`bypassing the reconciliation process `." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:9 +msgid "" +"**Using outstanding accounts is recommended**, as your bank account balance " +"stays accurate by taking into account checks yet to be cashed." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:13 +msgid "" +"Both methods produce the same data in your accounting at the end of the " +"process. But if you have checks that have not been cashed in, the " +"**Outstanding Account** method reports these checks in the **Outstanding " +"Receipts** account. However, funds appear in your bank account whether or " +"not they are reconciled, as the bank value is reflected at the moment of the" +" bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:20 +msgid ":ref:`Outstanding accounts `" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:21 +msgid ":ref:`Bank reconciliation `" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:26 +msgid "Method 1: Outstanding account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:28 +msgid "" +"When you receive a check, you :doc:`record a payment " +"<../bank/reconciliation>` by check on the invoice. Then, when your bank " +"account is credited with the check's amount, you reconcile the payment and " +"statement to move the amount from the **Outstanding Receipt** account to the" +" **Bank** account." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:33 +msgid "" +"You can create a new payment method named *Checks* if you would like to " +"identify such payments quickly. To do so, go to :menuselection:`Accounting " +"--> Configuration --> Journals --> Bank`, click the :guilabel:`Incoming " +"Payments` tab, and :guilabel:`Add a line`. As :guilabel:`Payment Method`, " +"select :guilabel:`Manual`, enter `Checks` as name, and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:41 +msgid "Method 2: Reconciliation bypass" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:43 +msgid "" +"When you receive a check, you :doc:`record a payment " +"<../bank/reconciliation>` on the related invoice. The amount is then moved " +"from the **Account Receivable** to the **Bank** account, bypassing the " +"reconciliation and creating only **one journal entry**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:47 +msgid "" +"To do so, you *must* follow the following setup. Go to " +":menuselection:`Accounting --> Configuration --> Journals --> Bank`. Click " +"the :guilabel:`Incoming Payments` tab and then :guilabel:`Add a line`, " +"select :guilabel:`Manual` as :guilabel:`Payment Method`, and enter `Checks` " +"as :guilabel:`Name`. Click the :guilabel:`⋮` button, tick " +":guilabel:`Outstanding Receipts accounts`, and in the :guilabel:`Outstanding" +" Receipts accounts` column, set the :guilabel:`Bank` account for the " +"**Checks** payment method, and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst-1 +msgid "Bypass the Outstanding Receipts account using the Bank account." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:61 +msgid "By default, there are two ways to register payments made by check:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:63 +msgid "**Manual**: for single checks;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:64 +msgid "**Batch**: for multiple checks at once." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:66 +msgid "" +"This documentation focuses on **single-check** payments. For **batch " +"deposits**, see :doc:`the batch payments documentation `." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:69 +msgid "" +"Once you receive a customer check, go to the related invoice " +"(:menuselection:`Accounting --> Customer --> Invoices)`, and click " +":guilabel:`Register Payment`. Fill in the payment information:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:72 +msgid ":guilabel:`Journal: Bank`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:73 +msgid "" +":guilabel:`Payment method`: :guilabel:`Manual` (or **Checks** if you have " +"created a specific payment method);" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:75 +msgid ":guilabel:`Memo`: enter the check number;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:76 +msgid "Click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst-1 +msgid "Check payment info" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:81 +msgid "" +"The generated journal entries are different depending on the payment " +"registration method chosen." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:87 +msgid "Outstanding account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:89 +msgid "" +"The invoice is marked as :guilabel:`In Payment` as soon as you record the " +"payment. This operation produces the following **journal entry**:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +msgid "Statement Match" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:95 +#: ../../content/applications/finance/accounting/payments/checks.rst:97 +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/accounting/payments/checks.rst:108 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +#: ../../content/applications/finance/accounting/payments/checks.rst:127 +msgid "100.00" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:97 +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:76 +msgid "Outstanding Receipts" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:100 +msgid "" +"Then, once you receive the bank statements, match this statement with the " +"check of the **Outstanding Receipts** account. This produces the following " +"**journal entry**:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +msgid "X" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:111 +msgid "" +"If you use this approach to manage received checks, you get the list of " +"checks that have not been cashed in the **Outstanding Receipt** account " +"(accessible, for example, from the general ledger)." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:115 +msgid "Reconciliation bypass" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:117 +msgid "" +"The invoice is marked as :guilabel:`Paid` as soon as you record the check." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:119 +msgid "" +"With this approach, you bypass the use of **outstanding accounts**, " +"effectively getting only one journal entry in your books and bypassing the " +"reconciliation:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:3 +msgid "Follow-up on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:5 +msgid "" +"A follow-up message can be sent to customers when a payment is overdue. Odoo" +" helps you identify late payments and allows you to schedule and send the " +"appropriate reminders using **follow-up actions** that automatically trigger" +" one or more actions according to the number of overdue days. You can send " +"your follow-ups via different means, such as email, post, or SMS." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:11 +msgid "" +"`Odoo Tutorials: Payment Follow-up " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:16 +msgid "" +"To configure a :guilabel:`Follow-Up Action`, go to " +":menuselection:`Accounting --> Configuration --> Follow-up Levels`. Several " +"follow-up actions are available by default, but you can create new ones if " +"required, and can change the **name** and the **number of days** after which" +" the follow-up actions are triggered. The follow-up :guilabel:`Actions` " +"available are:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:21 +msgid ":guilabel:`Send an email`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:22 +msgid ":ref:`Send an SMS message `;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:23 +msgid ":guilabel:`Print a letter`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:24 +msgid ":ref:`Send a letter `;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:25 +msgid ":guilabel:`Manual action` (creates a task)." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:27 +msgid "" +"It is possible to automatically send a reminder by enabling the " +":guilabel:`Auto Execute` option, and attaching the *open* invoice(s) by " +"enabling :guilabel:`Join open invoices`, within a specific follow-up action." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:31 +msgid "" +"Depending on the :guilabel:`Actions` enabled, the :guilabel:`Message` tab " +"contains different message options:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:34 +msgid "" +"The :guilabel:`Email Subject` and the :guilabel:`Description` or content of " +"the email automatically used;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:36 +msgid "If you selected :guilabel:`SMS`, the content of the SMS text;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:37 +msgid "" +"If you enabled :guilabel:`Manual Action`, you can assign someone in the " +":guilabel:`Assign a Responsible` field to manage that follow-up and the " +":guilabel:`Manual Action Type` (:guilabel:`Email`, :guilabel:`Call`, etc.), " +"as well as input a description of the :guilabel:`Action To Do`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:42 +msgid "The text between `%(text)s` automatically fetches the partner's info." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:44 +msgid "**%(partner_name)s**: Partner name;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:45 +msgid "**%(date)s**: Current date;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:46 +msgid "**%(amount_due)s**: Amount due by the partner;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:47 +msgid "**%(user_signature)s**: User name;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:48 +msgid "**%(company_name)s**: User's company name." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:51 +msgid "" +"Set a negative number of days to send a reminder before the actual due date." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:54 +msgid "Follow-up reports" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:56 +msgid "" +"Overdue invoices you need to follow up on are available in " +":menuselection:`Accounting --> Customers --> Follow-up Reports`. By default," +" Odoo filters by :guilabel:`Customer Invoices` that are :guilabel:`In need " +"of action`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:60 +msgid "" +"When selecting an invoice, you see all of the customer's unpaid invoices " +"(overdue or not), and their payments. The due dates of late invoices appear " +"in red. Select the invoices that are *not* late by clicking the " +":guilabel:`Excluded` column to exclude them from the reminder you send." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:64 +msgid "" +"It is up to you to decide how to remind your customer. You can select " +":guilabel:`Print Letter`, :guilabel:`Send By Email`, :guilabel:`Send By " +"Post`, :guilabel:`Send By SMS`. Then, click on :guilabel:`Done` to view the " +"next follow-up that needs your attention." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:69 +msgid "" +"The contact information on the invoice or the contact form is used to send " +"the reminder." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:70 +msgid "" +"When the reminder is sent, it is documented in the chatter of the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:71 +msgid "" +"If it is not the right time for a reminder, you can specify the " +":guilabel:`Next Reminder Date` and click on :guilabel:`Remind me later`. You" +" will get the next report according to the next reminder date set on the " +"statement." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:76 +msgid "" +"Reconcile all bank statements right before launching the follow-up process " +"to avoid sending a reminder to a customer that has already paid." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:80 +msgid "Debtor's trust level" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:82 +msgid "" +"To know whether a customer usually pays late or not, you can set a trust " +"level by marking them as :guilabel:`Good Debtor`, :guilabel:`Normal Debtor`," +" or :guilabel:`Bad Debtor` on their follow-up report. To do so, click on the" +" bullet next to the customer's name and select a trust level." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst-1 +msgid "Set debtor's trust level" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:90 +msgid "Send reminders in batches" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:92 +msgid "" +"You can send reminder emails in batches from the :guilabel:`Follow-up " +"Reports` page. To do so, select all the reports you would like to process, " +"click on the :guilabel:`Action` gear icon, and select :guilabel:`Process " +"follow-ups`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:97 +msgid ":doc:`../../../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:98 +msgid ":doc:`../../../marketing/sms_marketing/pricing/pricing_and_faq`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:99 +msgid ":doc:`../customer_invoices/snailmail`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:3 +msgid "Forecast future bills to pay" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:5 +msgid "" +"In Odoo, you can manage payments by setting automatic **Payments Terms** and" +" **follow-ups**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:8 +msgid "Configuration: payment terms" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:10 +msgid "" +"In order to track vendor conditions, we use **Payment Terms** in Odoo. They " +"allow keeping track of due dates on invoices. Examples of **Payment Terms** " +"are:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:13 +msgid "50% within 30 days" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:14 +msgid "50% within 45 days" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:16 +msgid "" +"To create them, go to :menuselection:`Accounting --> Configuration --> " +"Invoicing: Payment Terms` and click on :guilabel:`Create` to add new terms " +"or click existing ones to modify them." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:20 +msgid "" +"`Odoo Tutorials: Payment Terms `_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:23 +msgid "" +"Once **Payment Terms** are defined, you can assign them to your vendor by " +"default. To do so, go to :menuselection:`Vendors --> Vendors`, select a " +"vendor, click the :guilabel:`Sales & Purchase` tab, and select a specific " +"**Payment Term**. This way, every time you purchase from this vendor, Odoo " +"automatically proposes the chosen Payment Term." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:29 +msgid "" +"If you do not set a specific Payment Term on a vendor, you can still set one" +" on the vendor bill." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:32 +msgid "Forecast bills to pay with the aged payable report" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:34 +msgid "" +"To track amounts to be paid to the vendors, use the **Aged Payable** report." +" To access it, go to :menuselection:`Accounting --> Reporting --> Partner " +"Reports: Aged Payable`. 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 terms). This report tells you how much you will have to " +"pay within the following months." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:41 +msgid "Select bills to pay" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:43 +msgid "" +"You can get a list of all your vendor bills by going to " +":menuselection:`Vendors --> Bills`. To view only the bills that you need to " +"pay, click :menuselection:`Filters --> Bills to Pay`. To view only overdue " +"payments, select the :guilabel:`Overdue` filter instead." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:47 +msgid "" +"You can also group bills by their due date by clicking :menuselection:`Group" +" By --> Due Date` and selecting a time period." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:3 +msgid "Internal transfers" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:5 +msgid "" +"In Odoo, internal money transfers can be made in a few clicks. You need at " +"least either two bank accounts, two cash journals, or one bank account and " +"one cash journal." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:11 +msgid "" +"An internal transfer account is automatically created on your database based" +" on your company's localization and depending on your country’s legislation." +" If needed, the default :guilabel:`Internal transfer account` can be " +"modified by going to :menuselection:`Accounting app --> Configuration --> " +"Settings` and then under the :guilabel:`Default Accounts` section." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:17 +msgid "" +"At least two bank accounts are needed to make internal transfers. Refer to " +":doc:`Bank and cash accounts section <../bank>` to see how to add an " +"additional bank account to your database." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:22 +msgid "Register an internal transfer from one bank to another" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:24 +msgid "" +"Let's say you have two bank accounts registered on your database and you " +"want to transfer 1,000 USD from Bank A to Bank B." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:28 +msgid "Log an internal transfer" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:30 +msgid "" +"From the Accounting Dashboard, click on the drop-down selection button " +"(:guilabel:`⋮`) on one of your banks. In the :guilabel:`New` column click on" +" :guilabel:`Internal Transfer` and enter the information related to the " +"transfer." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst-1 +msgid "Fill in the information related to your internal transfer" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:39 +msgid "Fill in the :guilabel:`Memo` field for automatic reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:41 +msgid "" +":guilabel:`Save` and :guilabel:`Confirm` to register your internal transfer." +" The money is now booked in the transfer account and another payment is " +"**automatically** created in the destination journal (Bank B)." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:46 +msgid "Bank journal (Bank A)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:55 +msgid "Outstanding Payments account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:57 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:73 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:123 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:144 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:58 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:75 +msgid "**Internal transfer account**" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:59 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:77 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:127 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:146 +msgid "**$1,000**" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:63 +msgid "Automated booking - Bank journal (BANK B)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:72 +msgid "Outstanding Receipts account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:80 +msgid "" +"There are one outstanding payment and one outstanding receipt pending in " +"your two bank account journals, because the bank statement confirming the " +"sending and receiving of the money has not been booked yet." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst-1 +msgid "Outstanding Payments/Receipts pending bank statement booking" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:91 +msgid "Manage and reconcile bank statements" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:93 +msgid "" +"The next step is to book the bank statements to finalize the transaction by " +"creating, :doc:`importing <../bank/bank_statements>`, or :doc:`synchronizing" +" <../bank/bank_synchronization>` your :guilabel:`Transactions lines`. Fill " +"in the :guilabel:`Ending balance` and click on the :guilabel:`Reconcile` " +"button." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst-1 +msgid "Transaction lines to be filled in prior to reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:103 +msgid ":doc:`../bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:105 +msgid "" +"In the next window, choose counterparts for the payment - in this example, " +"the outstanding payment account - then click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst-1 +msgid "Reconcile your payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:113 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:133 +msgid "Bank journal entry" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:122 +msgid "Outstanding Payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:125 +msgid "Bank Account (BANK A)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:129 +msgid "" +"The same steps must be repeated once you receive the bank statement related " +"to Bank B. Book and reconcile your bank statement lines." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:142 +msgid "Outstanding Receipt" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:145 +msgid "Bank Account (BANK B)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:3 +msgid "Pay several bills at once" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:5 +msgid "" +"Odoo offers the possibility of grouping multiple bills' payments into one, " +"facilitating the reconciliation process." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:9 +msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:10 +msgid ":doc:`/applications/finance/accounting/bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:13 +msgid "Group payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:15 +msgid "" +"To register the payment of multiple bills at once, go to " +":menuselection:`Accounting app --> Vendors --> Bills`. Then, select the " +"bills you wish to register a payment for by **ticking** the boxes next to " +"the bills. When done, either click :guilabel:`Register Payment` or " +":menuselection:`Action --> Register Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst-1 +msgid "Register payment button." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:25 +msgid "Payments can only be registered for :guilabel:`posted` bills." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:27 +msgid "" +"When registering the payments, a **pop-up window** appears. From here, you " +"can either create **separate payments** for each bill all at once by " +"clicking :guilabel:`Create Payment`, *or* create one payment by combining " +"**all** bills' payments. To **combine** all payments, tick the " +":guilabel:`Group Payments` box." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:33 +msgid "" +"The :guilabel:`Group Payments` option only appears when selecting two or " +"more bills." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst-1 +msgid "Group payments options when registering a payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:39 +msgid "" +"When selecting :guilabel:`Group Payments`, the :guilabel:`amount, currency, " +"date and memo` are all set automatically, but you can modify them according " +"to your needs." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:43 +msgid "Partial group payments with cash discounts" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:45 +msgid "" +"In case of **partial group payments with cash discounts**, you can follow " +"the steps found on the :doc:`cash discount documentation page " +"`. Make " +"sure to apply the :doc:`payment terms " +"` to the " +"**bills** *instead* of the invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/multiple.rst:53 +msgid "" +":doc:`/applications/finance/accounting/customer_invoices/payment_terms`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:3 +msgid "Online payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:5 +msgid "" +"To make it more convenient for your customers to pay the invoices you issue," +" you can activate the **Invoice Online Payment** feature, which adds a *Pay " +"Now* button on their **Customer Portal**. This allows your customers to see " +"their invoices online and pay directly with their favorite payment method, " +"making the payment process much easier." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst-1 +msgid "Payment acquirer choice after having clicked on \"Pay Now\"" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:16 +msgid "" +"Make sure your :ref:`Payment Acquirers are correctly configured " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:19 +msgid "" +"By default, \":doc:`Wire Transfer " +"`\" is the only " +"Payment Acquirer activated, but you still have to fill out the payment " +"details." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:22 +msgid "" +"To activate the Invoice Online Payment, go to :menuselection:`Accounting -->" +" Configuration --> Settings --> Customer Payments`, enable **Invoice Online " +"Payment**, and click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:26 +msgid "Customer Portal" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:28 +msgid "" +"After issuing the invoice, click on *Send & Print* and send the invoice by " +"email to the customer. They will receive an email with a link that redirects" +" them to the invoice on their **Customer Portal**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst-1 +msgid "Email with a link to view the invoice online on the Customer Portal." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:35 +msgid "" +"They can choose which Payment Acquirer to use by clicking on *Pay Now*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst-1 +msgid "\"Pay now\" button on an invoice in the Customer Portal." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:42 +msgid ":doc:`/applications/finance/payment_acquirers`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:3 +msgid "Pay by checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:5 +msgid "" +"Once you decide to pay a supplier bill, you can select to pay by check. You " +"can then print all the payments registered by check. Finally, the bank " +"reconciliation process will match the checks you sent to suppliers with " +"actual bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:13 +msgid "Activate checks payment methods" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:15 +msgid "" +"To activate the checks payment method, go to :menuselection:`Accounting --> " +"Configuration --> Checks`, there you can activate the payment method as well" +" as set up the :guilabel:`Check Layout`. Once activated the " +":guilabel:`Checks` setting, the feature is automatically setup for your " +":guilabel:`Outgoing Payments`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:21 +msgid "" +"Some countries require specific modules to print checks; such modules may be" +" installed by default. For instance, the :guilabel:`U.S. Checks Layout` " +"module is required to print U.S. checks." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:26 +msgid "Compatible check stationery for printing checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:29 +msgid "United States" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:31 +msgid "For the United States, Odoo supports by default the check formats of:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:33 +msgid "" +"**Quickbooks & Quicken**: check on top, stubs in the middle and bottom;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:34 +msgid "**Peachtree**: check in the middle, stubs on top and bottom;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:35 +msgid "**ADP**: check in the bottom, and stubs on the top." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:38 +msgid "Pay a supplier bill with a check" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:40 +msgid "Paying a supplier with a check is done in three steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:42 +msgid "registering a payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:43 +msgid "printing checks in batch for all registered payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:44 +msgid "reconciling bank statements" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:47 +msgid "Register a payment by check" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:49 +msgid "" +"To register a payment, open any supplier bill from the menu " +":menuselection:`Purchases --> Vendor Bills`. Once the supplier bill is " +"validated, you can register a payment. Set the :guilabel:`Payment Method` to" +" :guilabel:`Checks` and validate the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:55 +msgid "Print checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:57 +msgid "" +"On your :guilabel:`Accounting Dashboard` in the :guilabel:`Bank` Journal, " +"you can see the number of checks registered. By clicking on " +":guilabel:`Checks to print` you have got the possibility to print the " +"reconciled checks." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:61 +msgid "" +"To print all checks in batch, select all payments from the list view and " +"click on :guilabel:`Print`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:3 +msgid "Pay with SEPA" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:5 +msgid "" +"SEPA, the Single Euro Payments Area, is a payment-integration initiative of " +"the European Union to simplify bank transfers denominated in euros. SEPA " +"allows you to send payment orders to your bank to automate bank wire " +"transfers." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:9 +msgid "SEPA is supported by the banks of the 27 EU member states, as well as:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:11 +msgid "EFTA countries:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:13 +msgid "Iceland;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:14 +msgid "Liechtenstein;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:15 +msgid "Norway;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:16 +msgid "Switzerland." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:18 +msgid "Non-EEA SEPA countries:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:20 +msgid "Andorra;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:21 +msgid "Monaco;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:22 +msgid "San Marino;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:23 +msgid "United Kingdom;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:24 +msgid "Vatican City State." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:26 +msgid "Non-EEA territories:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:28 +msgid "Saint-Pierre-et-Miquelon;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:29 +msgid "Guernsey;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:30 +msgid "Jersey;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:31 +msgid "Isle of Man." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:33 +msgid "" +"When paying a bill in Odoo, you can select SEPA mandates as a payment " +"option. At the day's end, you can generate the SEPA file containing all bank" +" wire transfers and send it to the bank." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:36 +msgid "" +"By default, the file follows the SEPA Credit Transfer **'pain.001.001.03'** " +"specifications. This is a well-defined standard among banks. However, for " +"Swiss and German companies, other formats are used " +"**'pain.001.001.03.ch.02'** for Switzerland and **'pain.001.003.03'** for " +"Germany." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:40 +msgid "" +"Once the payments are processed by your bank, you can directly import the " +"account statement in Odoo. The bank reconciliation process will seamlessly " +"match the SEPA orders you sent to your bank with actual bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:48 +msgid "Activate SEPA Credit Transfer (SCT)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:50 +msgid "" +"To pay suppliers with SEPA, you must activate the **SEPA Credit Transfer** " +"setting. To do so, go to :menuselection:`Accounting --> Configuration --> " +"Settings --> Vendor Payments: SEPA Credit Transfer (SCT)`. By activating the" +" setting and filling out your company data, you will be able to use the SCT " +"option when paying your vendor." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:56 +msgid "" +"According to the localization package installed, the **SEPA Direct Debit** " +"and **SEPA Credit Transfer** modules may be installed by default. If not, " +"they need to be :ref:`installed `." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:60 +msgid "Activate SEPA payment methods on banks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:62 +msgid "" +"From the accounting dashboard, click on the drop-down menu (:guilabel:`⋮`) " +"on your bank journal and select :guilabel:`Configuration`. Click the " +":guilabel:`Outgoing Payments` tab, and, if not already present, add " +":guilabel:`SEPA Credit Transfer` under :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:66 +msgid "" +"Make sure to specify the IBAN account number (domestic account numbers do " +"not work with SEPA) and the BIC (bank identifier code) in the " +":guilabel:`Journal Entries` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:70 +msgid "Registering payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:72 +msgid "" +"You can register and vendor payments made with SEPA. To do so, go to " +":menuselection:`Accounting --> Vendors --> Payments`. When creating your " +"payment, select :guilabel:`SEPA Credit Transfer` as the :guilabel:`Payment " +"Method`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:76 +msgid "" +"The first time you pay a vendor with SEPA, you have to fill in the " +":guilabel:`Recipient Bank Account` field with the bank name, IBAN, and BIC " +"(Bank Identifier Code). Odoo automatically verifies if the IBAN format is " +"respected." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:80 +msgid "" +"For future payments to this vendor, Odoo will automatically suggest you the " +"bank account, but it remains possible to select a new one." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:83 +msgid "" +"Once your payment is registered, do not forget to confirm it. You can also " +"pay vendor bills from the bill directly using the :guilabel:`Register " +"Payment` button at the top of a vendor bill. The form is the same, but the " +"payment is directly linked to the bill and will be automatically reconciled " +"with it." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:8 +msgid "Main reports available" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:10 +msgid "" +"Besides the reports created specifically in each localisation module, a few " +"very useful **generic** and **dynamic reports** are available for all " +"countries :" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:14 +msgid "**Balance Sheet**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:15 +msgid "**Profit and Loss**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:16 +msgid "**Executive Summary**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:17 +msgid "**General Ledger**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:18 +msgid "**Aged Payable**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:19 +msgid "**Aged Receivable**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:20 +msgid "**Cash Flow Statement**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:21 +msgid "**Tax Report**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:22 +msgid "**Bank Reconciliation**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:24 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:28 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:36 +msgid "" +"The **Balance Sheet** shows a snapshot of the assets, liabilities and equity" +" of your organisation as at a particular date." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:42 +msgid "Profit and Loss" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:44 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:51 +msgid "Executive Summary" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:53 +msgid "" +"The **Executive Summary** allows for a quick look at all the important " +"figures you need to run your company." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:56 +msgid "" +"In very basic terms, this is what each of the items in this section is " +"reporting :" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:71 +msgid "**Performance:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:62 +msgid "**Gross profit margin:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:61 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:68 +msgid "**Net profit margin:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:65 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:71 +msgid "**Return on investment (p.a.):**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:71 +msgid "" +"The ratio of net profit made, to the amount of assets the company used to " +"make those profits." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:91 +msgid "**Position:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:75 +msgid "**Average debtor days:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:75 +msgid "" +"The average number of days it takes your customers to pay you (fully), " +"across all your customer invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:78 +msgid "**Average creditor days:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:78 +msgid "" +"The average number of days it takes you to pay your suppliers (fully) across" +" all your bills." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:83 +msgid "**Short term cash forecast:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:81 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:91 +msgid "**Current assets to liabilities:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:86 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:96 +msgid "General Ledger" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:98 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:107 +msgid "Aged Payable" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:109 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:116 +msgid "Aged Receivable" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:118 +msgid "" +"The **Aged Receivables** report shows the sales invoices that were awaiting " +"payment during a selected month and several months prior." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:124 +msgid "Cash Flow Statement" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:126 +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 "" + +#: ../../content/applications/finance/accounting/reporting.rst:133 +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:101 +msgid "Tax Report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:135 +msgid "" +"This report allows you to see the **net** and **tax amounts** for all the " +"taxes grouped by type (sale/purchase)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:5 +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:111 +msgid "Analytic accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:8 +msgid ":doc:`analytic/timesheets`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:9 +msgid ":doc:`analytic/purchases_expenses`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:11 +msgid "The analytic accounting can be used for several purposes:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:13 +msgid "analyse costs of a company" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:15 +msgid "reinvoice time to a customer" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:17 +msgid "analyse performance of a service or a project" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:19 +msgid "" +"To manage analytic accounting, you have to activate it in " +":menuselection:`Configuration --> Settings`:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:24 +msgid "" +"To illustrate analytic accounts clearly, you will follow three use cases, " +"each in one of three different types of company:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:27 +msgid "Industrial company: Costs Analyse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:29 +msgid "Law Firm: reinvoice spent hours" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:31 +msgid "IT/Services Company: performance analysis" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:34 +msgid "Case 1: Industrial company: Costs Analyse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:36 +msgid "" +"In industry, you will often find analytic charts of accounts structured into" +" departments and products the company itself is built on." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:39 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:44 +msgid "" +"**Analytic Chart of Accounts for an Industrial Manufacturing Company**:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:46 +msgid "Marketing Department" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:48 +msgid "Commercial Department" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:50 +msgid "Administration Department" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:52 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:71 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:75 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:77 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:85 +msgid "Production Range 1" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:54 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:73 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:87 +msgid "Production Range 2" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:56 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:63 +msgid "" +"Here is a possible breakdown of some general accounting entries for the " +"example above, allocated to various analytic accounts:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:67 +msgid "**General accounts**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:67 +msgid "**Analytic accounts**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:69 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:160 +msgid "**Title**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:69 +msgid "**Value**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:71 +msgid "Purchase of Raw Material" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:71 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:73 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:75 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:77 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:89 +msgid "2122" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:71 +msgid "1500" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:71 +msgid "-1 500" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:73 +msgid "Subcontractors" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:73 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:77 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:89 +msgid "450" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:73 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:77 +msgid "-450" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:75 +msgid "Credit Note for defective materials" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:75 +msgid "200" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:77 +msgid "Transport charges" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:79 +msgid "Staff costs" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:79 +msgid "2121" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:79 +msgid "10000" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:79 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:89 +msgid "Marketing" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:79 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:85 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:87 +msgid "-2 000" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:81 +msgid "Commercial" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:81 +msgid "-3 000" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:83 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:170 +msgid "Administrative" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:83 +msgid "-1 000" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:89 +msgid "PR" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:89 +msgid "-400" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:92 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:98 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:106 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:110 +msgid "" +"This analytic representation by department is generally used by trading " +"companies and industries." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:113 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:118 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:123 +msgid "Case 2: Law Firm: costs of human resources?" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:125 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:129 +msgid "" +"A principal preoccupation of law firms is the invoicing of hours worked, and" +" the profitability by case and by employee." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:132 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:138 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:142 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:148 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:156 +msgid "" +"The following table shows an example of different analytic entries that you " +"can find for your analytic account:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:160 +msgid "**Amount**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:160 +msgid "**General Account**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:162 +msgid "Study the file (1 h)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:162 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:164 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:168 +#: ../../content/applications/finance/accounting/reporting/analytic.rst:172 +msgid "Case 1.1" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:162 +msgid "-15" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:164 +msgid "Search for information (3 h)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:164 +msgid "-45" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:166 +msgid "Consultation (4 h)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:166 +msgid "Case 2.1" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:166 +msgid "-60" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:168 +msgid "Service charges" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:168 +msgid "280" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:168 +msgid "705 – Billing services" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:170 +msgid "Stationery purchase" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:170 +msgid "-42" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:170 +msgid "601 – Furniture purchase" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:170 +msgid "42" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:172 +msgid "Fuel Cost -Client trip" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:172 +msgid "-35" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:172 +msgid "613 – Transports" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:172 +msgid "35" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:174 +msgid "Staff salaries" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:174 +msgid "6201 – Salaries" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:174 +msgid "3 000" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:177 +msgid "" +"Such a structure allows you to make a detailed study of the profitability of" +" various transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:180 +msgid "" +"For more details about profitablity, please read the following document: " +":doc:`analytic/timesheets`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:183 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:190 +msgid "Case 3: IT Services Company: performance analysis" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:192 +msgid "Most IT service companies face the following problems:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:194 +msgid "project planning," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:196 +msgid "invoicing, profitability and financial follow-up of projects," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:198 +msgid "managing support contracts." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:200 +msgid "" +"To deal with these problems, you would use an analytic chart of accounts " +"structured by project and by sale order." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:203 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:207 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:213 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:220 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:222 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic.rst:226 +msgid "" +"Analytic accounting is flexible and easy to use through all Odoo " +"applications (sales, purchase, timesheet, production, invoice, …)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:3 +msgid "Track costs of purchases, expenses, subcontracting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:8 +msgid "" +"Thanks to analytical accounting we can track costs of purchases, expenses " +"and subcontracting in the accounting module." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:29 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:38 +msgid "Enable Analytical accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:40 +msgid "" +"Next step is to activate the analytical accounting. In the accounting app, " +"select :menuselection:`Configuration --> Settings` and thick the Analytic " +"accounting box." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:47 +msgid "" +"Moreover, scroll down and tick the **Analytic accounting for purchases** " +"box." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:53 +msgid "Don't forget to save your changes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:56 +msgid "Create an Analytical account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:58 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:66 +msgid "We will point all our costs to this account to keep track of them." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:69 +msgid "Record an expense" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:71 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:76 +msgid "Create an expense product" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:78 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:87 +msgid "Book the expense" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:89 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:96 +msgid "" +"Submit to manager and wait for the manager to approve and post the journal " +"entries." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:100 +msgid "Create a Purchase Order linked to the analytical account" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:103 +msgid "Purchase Product" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:105 +msgid "" +"We also need to buy a software for our customers. In the purchase app create" +" a purchase order for the software product. Within the line we can link the " +"product's cost with the analytical account. Specify the order line and " +"select the correct analytical account. Confirm the sale." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:114 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:118 +msgid "Subcontracting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:120 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:127 +msgid "You can also track cost with timesheets, see: :doc:`timesheets`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:130 +msgid "Track costs in accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:132 +msgid "" +"Now that everything is booked and points to the analytical account. Simply " +"open it to check the costs related to that account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:135 +msgid "" +"Enter the accounting module, click on :menuselection:`Advisers --> Analytic " +"Accounts --> Open Charts`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:138 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:145 +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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:3 +msgid "Track costs of human resources with timesheets" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:38 +msgid "Apply your changes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:41 +msgid "Create an employee" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:62 +msgid "Issue a Sales Order" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/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 "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:75 +msgid "" +"For more information on how to create a sales order based on time and " +"material please see " +":doc:`/applications/sales/sales/invoicing/time_materials`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:78 +msgid "" +"We save a Sales Order with the service product **External Consulting**. An " +"analytical account will automatically be generated once the **Sales Order** " +"is confirmed. Our employees will have to point to that account (in this case" +" **SO002-Smith&Co**) in order to be able to invoice their hours (see picture" +" below)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:88 +msgid "Fill in timesheet" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:90 +msgid "" +"As an employee linked to a user, Harry can enter the **Timesheet** app and " +"specify his timesheets for the contract. Logged on Harry's account we enter " +"the **Timesheet** app and enter a detailed line pointing to the **Analytical" +" Account** discussed above." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:95 +msgid "Harry worked three hours on a SWOT analysis for Smith&Co." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:100 +msgid "" +"In the meantime, Cedric discussed businesses needs with the customer for 1 " +"hour and specified it as well in his personal timesheet, pointing as well on" +" the **Analytic Account**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:104 +msgid "" +"In the **Sales Order** we notice that the delivered amounts of hours is " +"automatically computed (see picture below)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:113 +msgid "" +"Thanks to analytic accounts we are able to have an overview of HR cost and " +"revenues. All the revenues and cost of this transactions have been " +"registered in the **SO002-Smith&Co** account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:117 +msgid "We can use two methods to analyze this situation." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:120 +msgid "Without filters" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:122 +msgid "" +"If we pointed all our costs and revenues of the project on the correct " +"analytical account we can easily retrieve the cost and revenues related to " +"this analytical account. Enter the *Accounting* app, select " +":menuselection:`Adviser --> Analytic Accounts --> Open Charts`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:127 +msgid "" +"Note : you can specify a period for **Analysis**. If you want to open the " +"current situation you should keep the fields empty. We can already note the " +"credit and debit balance of the account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:134 +msgid "" +"If we click on the account a special button is provided to have the details " +"of cost and revenues (see picture below)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:140 +msgid "" +"Click the button **Cost/Revenue** to have an overview of cost and revenues " +"with the corresponding description." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:144 +msgid "With filters" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:146 +msgid "We can thus filter this information from the **Analytic Entries**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:148 +msgid "" +"Enter the **Accounting** app, and click on :menuselection:`Adviser --> " +"Analytic Entries`. In this menu we have several options to analyse the human" +" resource cost." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:151 +msgid "" +"We filter on the **Analytic account** so we can see the cost and revenues of" +" the project. Add a custom **Filter** where the **Analytic Account** " +"contains the **Sales Order** number." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:158 +msgid "" +"In the results we see timesheets activities and invoiced lines with the " +"corresponding costs and revenues." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:164 +msgid "" +"We can group the different analytical accounts together and check their " +"respective revenues. Simply group by **Analytic account** and select the " +"**Graph view** to have a clear overview." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:3 +msgid "Financial budget" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:5 +msgid "" +"Managing budgets is an essential part of running a business. Budgets help " +"people become more intentional with how money is spent and direct people to " +"organize and prioritize their work to meet financial goals. They allow the " +"planning of a desired financial outcome and then measure the actual " +"performance against the plan. Odoo manages budgets using both **general** " +"and **analytic accounts**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:13 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> " +"Analytics section`, and enable :guilabel:`Budget Management`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:17 +msgid "Budgetary positions" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:19 +msgid "" +"Budgetary positions are lists of accounts for which you want to keep budgets" +" (typically expense or income accounts)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:22 +msgid "" +"To define budgetary positions, go to :menuselection:`Accounting --> " +"Configuration --> Management: Budgetary Positions` and :guilabel:`New`. Add " +"a :guilabel:`Name` to your budgetary position and select the " +":guilabel:`Company` it applies to. Click :guilabel:`Add a line` to add one " +"or more accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:28 +msgid "" +"Each budgetary position can have any number of accounts from the chart of " +"accounts, though it must have at least one." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:32 +msgid "Use case" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:34 +msgid "Let’s illustrate this with an example." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:36 +msgid "" +"We just started a project with *Smith & Co*, and we would like to budget the" +" income and expenses of that project. We plan on having a revenue of 1000, " +"and we don’t want to spend more than 700." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:39 +msgid "" +"First, we need to define what accounts relate to our project’s expenses. Go " +"to :menuselection:`Accounting --> Configuration --> Management: Budgetary " +"positions`, and click :guilabel:`New` to add a position. Add the accounts " +"wherein expenses will be booked." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "display the Smith and Co expenses" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:47 +msgid "" +"Let's repeat the steps to create a budgetary position that reflects the " +"revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "display the Smith and Co revenue" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:54 +msgid "Analytical accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:56 +msgid "" +"Odoo needs to know which costs or expenses are relevant to a specified " +"budget, as the above general accounts may be used for different projects. Go" +" to :menuselection:`Accounting --> Configuration --> Analytic Accounting: " +"Analytic Accounts` and click :guilabel:`New` to add a new **Analytic " +"Account** called *Smith & Co*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:61 +msgid "" +"The :guilabel:`Plan` field has to be completed. Plans group multiple " +"analytic accounts; they distribute costs and benefits to analyze business " +"performance. **Analytic Plans** can be created or configured by going to " +":menuselection:`Accounting --> Configuration --> Analytic Accounting: " +"Analytic Plans`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:66 +msgid "" +"When creating a new customer invoice and/or vendor bill, you have to refer " +"to this analytic account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "add analytic accounts in a new invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:73 +msgid "Define the budget" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:75 +msgid "" +"Let’s set our targets. We specified that we expect to gain 1000 with this " +"project, and we would like not to spend more than 700. Go to " +":menuselection:`Accounting --> Management: Budgets` and click " +":guilabel:`New` to create a new budget for *Smith & Co* project." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:79 +msgid "" +"First, fill in your :guilabel:`Budget Name`. Then, select the " +":guilabel:`Period` wherein the budget is applicable. Next, add the " +":guilabel:`Budgetary Position` you want to track, define the related " +":guilabel:`Analytic Account`, and add the :guilabel:`Planned Amount`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "budget lines display" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:88 +msgid "" +"When recording a planned amount related to expenses, the amount must be " +"negative." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:91 +msgid "Check your budget" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:93 +msgid "" +"Go to :menuselection:`Accounting --> Management: Budgets` and find the " +"*Smith & Co* Project to see how it evolves according to the expenses or " +"income for the related analytic account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:96 +msgid "" +"The :guilabel:`Practical Amount` evolves when a new journal entry related to" +" your analytic account and an account from your budgetary position is " +"created." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:99 +msgid "" +"The :guilabel:`Theoretical Amount` represents the amount of money you " +"theoretically could have spent or should have received based on the date. " +"For example, suppose your budget is 1200 for 12 months (January to " +"December), and today is 31 of January. In that case, the theoretical amount " +"will be 100 since this is the actual amount that could have been made." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:3 +msgid "Custom reports" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:8 +msgid "" +"Odoo 13 comes with a powerful and easy-to-use reporting framework. Creating " +"new reports (such as a tax report or a balance sheet or income statement " +"with specific groupings and layout ) to suit your needs is now easier than " +"ever." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:14 +msgid "Activate the developer mode" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:16 +msgid "" +"In order to have access to the financial report creation interface, the " +":ref:`developer mode ` needs to be activated." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:20 +msgid "Create your financial report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:22 +msgid "" +"First, you need to create your financial report. To do that, go to " +":menuselection:`Accounting --> Configuration --> Financial Reports`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:28 +msgid "" +"Once the name is entered, there are two other parameters that need to be " +"configured:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:31 +msgid "**Show Credit and Debit Columns**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:33 +msgid "**Analysis Period** :" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:35 +msgid "Based on date ranges (e.g. Profit and Loss)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:37 +msgid "Based on a single date (e.g. Balance Sheet)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:39 +msgid "" +"Based on date ranges with 'older' and 'total' columns and last 3 months " +"(e.g. Aged Partner Balances)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:42 +msgid "Bases on date ranges and cash basis method (e.g. Cash Flow Statement)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:46 +msgid "Add lines in your custom reports" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:48 +msgid "" +"After you've created the report, you need to fill it with lines. They all " +"need a **name**, a **code** (that is used to refer to the line), a " +"**sequence number** and a **level** (Used for the line rendering)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:55 +msgid "" +"In the **formulas** field you can add one or more formulas to assign a value" +" to the balance column (and debit and credit column if applicable – " +"separated by ;)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:59 +msgid "You have several objects available in the formula :" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:61 +msgid "" +"``Ndays`` : The number of days in the selected period (for reports with a " +"date range)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:64 +msgid "" +"Another report, referenced by its code. Use ``.balance`` to get its balance " +"value (also available are ``.credit``, ``.debit`` and ``.amount_residual``)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:68 +msgid "" +"A line can also be based on the sum of account move lines on a selected " +"domain. In which case you need to fill the domain field with an Odoo domain " +"on the account move line object. Then an extra object is available in the " +"formulas field, namely ``sum``, the sum of the account move lines in the " +"domain. You can also use the group by field to group the account move lines " +"by one of their columns." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:75 +msgid "Other useful fields :" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:77 +msgid "**Type** : Type of the result of the formula." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:79 +msgid "" +"**Is growth good when positive** : Used when computing the comparison " +"column. Check if growth is good (displayed in green) or not." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:82 +msgid "" +"**Special date changer** : If a specific line in a report should not use the" +" same dates as the rest of the report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:85 +msgid "" +"**Show domain** : How the domain of a line is displayed. Can be foldable " +"(``default``, hidden at the start but can be unfolded), ``always`` (always " +"displayed) or ``never`` (never shown)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:90 +msgid ":doc:`..`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:3 +msgid "Data inalterability check report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:5 +msgid "" +"Tax authorities in some countries require companies to **prove their posted " +"accounting entries are inalterable**, meaning that once an entry has been " +"posted, it can no longer be changed." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:8 +msgid "" +"To do so, Odoo can use the **SHA-256 algorithm** to create a unique " +"fingerprint for each posted entry. This fingerprint is called a hash. The " +"hash is generated by taking an entry's essential data (the values of the " +"`date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and " +"`partner_id` fields), concatenating it, and inputting it to the SHA-256 hash" +" function, which then outputs a fixed size (256-bit) string of characters. " +"The hash function is deterministic (:dfn:`the same input always creates the " +"same output`): any minor modification to the original data would completely " +"change the resulting hash. Consequently, the SHA-256 algorithm is often " +"used, among others, for data integrity verification purposes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:17 +msgid "" +"In addition, the previous entry's hash is always added to the next entry to " +"form a **hash chain**. This is used to ensure a new entry is not added " +"afterward between two posted entries, as doing so would break the hash " +"chain." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:22 +msgid "" +"Hashes generated by the SHA-256 algorithm are theoretically not unique, as " +"there is a finite number of possible values. However, this number is " +"exceptionally high: 2²⁵⁶, which is a lot bigger than the number of atoms in " +"the known universe. This is why hashes are considered unique in practice." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:30 +msgid "Lock posted entries with hash" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:32 +msgid "" +"To start using the hashing function, go to :menuselection:`Accounting --> " +"Configuration > Journals`. Open the journal for which you want to activate " +"the feature, go to the :guilabel:`Advanced Settings` tab, and enable " +":guilabel:`Lock Posted Entries with Hash`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:37 +msgid "" +"Once you post an entry on a locked journal, you cannot disable the feature " +"anymore, nor edit any posted entry." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:43 +msgid "Report download" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:45 +msgid "" +"To download the data inalterability check report, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Reporting` and" +" click on :guilabel:`Download the Data Inalterability Check Report`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:48 +msgid "" +"The report's first section is an overview of all your journals and their " +"configuration. Under the inalterability check column, you can see whether or" +" not a journal's posted entries are locked with a hash (V) or not (X). The " +"coverage column tells you when a journal's posted entries started being " +"locked." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst-1 +msgid "Configuration report for two journals" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:57 +msgid "" +"The second section gives you the result of the data consistency check for " +"each hashed journal. You can view the first hashed entry and its " +"corresponding hash and the last hashed entry and its corresponding hash." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst-1 +msgid "Data consistency check report for a journal" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:3 +msgid "Intrastat" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 +msgid "" +"`Intrastat `_ is the data collection and " +"statistics production system for goods traded among EU member states. It " +"collects data on:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:9 +msgid "" +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:11 +msgid "" +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:13 +msgid "Returns of goods." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:16 +msgid "" +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"`_, preferring instead " +"*intra-Union trade in goods statistics*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:23 +msgid "General configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:25 +msgid "" +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the **Customer Invoices** section, tick " +":guilabel:`Intrastat` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:31 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located, and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:34 +msgid "" +"If your warehouses are located in multiple regions, you can define the " +"region code for each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:43 +msgid "Default Incoterm" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "" +"You can set **default Incoterms** for your company by selecting an Intrastat" +" **code** in the :guilabel:`Default Incoterm` field of the **Customer " +"Invoices** section, and then clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:54 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:59 +msgid "Commodity code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:61 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature `_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:64 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:68 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:74 +msgid "Country of origin" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:76 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:82 +msgid "Invoices and bills configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:84 +msgid "" +"Once products are properly configured, several settings must be enabled on " +"the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:90 +msgid "Transaction code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:92 +msgid "" +"Transaction codes are used to identify a transaction's nature. To set a " +"transaction code on an invoice line, create an invoice or bill, click the " +":guilabel:`⋮` button, tick :guilabel:`Intrastat`, and use the newly-added " +":guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:101 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:107 +msgid "Partner country" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:109 +msgid "" +"The partner country is the vendor's or customer's country, depending on " +"whether it is an invoice or bill. It is automatically filled in using the " +":guilabel:`Country` field in the **contact form** of the partner." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:113 +msgid "" +"To edit the partner country manually, click on the :guilabel:`Other Info` " +"tab when on an invoice or bill, and select the :guilabel:`Intrastat " +"Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "Transport code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:121 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch). Once you have selected a :ref:`partner" +" country `, the :guilabel:`Intrastat Transport " +"Mode` becomes available." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "Value of the goods" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:130 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "Partner configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:138 +msgid "" +"Two fields from the partner's **contact form** are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set ` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:143 +msgid "Generate the Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:145 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration ` and the " +"information on the :ref:`products `, " +":ref:`invoices and bills `, and " +":ref:`partners `." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"Export the report as a PDF, XLSX, or XML file to submit it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:153 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:155 +msgid "Invoice or bill reference number;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:156 +msgid "" +":guilabel:`System`, which is a code automatically generated depending on " +"whether the document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:158 +msgid "" +":ref:`Country `, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:160 +msgid ":ref:`Transaction Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:161 +msgid "" +":ref:`Region Code ` (if your company is located in " +"Belgium);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:162 +msgid ":ref:`Commodity Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:163 +msgid ":ref:`Origin Country `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:164 +msgid ":ref:`Partner VAT `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid ":ref:`Transport Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:166 +msgid "" +":ref:`Value `, which is always expressed in EUR even if the" +" original invoice or bill used another currency." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 +msgid "Silverfin integration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:5 +msgid "" +"`Silverfin `_ is a third-party service provider " +"that offers a cloud platform for accountants." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:8 +msgid "" +"Odoo and Silverfin provide an integration to automate the synchronization of" +" data." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:13 +msgid "" +"To configure this integration, you need to input the following data into " +"your Silverfin account:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:15 +msgid "user's email address" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:16 +msgid ":ref:`Odoo API key `" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:17 +msgid "URL of the Odoo database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:18 +msgid "name of your Odoo database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:23 +msgid "Odoo API key" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:25 +msgid "" +"You can create Odoo external API keys either :ref:`for a single database " +"` (hosting: Odoo Online, On-premise, and Odoo.sh) or" +" :ref:`for multiple databases managed by a user ` " +"(hosting: Odoo Online)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:30 +msgid "" +"These API keys are personal and provide full access to your user account. " +"Store it securely." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:31 +msgid "" +"You can copy the API key only at its creation, and you cannot retrieve it " +"later." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:32 +msgid "If you need it again, create a new API key (and delete the old one)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:35 +msgid ":doc:`/developer/reference/external_api`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:40 +msgid "One key per database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:42 +msgid "" +"To create a new API key valid for a single database, click on the user menu," +" then on :guilabel:`My Profile`. Under the :guilabel:`Account Security` tab," +" click on :guilabel:`New API key`, confirm your password, give a descriptive" +" name to your new key, and copy the new API key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst-1 +msgid "creation of an Odoo external API key for a database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:51 +msgid ":ref:`api/external_api/keys`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:56 +msgid "One key for multiple databases (fiduciaries)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:58 +msgid "" +"To create a new API key valid for all the databases of a single user **(the " +"easiest for fiduciaries)**, navigate to `Odoo's website " +"`_ and sign in with your administrator account. Next," +" open `your account security settings in developer mode " +"`_, click on :guilabel:`New API " +"Key`, confirm your password, give a descriptive name to your new key, and " +"copy the new API key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst-1 +msgid "creation of an Odoo external API key for an Odoo user" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:3 +msgid "Tax return (VAT declaration)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:5 +msgid "" +"Companies with a registered :abbr:`VAT (Value Added Tax)` number must submit" +" a **tax return** on a monthly or quarterly basis, depending on their " +"turnover and the registration regulation. A tax return - or VAT return - " +"gives the tax authorities information about the taxable transactions made by" +" the company. The **output tax** is charged on the number of goods and " +"services sold by a business, while the **input tax** is the tax added to the" +" price when goods or services are purchased. Based on these values, the " +"company can calculate the tax amount they have to pay or be refunded." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:14 +msgid "" +"You can find additional information about VAT and its mechanism on this page" +" from the European Commission: `\"What is VAT?\" " +"`_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:25 +msgid "Tax Return Periodicity" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:27 +msgid "" +"The configuration of the **Tax Return Periodicity** allows Odoo to compute " +"your tax return correctly and also to send you a reminder to never miss a " +"tax return deadline." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:30 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. " +"Under the :guilabel:`Tax Return Periodicity`, you can set:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:33 +msgid "" +":guilabel:`Periodicity`: define here whether you submit your tax return on a" +" monthly or quarterly basis;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:35 +msgid "" +":guilabel:`Reminder`: define when Odoo should remind you to submit your tax " +"return;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:36 +msgid "" +":guilabel:`Journal`: select the journal in which to record the tax return." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "Configure how often tax returns have to be made in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:43 +msgid "" +"This is usually configured during the :doc:`app's initial set up " +"<../get_started>`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:48 +msgid "Tax Grids" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:50 +msgid "" +"Odoo generates tax reports based on the :guilabel:`Tax Grids` settings that " +"are configured on your taxes. Therefore, it is crucial to make sure that all" +" recorded transactions use the right taxes. You can see the :guilabel:`Tax " +"Grids` by opening the :guilabel:`Journal Items` tab of any invoice and bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "see which tax grids are used to record transactions in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:59 +msgid "" +"To configure your tax grids, go to :menuselection:`Accounting --> " +"Configuration --> Taxes`, and open the tax you want to modify. There, you " +"can edit your tax settings, along with the tax grids that are used to record" +" invoices or credit notes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "Configure taxes and their tax grids in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:68 +msgid "" +"Taxes and reports are usually already pre-configured in Odoo: a :ref:`fiscal" +" localization package ` is installed " +"according to the country you select at the creation of your database." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:75 +msgid "Close a tax period" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:80 +msgid "Tax Lock Date" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:82 +msgid "" +"Any new transaction whose accounting date prior to the :guilabel:`Tax Lock " +"Date` has its tax values moved to the next open tax period. This is useful " +"to make sure that no change can be made to a report once its period is " +"closed." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:86 +msgid "" +"Therefore, we recommend locking your tax date before working on your " +":guilabel:`Closing Journal Entry`. This way, other users cannot modify or " +"add transactions that would have an impact on the :guilabel:`Closing Journal" +" Entry`, which can help you avoid some tax declaration errors." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:91 +msgid "" +"To check the current :guilabel:`Tax Lock Date`, or to edit it, go to " +":menuselection:`Accounting --> Accounting --> Actions: Lock Dates`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "Lock your tax for a specific period in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:103 +msgid "" +"Once all the transactions involving taxes have been posted for the period " +"you want to report, open your :guilabel:`Tax Report` by going to " +":menuselection:`Accounting --> Reporting --> Audit Reports: Tax Report`. " +"Make sure to select the right period you want to declare by using the date " +"filter, this way you can have an overview of your tax report. From this " +"view, you can easily access different formats of your tax report, such as " +"`PDF` and XLSX. These include all the values to report to the tax " +"authorities, along with the amount you have to pay or be refunded." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "download the PDF with your Tax Report in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:115 +msgid "" +"If you forgot to lock your tax date before clicking on :guilabel:`Closing " +"Journal Entry`, then Odoo automatically locks your fiscal period on the same" +" date as the accounting date of your entry. This safety mechanism can " +"prevent some fiscal errors, but it is advised to lock your tax date manually" +" before, as described above." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:121 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:37 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:109 +#: ../../content/applications/finance/accounting/taxes/retention.rst:70 +msgid ":doc:`../taxes`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:122 +msgid ":doc:`../get_started`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:3 +msgid "Year-end closing" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.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 "" + +#: ../../content/applications/finance/accounting/reporting/year_end.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 "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:13 +msgid "Verify that all **customer invoices** have been entered and approved." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:15 +msgid "Confirm that you have entered and agreed all **vendor bills**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:17 +msgid "Validate all **expenses**, ensuring their accuracy." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:19 +msgid "" +"Corroborate that all **received payments** have been entered and recorded " +"accurately." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:25 +msgid "Manage fiscal years" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:27 +msgid "" +"In most cases, the fiscal years last 12 months. If it is your case, you just" +" have to define what is the last day of your fiscal year in the accounting " +"settings. By default, it is set on the 31st December." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:31 +msgid "" +"However, there might be some exceptions. For example, if it is the first " +"fiscal year of your business, it could last more or less than 12 months. In " +"this case, some additional configuration is required." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:35 +msgid "" +"Go to :menuselection:`accounting --> configuration --> settings` and " +"activate the fiscal years." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:38 +msgid "" +"You can then configure your fiscal years in :menuselection:`accounting --> " +"configuration --> fiscal years`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:42 +msgid "" +"You only have to create fiscal years if they last more or less than 12 " +"months." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:48 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1230 +msgid "Year-end checklist" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:50 +msgid "Run a **Tax report**, and verify that your tax information is correct." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:52 +msgid "Reconcile all accounts on your **Balance Sheet**:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:54 +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 "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:58 +msgid "" +"Reconcile all transactions in your cash and bank accounts by running your " +"**Aged Receivables** and **Aged Payables** reports." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:61 +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 "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:65 +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 "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:72 +msgid "" +"Your accountant/bookkeeper will likely verify your balance sheet items and " +"book entries for:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:75 +msgid "" +"Year-end manual adjustments, using the **Adviser Journal Entries** menu (For" +" example, the **Current Year Earnings** and **Retained Earnings** reports)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:79 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1252 +msgid "**Work in Progress**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:81 +msgid "**Depreciation Journal Entries**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:83 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1254 +msgid "**Loans**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:85 +msgid "**Tax adjustments**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:87 +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 "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:92 +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 "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:103 +msgid "Closing the fiscal year" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:105 +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 "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:112 +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 "" + +#: ../../content/applications/finance/accounting/taxes.rst:7 +msgid "" +"There are numerous types of **taxes**, and their application varies greatly," +" depending mostly on your company's localization. To make sure they are " +"recorded with accuracy, Odoo's tax engine supports all kinds of uses and " +"computations." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:16 +msgid "" +"**Default Taxes** define which taxes are automatically selected when there " +"is no other indication about which tax to use. For example, Odoo prefills " +"the **Taxes** field with the Default Taxes when you create a new product or " +"add a new line on an invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "" +"Odoo fills out the Tax field automatically according to the Default Taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:23 +msgid "" +"To change your **Default Taxes**, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Taxes --> Default Taxes`, select the " +"appropriate taxes for your default **Sales Tax** and **Purchase Tax**, and " +"click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Define which taxes to use by default on Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:31 +msgid "" +"**Default Taxes** are automatically set up according to the country selected" +" at the creation of your database, or when you set up a :ref:`fiscal " +"localization package ` for your company." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:38 +msgid "Activate Sales Taxes from the List view" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:40 +msgid "" +"As part of your :ref:`fiscal localization package " +"`, most of your country's sales taxes are " +"already preconfigured on your database. However, only a few of them are " +"activated by default, so that you can activate only the ones relevant for " +"your business." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:44 +msgid "" +"To activate Sale Taxes, go to :menuselection:`Accounting --> Configuration " +"--> Taxes` and use the *Activate* toggle button to activate or deactivate a " +"tax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Activate pre-configured taxes in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:55 +msgid "" +"To edit or create a **Tax**, go to :menuselection:`Accounting --> " +"Configuration --> Taxes` and open a tax or click on *Create*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Edition of a tax in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:64 +msgid "" +"Taxes have three different labels, each one having a specific use. Refer to " +"the following table to see where they are displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:68 +msgid ":ref:`Tax Name `" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:68 +msgid ":ref:`Label on Invoice `" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:68 +msgid ":ref:`Tax Group `" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:71 +msgid "Back end" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:71 +msgid "*Taxes* column on exported invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:71 +msgid "Above the *Total* line on exported invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:76 +msgid "Basic Options" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:81 +msgid "Tax Name" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:83 +msgid "" +"The **Tax Name** as you want to display it for backend users. This is the " +":ref:`label ` you see while editing Sales Orders, Invoices, " +"Products, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:89 +msgid "Tax Computation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:91 +msgid "**Group of Taxes**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:93 +msgid "" +"The tax is a combination of multiple sub-taxes. You can add as many taxes " +"you want, in the order you want them to be applied." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:97 +msgid "" +"Make sure that the tax sequence is correct, as the order in which they are " +"may impact the taxes' amounts computation, especially if one of the taxes " +":ref:`affects the base of the subsequent ones `." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:101 +msgid "**Fixed**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:103 +msgid "" +"The tax has a fixed amount in the default currency. The amount remains the " +"same, regardless of the Sales Price." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:106 +msgid "" +"For example, a product has a Sales Price of $1000, and we apply a *$10 " +"fixed* tax. We then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:138 +#: ../../content/applications/finance/accounting/taxes.rst:251 +msgid "Product's Sales Price" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:138 +#: ../../content/applications/finance/accounting/taxes.rst:251 +msgid "Price without tax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:138 +#: ../../content/applications/finance/accounting/taxes.rst:251 +msgid "Tax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:138 +#: ../../content/applications/finance/accounting/taxes.rst:251 +msgid "Total" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:112 +#: ../../content/applications/finance/accounting/taxes.rst:127 +#: ../../content/applications/finance/accounting/taxes.rst:141 +#: ../../content/applications/finance/accounting/taxes.rst:254 +msgid "1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:112 +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "10" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:112 +msgid "1,010.00" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:115 +msgid "**Percentage of Price**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:117 +msgid "" +"The *Sales Price* is the taxable basis: the tax's amount is computed by " +"multiplying the Sales Price by the tax's percentage." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:120 +msgid "" +"For example, a product has a Sales Price of $1000, and we apply a *10% of " +"Price* tax. We then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:127 +msgid "1,100.00" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:130 +msgid "**Percentage of Price Tax Included**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:132 +msgid "" +"The *Total* is the taxable basis: the tax's amount is a percentage of the " +"Total." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:134 +msgid "" +"For example, a product has a Sales Price of $1000, and we apply a *10% of " +"Price Tax Included* tax. We then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:141 +msgid "111.11" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:141 +msgid "1,111.11" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:147 +msgid "Active" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:149 +msgid "Only **Active** taxes can be added to new documents." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:152 +msgid "" +"It is not possible to delete taxes that have already been used. Instead, you" +" can deactivate them to prevent future use." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:156 +msgid "" +"This field can be modified from the *List View*. See :ref:`above " +"` for more information." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:162 +msgid "Tax Scope" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:164 +msgid "" +"The **Tax Scope** determines the tax's application, which also restricts " +"where it is displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:166 +msgid "**Sales**: Customer Invoices, Product's Customer Taxes, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:167 +msgid "**Purchase**: Vendor Bills, Product's Vendor Taxes, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:168 +msgid "**None**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:171 +msgid "" +"You can use **None** for taxes that you want to include in a :ref:`Group of " +"Taxes ` but that you don't want to list along with other " +"Sales or Purchase taxes." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:177 +msgid "Definition tab" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:179 +msgid "" +"Allocate with precision the amount of the taxable basis or percentages of " +"the computed tax to multiple accounts and Tax Grids." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Allocate tax amounts to the right accounts and tax grids" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:185 +msgid "**Based On**:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:187 +msgid "Base: the price on the invoice line" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:188 +msgid "% of tax: a percentage of the computed tax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:190 +msgid "**Account**: if defined, an additional Journal Item is recorded." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:191 +msgid "" +"**Tax Grids**: used to generate :doc:`Tax Reports ` " +"automatically, according to your country's regulations." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:197 +msgid "Advanced Options tab" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:202 +msgid "Label on Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:204 +msgid "" +"The label of the tax, as displayed on each invoice line in the **Taxes** " +"column. This is the :ref:`label ` visible to *front end* " +"users, on exported invoices, on their Customer Portals, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "The Label on Invoices is displayed on each invoice line" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:214 +msgid "Tax Group" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:216 +msgid "" +"Select to which **Tax Group** the tax belongs. The Tax Group name is the " +":ref:`label ` displayed above the *Total* line on exported " +"invoices, and the Customer Portals." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:219 +msgid "" +"Tax groups include different iterations of the same tax. This can be useful " +"when you must record differently the same tax according to :doc:`Fiscal " +"Positions `." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "The Tax Group name is different from the Label on Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:225 +msgid "" +"In the example above, we see a 0% tax for Intra-Community customers in " +"Europe. It records amounts on specific accounts and with specific tax grids." +" Still, to the customer, it is a 0% tax. That's why the :ref:`Label on the " +"Invoice ` indicates *0% EU*, and the Tax Group name, " +"above the *Total* line, indicates *0%*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:233 +msgid "Include in Analytic Cost" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:235 +msgid "" +"With this option activated, the tax's amount is assigned to the same " +"**Analytic Account** as the invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:241 +msgid "Included in Price" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:243 +msgid "" +"With this option activated, the total (including the tax) equals the **Sales" +" Price**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:245 +msgid ":dfn:`Total = Sales Price = Computed Tax-Excluded price + Tax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:247 +msgid "" +"For example, a product has a Sales Price of $1000, and we apply a *10% of " +"Price* tax, which is *included in the price*. We then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:254 +msgid "900.10" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:254 +msgid "90.9" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:254 +msgid "1,000.00" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:258 +msgid "" +"If you need to define prices accurately, both tax-included and tax-excluded," +" please refer to the following documentation: :doc:`taxes/B2B_B2C`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:262 +msgid "" +"**Invoices**: By default, the Line Subtotals displayed on your invoices are " +"*Tax-Excluded*. To display *Tax-Included* Line Subtotals, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Customer " +"Invoices`, and select *Tax-Included* in the **Line Subtotals Tax Display** " +"field, then click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:266 +msgid "" +"**eCommerce**: By default, the prices displayed on your eCommerce website " +"are *Tax-Excluded*. To display *Tax-Included* prices, go to " +":menuselection:`Website --> Configuration --> Settings --> Pricing`, and " +"select *Tax-Included* in the **Product Prices** field, then click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:273 +msgid "Affect Base of Subsequent Taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:275 +msgid "" +"With this option, the total tax-included becomes the taxable basis for the " +"other taxes applied to the same product." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:278 +msgid "" +"You can configure a new :ref:`Group of Taxes ` to include" +" this tax, or add it directly to a product line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "The eco-tax is taken into the basis of the 21% VAT tax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:285 +msgid "" +"The order in which you add the taxes on a product line has no effect on how " +"amounts are computed. If you add taxes directly on a product line, only the " +"tax sequence determines the order in which they are applied." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:289 +msgid "" +"To reorder the sequence, go to :menuselection:`Accounting --> Configuration " +"--> Taxes`, and drag and drop the lines with the handles next to the tax " +"names." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:0 +msgid "The taxes' sequence in Odoo determines which tax is applied first" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:297 +msgid ":doc:`taxes/fiscal_positions`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:298 +msgid ":doc:`taxes/B2B_B2C`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:299 +msgid ":doc:`taxes/taxcloud`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:300 +msgid ":doc:`reporting/tax_returns`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:3 +msgid "B2B (tax excluded) and B2C (tax included) pricing" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:5 +msgid "" +"When working with consumers, prices are usually expressed with taxes " +"included in the price (e.g., in most eCommerce). But, when you work in a B2B" +" environment, companies usually negotiate prices with taxes excluded." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:9 +msgid "" +"Odoo manages both use cases easily, as long as you register your prices on " +"the product with taxes excluded or included, but not both together. If you " +"manage all your prices with tax included (or excluded) only, you can still " +"easily do sales order with a price having taxes excluded (or included): " +"that's easy." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:15 +msgid "" +"This documentation is only for the specific use case where you need to have " +"two references for the price (tax included or excluded), for the same " +"product. The reason of the complexity is that there is not a symmetrical " +"relationship with prices included and prices excluded, as shown in this use " +"case, in belgium with a tax of 21%:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:21 +msgid "Your eCommerce has a product at **10€ (taxes included)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:23 +msgid "This would do **8.26€ (taxes excluded)** and a **tax of 1.74€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:25 +msgid "" +"But for the same use case, if you register the price without taxes on the " +"product form (8.26€), you get a price with tax included at 9.99€, because:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:29 +msgid "**8.26€ \\* 1.21 = 9.99€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:31 +msgid "" +"So, depending on how you register your prices on the product form, you will " +"have different results for the price including taxes and the price excluding" +" taxes:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:35 +msgid "Taxes Excluded: **8.26€ & 10.00€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:37 +msgid "Taxes Included: **8.26€ & 9.99€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:40 +msgid "" +"If you buy 100 pieces at 10€ taxes included, it gets even more tricky. You " +"will get: **1000€ (taxes included) = 826.45€ (price) + 173.55€ (taxes)** " +"Which is very different from a price per piece at 8.26€ tax excluded." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:45 +msgid "" +"This documentation explains how to handle the very specific use case where " +"you need to handle the two prices (tax excluded and included) on the product" +" form within the same company." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:50 +msgid "" +"In terms of finance, you have no more revenues selling your product at 10€ " +"instead of 9.99€ (for a 21% tax), because your revenue will be exactly the " +"same at 9.99€, only the tax is 0.01€ higher. So, if you run an eCommerce in " +"Belgium, make your customer a favor and set your price at 9.99€ instead of " +"10€. Please note that this does not apply to 20€ or 30€, or other tax rates," +" or a quantity >1. You will also make you a favor since you can manage " +"everything tax excluded, which is less error prone and easier for your " +"salespeople." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:63 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:14 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:13 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:13 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:65 +msgid "" +"The best way to avoid this complexity is to choose only one way of managing " +"your prices and stick to it: price without taxes or price with taxes " +"included. Define which one is the default stored on the product form (on the" +" default tax related to the product), and let Odoo compute the other one " +"automatically, based on the pricelist and fiscal position. Negotiate your " +"contracts with customers accordingly. This perfectly works out-of-the-box " +"and you have no specific configuration to do." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:73 +msgid "" +"If you can not do that and if you really negotiate some prices with tax " +"excluded and, for other customers, others prices with tax included, you " +"must:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:77 +msgid "" +"always store the default price **tax excluded** on the product form, and " +"apply a tax (price excluded on the product form)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:80 +msgid "" +"create a pricelist with prices in **tax included**, for specific customers" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:83 +msgid "" +"create a fiscal position that switches the tax excluded to a tax included" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:86 +msgid "" +"assign both the pricelist and the fiscal position to customers who want to " +"benefit to this pricelist and fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:89 +msgid "For the purpose of this documentation, we will use the above use case:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:91 +msgid "your product default sale price is 8.26€ tax excluded" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:93 +msgid "" +"but we want to sell it at 10€, tax included, in our shops or eCommerce " +"website" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:99 +msgid "eCommerce" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:101 +msgid "" +"If you only use B2C or B2B prices on your website, simply select the " +"appropriate setting in the **Website** app settings." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:104 +msgid "" +"If you have both B2B and B2C prices on a single website, please follow these" +" instructions:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:106 +msgid "" +"Activate the :ref:`developer mode ` and go to " +":menuselection:`General Settings --> Users & Companies --> Groups`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:108 +msgid "" +"Open either `Technical / Tax display B2B` or `Technical / Tax display B2C`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:109 +msgid "" +"Under the :guilabel:`Users` tab, add the users requiring access to the price" +" type. Add B2C users in the B2C group and B2B users in the B2B group." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:113 +msgid "Setting your products" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:115 +msgid "" +"Your company must be configured with tax excluded by default. This is " +"usually the default configuration, but you can check your **Default Sale " +"Tax** from the menu :menuselection:`Configuration --> Settings` of the " +"Accounting application." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:123 +msgid "" +"Once done, you can create a **B2C** pricelist. You can activate the " +"pricelist feature per customer from the menu: :menuselection:`Configuration " +"--> Settings` of the Sale application. Choose the option **different prices " +"per customer segment**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:128 +msgid "" +"Once done, create a B2C pricelist from the menu " +":menuselection:`Configuration --> Pricelists`. It's also good to rename the " +"default pricelist into B2B to avoid confusion." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:132 +msgid "" +"Then, create a product at 8.26€, with a tax of 21% (defined as tax not " +"included in price) and set a price on this product for B2C customers at 10€," +" from the :menuselection:`Sales --> Products` menu of the Sales application:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:141 +msgid "Setting the B2C fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:143 +msgid "" +"From the accounting application, create a B2C fiscal position from this " +"menu: :menuselection:`Configuration --> Fiscal Positions`. This fiscal " +"position should map the VAT 21% (tax excluded of price) with a VAT 21% (tax " +"included in price)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:152 +msgid "Test by creating a quotation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:154 +msgid "" +"Create a quotation from the Sale application, using the " +":menuselection:`Sales --> Quotations` menu. You should have the following " +"result: 8.26€ + 1.73€ = 9.99€." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:161 +msgid "" +"Then, create a quotation but **change the pricelist to B2C and the fiscal " +"position to B2C** on the quotation, before adding your product. You should " +"have the expected result, which is a total price of 10€ for the customer: " +"8.26€ + 1.74€ = 10.00€." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:169 +msgid "This is the expected behavior for a customer of your shop." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:172 +msgid "Avoid changing every sale order" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:174 +msgid "" +"If you negotiate a contract with a customer, whether you negotiate tax " +"included or tax excluded, you can set the pricelist and the fiscal position " +"on the customer form so that it will be applied automatically at every sale " +"of this customer." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:179 +msgid "" +"The pricelist is in the **Sales & Purchases** tab of the customer form, and " +"the fiscal position is in the accounting tab." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:182 +msgid "" +"Note that this is error prone: if you set a fiscal position with tax " +"included in prices but use a pricelist that is not included, you might have " +"wrong prices calculated for you. That's why we usually recommend companies " +"to only work with one price reference." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:3 +msgid "Avatax integration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:5 +msgid "Avatax is a tax calculation provider that can be integrated in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:10 +msgid "Credential configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:12 +msgid "" +"To integrate Avatax with Odoo, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Taxes` and add your Avatax credentials in the" +" :guilabel:`Avatax` section." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:16 +msgid "" +"If you do not yet have credentials, click on :guilabel:`How to Get " +"Credentials`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Configure Avatax settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:25 +msgid "Tax mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:27 +msgid "" +"The Avatax integration is available on Sale Orders and Invoices with the " +"included Avatax fiscal position." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:30 +msgid "" +"Before using the integration, specify an :guilabel:`Avatax Category` on the " +"product categories." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Specify Avatax Category on products" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:36 +msgid "" +"Avatax Categories may be overridden or set on individual products as well." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Override product categories as needed" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:45 +msgid "Address validation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:47 +msgid "" +"Manually validate customer addresses by clicking the :guilabel:`Validate " +"address` link in the customer form view." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Validate customer addresses" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:54 +msgid "" +"If preferred, choose to keep the newly validated address or the original " +"address in the wizard that pops up." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Address validation wizard" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:64 +msgid "Tax calculation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:66 +msgid "" +"Automatically calculate taxes on Odoo quotations and invoices with Avatax by" +" confirming the documents. Alternatively, calculate the taxes manually by " +"clicking the :guilabel:`Compute taxes using Avatax` button while these " +"documents are in draft mode." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:70 +msgid "" +"Use the :guilabel:`Avalara Code` field that's available on customers, " +"quotations, and invoices to cross-reference data in Odoo and Avatax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:74 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:39 +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:151 +msgid ":doc:`fiscal_positions`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:3 +msgid "Cash basis taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:5 +msgid "" +"Cash basis taxes are due when the payment is made, as opposed to standard " +"taxes that are due when the invoice is confirmed. Reporting your income and " +"expenses to the government based on the cash basis method is mandatory in " +"some countries and under some conditions." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:10 +msgid "" +"You sell a product in the 1st quarter of your fiscal year, and the payment " +"is received in the 2nd quarter. Based on the cash basis method, the tax you " +"must pay is for the 2nd quarter." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:16 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and under " +"the :guilabel:`Taxes` section, enable :guilabel:`Cash Basis`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:19 +msgid "" +"Then, define the :guilabel:`Tax Cash Basis Journal`. Click on the external " +"link button next to the journal to update its default properties such as the" +" :guilabel:`Journal Name`, :guilabel:`Type` or :guilabel:`Short Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst-1 +msgid "Select your Tax Cash Basis Journal and click on the external link" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:28 +msgid "" +"By default, the journal entries of the :guilabel:`Cash Basis Taxes` journal " +"are named using the :guilabel:`CABA` short code." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:31 +msgid "" +"Once this is done, go to :menuselection:`Accounting --> Configuration --> " +"Accounting: Taxes` to configure your taxes. You can either " +":guilabel:`Create` a new tax or update an existing one by clicking on it." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:35 +msgid "" +"The :guilabel:`Account` column reflects the proper transitional accounts to " +"post taxes until the payment is registered." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst-1 +msgid "" +"Fill in the account column with a transitional accounts where taxes go until the payment\n" +"is registered" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:43 +msgid "" +"In the :guilabel:`Advanced Options` tab, decide of the :guilabel:`Tax " +"Exigilibity`. Select :guilabel:`Based on Payment`, so the tax is due when " +"the payment of the invoice is received. You can then also define the " +":guilabel:`Cash Basis Transition Account` where the tax amount is recorded " +"as long as the original invoice has not been reconciled." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst-1 +msgid "" +"Fill in the Cash Basis Transition Account where taxes amounts go until payment\n" +"reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:54 +msgid "Impact of cash basis taxes on accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:56 +msgid "" +"To illustrate the impact of cash basis taxes on accounting transactions, " +"let's take an example with the sales of a product that costs 1,000$, with a " +"cash basis tax of 15%." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:63 +msgid "" +"The following entries are created in your accounting, and the tax report is " +"currently empty." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:66 +msgid "**Customer journal (INV)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:70 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:86 +msgid "Receivable $1,150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:72 +msgid "Income $1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:74 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:103 +msgid "Temporary tax account $150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:77 +msgid "When the payment is then received, it is registered as below :" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:80 +msgid "**Bank journal (BANK)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:84 +msgid "Bank $1,150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:90 +msgid "" +"Once the payment is registered, you can use the :guilabel:`Cash Basis " +"Entries` smart button on the invoice to access them directly." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:93 +msgid "" +"Finally, upon reconciliation of the invoice with the payment, the below " +"entry is automatically created:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:97 +msgid "**Tax Cash Basis Journal (Caba)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:101 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:105 +msgid "Income account $1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:107 +msgid "Tax Received $150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:110 +msgid "" +"The journal items :guilabel:`Income account` vs. :guilabel:`Income account` " +"are neutral, but they are needed to ensure correct tax reports in Odoo with " +"accurate base tax amounts." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:113 +msgid "" +"Using a default :guilabel:`Base Tax Received Account` is recommended so your" +" balance is at zero and your income account is not polluted by unnecessary " +"accounting movements. To do so, go to :menuselection:`Configuration --> " +"Settings --> Taxes`, and select a :guilabel:`Base Tax Received Account` " +"under :guilabel:`Cash Basis`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:3 +msgid "EU intra-community distance selling" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:5 +msgid "" +"EU intra-community distance selling involves the cross-border trade of goods" +" and services from vendors registered for VAT purposes to individuals (B2C) " +"located in a European Union member state. The transaction is conducted " +"remotely, typically through online platforms, mail orders, telephone, or " +"other means of communication." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:10 +msgid "" +"EU intra-community distance selling is subject to specific VAT rules and " +"regulations. The vendor must charge VAT per the VAT rate applicable in the " +"buyer's country." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:14 +msgid "" +"This remains applicable even if the vendor is located outside of the " +"European Union." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:19 +msgid "" +"The **EU Intra-community Distance Selling** feature helps you comply with " +"this regulation by creating and configuring new **fiscal positions** and " +"**taxes** based on your company's country. To enable it, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes`, tick " +":guilabel:`EU Intra-community Distance Selling`, and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst-1 +msgid "" +"EU intra-community Distance Selling feature in Odoo Accounting settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:28 +msgid "" +"Whenever you add or modify taxes, you can automatically update your fiscal " +"positions. To do so, go to :menuselection:`Accounting/Invoicing --> Settings" +" --> Taxes --> EU Intra-community Distance Selling` and click on the " +":guilabel:`Refresh tax mapping`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:33 +msgid "" +"We highly recommend checking that the proposed mapping is suitable for the " +"products and services you sell before using it." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:42 +msgid "One-Stop Shop (OSS)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:44 +msgid "" +"The :abbr:`OSS (One-Stop Shop)` system introduced by the European Union " +"simplifies VAT collection for **cross-border** sales of goods and services. " +"It primarily applies to business-to-consumer **(B2C)** cases. With the OSS, " +"businesses can register for VAT in their home country and use a single " +"online portal to handle VAT obligations for their sales within the EU. There" +" are **two primary schemes**: the **Union OSS** scheme for cross-border " +"services and the **Import OSS** scheme for goods valued at or below €150." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:52 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:679 +msgid "Reports" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:54 +msgid "" +"To generate **OSS sales** or **OSS imports** reports and submit them onto " +"the OSS portal, go to :menuselection:`Accounting --> Reporting --> Tax " +"Report`, click :guilabel:`Tax Report: Global Summary`, and select either " +":guilabel:`OSS Sales` or :guilabel:`OSS Imports`. Once selected, click on " +":guilabel:`PDF`, :guilabel:`XLSX`, or :guilabel:`XML` in the top-left " +"corner. This generates the currently-opened report in the selected format. " +"Once generated, log into the platform of your competent federal authority to" +" submit it onto the OSS portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst-1 +msgid "OSS reports view" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:65 +msgid "" +"`European Commission: OSS | Taxation and Customs Union " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:3 +msgid "Fiscal positions (tax and account mapping)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:5 +msgid "" +"Default taxes and accounts are set on products and customers to create new " +"transactions on the fly. However, you might have to use different taxes and " +"record the transactions on different accounts, according to your customers' " +"and providers' localizations and business types." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:9 +msgid "" +"**Fiscal Positions** allow you to create *sets of rules* to automatically " +"adapt the taxes and the accounts used for a transaction." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "" +"Example: Belgian to Intra-Community tax mapping with Fiscal Positions in " +"Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:16 +msgid "They can be applied in various ways:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:18 +msgid "" +":ref:`automatically applied, based on some rules " +"`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:19 +msgid ":ref:`manually applied on a transaction `" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:20 +msgid "" +":ref:`assigned to a partner, on its contact form " +"`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:23 +msgid "" +"A few Fiscal Positions are already preconfigured on your database, as part " +"of your :ref:`fiscal localization package `." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:30 +msgid "Tax and Account Mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:32 +msgid "" +"To edit or create a Fiscal Position, go to :menuselection:`Accounting --> " +"Configuration --> Fiscal Positions`, and open the entry you want to modify " +"or click on *Create*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:35 +msgid "" +"The mapping of taxes and accounts is based on the default taxes and accounts" +" defined in the products' forms." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:38 +msgid "" +"To map to another tax or account, fill out the right column (**Tax to " +"Apply**/**Account to Use Instead**)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:40 +msgid "" +"To remove a tax, rather than replacing it with another, leave the field " +"**Tax to Apply** empty." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:41 +msgid "" +"To replace a tax with multiple other taxes, add multiple lines with the same" +" **Tax on Product**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:44 +msgid "" +"The mapping only works with *active* taxes. Therefore, make sure they are " +"active by going to :menuselection:`Accounting --> Configuration --> Taxes`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:50 +msgid "Automatic application" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:52 +msgid "" +"You can configure your Fiscal Positions to be applied automatically, " +"following a set of conditions." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:54 +msgid "" +"To do so, open the Fiscal Position you want to modify and click on **Detect " +"Automatically**. You can configure a few conditions:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:57 +msgid "" +"**VAT Required**: The VAT number *must* be indicated in the customer's " +"contact form." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:58 +msgid "" +"**Country Group** / **Country**: The Fiscal Position is applied to these " +"countries." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Example of settings to apply a Fiscal Position automatically" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:65 +msgid "" +"Taxes on **eCommerce orders** are automatically updated once the visitor has" +" logged in or filled out their billing details." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:69 +msgid "" +"The Fiscal Positions' **sequence** - the order in which they are arranged - " +"defines which Fiscal Position to apply if the conditions are met in multiple" +" Fiscal Positions." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:72 +msgid "" +"For example, if the first Fiscal Position targets *country A*, and the " +"second Fiscal Position targets a *Country Group* that also comprises " +"*country A*, only the first Fiscal Position will be applied to customers " +"from *country A*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:79 +msgid "Application" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:84 +msgid "Assign a Fiscal Position to a partner" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:86 +msgid "" +"You can manually define which Fiscal Position must be used by default for a " +"specific partner." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:88 +msgid "" +"To do so, open the partner's contact form, go to the **Sales & Purchase** " +"tab, edit the **Fiscal Position** field, and click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "" +"Selection of a Fiscal Position on a Sales Order / Invoice / Bill in Odoo " +"Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:98 +msgid "Choose Fiscal Positions manually on Sales Orders, Invoices, and Bills" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:100 +msgid "" +"To manually select which Fiscal Position to use for a new Sales Order, " +"Invoice, or Bill, go to the **Other Info** tab and select the right **Fiscal" +" Position** *before* adding product lines." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:110 +msgid ":doc:`taxcloud`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:111 +msgid ":doc:`B2B_B2C`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:3 +msgid "Withholding taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:14 +msgid "As, an example, in Colombia you may have the following invoice:" +msgstr "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:39 +msgid "" +"Once the tax is defined, you can use it in your products, sales order or " +"invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:48 +msgid "Applying retention taxes on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/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 "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:63 +msgid "The printed invoice will show the different amounts in each tax group." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:3 +msgid "TaxCloud integration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:5 +msgid "" +"TaxCloud calculates the sales tax rate in real time for every state, city, " +"and special jurisdiction in the United States. It keeps track of which " +"products are exempt from sales tax and in which states each exemption " +"applies." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:10 +msgid "TaxCloud registration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:12 +msgid "" +"Register an account on `TaxCloud.com `_ and " +"complete the setup. Once you go live, get the :guilabel:`TaxCloud API Keys` " +"by clicking on :guilabel:`Stores`, then :guilabel:`Get Details`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst-1 +msgid "Example of a store's TaxCloud API Keys" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:21 +msgid "Enable TaxCloud" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:23 +msgid "" +"Go to :menuselection:`Accounting Dashboard --> Configuration --> Settings` " +"and in the :guilabel:`Taxes` section enable :guilabel:`TaxCloud`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:25 +msgid "" +"Add the store's :guilabel:`Login ID` under :guilabel:`API ID` and the " +"store's :guilabel:`Key` under :guilabel:`API KEY`. Click on " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:27 +msgid "" +"Click the :guilabel:`Refresh` button (:guilabel:`🗘`) next to " +":guilabel:`Default Category` to import the TIC :dfn:`Taxability Information " +"Codes` product categories from TaxCloud. Some categories may imply specific " +"tax rates or exemptions." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:30 +msgid "" +"Select a :guilabel:`Default Category` and :guilabel:`Save`. The " +":guilabel:`Default Category` is applied when no :guilabel:`TaxCloud " +"Category` is set on your products or product categories, or when no product " +"is found on an order/invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:0 +msgid "Filling in TaxCloud API Keys in Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:39 +msgid "Set TaxCloud categories on products" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:41 +msgid "" +"If you need to use more than one TIC category (i.e., the :guilabel:`Default " +"Category`), go to the product's :guilabel:`General Information` tab and " +"select a :guilabel:`TaxCloud Category`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:44 +msgid "" +"If you want to configure multiple products simultaneously, ensure they share" +" the same :guilabel:`Product Category` and click on the external link button" +" (:guilabel:`🡕`) to set a :guilabel:`TaxCloud Category` on the " +":guilabel:`Product Category` instead." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:49 +msgid "" +"If you set a :guilabel:`TaxCloud Category` on a product and another on its " +":guilabel:`Product Category`, Odoo only considers the :guilabel:`TaxCloud " +"Category` found on the product itself." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:52 +msgid "" +"A :guilabel:`TaxCloud Category` set on a **parent product category** does " +"not apply to its **child product categories**. For example, if you set " +":guilabel:`TaxCloud Category` on the *All* :guilabel:`Product Category`, it " +"is not applied to the *All/Sales* :guilabel:`Product Category`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:57 +msgid "" +"Make sure your company address is complete, including the state and the ZIP " +"code. Go to :menuselection:`Settings --> Companies: Update Info` to open and" +" edit your company address." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:61 +msgid "Automatically post taxes in the correct tax payable account" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:63 +msgid "" +"To make sure the new taxes generated by the TaxCloud integration are created" +" with the correct **Tax Payable** account, create a **user-defined " +"default**. This process should be repeated for each one of your companies " +"that uses TaxCloud." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:68 +msgid "" +"A user-defined default impacts all records at creation. It means that " +"**every** new tax is set up to record income in the specified Tax Payable " +"account unless the tax is manually edited to specify a different income " +"account (or if another user-defined default takes precedence)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:72 +msgid "" +"To do so, go to :menuselection:`Accounting Dashboard --> Configuration --> " +"Accounting: Chart of Accounts`, find the company's :guilabel:`Tax Payable` " +"account, and click on :guilabel:`Setup`. Take note of the number after `id=`" +" in the URL string; it is the **Tax Payable account ID** and will be used " +"later." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst-1 +msgid "Example of Tax Payable account id in the URL string" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:81 +msgid "" +"Activate the :ref:`developer mode `, then go to " +":menuselection:`Settings --> Technical --> Actions: User-defined Defaults` " +"and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:84 +msgid "" +"Click on :guilabel:`Field` drop-down menu and then on :guilabel:`Search " +"More...`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst-1 +msgid "User-defined Defaults Field search" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:90 +msgid "" +"Use the search bar to filter for the :guilabel:`Tax Repartition Line` model," +" and use it a second time to filter for the :guilabel:`Account` field. " +"Select the line with :guilabel:`Tax Repartition Line` under the " +":guilabel:`Model` column." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst-1 +msgid "Searching for the Tax Repartition Line model and Account field" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:98 +msgid "" +"Once you are back to the :guilabel:`User-defined Defaults` creation, enter " +"the **Tax Payable account ID** you took note of earlier under the " +":guilabel:`Default Value (JSON format)` field." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:101 +msgid "" +"Select the company for which this configuration should apply under the " +":guilabel:`Company` field and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst-1 +msgid "Example of a User-defined Defaults configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:109 +msgid "Automatically detect the fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:111 +msgid "" +"Sales taxes are calculated in Odoo based on :doc:`fiscal positions " +"`. A fiscal position for the United States is created when" +" enabling TaxCloud." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:114 +msgid "" +"You can configure Odoo to automatically detect to which customers the fiscal" +" position should be applied. To do so, go to :menuselection:`Accounting " +"Dashboard --> Configuration --> Accounting: Fiscal Positions` and select " +":guilabel:`Automatic Tax Mapping (TaxCloud)`. Enable :guilabel:`Detect " +"Automatically` and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst-1 +msgid "Detect Automatically setting on the TaxCloud fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:123 +msgid "" +"Now, this fiscal position is automatically set on any order or invoice if " +"the customer country is *United States*. This triggers the automated tax " +"computation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:127 +msgid "" +"To get the sales taxes on a sales order, confirm it or click the " +":guilabel:`Update Taxes` button next to :guilabel:`Add Shipping`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:131 +msgid "Interaction with coupons and promotions" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:133 +msgid "" +"If you use the **Coupon** or **Promotion Programs**, the integration with " +"TaxCloud might behave unexpectedly. Indeed, as TaxCloud does not accept " +"lines with negative amounts as part of the tax computation, the amount of " +"the lines added by the promotion program must be deduced from the total of " +"the lines it impacts." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:139 +msgid "" +"This means, amongst other complications, that orders using coupons or " +"promotions with a TaxCloud fiscal position **must** be invoiced completely -" +" you cannot create invoices for partial deliveries, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:143 +msgid "" +"Another unexpected behavior is possible. For example, you sell a product for" +" which you have a promotion program that provides a 50% discount. If the " +"product's tax rate is 7%, the tax rate computed from the TaxCloud " +"integration displays 3.5%. This happens because the discount is included in " +"the price sent to TaxCloud. However, in Odoo, the discount is on another " +"line entirely. Still, the tax computation is correct. Indeed, a 3.5% tax on " +"the full price is the equivalent of a 7% tax on half the price, but this " +"might be unexpected from a user point of view." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:3 +msgid "VAT numbers verification (VIES)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:5 +msgid "" +"**VAT Information Exchange System** - abbreviated **VIES** - is a tool " +"provided by the European Commission that allows you to check the validity of" +" VAT numbers of companies registered in the European Union." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:9 +msgid "" +"Odoo provides a feature to **Verify VAT Numbers** when you save a contact. " +"This helps you make sure that your contacts provided you with a valid VAT " +"number without leaving Odoo interface." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:15 +msgid "" +"To enable this feature, go to :menuselection:`Accounting --> Configuration " +"--> Settings --> Taxes`, enable the **Verify VAT Numbers** feature, and " +"click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst-1 +msgid "Enable \"Verify VAT Numbers\" in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:23 +msgid "VAT Number validation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:25 +msgid "" +"Whenever you create or modify a contact, make sure to fill out the " +"**Country** and **VAT** fields." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst-1 +msgid "" +"Fill out the contact form with the country and VAT number before clicking on" +" *Save*" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:31 +msgid "" +"When you click on *Save*, Odoo runs a VIES VAT number check, and displays an" +" error message if the VAT number is invalid." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst-1 +msgid "" +"Odoo displays an error message instead of saving when the VAT number is " +"invalid" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:39 +msgid "" +"This tool checks the VAT number's validity but does not check the other " +"fields' validity." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:43 +msgid "" +"`European Commission: VIES search engine " +"`__" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:5 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:585 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:291 +msgid "Vendor bills" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:7 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:12 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:17 +msgid "From Vendor Bill to Payment" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:20 +msgid "Record a new vendor bill" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:22 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:28 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:48 +msgid "Validate The Vendor Bill" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:54 +msgid "" +"For most European countries, the journal entry will use the following " +"accounts:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:57 +#: ../../content/applications/finance/accounting/vendor_bills.rst:66 +msgid "**Accounts Payable:** defined on the vendor form" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:59 +#: ../../content/applications/finance/accounting/vendor_bills.rst:68 +msgid "**Taxes:** defined on the products and per line" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:61 +msgid "**Expenses:** defined on the line item product used" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:63 +msgid "" +"For Anglo-Saxon (US) accounting, the journal entry will use the following " +"accounts:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:70 +msgid "**Goods Received:** defined on the product form" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:77 +msgid "Pay a bill" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:92 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:97 +msgid "Printing vendor Checks" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:99 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:104 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:109 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:112 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:123 +msgid "Aged payable balance" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:125 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:132 +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 "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:139 +msgid ":doc:`customer_invoices`" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:3 +msgid "Non-current assets and fixed assets" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:5 +msgid "" +"**Non-current Assets**, also known as **long-term assets**, are investments " +"that are expected to be realized after one year. They are capitalized rather" +" than being expensed and appear on the company's balance sheet. Depending on" +" their nature, they may undergo **depreciation**." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:9 +msgid "" +"**Fixed Assets** are a type of Non-current Assets and include the properties" +" bought for their productive aspects, such as buildings, vehicles, " +"equipment, land, and software." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:12 +msgid "" +"For example, let's say we buy a car for $ 27,000. We plan to amortize it " +"over five years, and we will sell it for $ 7,000 afterward. Using the " +"linear, or straight-line, depreciation method, $ 4,000 are expensed each " +"year as **depreciation expenses**. After five years, the **Accumulated " +"Depreciation** amount reported on the balance sheet equals $ 20,000, leaving" +" us with $ 7,000 of **Not Depreciable Value**, or Salvage value." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:18 +msgid "" +"Odoo Accounting handles depreciation by creating all depreciation entries " +"automatically in *draft mode*. They are then posted periodically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:21 +msgid "Odoo supports the following **Depreciation Methods**:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:23 +msgid "Straight Line" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:24 +msgid "Declining" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:25 +msgid "Declining Then Straight Line" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:34 +msgid "" +"Such transactions must be posted on an **Assets Account** rather than on the" +" default expense account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:38 +msgid "Configure an Assets Account" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Configuration of an Assets Account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:48 +msgid "" +"This account's type must be either *Fixed Assets* or *Non-current Assets*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:51 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:48 +msgid "Post an expense to the right account" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:54 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:51 +msgid "Select the account on a draft bill" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:56 +msgid "" +"On a draft bill, select the right account for all the assets you are buying." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Selection of an Assets Account on a draft bill in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:65 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:61 +msgid "Choose a different Expense Account for specific products" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:67 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:63 +msgid "" +"Start editing the product, go to the *Accounting* tab, select the right " +"**Expense Account**, and save." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Change of the Assets Account for a product in Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:75 +msgid "" +"It is possible to :ref:`automate the creation of assets entries ` for these products." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:83 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:77 +msgid "" +"To do so, open your Purchases Journal by going to :menuselection:`Accounting" +" --> Accounting --> Purchases`, select the journal item you want to modify, " +"click on the account, and select the right one." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:92 +msgid "Assets entries" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:99 +msgid "" +"An **Asset entry** automatically generates all journal entries in *draft " +"mode*. They are then posted one by one at the right time." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:102 +msgid "" +"To create a new entry, go to :menuselection:`Accounting --> Accounting --> " +"Assets`, click on *Create*, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:105 +msgid "" +"Click on **select related purchases** to link an existing journal item to " +"this new entry. Some fields are then automatically filled out, and the " +"journal item is now listed under the **Related Purchase** tab." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Assets entry in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:113 +msgid "" +"Once done, you can click on *Compute Depreciation* (next to the *Confirm* " +"button) to generate all the values of the **Depreciation Board**. This board" +" shows you all the entries that Odoo will post to depreciate your asset, and" +" at which date." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Depreciation Board in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:124 +msgid "" +"The **Prorata Temporis** feature is useful to depreciate your assets the " +"most accurately possible." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:126 +msgid "" +"With this feature, the first entry on the Depreciation Board is computed " +"based on the time left between the *Prorata Date* and the *First " +"Depreciation Date* rather than the default amount of time between " +"depreciations." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:130 +msgid "" +"For example, the Depreciation Board above has its first depreciation with an" +" amount of $ 241.10 rather than $ 4,000.00. Consequently, the last entry is " +"also lower and has an amount of $ 3758.90." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:134 +msgid "What are the different Depreciation Methods" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:136 +msgid "" +"The **Straight Line Depreciation Method** divides the initial Depreciable " +"Value by the number of depreciations planned. All depreciation entries have " +"the same amount." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:139 +msgid "" +"The **Declining Depreciation Method** multiplies the Depreciable Value by " +"the **Declining Factor** for each entry. Each depreciation entry has a lower" +" amount than the previous entry. The last depreciation entry doesn't use the" +" declining factor but instead has an amount corresponding to the balance of " +"the depreciable value so that it reaches $0 by the end of the specified " +"duration." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:144 +msgid "" +"The **Declining Then Straight Line Depreciation Method** uses the Declining " +"Method, but with a minimum Depreciation equal to the Straight Line Method. " +"This method ensures a fast depreciation at the beginning, followed by a " +"constant one afterward." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:149 +msgid "Assets from the Purchases Journal" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:151 +msgid "" +"You can create an asset entry from a specific journal item in your " +"**Purchases Journal**." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:153 +msgid "" +"To do so, open your Purchases Journal by going to :menuselection:`Accounting" +" --> Accounting --> Purchases`, and select the journal item you want to " +"record as an asset. Make sure that it is posted in the right account (see: " +":ref:`journal-assets-account`)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:157 +msgid "" +"Then, click on *Action*, select **Create Asset**, and fill out the form the " +"same way you would do to :ref:`create a new entry `." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Create Asset Entry from a journal item in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:165 +msgid "Modification of an Asset" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:167 +msgid "" +"You can modify the values of an asset to increase or decrease its value." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:169 +msgid "" +"To do so, open the asset you want to modify, and click on *Modify " +"Depreciation*. Then, fill out the form with the new depreciation values and " +"click on *Modify*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:172 +msgid "" +"A **decrease in value** posts a new Journal Entry for the **Value Decrease**" +" and modifies all the future *unposted* Journal Entries listed in the " +"Depreciation Board." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:175 +msgid "" +"An **increase in value** requires you to fill out additional fields related " +"to the account movements and creates a new Asset entry with the **Value " +"Increase**. The Gross Increase Asset Entry can be accessed with a Smart " +"Button." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Gross Increase smart button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:184 +msgid "Disposal of Fixed Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:186 +msgid "" +"To **sell** an asset or **dispose** of it implies that it must be removed " +"from the Balance Sheet." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:188 +msgid "" +"To do so, open the asset you want to dispose of, click on *Sell or Dispose*," +" and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Disposal of Assets in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:194 +msgid "" +"Odoo Accounting then generates all the journal entries necessary to dispose " +"of the asset, including the gain or loss on sale, which is based on the " +"difference between the asset's book value at the time of the sale and the " +"amount it is sold for." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:199 +msgid "" +"To record the sale of an asset, you must first post the related Customer " +"Invoice so you can link the sale of the asset with it." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:203 +msgid "Assets Models" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:205 +msgid "" +"You can create **Assets Models** to create your Asset entries faster. It is " +"particularly useful if you recurrently buy the same kind of assets." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:208 +msgid "" +"To create a model, go to :menuselection:`Accounting --> Configuration --> " +"Assets Models`, click on *Create*, and fill out the form the same way you " +"would do to create a new entry." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:212 +msgid "" +"You can also convert a *confirmed Asset entry* into a model by opening it " +"from :menuselection:`Accounting --> Accounting --> Assets` and then, by " +"clicking on the button *Save Model*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:217 +msgid "Apply an Asset Model to a new entry" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:219 +msgid "" +"When you create a new Asset entry, fill out the **Fixed Asset Account** " +"with the right asset account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Assets model button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:232 +msgid "Automate the Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:234 +msgid "" +"When you create or edit an account of which the type is either *Non-current " +"Assets* or *Fixed Assets*, you can configure it to create assets for the " +"expenses that are credited on it automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:238 +msgid "You have three choices for the **Automate Assets** field:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:241 +msgid "" +"**Create in draft:** whenever a transaction is posted on the account, a " +"draft *Assets entry* is created, but not validated. You must first fill out " +"the form in :menuselection:`Accounting --> Accounting --> Assets`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:244 +msgid "" +"**Create and validate:** you must also select an Asset Model (see: `Assets " +"Models`_). Whenever a transaction is posted on the account, an *Assets " +"entry* is created and immediately validated." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Automate Assets on an account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:252 +msgid "" +"You can, for example, select this account as the default **Expense Account**" +" of a product to fully automate its purchase. (see: :ref:`product-assets-" +"account`)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:3 +msgid "Deferred expenses and prepayments" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:5 +msgid "" +"**Deferred expenses** and **prepayments** (also known as **prepaid " +"expense**), are both costs that have already occurred for unconsumed " +"products or services yet to receive." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:8 +msgid "" +"Such costs are **assets** for the company that pays them since it already " +"paid for products and services still to receive or that are yet to be used. " +"The company cannot report them on the current **Profit and Loss statement**," +" or *Income Statement*, since the payments will be effectively expensed in " +"the future." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:13 +msgid "" +"These future expenses must be deferred on the company's balance sheet until " +"the moment in time they can be **recognized**, at once or over a defined " +"period, on the Profit and Loss statement." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:16 +msgid "" +"For example, let's say we pay $ 1200 at once for one year of insurance. We " +"already pay the cost now but haven't used the service yet. Therefore, we " +"post this new expense in a *prepayment account* and decide to recognize it " +"on a monthly basis. Each month, for the next 12 months, $ 100 will be " +"recognized as an expense." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:21 +msgid "" +"Odoo Accounting handles deferred expenses and prepayments by spreading them " +"in multiple entries that are automatically created in *draft mode* and then " +"posted periodically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:31 +msgid "" +"Such transactions must be posted on a **Deferred Expense Account** rather " +"than on the default expense account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:35 +msgid "Configure a Deferred Expense Account" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Configuration of a Deferred Expense Account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:45 +msgid "This account's type must be either *Current Assets* or *Prepayments*" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:53 +msgid "" +"On a draft bill, select the right account for all the products of which the " +"expenses must be deferred." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "" +"Selection of a Deferred Expense Account on a draft bill in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Change of the Expense Account for a product in Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:71 +msgid "" +"It is possible to automate the creation of expense entries for these " +"products (see: `Automate the Deferred Expenses`_)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:86 +msgid "Deferred Expenses entries" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:91 +msgid "" +"A **Deferred Expense entry** automatically generates all journal entries in " +"*draft mode*. They are then posted one by one at the right time until the " +"full amount of the expense is recognized." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:94 +msgid "" +"To create a new entry, go to :menuselection:`Accounting --> Accounting --> " +"Deferred Expense`, click on *Create*, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:97 +msgid "" +"Click on **select related purchases** to link an existing journal item to " +"this new entry. Some fields are then automatically filled out, and the " +"journal item is now listed under the **Related Expenses** tab." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Deferred Expense entry in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:105 +msgid "" +"Once done, you can click on *Compute Deferral* (next to the *Confirm* " +"button) to generate all the values of the **Expense Board**. This board " +"shows you all the entries that Odoo will post to recognize your expense, and" +" at which date." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Expense Board in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:116 +msgid "" +"The **Prorata Temporis** feature is useful to recognize your expense the " +"most accurately possible." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:118 +msgid "" +"With this feature, the first entry on the Expense Board is computed based on" +" the time left between the *Prorata Date* and the *First Recognition Date* " +"rather than the default amount of time between recognitions." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:122 +msgid "" +"For example, the Expense Board above has its first expense with an amount of" +" $ 70.97 rather than $ 100.00. Consequently, the last entry is also lower " +"and has an amount of $ 29.03." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:126 +msgid "Deferred Entry from the Purchases Journal" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:128 +msgid "" +"You can create a deferred entry from a specific journal item in your " +"**Purchases Journal**." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:130 +msgid "" +"To do so, open your Purchases Journal by going to :menuselection:`Accounting" +" --> Accounting --> Purchases`, and select the journal item you want to " +"defer. Make sure that it is posted in the right account (see: `Change the " +"account of a posted journal item`_)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:142 +msgid "Deferred Expense Models" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:144 +msgid "" +"You can create **Deferred Expense Models** to create your Deferred Expense " +"entries faster." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:146 +msgid "" +"To create a model, go to :menuselection:`Accounting --> Configuration --> " +"Deferred Expense Models`, click on *Create*, and fill out the form the same " +"way you would do to create a new entry." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:150 +msgid "" +"You can also convert a *confirmed Deferred Expense entry* into a model by " +"opening it from :menuselection:`Accounting --> Accounting --> Deferred " +"Expenses` and then, by clicking on the button *Save Model*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:155 +msgid "Apply a Deferred Expense Model to a new entry" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:157 +msgid "" +"When you create a new Deferred Expense entry, fill out the **Deferred " +"Expense Account** with the right recognition account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Deferred Expense model button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:170 +msgid "Automate the Deferred Expenses" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:172 +msgid "" +"When you create or edit an account of which the type is either *Current " +"Assets* or *Prepayments*, you can configure it to defer the expenses that " +"are credited on it automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:175 +msgid "You have three choices for the **Automate Deferred Expense** field:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:178 +msgid "" +"**Create in draft:** whenever a transaction is posted on the account, a " +"draft *Deferred Expenses entry* is created, but not validated. You must " +"first fill out the form in :menuselection:`Accounting --> Accounting --> " +"Deferred Expenses`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:181 +msgid "" +"**Create and validate:** you must also select a Deferred Expense Model (see:" +" `Deferred Expense Models`_). Whenever a transaction is posted on the " +"account, a *Deferred Expenses entry* is created and immediately validated." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Automate Deferred Expense on an account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:190 +msgid "" +"You can, for example, select this account as the default **Expense Account**" +" of a product to fully automate its purchase. (see: `Choose a different " +"Expense Account for specific products`_)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:5 +msgid "" +"**Invoice digitization** is the process of automatically encoding " +"traditional paper invoices into vendor bills and customer invoices forms in " +"your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:8 +msgid "" +"Odoo uses :abbr:`OCR (optical character recognition)` and artificial " +"intelligence technologies to recognize the content of the documents. Vendor " +"bills and customer invoices forms are automatically created and populated " +"based on the scanned invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:13 +msgid "" +"`Test Odoo's invoice digitization `_" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:14 +msgid ":doc:`/applications/general/in_app_purchase`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:15 +msgid "" +"`Odoo Tutorials: Invoice Digitization with OCR " +"`_." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:19 +msgid "" +"The more documents you scan, the better the system identifies the correct " +"data." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:24 +msgid "" +"In :menuselection:`Accounting --> Configuration --> Settings --> " +"Digitalization`, check the box :guilabel:`Document Digitalization` and " +"choose whether :guilabel:`Vendor Bills` and :guilabel:`Customer Invoices` " +"should be processed automatically or manually." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:28 +msgid "" +"The :guilabel:`Single Invoice Line Per Tax` option can also be selected. It " +"enables to get only one line created per tax in the new bill, regardless of " +"the number of lines from the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:32 +msgid "Invoice upload" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:35 +msgid "Upload invoices manually" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:37 +msgid "" +"From the :guilabel:`Accounting Dashboard`, click on the :guilabel:`Upload` " +"button of your vendor bills journal. Alternatively, go to " +":menuselection:`Accounting --> Customers --> Invoices` or " +":menuselection:`Accounting --> Vendors --> Bills` and select " +":guilabel:`Upload`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:43 +msgid "Upload invoices using an email alias" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:45 +msgid "" +"You can configure your connected scanner to send scanned documents to an " +"email alias. Emails sent to these aliases are converted into new draft " +"customer invoices or vendor bills." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:48 +msgid "" +"You can modify the email alias of a journal by going to " +":menuselection:`Accounting --> Configuration --> Journals`, opening the " +"appropriate journal, opening the :guilabel:`Advanced Settings` tab, and " +"modifying the :guilabel:`Email Alias` field." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:52 +msgid "" +"If you use the :doc:`Documents <../../documents>` app, you can send your " +"scanned invoices to the :guilabel:`Finance` workspace (e.g., `inbox-" +"financial@example.odoo.com`)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:56 +msgid "Invoice digitization" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:58 +msgid "" +"According to your settings, the document is either processed automatically, " +"or you need to click on :guilabel:`Send for digitalization` to do it " +"manually." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:61 +msgid "" +"Once the data is extracted from the PDF, you can correct it if necessary by " +"clicking on the respective tags (available in Edit mode) and selecting the " +"proper information instead." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:68 +msgid "" +"The **invoice digitization** is an In-App Purchase (IAP) service that " +"requires prepaid credits to work. Digitizing one document consumes one " +"credit." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:71 +msgid "" +"To buy credits, go to :menuselection:`Accounting --> Configuration --> " +"Settings --> Digitization` and click on :guilabel:`Buy credits`, or go to " +":menuselection:`Settings --> Odoo IAP` and click on :guilabel:`View My " +"Services`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:78 +msgid "`Our Privacy Policy `_." +msgstr "" + +#: ../../content/applications/finance/documents.rst:3 +msgid "Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:5 +msgid "" +"**Odoo Documents** allows you to store, view and manage files within Odoo." +msgstr "" + +#: ../../content/applications/finance/documents.rst:7 +msgid "" +"You can upload any type of file (max 64MB per file on Odoo Online), and " +"organize them in various workspaces." +msgstr "" + +#: ../../content/applications/finance/documents.rst:11 +msgid "`Odoo Documents: product page `_" +msgstr "" + +#: ../../content/applications/finance/documents.rst:14 +msgid "Workflow actions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:16 +msgid "" +"Workflow actions are automated actions you can create and customize at the " +"level of each workspace. They appear next to a file whenever it meets the " +"criteria you set. That way you can, for example, add tags to a file or move " +"it to another workspace with a single click. Workflow actions help you " +"streamline the management of your documents and your overall business " +"operations." +msgstr "" + +#: ../../content/applications/finance/documents.rst:22 +msgid "Create workflow actions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:24 +msgid "" +"To create workflow actions, go to :menuselection:`Documents --> " +"Configuration --> Workspaces` and select the workspace where the action " +"should apply. Click on the *Actions* smart button, and then on *Create*." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Workflow actions smart button in Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:33 +msgid "" +"An action applies to all *Child Workspaces* under the *Parent Workspace* you" +" selected." +msgstr "" + +#: ../../content/applications/finance/documents.rst:36 +msgid "" +"If you use the :ref:`developer mode `, you can directly " +"access all your actions by going to :menuselection:`Documents --> " +"Configuration --> Actions`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:40 +msgid "Set the conditions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:42 +msgid "" +"After naming your workflow action, you can set the conditions that trigger " +"the appearance of the action button on the right-side panel when selecting a" +" file." +msgstr "" + +#: ../../content/applications/finance/documents.rst:45 +msgid "There are three basic types of conditions you can set:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:47 +msgid "" +"**Tags**: you can both use the *Contains* and *Does not contain* conditions," +" meaning the files *must have* or *mustn't have* the tags set here." +msgstr "" + +#: ../../content/applications/finance/documents.rst:50 +msgid "**Contact**: the files must be associated with the contact set here." +msgstr "" + +#: ../../content/applications/finance/documents.rst:52 +msgid "**Owner**: the files must be associated with the owner set here." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Example of a workflow action's basic condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:59 +msgid "" +"If you don't set any conditions, the action button appears for all files " +"located inside the selected workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:63 +msgid "Advanced condition type: domain" +msgstr "" + +#: ../../content/applications/finance/documents.rst:66 +msgid "" +"It is recommended to have some knowledge of Odoo development to properly " +"configure *Domain* filters." +msgstr "" + +#: ../../content/applications/finance/documents.rst:69 +msgid "" +"To access the *Domain* condition, the :ref:`developer mode `" +" needs to be activated. Once that's done, select the *Domain* condition " +"type, and click on *Add Filter*." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Activating the domain condition type in Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:76 +msgid "" +"To create a rule, you typically select a field, an operator, and a value. " +"For example, if you want to add a workflow action to all the PDF files " +"inside a workspace, set the field to *Mime Type*, the operator to " +"*contains*, and the value to *pdf*." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Example of a workflow action's domain condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:84 +msgid "" +"Click on *Add node* (plus-circle icon) and *Add branch* (ellipsis icon) to " +"add conditions and sub-conditions. You can then specify if your rule should " +"match *ALL* or *ANY* conditions. You can also edit the rule directly using " +"the *Code editor*." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "" +"Add a node or a branch to a workflow action's condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:93 +msgid "Configure the actions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:95 +msgid "" +"Select the *Actions* tab to set up your action. You can simultaneously:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:97 +msgid "" +"**Set Contact**: add a contact to the file, or replace an existing contact " +"with a new one." +msgstr "" + +#: ../../content/applications/finance/documents.rst:98 +msgid "" +"**Set Owner**: add an owner to the file, or replace an existing owner with a" +" new one." +msgstr "" + +#: ../../content/applications/finance/documents.rst:99 +msgid "**Move to Workspace**: move the file to any workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:100 +msgid "" +"**Create**: create one of the following items attached to the file in your " +"database:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:102 +msgid "**Product template**: create a product you can edit directly." +msgstr "" + +#: ../../content/applications/finance/documents.rst:103 +msgid "**Task**: create a Project task you can edit directly." +msgstr "" + +#: ../../content/applications/finance/documents.rst:104 +msgid "**Signature request**: create a new Sign template to send out." +msgstr "" + +#: ../../content/applications/finance/documents.rst:105 +msgid "**Sign directly**: create a Sign template to sign directly." +msgstr "" + +#: ../../content/applications/finance/documents.rst:106 +msgid "" +"**Vendor bill**: create a vendor bill using OCR and AI to scrape information" +" from the file content." +msgstr "" + +#: ../../content/applications/finance/documents.rst:108 +msgid "" +"**Customer invoice**: create a customer invoice using OCR and AI to scrape " +"information from the file." +msgstr "" + +#: ../../content/applications/finance/documents.rst:110 +msgid "" +"**Vendor credit note**: create a vendor credit note using OCR and AI to " +"scrape information from the file." +msgstr "" + +#: ../../content/applications/finance/documents.rst:112 +msgid "" +"**Credit note**: create a customer credit note using OCR and AI to scrape " +"information from the file." +msgstr "" + +#: ../../content/applications/finance/documents.rst:114 +msgid "**Applicant**: create a new HR application you can edit directly." +msgstr "" + +#: ../../content/applications/finance/documents.rst:116 +msgid "**Set Tags**: add, remove, and replace any number of tags." +msgstr "" + +#: ../../content/applications/finance/documents.rst:117 +msgid "" +"**Activities - Mark all as Done**: mark all activities linked to the file as" +" done." +msgstr "" + +#: ../../content/applications/finance/documents.rst:118 +msgid "" +"**Activities - Schedule Activity**: create a new activity linked to the file" +" as configured in the action. You can choose to set the activity on the " +"document owner." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Example of a workflow action Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:5 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:104 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:107 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:110 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:113 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:7 +msgid "" +"Odoo **Expenses** streamlines the management of expenses. After an employee" +" submits their expenses in Odoo, the expenses are reviewed by management and" +" accounting teams. Once approved, payments can then be processed and " +"disbursed back to the employee for reimbursement(s)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:12 +msgid "`Odoo Expenses: product page `_" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:15 +msgid "Set expense types" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:17 +msgid "" +"The first step to track expenses is to configure the different *expense " +"types* for the company (managed as *products* in Odoo). Each \"product\" can" +" be as specific or generalized as needed. Go to :menuselection:`Expenses app" +" --> Configuration --> Expense Products` to view the current expensable " +"products in a default kanban view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Set expense costs on products." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:26 +msgid "" +"To create a new expense product, click :guilabel:`Create`. A product form " +"will appear. Only the :guilabel:`Product Name` and :guilabel:`Unit of " +"Measure` fields are required to create a new expense product. Enter the " +":guilabel:`Product Name` in the field, and select the :guilabel:`Unit of " +"Measure` from the drop-down menu (most products will be set to " +":guilabel:`Units`, which is the default selection)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:33 +msgid "" +"The *Sales* app is where specification on the units of measure are created " +"and edited (e.g. units, miles, nights, etc.). Go to :menuselection:`Sales " +"app --> Configuration --> Settings` and ensure `Units of Measure` is enabled" +" in the `Product Catalog` section. Click on the :guilabel:`Units of Measure`" +" internal link to view, create, and edit the units of measure. Refer to " +":doc:`this document " +"` to " +"learn more about units of measure and how to configure them." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:44 +msgid "" +"The :guilabel:`Cost` field on the product form is populated with a value of " +"`0.00` by default. When a specific expense should always be reimbursed for a" +" particular price, enter that amount in the :guilabel:`Cost` field. " +"Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will " +"report the actual cost when submitting an expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:50 +msgid "" +"Here are some examples for when to set a specific :guilabel:`Cost` on a " +"product vs. leaving the :guilabel:`Cost` at `0.00`:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:53 +msgid "" +"**Meals**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an " +"expense for a meal, they enter the actual amount of the bill and will be " +"reimbursed for that amount. An expense for a meal costing $95.23 would equal" +" a reimbursement for $95.23." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:56 +msgid "" +"**Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an " +"expense for \"mileage\", they enter the number of miles driven, and are " +"reimbursed 0.30 per mile they entered. An expense for 100 miles would equal " +"a reimbursement for $30.00." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:59 +msgid "" +"**Monthly Parking**: Set the :guilabel:`Cost` to `75.00`. When an employee " +"logs an expense for \"monthly parking\", the reimbursement would be for " +"$75.00." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:61 +msgid "" +"**Expenses**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an " +"expense that is not a meal, mileage, or monthly parking, they use the " +"generic :guilabel:`Expenses` product. An expense for a laptop costing " +"$350.00 would be logged as an :guilabel:`Expenses` product, and the " +"reimbursement would be for $350.00." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:66 +msgid "" +"Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It" +" is recommended to check with the accounting department to determine the " +"correct account to reference in this field as it will affect reports." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:70 +msgid "" +"Set a tax on each product in the :guilabel:`Vendor Taxes` and " +":guilabel:`Customer Taxes` fields if applicable. It is considered good " +"practice to use a tax that is configured with :ref:`Tax Included in Price " +"`. Taxes will be automatically configured if this " +"is set." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:77 +msgid "Record expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:80 +msgid "Manually create a new expense" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:82 +msgid "" +"To record a new expense, begin in the main :menuselection:`Expenses` app " +"dashboard, which presents the default :guilabel:`My Expenses to Report` " +"view. This view can also be accessed from :menuselection:`Expenses app --> " +"My Expenses --> My Expenses to Report`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:86 +msgid "" +"First, click :guilabel:`Create`, and then fill out the various fields on the" +" form." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:88 +msgid "" +":guilabel:`Description`: Enter a short description for the expense in the " +":guilabel:`Description` field. This should be short and informative, such as" +" `lunch with client` or `hotel for conference`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:91 +msgid "" +":guilabel:`Product`: Select the product from the drop-down menu that most " +"closely corresponds to the expense. For example, an airplane ticket would be" +" appropriate for an expense :guilabel:`Product` named :guilabel:`Air " +"Travel`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:94 +msgid "" +":guilabel:`Total`: Enter the total amount paid for the expense in one of two" +" ways:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:96 +msgid "" +"If the expense is for one single item/expense with a variable price, enter " +"the cost in the :guilabel:`Total` field. Odoo will not display the " +":guilabel:`Quantity` field for a product if it does not need to have the " +"quantity specified (a product with a unit price of `0.00` and a quantity of " +"`1.00`)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:101 +msgid "" +"If the expense is for multiples of the same item/expense with a fixed price," +" the :guilabel:`Unit Price` is displayed. Enter the quantity in the " +":guilabel:`Quantity` field, and the :guilabel:`Total` is automatically " +"updated with the correct total (the :guilabel:`Quantity` x the " +":guilabel:`Unit Price` = the :guilabel:`Total`)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:107 +msgid "" +"For example, in the case of mileage driven, the :guilabel:`Unit Price` would" +" be set in the product form as the cost *per mile*. Simply set the " +":guilabel:`Quantity` to the *number of miles* driven, and the total for the " +"expense is updated." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:111 +msgid "" +":guilabel:`Bill Reference`: If there is any reference text that should be " +"included for the expense, enter it in this field. This field is not visible " +"for expense products that require a :guilabel:`Quantity` to be entered." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:114 +msgid "" +":guilabel:`Expense Date`: Using the calendar module, enter the date the " +"expense was incurred. Use the :guilabel:`< (left)` and :guilabel:`> (right)`" +" arrows to navigate to the correct month, then click on the specific day to " +"enter the selection." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:117 +msgid "" +":guilabel:`Account`: Select the expense account that this expense should be " +"logged on from the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:119 +msgid "" +":guilabel:`Customer to Reinvoice`: If the expense is something that should " +"be paid for by a customer, select the customer and related sales order that " +"will be invoiced for this expense from the drop-down menu. For example, if a" +" customer wishes to have a custom designed piece of furniture, and purchased" +" design hours from our employee, that sales order listing the hours would be" +" referenced as the :guilabel:`Customer to Reinvoice`. In the list view, " +"there may be many different sales orders referencing the same company, so be" +" sure the correct sales order is selected." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:128 +msgid "" +"The :guilabel:`Customer to Reinvoice` field is only visible if the expense " +"product has either :guilabel:`At cost` or :guilabel:`Sales price` selected " +"under the :guilabel:`Re-Invoice Expenses` section. If :guilabel:`No` is " +"selected for the :guilabel:`Re-Invoice Expenses` section, the " +":guilabel:`Customer to Reinvoice` field is hidden." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:133 +msgid "" +":guilabel:`Analytic Account`: Select the account the expense should be " +"written against from the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:135 +msgid "" +":guilabel:`Company`: If multiple companies are set-up, select the company " +"this expense should be filed for from the drop-down menu. If there is only " +"one company, this field will be automatically populated." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:138 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee this " +"expense is for." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:139 +msgid "" +":guilabel:`Paid By`: Click the radio button to indicate who paid for the " +"expense and should be reimbursed. If the employee paid for the expense (and " +"should be reimbursed) select :guilabel:`Employee (to reimburse)`. If the " +"company paid directly instead (e.g. if the company credit card was used to " +"pay for the expense) select :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:143 +msgid "" +":guilabel:`Notes...`: If any notes are needed in order to clarify the " +"expense, enter them in the notes field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:146 +msgid "Once all the fields have been filled out, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "A filled in expense form for a client lunch." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:153 +msgid "Attach a receipt" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:155 +msgid "" +"After the expense is saved, the next step is to attach a receipt. A new " +":guilabel:`Attach Receipt` button appears after the entry is saved, beneath " +"the former :guilabel:`Save` button (which turns into an :guilabel:`Edit` " +"button)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Attach a receipt after saving the record." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:163 +msgid "" +"Click the new :guilabel:`Attach Receipt` button, and a file explorer " +"appears. Navigate to the receipt to be attached, and click :guilabel:`Open`." +" The new receipt is recorded in the chatter, and the number of receipts will" +" appear next to the :guilabel:`📎(paperclip)` icon beneath the expense form. " +"More than one receipt can be attached to an individual expense, as needed. " +"The number of receipts attached to the expense will be noted on the " +"paperclip icon." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"View receipts in the chatter and see how many receipts are attached byu looking at the\n" +"paperclip icon in the chatter beneath the record." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:175 +msgid "Create new expenses from a scanned receipt" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:177 +msgid "" +"Rather than manually inputting all of the information for an expense, " +"expenses can be created automatically by scanning a PDF receipt." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:180 +msgid "" +"First, in the main :guilabel:`Expenses` app dashboard view (this view can " +"also be accessed from :menuselection:`Expenses app --> My Expenses --> My " +"Expenses to Report`), click :guilabel:`Scan`, and a file explorer pops up. " +"Navigate to the receipt to be uploaded, click on it to select it, and then " +"click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Create an expense by scanning a receipt. Click Scan at the top of the Expenses dashboard\n" +"view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:190 +msgid "" +"The receipt is scanned, and a new entry is created with today's date as the " +":guilabel:`Expense Date`, and any other fields it can populate based on the " +"scanned data, such as the total. Click on the new entry to open the " +"individual expense form, and click :guilabel:`Edit` to make changes. The " +"receipt that was scanned in appears in the chatter. Make any edits to the " +"form, then click :guilabel:`Save` when all the information is entered." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:197 +msgid "Automatically create new expenses from an email" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:199 +msgid "" +"Instead of individually creating each expense in the *Expenses* app, " +"expenses can be automatically created by sending an email to an email alias." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:202 +msgid "" +"To do so, first, an email alias needs to be configured. Go to " +":menuselection:`Expenses app --> Configuration --> Settings`. Ensure " +":guilabel:`Incoming Emails` is enabled." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +#: ../../content/applications/finance/expenses.rst:0 +msgid "Create the domain alias by clicking the link." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:210 +msgid "" +"If the domain alias needs to be set up, :guilabel:`Setup your domain alias` " +"will appear beneath the incoming emails check box instead of the email " +"address field. Refer to this documentation for setup instructions and more " +"information: :doc:`/administration/maintain/domain_names`. Once the domain " +"alias is configured, the email address field will be visible beneath the " +"incoming emails section." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:216 +msgid "" +"Next, enter the email address to be used in the email field, then click " +":guilabel:`Save`. Now that the email address has been entered, emails can be" +" sent to that alias to create new expenses without having to be in the Odoo " +"database." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:220 +msgid "" +"To submit an expense via email, create a new email and enter the product's " +"*internal reference* code (if available) and the amount of the expense in " +"the email subject. Next, attach the receipt to the email. Odoo creates the " +"expense by taking the information in the email subject and combining it with" +" the receipt." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:225 +msgid "" +"To check an expense product's internal reference, go to " +":menuselection:`Expenses app --> Configuration --> Expense Products`. If an " +"internal reference is listed on the product, it is visible in this view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Internal reference numbers are listed in the main Expense Products view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:233 +msgid "" +"To add an internal reference on an expense product, click on the product, " +"then click :guilabel:`Edit`. In edit mode, enter the :guilabel:`Internal " +"Reference` in the field. Beneath the :guilabel:`Internal Reference` field, " +"this sentence appears: :guilabel:`Use this reference as a subject prefix " +"when submitting by email.`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:243 +msgid "" +"For security purposes, only authenticated employee emails are accepted by " +"Odoo when creating an expense from an email. To confirm an authenticated " +"employee email address, go to the employee card in the :guilabel:`Employees`" +" app, and refer to the :guilabel:`Work Email` in the main field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:252 +msgid "" +"If submitting an expense via email for a $25.00 meal during a work trip, the" +" email subject would be `Ref005 Meal $25.00`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:255 +msgid "Explanation:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:257 +msgid "" +"The :guilabel:`Internal Reference` for the expense product `Meals` is " +"`Ref005`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:258 +msgid "The :guilabel:`Cost` for the expense is `$25.00`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:263 +msgid "Create an expense report" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:265 +msgid "" +"When expenses are ready to submit (such as at the end of a business trip, or" +" once a month), an *expense report* needs to be created. Go to the main " +":menuselection:`Expenses` app dashboard, which displays a default " +":guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My " +"Expenses --> My Expenses to Report`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:270 +msgid "" +"First, each individual expense for the report must be selected by clicking " +"the check box next to each entry, or quickly select all the expenses in the " +"list by clicking the check box next to :guilabel:`Expense Date`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Select the expenses to submit, then create the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:278 +msgid "" +"Once the expenses have been selected, click the :guilabel:`Create Report` " +"button. The new report appears with all the expenses listed, and the " +":guilabel:`Employee`, :guilabel:`Paid By`, :guilabel:`Expense Journal`, and " +":guilabel:`Company` fields are automatically populated from the individual " +"expenses in the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:283 +msgid "" +"It is recommended to add a short summary for each report to help keep " +"expenses organized. Enter a short description for the expense report (such " +"as `Client Trip NYC`, or `Repairs for Company Car`) in the " +":guilabel:`Expense Report Summary` field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:288 +msgid "" +"If all the expenses are listed for the same date, the :guilabel:`Expense " +"Report Summary` field will be pre-populated with the date for the expenses." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:291 +msgid "" +"Next, select a :guilabel:`Manager` from the drop-down menu to assign a " +"manager to review the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Enter a short description and select a manager for the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:297 +msgid "" +"If some expenses are not on the report that should be, they can still be " +"added. Click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense`" +" tab. Click the check box next to each expense to add, then click " +":guilabel:`Select`. The items now appear on the report that was just " +"created." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Add more expenses to the report before submitting." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:305 +msgid "" +"When all edits have been completed, click :guilabel:`Save`. Once the expense" +" report is saved, an :guilabel:`Expenses` smart button appears in the top-" +"right corner, listing the number of expenses on the report. Click the " +":guilabel:`Expenses` smart button to view the individual expenses for the " +"report in a list." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "An Expenses smart button appears after saving the expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:317 +msgid "Submit an expense report" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:319 +msgid "" +"When an expense report is completed, the next step is to submit the report " +"to a manager for approval. Reports must be individually submitted, and " +"cannot be submitted in batches. Open the specific report from the list of " +"expense reports (if the report is not already open). To view all expense " +"reports, go to :menuselection:`Expenses app --> My Expenses --> My Reports`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:324 +msgid "" +"If the list is large, grouping the results by status may be helpful since " +"only reports that are in a :guilabel:`Draft` mode need to be submitted, " +"reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Submit the report to the manager." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:333 +msgid "" +"The status of each report is shown in the :guilabel:`Status` column on the " +"far right. If the :guilabel:`Status` column is not visible, click the " +":guilabel:`⋮ (additional options)` icon at the end of the row, and check the" +" box next to :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:337 +msgid "" +"Click on a report to open it, then click :guilabel:`Submit To Manager`. " +"After submitting a report, the next step is to wait for the manager to " +"approve it." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:341 +msgid "" +"The :ref:`expenses/approve`, :ref:`expenses/post`, and " +":ref:`expenses/reimburse` sections are **only** for users with the " +"*necessary rights*." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:347 +msgid "Approve expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:349 +msgid "" +"In Odoo, not just anyone can approve expense reports— only users with the " +"necessary rights (or permissions) can. This means that a user must have at " +"least *Team Approver* rights for the *Expenses* app. Employees with the " +"necessary rights can review expense reports, and approve or reject them, as " +"well as provide feedback thanks to the integrated communication tool." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:354 +msgid "" +"To see who has rights to approve, go to the main :menuselection:`Settings` " +"app and click on :guilabel:`Manage Users`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:358 +msgid "" +"If the *Settings* app is not available, then certain rights are not set on " +"the account. In the :guilabel:`Access Rights` tab of a user's card in the " +":menuselection:`Settings` app, the :guilabel:`Administration` section is set" +" to one of three options:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:362 +msgid "" +":guilabel:`None (blank)`: The user cannot access the *Settings* app at all." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:363 +msgid "" +":guilabel:`Access Rights`: The user can only view the :guilabel:`User's & " +"Companies` section of the *Settings* app." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:365 +msgid "" +":guilabel:`Settings`: The user has access to the entire *Settings* app with " +"no restrictions." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:367 +msgid "" +"Please refer to :doc:`this document " +"` to learn more about managing " +"users and their access rights." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:370 +msgid "" +"Click on an individual to view their card, which displays the " +":guilabel:`Access Rights` tab in the default view. Scroll down to the " +":guilabel:`Human Resources` section. Under :guilabel:`Expenses`, there are " +"four options:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:374 +msgid "" +":guilabel:`None (blank)`: A blank field means the user has no rights to view" +" or approve expense reports, and can only view their own." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:376 +msgid "" +":guilabel:`Team Approver`: The user can only view and approve expense " +"reports for their own specific team." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:378 +msgid "" +":guilabel:`All Approver`: The user can view and approve any expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:379 +msgid "" +":guilabel:`Administrator`: The user can view and approve any expense report " +"as well as access the reporting and configuration menus in the *Expenses* " +"app." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:382 +msgid "" +"Users who are able to approve expense reports (typically managers) can " +"easily view all expense reports to validate. Go to :menuselection:`Expenses " +"app --> Expense Reports --> Reports to Approve`. This view lists all the " +"expense reports that have been submitted but not approved, as noted by the " +":guilabel:`Submitted` tag in the status column." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Reports to validate are found on the Reports to Approve page." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:391 +msgid "" +"Reports can be approved in two ways (individually or several at once) and " +"refused only one way. To approve multiple expense reports at once, remain in" +" the list view. First, select the reports to approve by clicking the check " +"box next to each report, or click the box next to :guilabel:`Employee` to " +"select all reports in the list. Next, click the :guilabel:`Approve Report` " +"button. The number of reports that are selected appear next to the " +":guilabel:`Approve Report` button, in an :guilabel:`X Selected` button, with" +" X being the number of reports currently selected." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Approve multiple reports by clicking the checkboxes next to each report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:402 +msgid "" +"To approve an individual report, click on a report to go to a detailed view " +"of that report. In this view, several options are presented: " +":guilabel:`Approve`, :guilabel:`Refuse`, or :guilabel:`Reset to draft`. " +"Click :guilabel:`Approve` to approve the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:406 +msgid "" +"If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief " +"explanation for the refusal in the :guilabel:`Reason to refuse Expense` " +"field, then click :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +#: ../../content/applications/finance/expenses.rst:0 +msgid "Send messages in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:413 +msgid "" +"Team managers can easily view all the expense reports to approve for their " +"team members. While in the :guilabel:`Reports to Approve` view, click on " +":guilabel:`Filters`, then click :guilabel:`My Team`. This presents all the " +"reports to approve for the manager's team. Manager's can easily view *all* " +"reports for their team by simply clicking on and removing the :guilabel:`To " +"Approve` filter in the :guilabel:`Search...` bar, leaving only the " +":guilabel:`My Team` filter active." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Select the My Team filter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:424 +msgid "" +"If more information is needed, such as a missing receipt, communication is " +"easy from the chatter. In an individual report, simply click :guilabel:`Send" +" Message`, then type in a message in the text box that appears, tagging the " +"proper person (if needed), and post it to the chatter by clicking " +":guilabel:`Send`. The message is posted in the chatter, and the person " +"tagged will be notified via email of the message, as well as anyone " +"following." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:430 +msgid "" +"Note that only followers can be tagged in a message. To tag someone who is " +"not following, add them as a follower first. Click the :guilabel:`👤 " +"(person)` icon, then click :guilabel:`Add Followers`, then enter their name " +"in the :guilabel:`Recipients` field, and finally, click :guilabel:`Add " +"Followers`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:442 +msgid "Post expenses in accounting" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:444 +msgid "" +"Once an expense report is approved, the next step is to post the report to " +"the accounting journal. To view all expense reports to post, go to " +":menuselection:`Expenses --> Expense Reports --> Reports To Post`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"View reports to post by clicking on expense reports, then reports to post." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:452 +msgid "" +"Just like approvals, expense reports can be posted in two ways (individually" +" or several at once). To post multiple expense reports at once, remain in " +"the list view. First, select the reports to post by clicking the check box " +"next to each report, or click the box next to :guilabel:`Employee` to select" +" all reports in the list. Next, click :guilabel:`Post Entries`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Post multiple reports from the Post Entries view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:461 +msgid "" +"To post an individual report, click on a report to go to the detailed view " +"of that report. In this view, several options are presented: :guilabel:`Post" +" Journal Entries`, :guilabel:`Report In Next Payslip`, :guilabel:`Refuse`, " +"or :guilabel:`Reset to Draft`. Click :guilabel:`Post Journal Entries` to " +"post the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:466 +msgid "" +"If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief " +"explanation for the refusal in the :guilabel:`Reason to refuse Expense` " +"field, then click :guilabel:`Refuse`. Refused reports can be viewed by going" +" to :menuselection:`Expenses app --> Expense Reports --> All Reports`. This" +" list shows all reports, including the refused ones." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:472 +msgid "" +"To post expense reports to an accounting journal, the user must have " +"following access rights:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:474 +msgid "Accounting: Accountant or Adviser" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:475 +msgid "Expenses: Manager" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:480 +msgid "Reimburse employees" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:482 +msgid "" +"After an expense report is posted to an accounting journal, the next step is" +" to reimburse the employee. To view all expense reports to pay, go to " +":menuselection:`Expenses --> Expense Reports --> Reports To Pay`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"View reports to pay by clicking on expense reports, then reports to pay." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:490 +msgid "" +"Just like approvals and posting, expense reports can be paid in two ways " +"(individually or several at once). To pay multiple expense reports at once, " +"remain in the list view. First, select the reports to pay by clicking the " +"check box next to each report, or click the box next to :guilabel:`Employee`" +" to select all reports in the list. Next, click :guilabel:`Register " +"Payment`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Post multiple reports by clicking the checkboxes, clicking the gear, then " +"post the entries." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:499 +msgid "" +"To pay an individual report, click on a report to go to a detailed view of " +"that report. Click :guilabel:`Register Payment` to pay the employee." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:503 +msgid "Re-invoice expenses to customers" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:505 +msgid "" +"If an expense is to be reimbursed by a customer and not the company, the " +"expense can be automatically charged to the customer. This is done by first " +"referencing the :abbr:`SO (Sales Order)` the expense should be applied to " +"when creating the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:509 +msgid "" +"The next steps are the same as if the expense is being reimbursed by the " +"company instead of a customer. The expense or expenses are placed on an " +"expense report, and then the expense report is submitted for approval. Next," +" managers approve the expense report, and the accounting department post the" +" journal entry." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:514 +msgid "" +"Finally, once the expense report is posted to a journal, the expense then " +"appears on the :abbr:`SO (Sales Order)` that was referenced when the expense" +" was first created." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:517 +msgid "" +"The sales order can then be invoiced, thus invoicing the customer for the " +"expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:520 +#: ../../content/applications/finance/fiscal_localizations/india.rst:56 +#: ../../content/applications/finance/fiscal_localizations/india.rst:196 +msgid "Setup" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:522 +msgid "" +"First, specify the invoicing policy for each expense product. Go to " +":menuselection:`Expenses app --> Configuration --> Expense Products`. Click " +"on the expense product to edit, then click :guilabel:`Edit`. Under the " +":guilabel:`Invoicing` section, select the :guilabel:`Invoicing Policy` and " +":guilabel:`Re-Invoicing Policy` by clicking the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:527 +msgid ":guilabel:`Invoicing Policy`:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:529 +msgid "" +":guilabel:`Ordered quantities`: Expense product will only invoice expenses " +"based on the ordered quantity." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:531 +msgid "" +":guilabel:`Delivered quantities`: Expense product will only invoice expenses" +" based on the delivered quantity." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:534 +msgid ":guilabel:`Re-Invoicing Policy`:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:536 +msgid ":guilabel:`No`: Expense product will not be re-invoiced." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:537 +msgid "" +":guilabel:`At cost`: Expense product will invoice expenses at their real " +"cost." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:538 +msgid "" +":guilabel:`At sales price`: Expense product will invoice the price set on " +"the sale order." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:541 +msgid "Create an expense and expense report" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:543 +msgid "" +"First, when :ref:`creating a new expense `, the correct " +"information needs to be entered in order to re-invoice a customer. Using the" +" drop-down menu, select the *sales order* the expense will appear on in the " +":guilabel:`Customer to Reinvoice` section. Next, select the " +":guilabel:`Analytic Account` the expense will be posted to. After the " +"expense(s) is created, the expense report needs to be :ref:`created " +"` and :ref:`submitted ` as usual." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Ensure the customer to be invoiced is called out on the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:555 +msgid "" +"Selecting a :guilabel:`Customer to Reinvoice` when creating an expense is " +"critical, since this field is unable to be modified once the expense is " +"added to an expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:559 +msgid "Validate and post expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:561 +msgid "" +"Only employees with permissions (typically managers or supervisors) can " +":ref:`approve expenses `. Before approving an expense " +"report, ensure the :guilabel:`Analytic Account` is set on every expense line" +" of a report. If an :guilabel:`Analytic Account` is missing, click " +":guilabel:`Edit` and select the correct account from the drop-down menu, " +"then click :guilabel:`Approve` or :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:567 +msgid "" +"The accounting department is typically responsible for :ref:`posting journal" +" entries `. Once an expense report is approved, it can then " +"be posted. The :abbr:`SO (Sales Order)` is **only** updated *after the " +"journal entry is posted*, and the expense(s) now appear on the referenced " +":abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:573 +msgid "Invoice expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:575 +msgid "" +"Once the :abbr:`SO (Sales Order)` has been updated, it is time to invoice " +"the customer. After the expense report has been approved and the journal " +"entry has been posted, the :abbr:`SO (Sales Order)` can be opened and the " +"expenses can be seen on it. Click anywhere on an expense line, and the " +"details for that individual expense appears in a pop-up. Click on the " +":abbr:`SO (Sales Order)` that is listed next to :guilabel:`Customer to " +"Reinvoice`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"After the expense report is posted to the journal entry, the sales order can be called up\n" +"by clicking on the sales order number." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:586 +msgid "" +"The :abbr:`SO (Sales Order)` appears, and now the expenses are listed in the" +" :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "See the expenses listed on the sales order after clicking into it." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:593 +msgid "" +"Next, click :guilabel:`Create Invoice`, and select if the invoice is for a " +":guilabel:`Regular invoice`, a :guilabel:`Down payment (percentage)`, or a " +":guilabel:`Down payment (fixed amount)` by clicking the radio button next to" +" it. Then, click :guilabel:`Create Invoice`. The customer has now been " +"invoiced for the expenses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:5 +msgid "Fiscal localizations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:10 +msgid "Fiscal localization packages" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:12 +msgid "" +"**Fiscal Localization Packages** are country-specific modules that install " +"pre-configured taxes, fiscal positions, chart of accounts, and legal " +"statements on your database. Some additional features, such as the " +"configuration of specific certificates, are also added to your Accounting " +"app, following your fiscal administration requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:18 +msgid "" +"Odoo continuously adds new localizations and improves the existing packages." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:23 +msgid "" +"Odoo automatically installs the appropriate package for your company, " +"according to the country selected at the creation of the database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:27 +msgid "" +"As long as you haven't posted any entry, you can still add and select " +"another package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:29 +msgid "" +"To install a new package, go to :menuselection:`Accounting --> Configuration" +" --> Fiscal Localization`, click on **Install More Packages**, and install " +"your country's module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst-1 +msgid "" +"Install the appropriate module as fiscal localization package in Odoo " +"Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:36 +msgid "Once done, select your country's package, and click on *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst-1 +msgid "Select your country's fiscal localization package in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:43 +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "Use" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:45 +msgid "" +"These packages require you to fine-tune your chart of accounts according to " +"your needs, activate the taxes you use, and configure your country-specific " +"statements and certifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:49 +msgid ":doc:`accounting/get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:50 +msgid ":doc:`accounting/taxes`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:55 +msgid "List of supported countries" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:57 +msgid "" +"Odoo Accounting can be used in many countries out of the box by installing " +"the appropriate module. Here is a list of all :ref:`fiscal localization " +"package ` that are available on Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:61 +msgid "Algeria - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:62 +msgid ":doc:`Argentina - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:63 +msgid ":doc:`Australian - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:64 +msgid "Austria - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:65 +msgid ":doc:`Belgium - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:66 +msgid "Bolivia - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:67 +msgid "Brazilian - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:68 +msgid "Canada - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:69 +msgid ":doc:`Chile - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:70 +msgid "China - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:71 +msgid "" +":doc:`Colombia - Accounting ` (:doc:`doc in " +"Spanish `)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:73 +msgid "Costa Rica - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:74 +msgid "Croatia - Accounting (RRIF 2012)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:75 +msgid "Czech - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:76 +msgid "Denmark - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:77 +msgid "Dominican Republic - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:78 +msgid "Ecuadorian - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:79 +msgid ":doc:`Egypt - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:80 +msgid "Ethiopia - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:81 +msgid "Finnish Localization" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:82 +msgid ":doc:`France - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:83 +msgid "Generic - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:84 +msgid ":doc:`Germany `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:86 +msgid "Germany SKR03 - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:87 +msgid "Germany SKR04 - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:89 +msgid "Greece - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:90 +msgid "Guatemala - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:91 +msgid "Honduras - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:92 +msgid "Hong Kong - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:93 +msgid "Hungarian - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:94 +msgid ":doc:`Indian - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:95 +msgid ":doc:`Indonesian - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:96 +msgid "Ireland - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:97 +msgid "Israel - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:98 +msgid ":doc:`Italy - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:99 +msgid "Japan - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:100 +msgid ":doc:`Kenya - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:101 +msgid "Lithuania - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:102 +msgid ":doc:`Luxembourg - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:103 +msgid "Maroc - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:104 +msgid ":doc:`Mexico - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:105 +msgid "Mongolia - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:106 +msgid ":doc:`Netherlands - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:107 +msgid "New Zealand - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:108 +msgid "Norway - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:109 +msgid "OHADA - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:110 +msgid "Pakistan - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:111 +msgid "Panama - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:112 +msgid ":doc:`Peru - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:113 +msgid "Poland - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:114 +msgid "Portugal - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:115 +msgid "Romania - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:116 +msgid "Saudi Arabia - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:117 +msgid "Singapore - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:118 +msgid "Slovak - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:119 +msgid "Slovenian - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:120 +msgid "South Africa - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:121 +msgid ":doc:`Spain - Accounting (PGCE 2008) `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:122 +msgid "Sweden - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:123 +msgid ":doc:`Switzerland - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:124 +msgid "Taiwan - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:125 +msgid "Thailand - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:126 +msgid "Turkey - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:127 +msgid "" +":doc:`United Arab Emirates - Accounting " +"`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:128 +msgid ":doc:`UK - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:129 +msgid "Ukraine - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:130 +msgid "United States - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:131 +msgid "Uruguay - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:132 +msgid "Venezuela - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:133 +msgid "Vietnam - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:3 +msgid "Argentina" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:6 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:6 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:6 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:6 +msgid "Webinars" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:8 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:8 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:8 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:8 +msgid "" +"Below you can find videos with a general description of the localization, " +"and how to configure it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:10 +msgid "`VIDEO WEBINAR `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:11 +msgid "" +"`VIDEO WEBINAR ECOMMERCE `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:17 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:61 +msgid "Modules installation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:19 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Argentinean localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:28 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/india.rst:18 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:19 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 +msgid "Description" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:29 +msgid ":guilabel:`Argentina - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:30 +msgid "`l10n_ar`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:31 +msgid "" +"Default :ref:`fiscal localization package `, " +"which represents the minimal configuration to operate in Argentina under the" +" :abbr:`AFIP (Administración Federal de Ingresos Públicos)` regulations and " +"guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:34 +msgid ":guilabel:`Argentinean Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:35 +msgid "`l10n_ar_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:36 +msgid "VAT Book report and VAT summary report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:37 +msgid ":guilabel:`Argentinean Electronic Invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:38 +msgid "`l10n_ar_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:39 +msgid "" +"Includes all technical and functional requirements to generate electronic " +"invoices via web service, based on the AFIP regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:41 +msgid ":guilabel:`Argentinean eCommerce`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:42 +msgid "`l10n_ar_website_sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:43 +msgid "" +"(optional) Allows the user to see Identification Type and AFIP " +"Responsibility in the eCommerce checkout form in order to create electronic " +"invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:47 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:43 +msgid "Configure your company" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:49 +msgid "" +"Once the localization modules are installed, the first step is to set up the" +" company's data. In addition to the basic information, a key field to fill " +"in is the :guilabel:`AFIP Responsibility Type`, which represents the fiscal " +"obligation and structure of the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Select AFIP Responsibility Type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:58 +msgid "Chart of account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:60 +msgid "" +"In Accounting, there are three different :guilabel:`Chart of Accounts` " +"packages to choose from. They are based on a company's AFIP responsibility " +"type, and consider the frence between companies that do not require as many " +"accounts as the companies that have more complex fiscal requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:65 +msgid "Monotributista (227 accounts);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:66 +msgid "IVA Exento (290 accounts);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:67 +msgid "Responsable Inscripto (298 Accounts)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Select Fiscal Localization Package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:74 +msgid "Configure master data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:77 +msgid "Electronic Invoice Credentials" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:80 +msgid "Environment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:82 +msgid "" +"The AFIP infrastructure is replicated in two separate environments, " +"**testing** and **production**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:84 +msgid "" +"Testing is provided so that the companies can test their databases until " +"they are ready to move into the **Production** environment. As these two " +"environments are completely isolated from each other, the digital " +"certificates of one instance are not valid in the other one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:88 +msgid "" +"To select a database environment, go to :menuselection:`Accounting --> " +"Settings --> Argentinean Localization` and choose either :guilabel:`Prueba " +"(Testing)` or :guilabel:`Produccion (Production)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Select AFIP database environment: Testing or Production." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:96 +msgid "AFIP certificates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:98 +msgid "" +"The electronic invoice and other AFIP services work with :guilabel:`Web " +"Services (WS)` provided by the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:101 +msgid "" +"In order to enable communication with the AFIP, the first step is to request" +" a :guilabel:`Digital Certificate` if you do not have one already." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:104 +msgid "" +":guilabel:`Generate Certificate Sign Request (Odoo)`. When this option is " +"selected, a file with extension `.csr` (certificate signing request) is " +"generated to be used in the AFIP portal to request the certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Request a certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:111 +msgid "" +":guilabel:`Generate Certificate (AFIP)`. Access the AFIP portal and follow " +"the instructions described in `this document " +"`_ " +"to get a certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:115 +msgid "" +":guilabel:`Upload Certificate and Private Key (Odoo)`. Once the certificate " +"is generated, upload it to Odoo using the :guilabel:`Pencil` icon next to " +"the field :guilabel:`Certificado` and select the corresponding file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Upload Certificate and Private Key." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:123 +msgid "" +"In case you need to configure the Homologation Certificate, please refer to " +"the AFIP official documentation: `Homologation Certificate " +"`_. Furthermore, " +"Odoo allows the user to test electronic invoicing locally without a " +"Homologation Certificate. The following message will be in the chatter when " +"testing locally:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "" +"Invoice validated locally because it is in a testing environment without testing\n" +"certificate/keys." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:138 +msgid "Identification type and VAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:140 +msgid "" +"As part of the Argentinean localization, document types defined by the AFIP " +"are now available in the **Partner form**. Information is essential for most" +" transactions. There are six :guilabel:`Identification Types` available by " +"default, as well as 32 inactive types." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "A list of AR Localization document types in Odoo, as defined by AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:149 +msgid "" +"The complete list of :guilabel:`Identification Types` defined by the AFIP is" +" included in Odoo, but only the common ones are active." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:153 +msgid "AFIP responsibility type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:155 +msgid "" +"In Argentina, the document type and corresponding transactions associated " +"with customers and vendors is defined by the AFIP Responsibility type. This " +"field should be defined in the **Partner form**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:166 +msgid "" +"As part of the localization module, the taxes are created automatically with" +" their related financial account and configuration, e.g., 73 taxes for " +":guilabel:`Responsable Inscripto`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "" +"A list of AR Localization taxes with financial amount and configuration in " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:174 +msgid "Taxes types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:176 +msgid "Argentina has several tax types, the most common ones are:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:178 +msgid "" +":guilabel:`VAT`: this is the regular VAT and can have various percentages;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:179 +msgid "" +":guilabel:`Perception`: advance payment of a tax that is applied on " +"invoices;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:180 +msgid "" +":guilabel:`Retention`: advance payment of a tax that is applied on payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:183 +msgid "Special taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:185 +msgid "" +"Some Argentinean taxes are not commonly used for all companies, and those " +"less common options are labeled as inactive in Odoo by default. Before " +"creating a new tax, be sure to check if that tax is not already included as " +"inactive." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "" +"A list showing less common Argentinean tax options, which are labeled as inactive in Odoo\n" +"by default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:197 +msgid "Document types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:199 +msgid "" +"In some Latin American countries, like Argentina, some accounting " +"transactions such as invoices and vendor bills are classified by document " +"types defined by the governmental fiscal authorities. In Argentina, the " +"`AFIP `__ is the governmental fiscal authority " +"that defines such transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:204 +msgid "" +"The document type is an essential piece of information that needs to be " +"clearly displayed in printed reports, invoices, and journal entries that " +"list account moves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:207 +msgid "" +"Each document type can have a unique sequence per journal where it is " +"assigned. As part of the localization, the document type includes the " +"country in which the document is applicable (this data is created " +"automatically when the localization module is installed)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:211 +msgid "" +"The information required for the :guilabel:`Document Types` is included by " +"default so the user does not need to fill anything on this view:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "A list of document types in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:219 +msgid "" +"There are several :guilabel:`Document Types` types that are inactive by " +"default, but can be activated as needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:223 +msgid "Letters" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:225 +msgid "" +"For Argentina, the :guilabel:`Document Types` include a letter that helps " +"indicate the type of transaction or operation. For example, when an invoice " +"is related to a(n):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:228 +msgid "" +":guilabel:`B2B transaction`, a document type :guilabel:`A` must be used;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:229 +msgid "" +":guilabel:`B2C transaction`, a document type :guilabel:`B` must be used;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:230 +msgid "" +":guilabel:`Exportation Transaction`, a document type :guilabel:`E` must be " +"used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:232 +msgid "" +"The documents included in the localization already have the proper letter " +"associated with each :guilabel:`Document Type`, so there is no further " +"configuration necessary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "document types grouped by letters." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:240 +msgid "Use on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:242 +msgid "" +"The :guilabel:`Document Type` on each transaction will be determined by:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:244 +msgid "" +"The journal entry related to the invoice (if the journal uses documents);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:245 +msgid "" +"The onditions applied based on the type of issuer and receiver (e.g., the " +"type of fiscal regime of the buyer and the type of fiscal regime of the " +"vendor)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:251 +msgid "" +"In the Argentinean localization, the journal can have a different approach " +"depending on its usage and internal type. To configure journals, go to " +":menuselection:`Accounting --> Configuration --> Journals`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:255 +msgid "" +"For sales and purchase journals, it's possible to activate the option " +":guilabel:`Use Documents`, which enables a list of :guilabel:`Document " +"Types` that can be related to the invoices and vendor bills. For more detail" +" on invoices, please refer to the section :ref:`2.3 document types " +"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:260 +msgid "" +"If the sales or purchase journals do not have the :guilabel:`Use Documents` " +"option activated, they will not be able to generate fiscal invoices, " +"meaning, their use case will be mostly limited to monitoring account moves " +"related to internal control processes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:265 +msgid "AFIP information (also known as AFIP Point of Sale)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:267 +msgid "" +"The :guilabel:`AFIP POS System` is a field only visible for the **Sales** " +"journals and defines the type of AFIP POS that will be used to manage the " +"transactions for which the journal is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:270 +msgid "The AFIP POS defines the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:272 +msgid "the sequences of document types related to the web service;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:273 +msgid "the structure and data of the electronic invoice file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "A AFIP POS System field which is available on Sales journals in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:280 +msgid "Web services" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:282 +msgid "" +"**Web services** help generate invoices for different purposes. Below are a " +"few options to choose from:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:285 +msgid "" +":guilabel:`wsfev1: Electronic Invoice`: is the most common service, which is" +" used to generate invoices for document types A, B, C, M with no detail per" +" item;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:287 +msgid "" +":guilabel:`wsbfev1: Electronic Fiscal Bond`: is for those who invoice " +"capital goods and wish to access the benefit of the Electronic Tax Bonds " +"granted by the Ministry of Economy. For more details go to: `Fiscal Bond " +"`__;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:291 +msgid "" +":guilabel:`wsfexv1: Electronic Exportation Invoice`: is used to generate " +"invoices for international customers and transactions that involve " +"exportation processes, the document type related is type \"E\"." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Web Services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:299 +msgid "Here are some useful fields to know when working with web services:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:301 +msgid "" +":guilabel:`AFIP POS Number`: is the number configured in the AFIP to " +"identify the operations related to this AFIP POS;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:303 +msgid "" +":guilabel:`AFIP POS Address`: is the field related to the commercial address" +" registered for the POS, which is usually the same address as the company. " +"For example, if a company has multiple stores (fiscal locations) then the " +"AFIP will require the company to have one AFIP POS per location. This " +"location will be printed in the invoice report;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:307 +msgid "" +":guilabel:`Unified Book`: when the AFIP POS System is Preimpresa, then the " +"document types (applicable to the journal) with the same letter will share " +"the same sequence. For example:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:310 +msgid "Invoice: FA-A 0001-00000002;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:311 +msgid "Credit Note: NC-A 0001-00000003;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:312 +msgid "Debit Note: ND-A 0001-00000004." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:315 +msgid "Sequences" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:317 +msgid "" +"For the first invoice, Odoo synchronizes with the AFIP automatically and " +"displays the last sequence used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:321 +msgid "" +"When creating :guilabel:`Purchase Journals`, it's possible to define whether" +" they are related to document types or not. In the case where the option to " +"use documents is selected, there would be no need to manually associate the " +"document type sequences, since the document number is provided by the " +"vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:327 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:168 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:347 +msgid "Usage and testing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:330 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:171 +msgid "Invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:332 +msgid "" +"The information below applies to invoice creation once the partners and " +"journals are created and properly configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:336 +msgid "Document type assignation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:338 +msgid "" +"When the partner is selected, the :guilabel:`Document Type` field will be " +"filled in automatically based on the AFIP document type:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:341 +msgid "" +"**Invoice for a customer IVA Responsable Inscripto, prefix A** is the type " +"of document that shows all the taxes in detail along with the customer's " +"information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Invoice for a customer IVA Responsable Inscripto, prefix A." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:347 +msgid "" +"**Invoice for an end customer, prefix B** is the type of document that does " +"not detail the taxes, since the taxes are included in the total amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Invoice for an end customer, prefix B." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:353 +msgid "" +"**Exportation Invoice, prefix E** is the type of document used when " +"exporting goods that shows the incoterm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Exportation Invoice, prefix E" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:359 +msgid "" +"Even though some invoices use the same journal, the prefix and sequence are " +"given by the :guilabel:`Document Type` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:362 +msgid "" +"The most common :guilabel:`Document Type` will be defined automatically for " +"the different combinations of AFIP responsibility type but it can be updated" +" manually by the user before confirming the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:367 +msgid "Electronic invoice elements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:369 +msgid "" +"When using electronic invoices, if all the information is correct then the " +"invoice is posted in the standard way unless there is an error that needs to" +" be addressed. When error messages pop up, they indicate both the issue that" +" needs attention along with a proposed solution. If an error persists, the " +"invoice remains in draft until the issue is resolved." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:374 +msgid "" +"Once the invoice is posted, the information related to the AFIP validation " +"and status is displayed in the AFIP tab, including:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:377 +msgid ":guilabel:`AFIP Autorisation`: CAE number;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:378 +msgid "" +":guilabel:`Expiration Date`: deadline to deliver the invoice to the " +"customers (normally 10 days after the CAE is generated);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:380 +msgid "" +":guilabel:`Result:` indicates if the invoice has been :guilabel:`Aceptado en" +" AFIP` and/or :guilabel:`Aceptado con Observaciones`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "AFIP Status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:388 +msgid "Invoice taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:390 +msgid "" +"Based on the :guilabel:`AFIP Responsibility type`, the VAT tax can apply " +"differently on the PDF report:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:393 +msgid "" +":guilabel:`A. Tax excluded`: in this case the taxed amount needs to be " +"clearly identified in the report. This condition applies when the customer " +"has the following AFIP Responsibility type of **Responsable Inscripto**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Tax excluded." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:400 +msgid "" +":guilabel:`B. Tax amount included`: this means that the taxed amount is " +"included as part of the product price, subtotal, and totals. This condition " +"applies when the customer has the following AFIP Responsibility types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:404 +msgid "IVA Sujeto Exento;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:405 +msgid "Consumidor Final;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:406 +msgid "Responsable Monotributo;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:407 +msgid "IVA liberado." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Tax amount included." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:414 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:643 +msgid "Special use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:417 +msgid "Invoices for services" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:419 +msgid "" +"For electronic invoices that include :guilabel:`Services`, the AFIP requires" +" to report the service starting and ending date, this information can be " +"filled in the tab :guilabel:`Other Info`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Invoices for Services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:426 +msgid "" +"If the dates are not selected manually before the invoice is validated, the " +"values will be filled automatically with the first and last day of the " +"invoice's month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Service Dates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:434 +msgid "Exportation invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:436 +msgid "" +"Invoices related to :guilabel:`Exportation Transactions` require that a " +"journal uses the AFIP POS System **Expo Voucher - Web Service** so that the " +"proper document type(s) can be associated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Exporation journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:443 +msgid "" +"When the customer selected in the invoice is configured with an AFIP " +"responsibility type :guilabel:`Cliente / Proveedor del Exterior` - " +":guilabel:`Ley N° 19.640`, Odoo automatically assigns the:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:447 +msgid "Journal related to the exportation Web Service;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:448 +msgid "Exportation document type;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:449 +msgid "Fiscal position: Compras/Ventas al exterior;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:450 +msgid "Concepto AFIP: Products / Definitive export of goods;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:451 +msgid "Exempt Taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Export invoice fields autofilled in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:458 +msgid "" +"The Exportation Documents require Incoterms to be enabled and configured, " +"which can be found in :menuselection:`Other Info --> Accounting`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Export invoice - Incoterm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:466 +msgid "Fiscal bond" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:468 +msgid "" +"The :guilabel:`Electronic Fiscal Bond` is used for those who invoice capital" +" goods and wish to access the benefit of the Electronic Tax Bonds granted by" +" the Ministry of Economy." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:471 +msgid "" +"For these transactions, it is important to consider the following " +"requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:473 +msgid "Currency (according to the parameter table) and invoice quotation;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:474 +msgid "Taxes;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:475 +msgid "Zone;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:476 +msgid "Detail each item;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:478 +msgid "Code according to the Common Nomenclator of Mercosur (NCM);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:479 +msgid "Complete description;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:480 +msgid "Unit Net Price;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:481 +msgid "Quantity;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:482 +msgid "Unit of measurement;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:483 +msgid "Bonus;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:484 +msgid "VAT rate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:487 +msgid "Electronic credit invoice MiPyme (FCE)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:489 +msgid "" +"For SME invoices, there are several document types that are classified as " +"**MiPyME**, which are also known as **Electronic Credit Invoice** (or " +"**FCE** in Spanish). This classification develops a mechanism that improves " +"the financing conditions for small and medium-sized businesses, and allows " +"them to increase their productivity, through the early collection of credits" +" and receivables issued to their clients and/or vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:495 +msgid "" +"For these transactions it's important to consider the following " +"requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:497 +msgid "specific document types (201, 202, 206, etc);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:498 +msgid "the emitter should be eligible by the AFIP to MiPyME transactions;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:499 +msgid "the amount should be bigger than 100,000 ARS;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:500 +msgid "" +"A bank account type CBU must be related to the emisor, otherwise the invoice" +" cannot be validated, having an error message such as the following." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Bank account relation error." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:507 +msgid "" +"To set up the :guilabel:`Transmission Mode`, go to settings and select " +"either :guilabel:`SDC` or :guilabel:`ADC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Transmission Mode." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:514 +msgid "" +"To change the :guilabel:`Transmission Mode` for a specific invoice, go to " +"the :guilabel:`Other Info` tab and change it before confirming." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:518 +msgid "" +"Changing the :guilabel:`Transmission Mode` will not change the mode selected" +" in :guilabel:`Settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Transmission Mode on Invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:525 +msgid "" +"When creating a :guilabel:`Credit/Debit` note related to a FCE document:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:527 +msgid "" +"use the :guilabel:`Credit and Debit Note` buttons, so all the information " +"from the invoice is transferred to the new :guilabel:`Credit and Debit " +"Note`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:529 +msgid "" +"the document letter should be the same as than the originator document " +"(either A or B);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:530 +msgid "" +"the same currency as the source document must be used. When using a " +"secondary currency there is an exchange difference if the currency rate is " +"different between the emission day and the payment date. It is possible to " +"create a credit/debit note to decrease/increase the amount to pay in ARS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Credit & debit notes buttons." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:538 +msgid "When creating a :guilabel:`Credit Note` we can have two scenarios:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:540 +msgid "" +"the FCE is rejected so the :guilabel:`Credit Note` should have the field " +":guilabel:`FCE, is Cancellation?` as *True*; or;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:542 +msgid "" +"the :guilabel:`Credit Note`, is created to annulate the FCE document, in " +"this case the field :guilabel:`FCE, is Cancellation?` must be *empty* " +"(false)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "FCE: Es Cancelación?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:550 +msgid "Invoice printed report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:552 +msgid "" +"The :guilabel:`PDF Report` related to electronic invoices that have been " +"validated by the AFIP includes a barcode at the bottom of the format which " +"represents the CAE number. The expiration date is also displayed as it is a " +"legal requirement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Invoice printed report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:561 +msgid "Troubleshooting and auditing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:563 +msgid "" +"For auditing and troubleshooting purposes, it is possible to obtain detailed" +" information of an invoice number that has been previously sent to the AFIP." +" To retrieve this information, activate the :ref:`developer mode `, then go to the :menuselection:`Accounting` menu and click on the " +"button :guilabel:`Consult Invoice` button in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Consult invoice in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Details of invoice consulted in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:576 +msgid "" +"It is also possible to retrieve the last number used in AFIP for a specific " +"document type and POS Number as a reference for any possible issues on the " +"sequence synchronization between Odoo and AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Consult the last invoice number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:587 +msgid "" +"Based on the purchase journal selected for the vendor bill, the " +":guilabel:`Document Type` is now a required field. This value is auto-" +"populated based on the AFIP Responsibility type of Issuer and Customer, but " +"the value can be changed if necessary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Changing journal and document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:595 +msgid "" +"The :guilabel:`Document Number` field needs to be registered manually and " +"the format will be validated automatically. However, in case the format is " +"invalid, a user error will be displayed indicating the correct format that " +"is expected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Vendor bill document number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:603 +msgid "" +"The vendor bill number is structured in the same way as the customer " +"invoices, excepted that the document sequence is entered by the user using " +"the following format: *Document Prefix - Letter - Document Number*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:608 +msgid "Validate vendor bill number in AFIP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:610 +msgid "" +"As most companies have internal controls to verify that the vendor bill is " +"related to an AFIP valid document, an automatic validation can be set in " +":menuselection:`Accounting --> Settings --> Argentinean Localization --> " +"Validate document in the AFIP`, considering the following levels:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:614 +msgid "" +":guilabel:`Not available:` the verification is not done (this is the default" +" value);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:615 +msgid "" +":guilabel:`Available:` the verification is done. In case the number is not " +"valid it, only displays a warning but still allows the vendor bill to be " +"posted;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:617 +msgid "" +":guilabel:`Required:` the verification is done and it does not allow the " +"user to post the vendor bill if the document number is not valid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Verify Vendor Bills validity in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:625 +msgid "Validate vendor bills in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:627 +msgid "" +"With the vendor validation settings enabled, a new button shows up on the " +"vendor bills inside of Odoo, labeled :guilabel:`Verify on AFIP`, which is " +"located next to the :guilabel:`AFIP Authorization code` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Verify on AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:635 +msgid "" +"In case the vendor bill cannot be validated in AFIP, a value of " +":guilabel:`Rejected` will be displayed on the dashboard and the details of " +"the invalidation will be added to the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "AFIP authorization Rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:646 +msgid "Untaxed concepts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:648 +msgid "" +"There are some transactions that include items that are not a part of the " +"VAT base amount, such as fuel and gasoline invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:651 +msgid "" +"The vendor bill will be registered using one item for each product that is " +"part of the VAT base amount, and an additional item to register the amount " +"of the exempt concept." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "VAT exempt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:659 +msgid "Perception taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:661 +msgid "" +"The vendor bill will be registered using one item for each product that is " +"part of the VAT base amount, and the perception tax can be added in any of " +"the product lines. As a result, there will be one tax group for the VAT and " +"another for the perception. The perception default value is always " +":guilabel:`0.10`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "VAT perception." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:670 +msgid "" +"To edit the VAT perception and set the correct amount, you should use the " +":guilabel:`Pencil` icon that is the next to the :guilabel:`Perception` " +"amount. After the VAT perception amount has been set, the invoice can then " +"be validated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Enter the perception amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:681 +msgid "" +"As part of the localization installation, financial reporting for Argentina " +"was added to the :guilabel:`Accounting` dashboard. Access these reports by " +"navigating to :menuselection:`Accounting --> Reporting --> Argentinean " +"Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Argentinean reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:690 +msgid "VAT reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:693 +msgid "Sales VAT book" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:695 +msgid "" +"In this report, all the sales are recorded, which are taken as the basis for" +" the accounting records to determine the VAT (Tax Debit)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:698 +msgid "" +"The :guilabel:`Sales VAT` book report can be exported in a `.zip` file " +":guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` " +"files to upload in the AFIP portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Sales VAT book." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:706 +msgid "Purchases VAT book" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:708 +msgid "" +"The :guilabel:`Purchases VAT` book report can be exported in a `.zip` file " +":guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` " +"files to upload in the AFIP portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Purchases VAT book." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:716 +msgid "VAT summary" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:718 +msgid "" +"Pivot table designed to check the monthly VAT totals. This report is for " +"internal usage, it is not sent to the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "VAT Summary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:726 +msgid "IIBB - Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:729 +msgid "IIBB - Sales by jurisdiction" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:731 +msgid "" +"Pivot table where you can validate the gross income in each jurisdiction. " +"Affidavit for the corresponding taxes to pay, therefore it is not sent to " +"the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "IIBB Sales by jurisdiction." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:739 +msgid "IIBB - Purchases by jurisdiction" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:741 +msgid "" +"Pivot table where you can validate the gross purchases in each jurisdiction." +" Affidavit for the corresponding taxes to pay, therefore it is not sent to " +"the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "IIBB Purchases by jurisdiction." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:8 +msgid "Employment Hero Australian Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:10 +msgid "" +"The Employment Hero module synchronizes payslip accounting entries (e.g., " +"expenses, social charges, liabilities, taxes) from Employment Hero to Odoo " +"automatically. Payroll administration is still done in Employment Hero. We " +"only record the journal entries in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:15 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:20 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Australian " +"Payroll` module (technical name: `l10n_au_keypay`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:22 +msgid "" +"Configure the **Employment Hero API** by going to :menuselection:`Accounting" +" --> Configuration --> Settings`. More fields become visible after clicking " +"on :guilabel:`Enable Employment Hero Integration`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:30 +msgid "" +"You can find the API Key in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:35 +msgid "" +"The **Payroll URL** is pre-filled with `https://keypay.yourpayroll.com.au`. " +"*Please do not change it.*" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:37 +msgid "" +"You can find the **Business ID** in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "The Employment Hero \"Business ID\" number is in the URL" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:42 +msgid "You can choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:45 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:47 +msgid "" +"The API syncs the journal entries from Employment Hero to Odoo and leaves " +"them in draft mode. The reference includes the Employment Hero payslip entry" +" ID in brackets for the user to easily retrieve the same record in " +"Employment Hero and Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:54 +msgid "" +"By default, the synchronization happens once per week. You can fetch the " +"records manually by going to :menuselection:`Accounting --> Configuration " +"--> Settings` and, in the :guilabel:`Enable Employment Hero Integration` " +"option, click on :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:58 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:60 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:65 +msgid "" +"For the API to work, you need to create the same accounts as the default " +"accounts of your Employment Hero business (**same name and same code**) in " +"Odoo. You also need to choose the correct account types in Odoo to generate " +"accurate financial reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 +msgid "Fiscal certification: POS restaurant" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:10 +msgid "" +"In Belgium, the owner of a cooking business such as a restaurant or food " +"truck is required by law to use a government-certified **Cash Register " +"System** for their receipts. This applies if their yearly earnings " +"(excluding VAT, drinks, and take-away food) exceed 25,000 euros." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:14 +msgid "" +"This government-certified system entails the use of a :ref:`certified POS " +"system `, along with a device called a :ref:`Fiscal " +"Data Module ` (or **black box**) and a :ref:`VAT Signing Card " +"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:19 +msgid "" +"Do not forget to register as *foodservice industry manager* on the `Federal " +"Public Service Finance registration form " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:25 +msgid "Certified POS system" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:27 +msgid "" +"The Odoo POS system is certified for the major versions of databases hosted " +"on **Odoo Online** and **Odoo.sh**. Please refer to the following table to " +"ensure that your POS system is certified." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:35 +#: ../../content/applications/finance/payment_acquirers/stripe.rst:17 +msgid "Odoo Online" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:36 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:37 +msgid "On-Premise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:38 +msgid "Odoo 16.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:39 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:40 +msgid "Review in progress" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:41 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:43 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:44 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:45 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:49 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:53 +msgid "Not certified" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:42 +msgid "Odoo 15.2" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:46 +msgid "Odoo 15.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:47 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:51 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:52 +msgid "Certified" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:50 +msgid "Odoo 14.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:56 +msgid ":doc:`/administration/maintain/supported_versions`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:58 +msgid "" +"A `certified POS system " +"`_ must " +"adhere to rigorous government regulations, which means it operates " +"differently from a non-certified POS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:62 +msgid "On a certified POS, you cannot:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:64 +msgid "" +"Set up and use the **global discounts** feature (the `pos_discount` module " +"is blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:66 +msgid "" +"Set up and use the **loyalty programs** feature (the `pos_loyalty` module is" +" blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:68 +msgid "" +"Reprint receipts (the `pos_reprint` module is blacklisted and cannot be " +"activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:69 +msgid "Modify prices in order lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:70 +msgid "Modify or delete order lines in POS orders." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:71 +msgid "Sell products without a valid VAT number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:72 +msgid "Use a POS that is not connected to an IoT box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:74 +msgid "" +"The :doc:`cash rounding <../../sales/point_of_sale/pricing/cash_rounding>` " +"feature must be activated and set to a :guilabel:`Rounding Precision` of " +"`0,05` and a :guilabel:`Rounding Method` set as :guilabel:`Half-Up`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:77 +msgid "" +"Taxes must be set as included in the price. To set it up, go to " +":menuselection:`Point of Sale --> Configuration --> Settings`, and from the " +":guilabel:`Accounting` section, open the :guilabel:`Default Sales Tax` form " +"by clicking the arrow next to the default sales tax field. There, click " +":guilabel:`Advanced Options` and enable :guilabel:`Included in Price`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:81 +msgid "" +"At the start of a POS session, users must click :guilabel:`Work in` to clock" +" in. Doing so allows the registration of POS orders. If users are not " +"clocked in, they cannot make POS orders. Likewise, they must click " +":guilabel:`Work Out` to clock out at the end of the session." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:86 +msgid "" +"If you configure a POS to work with a black box, you cannot use it again " +"without it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:91 +msgid "The Fiscal Data Module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:93 +msgid "" +"The :abbr:`FDM (Fiscal Data Module)`, or `black box " +"`_, is a government-certified " +"device that works together with the Point of Sale application and saves your" +" POS orders information. Concretely, a **hash** (:dfn:`unique code`) is " +"generated for each POS order and added to its receipt. This allows the " +"government to verify that all revenue is declared." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:99 +msgid "" +"Ensure your black box is approved by the Belgian government. You can check " +"the compliance of your black box by visiting the `Federal Public Service " +"Finance `_ website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:106 +msgid "" +"Before setting up your database to work with an FDM, ensure you have the " +"following hardware:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:108 +msgid "" +"a registered :ref:`black box ` (go to `www.boîtenoire.be " +"`_ to order yours);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:110 +msgid "an RS-232 serial null modem cable per FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:111 +msgid "an RS-232 serial-to-USB adapter per FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:112 +msgid "an :ref:`IoT Box ` (one IoT box per black box); and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:113 +msgid "a receipt printer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:118 +msgid "Black box module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:120 +msgid "" +"As a pre-requisite, :ref:`activate ` the `Belgian " +"Registered Cash Register` module (technical name: `pos_blackbox_be`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "black box modules for belgian fiscal certification" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:126 +msgid "" +"Once the module is activated, add your VAT number to your company " +"information. To set it up, go to :menuselection:`Settings --> Companies --> " +"Update Info`, and fill in the :guilabel:`VAT` field. Then, enter a national " +"registration number for every staff member who operates the POS system. To " +"do so, go to the :guilabel:`Employees` app and open an employee form. There," +" go to :menuselection:`HR settings tab --> Attendance/Point of Sale`, and " +"fill in the :guilabel:`INSZ or BIS number` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "ISNZ or BIS number field on employee form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:136 +msgid "" +"To input your information, click on your avatar, go to :menuselection:`My " +"Profile --> Preference tab`, and enter your INSZ or BIS number in the " +"designated field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:140 +msgid "" +"You must configure the black box directly in the production database. " +"Utilizing it in a testing environment may result in incorrect data being " +"stored within the black box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:146 +msgid "IoT Box" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:148 +msgid "" +"In order to use a Fiscal Data Module, you need a registered IoT Box. To " +"register your IoT box, you must contact us through our `support contact form" +" `_ and provide the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:152 +msgid "your VAT number;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:153 +msgid "your company's name, address, and legal structure; and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:154 +msgid "the Mac address of your IoT Box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:156 +msgid "" +"Once your IoT box is certified, :doc:`connect " +"<../../productivity/iot/config/connect>` it to your database. To verify that" +" the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the " +":guilabel:`IOT Device` section, which should display the FDM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Hardware status page on a registered IoT Box" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:163 +msgid "" +"Then, add the IoT to your POS. To do so, go to :menuselection:`Point of Sale" +" --> Configuration --> Point of Sale`, select your POS, scroll down to the " +":guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. " +"Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:168 +msgid "" +"To be able to use an FDM, you must at least connect one :guilabel:`Receipt " +"Printer`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:173 +msgid "VAT signing card" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:175 +msgid "" +"When you open a POS session and make your initial transaction, you are " +"prompted to enter the PIN provided with your :abbr:`VSC (VAT signing card)`." +" The card is delivered by the :abbr:`FPS (Service Public Federal Finances)` " +"upon `registration " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:3 +msgid "Chile" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:10 +msgid "" +"`VIDEO WEBINAR OF CHILEAN LOCALIZATION: INTRO AND DEMO " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:11 +msgid "`VIDEO WEBINAR OF DELIVERY GUIDE `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:16 +msgid "" +"The Chilean localization has been improved and extended in Odoo v13. In this" +" version, the next modules are available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:19 +msgid "" +"**l10n_cl:** Adds accounting features for the Chilean localization, which " +"represent the minimal configuration required for a company to operate in " +"Chile and under the SII (Servicio de Impuestos Internos) regulations and " +"guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:23 +msgid "" +"**l10n_cl_edi:** Includes all technical and functional requirements to " +"generate and receive Electronic Invoice via web service, based on the SII " +"regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:26 +msgid "" +"**l10n_cl_reports:** Adds the reports Propuesta F29 y Balance Tributario (8 " +"columnas)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:32 +msgid "Install the Chilean localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:34 +msgid "" +"For this, go to *Apps* and search for Chile. Then click *Install* in the " +"module **Chile E-invoicing**. This module has a dependency with **Chile - " +"Accounting**. In case this last one is not installed, Odoo installs it " +"automatically with E-invoicing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean module to install on Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:43 +msgid "" +"When you install a database from scratch selecting Chile as country, Odoo " +"will automatically install the base module: Chile - Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:48 +msgid "Company Settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:50 +msgid "" +"Once the modules are installed, the first step is to set up your company " +"data. Additional to the basic information, you need to add all the data and " +"elements required for Electronic Invoice, the easiest way to configure it is" +" in :menuselection:`Accounting --> Settings --> Chilean Localization`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:56 +msgid "" +"All the following configuration and functionality is only available in Odoo " +"if your company already passed the `Certification process " +"`_ in the SII - Sistema de " +"Facturación de Mercado, this certification enables you to generate " +"electronic invoices from your ERP and send them automatically to the SII. If" +" your company has not passed this certification yet, make sure you " +"communicate this to your Account Manager as a special process outside Odoo " +"is required in order to complete this certification." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:66 +msgid "Fiscal Information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:68 +msgid "" +"Fill in the fiscal information for your company according to the SII " +"register, follow the instructions on each section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean company fiscal data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:76 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:186 +msgid "Electronic Invoice Data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:78 +msgid "" +"This is part of the main information required to generate electronic " +"Invoice, select your environment and the legal information, as well as the " +"email address to receive invoices from your vendors and the alias you use to" +" send invoices to your customers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean edi environment settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:87 +msgid "Configure DTE Incoming email server" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:89 +msgid "" +"In order to receive you the claim and acceptance emails from your customers," +" it is crucial to define the DTE incoming email server, considering this " +"configuration:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Incoming email server configuration for Chilean DTE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:97 +msgid "" +"For your Go-live make sure you archive/remove from your inbox all the emails" +" related to vendor bills that are not required to be processed in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:101 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:215 +msgid "Certificate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:103 +msgid "" +"In order to generate the electronic invoice signature, a digital certificate" +" with the extension ``pfx`` is required, proceed to this section and load " +"your file and password." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Digital certificate access." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Digital certificate configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:114 +msgid "" +"A certificate can be shared between several users. If this is the case leave" +" the user field empty, so all your billing users can use the same one. On " +"the other hand, if you need to restrict the certificate for a particular " +"user, just define the users in the certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:119 +msgid "" +"In some cases, depending on the certificate format, it is possible that the " +"field Subject Serial Number is not loaded automatically. If this is the " +"case, you can manually edit this field by filling it with the Certificate's " +"legal representative RUT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:124 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:874 +msgid "Financial Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:126 +msgid "" +"The report Propuesta F29 requires two values that need to be defined as part" +" of the company configuration:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Fiscal reports parameters." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:134 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:226 +msgid "Multicurrency" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:136 +msgid "" +"The official currency rate in Chile is provided by the Chilean service " +"`mindicador.cl `_. You can find this service in the " +"currency rate configuration, and you can set a predefined interval for the " +"rate updates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Currency reate service for Chile." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:147 +msgid "" +"The chart of accounts is installed by default as part of the set of data " +"included in the localization module. The accounts are mapped automatically " +"in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:150 +msgid "Taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:151 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:70 +msgid "Default Account Payable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:152 +msgid "Default Account Receivable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:153 +msgid "Transfer Accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:154 +msgid "Conversion Rate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:158 +msgid "Master Data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:164 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:324 +msgid "Identification Type and VAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:166 +msgid "" +"As part of the Chilean localization, the identification types defined by the" +" SII are now available on the Partner form. This information is essential " +"for most transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean identification types for partners." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:174 +msgid "TaxpayerType" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:176 +msgid "" +"In Chile, the document type associated with customers and vendors " +"transactions is defined based on the Taxpayer Type. This field should be " +"defined in the partner form, when creating a customer is important you make " +"sure this value is set:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean taxpayer types for partners." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:188 +msgid "" +"As part of the information that is sent in the electronic Invoice, you need " +"to define the email that is going to appear as the sender of the electronic " +"invoice to your customer, and the Industry description." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean electronic invoice data for partners." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:200 +msgid "" +"As part of the localization module, the taxes are created automatically with" +" their related financial account and configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean taxes list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:208 +msgid "Taxes Types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:210 +msgid "Chile has several tax types, the most common ones are:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:212 +msgid "VAT. Is the regular VAT and it can have several rates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:213 +msgid "" +"ILA (Impuesto a la Ley de Alcholes). Taxes for alcoholic drinks. It has a " +"different rate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:217 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:264 +msgid "Fiscal Positions" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:219 +msgid "" +"Based on the purchase transactions, the VAT can have different affections. " +"This will be done in Odoo using the default purchase fiscal positions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:224 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:273 +msgid "Document Types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:226 +msgid "" +"In some Latin American countries, including Chile, some accounting " +"transactions like invoices and vendor bills are classified by document types" +" defined by the government fiscal authorities (In Chile case: SII)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:230 +msgid "" +"The document type is essential information that needs to be displayed in the" +" printed reports and that needs to be easily identified within the set of " +"invoices as well of account moves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:233 +msgid "" +"Each document type can have a unique sequence per company. As part of the " +"localization, the Document Type includes the country on which the document " +"is applicable and the data is created automatically when the localization " +"module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:237 +msgid "" +"The information required for the document types is included by default so " +"the user doesn't need to fill anything on this view:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean fiscal document types list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:245 +msgid "" +"There are several document types that are inactive by default but can be " +"activated if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:249 +msgid "Use on Invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:251 +msgid "The document type on each transaction will be determined by:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:253 +msgid "" +"The Journal related to the Invoice, identifying if the journal uses " +"documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:254 +msgid "" +"Condition applied based on the type of Issues and Receiver (ex. Type of " +"fiscal regimen of the buyer and type of fiscal regimen of the vendor)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:267 +msgid "" +"Sales Journals in Odoo usually represent a business unit or location, " +"example:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:269 +msgid "Ventas Santiago." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:270 +msgid "Ventas Valparaiso." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:272 +msgid "For the retail stores is common to have one journal per POS:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:274 +msgid "Cashier 1." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:275 +msgid "Cashier 2." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:279 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "Purchases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:281 +msgid "" +"The transactions purchase can be managed with a single journal, but " +"sometimes companies use more than one in order to handle some accounting " +"transactions that are not related to vendor bills but can be easily " +"registered using this model, for example:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:285 +msgid "Tax Payments to government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:286 +msgid "Employees payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:292 +msgid "When creating sales journals the next information must be filled in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:294 +msgid "" +"**Point of sale type**: If the Sales journal will be used for electronic " +"documents, the option Online must be selected. Otherwise, if the journal is " +"used for invoices imported from a previous system or if you are using the " +"SII portal “Facturación MiPyme“ you can use the option Manual." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:298 +msgid "" +"**Use Documents**: This field is used to define if the journal will use " +"Document Types. It is only applicable to Purchase and Sales journals that " +"can be related to the different sets of document types available in Chile. " +"By default, all the sales journals created will use documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Document type configuration on Journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:307 +msgid "" +"For the Chilean localization, it is important to define the default Debit " +"and Credit accounts as they are required for one of the debit notes use " +"cases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:313 +msgid "CAF" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:315 +msgid "" +"A CAF (Folio Authorization Code) is required, for each document type that is" +" issued to your customers, the CAF is a file the SII provides to the Emisor " +"with the folio/sequence authorized for the electronic invoice documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:319 +msgid "" +"Your company can make several requests for folios and obtain several CAFs, " +"each one associated with different ranges of folios. The CAFs are shared " +"within all the journals, this means that you only need one active CAF per " +"document type and it will be applied on all journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:323 +msgid "" +"Please refer to the `SII documentation " +"`_ to check the detail on how to" +" acquire the CAF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:327 +msgid "" +"The CAFs required by the SII are different from Production to Test " +"(Certification mode). Make sure you have the correct CAF set depending on " +"your environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:334 +msgid "" +"Once you have the CAF files you need to associate them with a document type " +"in Odoo, in order to add a CAF, just follow these steps:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:337 +msgid "Access to :menuselection:`Accounting --> Settings --> CAF`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:338 +msgid "Upload the file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:339 +msgid "Save the CAF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Steps to add a new CAF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:345 +msgid "" +"Once loaded, the status changes to *In Use*. At this moment, when a " +"transaction is used for this document type, the invoice number takes the " +"first folio in the sequence." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:349 +msgid "" +"In case you have used some folios in your previous system, make sure you set" +" the next valid folio when the first transaction is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:355 +msgid "Usage and Testing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:358 +msgid "Electronic Invoice Workflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:360 +msgid "" +"In the Chilean localization the electronic Invoice workflow covers the " +"Emission of Customer Invoices and the reception of Vendor Bills, in the next" +" diagram we explain how the information transmitted to the SII and between " +"the customers and Vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Diagram with Electronic invoice transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:370 +msgid "Customer invoice Emission" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:372 +msgid "" +"After the partners and journals are created and configured, the invoices are" +" created in the standard way, for Chile one of the differentiators is the " +"document type which is selected automatically based on the Taxpayer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:376 +msgid "You can manually change the document type if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Document type selection on invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:383 +msgid "" +"Documents type 33: Electronic Invoice must have at least one item with tax, " +"otherwise the SII rejects the document validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:389 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 +msgid "Validation and DTE Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:391 +msgid "" +"When all the invoice information is filled, either manually or automatically" +" when it's created from a sales order, proceed to validate the invoice. " +"After the invoice is posted:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:394 +msgid "" +"The DTE File (Electronic Tax Document) is created automatically and added in" +" the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:395 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:762 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 +msgid "The DTE SII status is set as: Pending to be sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "DTE XML File displayed in chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:401 +msgid "" +"The DTE Status is updated automatically by Odoo with a scheduled action that" +" runs every day at night, if you need to get the response from the SII " +"immediately you can do it manually as well. The DTE status workflow is as " +"follows:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Transition of DTE statuses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:410 +msgid "" +"In the first step the DTE is sent to the SII, you can manually send it using" +" the button: Enviar Ahora, a SII Tack number is generated and assigned to " +"the invoice, you can use this number to check the details the SII sent back " +"by email. The DTE status is updated to Ask for Status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:415 +msgid "" +"Once the SII response is received Odoo updates the DTE Status, in case you " +"want to do it manually just click on the button: Verify on SII. The result " +"can either be Accepted, Accepted With Objection or Rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Identification transaction for invoice and Status update." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:424 +msgid "" +"There are several internal status in the SII before you get Acceptance or " +"Rejection, in case you click continuously the Button Verify in SII, you will" +" receive in the chatter the detail of those intermediate statuses:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Descprtion of each DTE status in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:432 +msgid "The final response from the SII, can take on of these values:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:434 +msgid "" +"**Accepted:** Indicates the invoice information is correct, our document is " +"now fiscally valid and it's automatically sent to the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:437 +msgid "" +"**Accepted with objections:** Indicates the invoice information is correct " +"but a minor issue was identified, nevertheless our document is now fiscally " +"valid and it's automatically sent to the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Email track once it is sent to the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:445 +msgid "" +"**Rejected:** Indicates the information in the invoice is incorrect and " +"needs to be corrected, the detail of the issue is received in the emails you" +" registered in the SII, if it is properly configured in Odoo, the details " +"are also retrieved in the chatter once the email server is processed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:450 +msgid "If the invoice is Rejected please follow this steps:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:452 +msgid "Change the document to draft." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:453 +msgid "" +"Make the required corrections based on the message received from the SII." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:454 +msgid "Post the invoice again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Message when an invoice is rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:462 +msgid "Crossed references" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:464 +msgid "" +"When the Invoice is created as a result of another fiscal document, the " +"information related to the originator document must be registered in the Tab" +" Cross Reference, which is commonly used for credit or debit notes, but in " +"some cases can be used on Customer Invoices as well. In the case of the " +"credit and debit notes, they are set automatically by Odoo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Invoice tab with origin document number and data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:474 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:449 +msgid "Invoice PDF Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:476 +msgid "" +"Once the invoice is accepted and validated by the SII and the PDF is " +"printed, it includes the fiscal elements that indicate that the document is " +"fiscally valid:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Barcode and fiscal elements in the invoice report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:484 +msgid "" +"If you are hosted in Odoo SH or On-Premise, you should manually install the " +"``pdf417gen`` library. Use the following command to install it: ``pip " +"install pdf417gen``." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:488 +msgid "Commercial Validation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:490 +msgid "Once the invoice has been sent to the customer:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:492 +msgid "DTE partner status changes to “Sent”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:493 +msgid "The customer must send a reception confirmation email." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:494 +msgid "" +"Subsequently, if all the commercial terms and invoice data are correct, they" +" will send the Acceptance confirmation, otherwise they send a Claim." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:496 +msgid "The field DTE acceptation status is updated automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Message with the commercial acceptance from the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:504 +msgid "Processed for Claimed invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:506 +msgid "" +"Once the invoice has been Accepted by the SII **it can not be cancelled in " +"Odoo**. In case you get a Claim for your customer the correct way to proceed" +" is with a Credit Note to either cancel the Invoice or correct it. Please " +"refer to the :ref:`chile/credit-notes` section for more details." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Invoice Comercial status updated to Claimed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:515 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:425 +msgid "Common Errors" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:517 +msgid "" +"There are multiple reasons behind a rejection from the SII, but these are " +"some of the common errors you might have and which is the related solution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:520 +msgid "Error: ``RECHAZO- DTE Sin Comuna Origen.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:522 +msgid "" +"*Hint:* Make sure the Company Address is properly filled including the State" +" and City." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:524 +msgid "Error en Monto: ``- IVA debe declararse.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:530 +msgid "" +"*Hint:* The invoice lines should include one VAT tax, make sure you add one " +"on each invoice line." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 +msgid "Error: ``Rut No Autorizado a Firmar.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:532 +msgid "" +"Error: ``Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : " +"(Firma_DTE[AAAA-MM-DD] - CAF[AAAA-MM-DD]) > 6 meses.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:535 +msgid "" +"*Hint:* Try to add a new CAF related to this document as the one you're " +"using is expired." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:537 +msgid "" +"Error: ``Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element is " +"not expected. Expected is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:540 +msgid "" +"*Hint:* Make sure the field Document Type and VAT are set either in the " +"Customer and in the main company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:543 +msgid "GLOSA: ``Usuario sin permiso de envio.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:545 +msgid "" +"*Hint:* This error indicates that most likely, your company has not passed " +"the `Certification process " +"`_" +" in the SII - Sistema de Facturación de Mercado. If this is the case, please" +" contact your Account Manager or Customer Support as this certification is " +"not part of the the Odoo services, but we can give you some alternatives." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:554 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:554 +msgid "Credit Notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:556 +msgid "" +"When a cancellation or correction is needed over a validated invoice, a " +"credit note must be generated. It is important to consider that a CAF file " +"is required for the Credit Note, which is identified as document 64 in the " +"SII." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Creation of CAF for Credit notes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:566 +msgid "" +"Refer to the :ref:`CAF section ` where we described" +" the process to load the CAF on each document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:570 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:622 +msgid "Use Cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:573 +msgid "Cancel Referenced document" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:575 +msgid "" +"In case you need to cancel or invalid an Invoice, use the button Add Credit " +"note and select Full Refund, in this case the SII reference Code is " +"automatically set to: Anula Documento de referencia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Full invoice refund with SII reference code 1." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:583 +msgid "Corrects Referenced Document Text" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:585 +msgid "" +"If a correction in the invoice information is required, for example the " +"Street Name, use the button Add Credit note,select Partial Refund and select" +" the option “Solo corregir Texto”. In this case the SII reference Code is " +"automatically set to: Corrige el monto del Documento de Referencia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Partial refund to correct text including the corrected value." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:593 +msgid "" +"Odoo creates a Credit Note with the corrected text in an invoice and price " +"0." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Credit note with the corrected value on the invoice lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:600 +msgid "" +"It's important to define the default credit account in the Sales journal as " +"it is taken for this use case in specific." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:604 +msgid "Corrects Referenced Document Amount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:606 +msgid "" +"When a correction on the amounts is required, use the button Add Credit note" +" and select Partial Refund. In this case the SII reference Code is " +"automatically set to: Corrige el monto del Documento de Referencia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Credit note for partial refund to correct amounts, using the SII reference " +"code 3." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:615 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:581 +msgid "Debit Notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:617 +msgid "" +"As part of the Chilean localization, besides creating credit notes from an " +"existing document you can also create debit Notes. For this just use the " +"button “Add Debit Note”. The two main use cases for debit notes are detailed" +" below." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:625 +msgid "Add debt on Invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:627 +msgid "" +"The most common use case for debit notes is to increase the value of an " +"existing invoice, you need to select option 3 in the field Reference code " +"SII:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Debit note for partial refund to crrect amounts, using the SII reference " +"code 3." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:635 +msgid "" +"In this case Odoo automatically includes the source invoice in the cross " +"reference section:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Invoice data on crossed reference section for debit notes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:642 +msgid "Cancel Credit Notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:644 +msgid "" +"In Chile the debits notes are used to cancel a validated Credit Note, in " +"this case just select the button Add debit note and select the first option " +"in the wizard: *1: Anula Documentos de referencia.*" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Creating a debit note to cancel a credit note with the SII code reference 1." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:653 +msgid "Vendor Bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:655 +msgid "" +"As part of the Chilean localization, you can configure your Incoming email " +"server as the same you have register in the SII in order to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:658 +msgid "" +"Automatically receive the vendor bills DTE and create the vendor bill based " +"on this information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:659 +msgid "Automatically Send the reception acknowledgement to your vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:660 +msgid "Accept or Claim the document and send this status to your vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:663 +msgid "Reception" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:665 +msgid "" +"As soon as the vendor email with the attached DTE is received: 1. The vendor" +" Bill mapping all the information included in the xml. 2. An email is sent " +"to the vendor with the Reception acknowledgement. 3. The DTE status is set " +"as: Acuse de Recibido Enviado" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Messages recorded in the chatter with the reception notification for the " +"vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:675 +msgid "Acceptation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:677 +msgid "" +"If all the commercial information is correct on your vendor bill then you " +"can accept the document using the :guilabel:`Aceptar Documento` button. Once" +" this is done the DTE Acceptation Status changes to :guilabel:`Accepted`` " +"and an email of acceptance is sent to the vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Acceptance button in vendor bills to inform vendor the document is " +"comercially accepted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:686 +msgid "Claim" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:688 +msgid "" +"In case there is a commercial issue or the information is not correct on " +"your vendor bill, you can Claim the document before validating it, using the" +" button: Claim, once this is done the DTE Acceptation Status change to: " +"Claim and an email of acceptance is sent to the vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Claim button in vendor bills to inform the vendor all the document is " +"comercially rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:696 +msgid "" +"If you claim a vendor bill, the status changes from draft to cancel " +"automatically. Considering this as best practice, all the Claim documents " +"should be canceled as they won't be valid for your accounting records." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:701 +msgid "Delivery Guide" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:703 +msgid "" +"To install the Delivery Guide module, go to :menuselection:`Apps` and search" +" for :guilabel:`Chile (l10n_cl)`. Then click :guilabel:`Install` on the " +"module :guilabel:`Chile - E-Invoicing Delivery Guide`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:708 +msgid "" +"*Chile - E-Invoicing Delivery Guide* has a dependency with *Chile - " +"Facturación Electrónica*. Odoo will install the dependency automatically " +"when the Delivery Guide module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:711 +msgid "" +"The Delivery Guide module includes sending the DTE to SII and the stamp in " +"PDF reports for deliveries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Install Delivery Guide Module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:718 +msgid "" +"Once all configurations have been made for electronic invoices (e.g., " +"uploading a valid company certificate, setting up master data, etc.), " +"Delivery Guides need their own CAFs. Please refer to the :ref:`CAF " +"documentation ` to check the details on how to " +"acquire the CAFs for electronic Delivery Guides." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:723 +msgid "" +"Verify the following important information in the *Price for the Delivery " +"Guide* configuration:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:725 +msgid "" +":guilabel:`From Sales Order`: Delivery Guide takes the product price from " +"the Sales Order and shows it on the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:727 +msgid "" +":guilabel:`From Product Template`: Odoo takes the price configured in the " +"product template and shows it on the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:729 +msgid ":guilabel:`No show price`: no price is shown in the Delivery Guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:731 +msgid "" +"Electronic delivery guides are used to move stock from one place to another " +"and they can represent sales, sampling, consignment, internal transfers, and" +" basically any product move." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:735 +msgid "Delivery Guide from a Sales Process" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:738 +msgid "" +"A delivery guide should **not** be longer than one page or contain more than" +" 60 product lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:740 +msgid "" +"When a Sales Order is created and confirmed, a Delivery Order is generated. " +"After validating the Delivery Order, the option to create a Delivery Guide " +"is activated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Create Delivery Guide Button" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:747 +msgid "" +"When clicking on :guilabel:`Create Delivery Guide` for the first time, a " +"warning message pops up, showing the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "An example sequence error when creating a Delivery Guide in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:754 +msgid "" +"This warning message means the user needs to indicate the next sequence " +"number Odoo has to take to generate the Delivery Guide, and only only " +"happens the *first time* a Delivery Guide is created in Odoo. After the " +"first document has been correctly generated, Odoo takes the CAFs next " +"available number to generate the following Delivery Guide and so on." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:759 +msgid "After the Delivery Guide is created:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:761 +msgid "" +"The DTE file (Electronic Tax Document) is automatically created and added to" +" the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "DTE Status in SII and creation of DTE/XML" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:768 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:832 +msgid "" +"The DTE Status is automatically updated by Odoo with a scheduled action that" +" runs every day at night. To get a response from the SII immediately, press " +"the :guilabel:`Send now to SII` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:771 +msgid "" +"Once the Delivery Guide is sent, it may then be printed by clicking on the " +":guilabel:`Print Delivery Guide` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Printing Delivery Guide PDF" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 +msgid "Electronic Receipt" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:781 +msgid "" +"To install the Electronic Receipt module, go to :menuselection:`Apps` and " +"search for :guilabel:`Chile (l10n_cl)`. Then click :guilabel:`Install` on " +"the module :guilabel:`Chile - Electronic Receipt`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 +msgid "" +"*Chile - Electronic Receipt* has a dependency with *Chile - Facturación " +"Electrónica*. Odoo will install the dependency automatically when the " +"E-invoicing Delivery Guide module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:789 +msgid "" +"This module contains the electronic receipt and daily sales report, which " +"are automatically sent to SII." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Install Electronic Receipt module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:796 +msgid "" +"Once all configurations have been made for Electronic Invoices (e.g., " +"uploading a valid company certificate, setting up master data, etc.), " +"Electronic Receipts need their own CAFs. Please refer to the :ref:`CAF " +"documentation ` to check the details on how to " +"acquire the CAFs for Electronic Receipts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:801 +msgid "" +"Electronic Receipts are useful when clients do not need an Electronic " +"Invoice. By default, there is a partner in the database called *Anonymous " +"Final Consumer* with a generic RUT 66666666-6 and taxpayer type of *Final " +"Consumer*. This partner can be used for Electronic Receipts or a new record " +"may be created for the same purpose." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:806 +msgid "" +"Although Electronic Receipts should be used for final consumers with a " +"generic RUT, it can also be used for specific partners. After the partners " +"and journals are created and configured, the Electronic Receipts are created" +" in the standard way as Electronic Invoice, but the type of document " +":guilabel:`(39) Electronic Receipt` should be selected, like so:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Select type of Document: (39) Boleta Electrónica" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:818 +msgid "" +"When all of the Electronic Receipt information is filled, either manually or" +" automatically from a Sales Order, proceed to validate the receipt. By " +"default, Electronic Invoice is selected as the Document Type, however in " +"order to validate the receipt correctly, make sure to edit the Document Type" +" and change to Electronic Receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:823 +msgid "After the receipt is posted:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:825 +msgid "" +"The DTE file (Electronic Tax Document) is created automatically and added to" +" the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "DTE status in SII and creation of DTE/XML" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:835 +msgid "" +"Please refer to the :ref:`DTE Workflow ` for Electronic Invoices as the workflow for Electronic Receipt " +"follows the same process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:839 +msgid "Daily Sales Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:841 +msgid "" +"Once Electronic Receipts have been created, the system creates a daily sales" +" report containing all Electronic Receipts per day. This report is " +"electronically stamped and sent to the SII overnight in XML format. These " +"daily reports can be found in :menuselection:`Reports --> Daily Sales " +"Reports`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Find Electronic Receipts in the Reports menu, under Daily Sales Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:849 +msgid "A list of daily reports is displayed with all daily DTE sent to SII." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "List of Daily Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:855 +msgid "" +"If no Electronic Receipt was made on a particular day, the report is sent " +"but it will not have any receipts in it. The report will also have an answer" +" from the SII if it was accepted or rejected (depending on the company's " +"certificate and validated receipts)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Daily Sales Book example" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:864 +msgid "" +"For Chilean localization, note that the feature tax included in the price is" +" *not* supported for the Electronic Receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:867 +msgid "" +"If a Daily Sales Report has already been created for a specific day in " +"another system, the daily report in Odoo will be rejected due to the " +"sequence number used. If that is the case, the user has to manually click on" +" :guilabel:`Retry` in order for a new sequence number to be generated (this " +"action is automatically done by Odoo). Afterwards, users can manually verify" +" report status with SII or wait for Odoo to update status later at night." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:877 +msgid "Balance Tributario de 8 Columnas" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:879 +msgid "" +"This report presents the accounts in detail (with their respective " +"balances), classifying them according to their origin and determining the " +"level of profit or loss that the business had within the evaluated period of" +" time, so that a real and complete knowledge of the status of a company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:883 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:899 +msgid "" +"You can find this report in :menuselection:`Accounting --> Accounting --> " +"Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Columns and data displayed in the report Balance Tributario 8 Columnas." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:890 +msgid "Propuesta F29" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:892 +msgid "" +"The form F29 is a new system that the SII enabled to taxpayers, and that " +"replaces the Purchase and Sales Books. This report is integrated by Purchase" +" Register (CR) and the Sales Register (RV). Its purpose is to support the " +"transactions related to VAT, improving its control and declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:896 +msgid "" +"This record is supplied by the electronic tax documents (DTE's) that have " +"been received by the SII." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Parameters to required to generate the Report Propuesta F29" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:3 +msgid "Colombia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:10 +msgid "`VIDEO WEBINAR OF A COMPLETE DEMO `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:15 +msgid "" +"Electronic invoicing for Colombia is available from Odoo 12 and requires the" +" next modules:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:18 +msgid "" +"**l10n_co**: All the basic data to manage the accounting module, contains " +"the default setup for: chart of accounts, taxes, retentions, identification " +"document types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 +msgid "" +"**l10n_co_edi**: This module includes all the extra fields that are required" +" for the Integration with Carvajal and generate the electronic invoice, " +"based on the DIAN legal requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:26 +#: ../../content/applications/finance/fiscal_localizations/india.rst:112 +#: ../../content/applications/finance/fiscal_localizations/india.rst:245 +msgid "Workflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 +msgid "Install the Colombian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:37 +msgid "" +"To :ref:`install ` the modules, go to " +":menuselection:`Apps`, remove the *Apps* filter and search for \"Colombia\"." +" Then click on *Install* for the first two modules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:44 +msgid "Configure credentials for Carvajal web service" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:46 +msgid "" +"Once that the modules are installed, in order to be able to connect with " +"Carvajal Web Service, it's necessary to configure the user and credentials, " +"this information will be provided by Carvajal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:50 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:79 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and look " +"for the *Colombian Electronic Invoice* section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:56 +msgid "" +"Using the Testing mode it is possible to connect with a Carvajal testing " +"environment. This allows users to test the complete workflow and integration" +" with the CEN Financiero portal, which is accessible here:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:62 +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:63 +msgid "CTS (Carvajal T&S)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:62 +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:63 +msgid "https://cenflab.cen.biz/site/" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:65 +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:66 +msgid "CSC (Carvajal Servicios de Comunicación)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:65 +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:66 +msgid "https://web-stage.facturacarvajal.com/" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:67 +msgid "CSC is the default for new databases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:69 +msgid "" +"Once that Odoo and Carvajal are fully configured and ready for production " +"the testing environment can be disabled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:73 +msgid "Configure your report data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:75 +msgid "" +"As part of the configurable information that is sent in the XML, you can " +"define the data for the fiscal section and the bank information in the PDF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:86 +msgid "Configure data required in the XML" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:92 +msgid "Identification" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:94 +msgid "" +"As part of the Colombian Localization, the document types defined by the " +"DIAN are now available on the Partner form. Colombian partners have to have " +"their identification number and document type set:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:101 +msgid "" +"When the document type is RUT the identification number needs to be " +"configured in Odoo including the verification digit, Odoo will split this " +"number when the data to the third party vendor is sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:107 +msgid "Fiscal structure (RUT)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:109 +msgid "" +"The partner's responsibility codes (section 53 in the RUT document) are " +"included as part of the electronic invoice module given that is part of the " +"information required by the DIAN ." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:113 +msgid "" +"These fields can be found in :menuselection:`Partner --> Sales & Purchase " +"Tab --> Fiscal Information`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:119 +msgid "" +"Additionally two booleans fields were added in order to specify the fiscal " +"regimen of the partner." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:125 +msgid "" +"If your sales transactions include products with taxes, it's important to " +"consider that an extra field *Value Type* needs to be configured per tax. " +"This option is located in the Advanced Options tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:132 +msgid "" +"Retention tax types (ICA, IVA, Fuente) are also included in the options to " +"configure your taxes. This configuration is used in order to correctly " +"display taxes in the invoice PDF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:142 +msgid "" +"Once the DIAN has assigned the official sequence and prefix for the " +"electronic invoice resolution, the Sales journals related to your invoice " +"documents need to be updated in Odoo. The sequence can be accessed using " +"the :ref:`developer mode `: :menuselection:`Accounting --> " +"Settings --> Configuration Setting --> Journals`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:151 +msgid "" +"Once that the sequence is opened, the Prefix and Next Number fields should " +"be configured and synchronized with the CEN Financiero." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:158 +msgid "Users" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:160 +msgid "" +"The default template that is used by Odoo on the invoice PDF includes the " +"job position of the salesperson, so these fields should be configured:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:173 +msgid "" +"When all your master data and credentials has been configured, it's possible" +" to start testing the electronic invoice workflow." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:179 +msgid "" +"The functional workflow that takes place before an invoice validation " +"doesn't change. The main changes that are introduced with the electronic " +"invoice are the next fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:186 +msgid "There are three types of documents:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:188 +msgid "" +"**Factura Electronica**: This is the regular type of document and its " +"applicable for Invoices, Credit Notes and Debit Notes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:190 +msgid "" +"**Factura de Importación**: This should be selected for importation " +"transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 +msgid "" +"**Factura de contingencia**: This is an exceptional type that is used as a " +"manual backup in case that the company is not able to use the ERP and it's " +"necessary to generate the invoice manually, when this invoice is added to " +"the ERP, this invoice type should be selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:199 +#: ../../content/applications/finance/fiscal_localizations/india.rst:117 +#: ../../content/applications/finance/fiscal_localizations/india.rst:262 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:385 +msgid "Invoice validation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:201 +msgid "" +"After the invoice is validated an XML file is created and sent automatically" +" to Carvajal, this file is displayed in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:207 +msgid "" +"An extra field is now displayed in \"Other Info\" tab with the name of the " +"XML file. Additionally there is a second extra field that is displayed with " +"the Electronic Invoice status, with the initial value \"In progress\":" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:216 +msgid "Reception of legal XML and PDF" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:218 +msgid "" +"The electronic invoice vendor receives the XML file and proceeds to validate" +" the structure and the information in it, if everything is correct the " +"invoice status changes to \"Validated\" after using the \"Check Carvajal " +"Status\" button in the Action dropdown. They then proceed to generate a " +"Legal XML which includes a digital signature and a unique code (CUFE), a PDF" +" invoice that includes a QR code and the CUFE is also generated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:226 +msgid "After this:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:228 +msgid "" +"A ZIP containing the legal XML and the PDF is downloaded and displayed in " +"the invoice chatter:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:235 +msgid "The Electronic Invoice status changes to \"Accepted\"" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:238 +msgid "Common errors" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:240 +msgid "" +"During the XML validation the most common errors are usually related to " +"missing master data. In such cases, error messages are shown in the chatter " +"after updating the electronic invoice status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 +msgid "" +"After the master data is corrected, it's possible to reprocess the XML with " +"the new data and send the updated version, using the following button:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:258 +msgid "Additional use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:260 +msgid "" +"The process for credit and debit notes is exactly the same as the invoice, " +"the functional workflow remains the same as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:3 +msgid "Colombia (ES)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:6 +msgid "Introducción" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:8 +msgid "" +"La Facturación Electrónica para Colombia está disponible en Odoo 12 y " +"requiere los siguientes Módulos:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:11 +msgid "" +"**l10n_co**: Contiene los datos básicos para manejar el módulo de " +"contabilidad, incluyendo la configuración por defecto de los siguientes " +"puntos:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:15 +msgid "Plan Contable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:16 +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:131 +msgid "Impuestos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:17 +msgid "Retenciones" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:18 +msgid "Tipos de Documentos de Identificación" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:20 +msgid "" +"**l10n_co_edi**: Este módulo incluye todos los campos adicionales que son " +"requeridos para la Integración entre Carvajal y la generación de la Factura " +"Electrónica, basado en los requisitos legales de la DIAN." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:26 +msgid "Flujo General" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:33 +msgid "Configuración" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:36 +msgid "Instalación de los módulos de Localización Colombiana" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:38 +msgid "" +"Para esto ve a las aplicaciones y busca “Colombia”, luego da click en " +"Instalar a los primeros dos módulos:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:46 +msgid "Configuración de las credenciales del Servicio Web de Carvajal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:50 +msgid "" +"Una vez que los módulos están instalados, para poderte conectar con el " +"Servicio Web de Carvajal, es necesario configurar el Usuario y las " +"Credenciales. Esta información será provista por Carvajal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:52 +msgid "" +"Ve a :menuselection:`Facturación --> Configuración --> Configuración` y " +"busca la sección **Facturación Electrónica Colombiana**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:57 +msgid "" +"La funcionalidad de pruebas le permite conectarse e interactuar con el " +"ambiente piloto de Carvajal, esto permite a los usuarios probar el flujo " +"completo y la integración con el Portal Financiero CEN, al cual se accede a " +"través de la siguiente liga:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:68 +msgid "CSC es el predeterminado para nuevas bases de datos." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:70 +msgid "" +"Una vez que el ambiente de producción está listo en Odoo y en Carvajal el " +"ambiente de pruebas debe ser deshabilitado para poder enviar la información " +"al ambiente de producción de Carvajal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:76 +msgid "Configuración de Información para PDF" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:80 +msgid "" +"Como parte de la información configurable que es enviada en el XML, puedes " +"definir los datos de la sección fiscal del PDF, así como de la información " +"Bancaria." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:82 +msgid "" +"Ve a :menuselection:`Contabilidad --> Configuración --> Ajustes` y busca la " +"sección **Facturación Electrónica Colombiana**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:89 +msgid "Configuración de los Datos Principales Requeridos en el XML" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:92 +msgid "Contacto (Tercero)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:95 +msgid "Identificación" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:97 +msgid "" +"Como parte de la Localización Colombiana, los tipos de documentos definidos " +"por la DIAN ahora están disponibles en el formulario de Contactos, por lo " +"cual ya es posible asignarles su número de identificación asociado al tipo " +"de documento correspondiente." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:105 +msgid "" +"Nota: Cuando el tipo de documento es RUT la identificación necesita ser " +"ingresada en Odoo incluyendo el Dígito de Verificación. Odoo separará este " +"número cuando la información sea enviada a los proveedores terceros." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:112 +msgid "Estructura Fiscal (RUT)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:114 +msgid "" +"Los Códigos de tipo de Obligación aplicables a los terceros (sección 53 en " +"el documento de RUT), son incluidos como parte del módulo de Facturación " +"Electrónica, dado que es información requerida por la DIAN." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:118 +msgid "" +"Estos campos se encuentran en :menuselection:`Contactos --> Pestaña de " +"Ventas y Compras --> Información Fiscal`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:124 +msgid "" +"Adicionalmente dos últimos campos fueron agregados para especificar el " +"régimen fiscal del contacto. Cabe aclarar que para envío de Factura " +"electrónica de Carvajal, únicamente se hace distinción de entre Grandes " +"Contribuyentes y Régimen simplificado, por lo se muestran solo estas dos " +"opciones." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:133 +msgid "" +"Si tus transacciones de ventas incluyen productos con impuestos, es " +"importante considerar que un campo adicional llamado *Tipo de Valor* " +"necesita ser configurado en la siguiente ruta: :menuselection:`Contabilidad " +"--> Configuración --> Impuestos: --> Opciones Avanzadas --> Tipo de Valor`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:141 +msgid "" +"Los impuestos para Retenciones (ICA, IVA y Fuente) también están incluidos " +"en las opciones para configurar tus impuestos, esta configuración es " +"considerada para desplegar correctamente los impuestos en la representación " +"gráfica de la Factura. (PDF)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:151 +msgid "Diarios" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:153 +msgid "" +"Una vez que la DIAN ha asignado la secuencia y prefijo oficiales para la " +"resolución de la Facturación Electrónica, los Diarios de Ventas relacionados" +" con tus documentos de facturación necesitan ser actualizados en Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:158 +msgid "" +"La secuencia es configurada usando el modo de desarrollador en la siguiente " +"ruta: :menuselection:`Contabilidad --> Configuración --> Diarios --> Liga de" +" Secuencia`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:165 +msgid "" +"Una vez que la secuencia es abierta, los campos de Prefijo y Siguiente " +"Número deben ser configurados y sincronizados con el CEN Financiero." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:173 +msgid "Usuarios" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:175 +msgid "" +"La plantilla por defecto que es usada por Odoo en la representación gráfica " +"incluye el nombre del Vendedor, así que estos campos deben ser considerados:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:184 +msgid "Uso y Pruebas" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:187 +msgid "Facturas" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:189 +msgid "" +"Una vez que toda la información principal y las credenciales han sido " +"configuradas, es posible empezar a probar el flujo de la Facturación " +"Electrónica siguiendo las instrucciones que se detallan a continuación:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:195 +msgid "Invoice Creation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:197 +msgid "" +"El flujo de trabajo funcional que lleva lugar antes de la validación de una " +"factura continua siendo igual con Facturación Electrónica, " +"independientemente de si es creada desde una Orden de Venta o si es creado " +"manualmente." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:202 +msgid "" +"Los cambios principales que son introducidos con la Facturación Electrónica " +"son los siguientes:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:205 +msgid "Hay tres tipos de documentos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:207 +msgid "" +"**Factura electrónica**. Este es el documento normal y aplica para Facturas," +" Notas de Crédito y Notas de Débito." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:210 +msgid "" +"**Factura de Importación**. Debe ser seleccionada para transacciones de " +"importación." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:213 +msgid "" +"**Factura de Contingencia**. Esta es un caso excepcional y es utilizada como" +" un respaldo manual en caso que la compañía no pueda usar el ERP y hay " +"necesidad de crear la factura manualmente. Al ingresar esta factura en el " +"ERP, se debe seleccionar este tipo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:223 +msgid "Invoice Validation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:225 +msgid "" +"Después que la factura fue validada, un archivo XML es creado y enviado " +"automáticamente al proveedor de la factura electrónica. Este archivo es " +"desplegado en el historial." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:232 +msgid "" +"Un campo adicional es ahora desplegado en la pestaña de “Otra Información” " +"con el nombre del archivo XML. Adicionalmente hay un segundo campo adicional" +" que es desplegado con el estatus de la Factura Electrónica, con el valor " +"inicial **En Proceso**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:242 +msgid "Recepción del XML y PDF Legal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:249 +msgid "" +"El proveedor de la Factura Electrónica recibe el archivo XML y procede a " +"validar la información y la estructura contenida. Si todo es correcto, el " +"estatus de la Factura cambia a “Validado”. Como parte de este proceso se " +"generar el XML Legal, el cual incluye una firma digital y un código único " +"(CUFE) y generan el PDF de la Factura (el cual incluye un código QR) y el " +"CUFE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:253 +msgid "" +"Odoo envía una petición de actualización automáticamente para verificar que " +"el XML fue creado. Si este es el caso, las siguientes acciones son hechas " +"automáticamente:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:255 +msgid "" +"El XML Legal y el PDF son incluidos en un archivo ZIP y desplegados en el " +"historial de la Factura." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:260 +msgid "El estatus de la Factura Electrónica es cambiado a “Aceptado”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:265 +msgid "" +"En caso que el PDF y el XML sean requeridos inmediatamente, es posible " +"mandar manualmente la petición del estatus usando el siguiente botón:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:274 +msgid "Errores Frecuentes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:276 +msgid "" +"Durante la validación del XML los errores más comunes usualmente están " +"relacionados con información principal faltante. En estos casos, los " +"detalles del error son recuperados en la petición de actualización y " +"desplegados en el historial." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:284 +msgid "" +"Si la información principal es corregida, es posible re procesar el XML con " +"la nueva información y mandar la versión actualizada usando el siguiente " +"botón:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:296 +msgid "Casos de Uso adicionales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:298 +msgid "" +"El proceso para las Notas de Crédito y Débito (Proveedores) es exactamente " +"el mismo que en las Facturas. Su flujo de trabajo funcional se mantiene " +"igual." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:303 +msgid "Consideraciones del Anexo 1.7" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:306 +msgid "Contexto" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:309 +msgid "Contexto Normativo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:311 +msgid "Soporte Normativo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:312 +msgid "" +"Resolución DIAN Número 000042 ( 5 de Mayo de 2020) Por la cual se " +"desarrollan:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:314 +msgid "Los sistemas de facturación," +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:315 +msgid "Los proveedores tecnológicos," +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:316 +msgid "El registro de la factura electrónica de venta como título valor," +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:317 +msgid "Se expide el anexo técnico de factura electrónica de venta y" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:318 +msgid "Se dictan otras disposiciones en materia de sistemas de facturación." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:321 +msgid "Anexo 1.7: Principales Cambios" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:323 +msgid "Cambios en la definición de Consumidor Final." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:324 +msgid "Informar bienes cubiertos para los 3 dias sin IVA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:325 +msgid "Actualización de descripción de Impuestos." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:326 +msgid "Se agrega concepto para IVA Excluido." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:327 +msgid "Informar la fecha efectiva de entrega de los bienes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:328 +msgid "Adecuaciones en la representación Gráfica (PDF)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:331 +msgid "Calendario" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:333 +msgid "" +"Se tiene varias fechas límites para la salida a producción bajo las " +"condiciones del Anexo 1.7 las cuales dependen de los siguientes factores:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:336 +msgid "" +"Calendario de implementación de acuerdo con la actividad económica principal" +" en el RUT:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:341 +msgid "Calendario de implementación, para otros sujetos obligados:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:346 +msgid "Calendario de implementación permanente:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:352 +msgid "Requerimientos en Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:354 +msgid "" +"Con la finalidad de facilitar el proceso de preparación de las bases de Odoo" +" estándar V12 y v13, únicamente será necesario que los administradores " +"actualicen algunos módulos y creen los datos maestros relacionados a los " +"nuevos procesos." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:359 +msgid "Actualización de listado de Apps" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:361 +msgid "" +"Utilizando el modo desarrollador, acceder al módulo de Aplicaciones y " +"seleccionar el menú *Actualizar Lista*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:368 +msgid "Actualización de Módulos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:370 +msgid "" +"Una vez actualizado Buscar *Colombia*, los siguientes módulos serán " +"desplegados, se requieren actualizar dos módulos." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:373 +msgid "Colombia - Contabilidad - l10n_co" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:374 +msgid "" +"Electronic invoicing for Colombia with Carvajal UBL 2.1 - " +"l10n_co_edi_ubl_2_1" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:379 +msgid "" +"En cada módulo o ícono hay que desplegar el menú opciones utilizando los 3 " +"puntos de la esquina superior derecha y seleccionamos *Actualizar*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:382 +msgid "Primero lo hacemos con en el módulo l10n_co:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:387 +msgid "Posteriormente lo hacemos con el módulo l10n_co_edi_ubl_2_1:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:393 +msgid "Creación de Datos Maestros" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:395 +msgid "" +"Las bases de datos existentes a Junio 2020 tanto en V12 como V13, deberán " +"crear algunos datos maestros necesarios para operar correctamente con los " +"cambios del Anexo 1.7." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:399 +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:498 +msgid "Consumidor Final" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:401 +msgid "" +"La figura del consumidor final será utilizada para aquellas ventas sobre las" +" cuales no es posible identificar toda la información fiscal y demográfica " +"del cliente por lo que la factura se genera a nombre de este registro " +"genérico." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:405 +msgid "" +"Es importante coordinar y definir los casos de uso en los que dependiendo de" +" su empresa se tendrá permitido utilizar este registro genérico." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:408 +msgid "" +"Dentro de Odoo se tendrá que crear un contacto con las siguientes " +"características, es importante que se defina de esta manera debido a que son" +" los parámetros definidos por la DIAN." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:411 +msgid "**Tipo de contacto:** Individuo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:412 +msgid "**Nombre:** Consumidor Final" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:413 +msgid "**Tipo de documento:** Cedula de Ciudadania" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:414 +msgid "**Numero de Identificacion:** 222222222222" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:419 +msgid "" +"Dentro de la pestaña Ventas y Compras, en la sección Información Fiscal, del" +" campo Obligaciones y Responsabilidades colocaremos el valor: **R-99-PN**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:426 +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:513 +msgid "IVA Excluido - Bienes Cubiertos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:428 +msgid "" +"Para reportar las transacciones realizadas mediante Bienes Cubiertos para " +"los tres días sin IVA, será necesario crear un nuevo Impuesto al cual se le " +"debe de asociar un grupo de impuestos específico que será utilizado por Odoo" +" para agregar la sección requerida en el XML de factura electrónica." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:433 +msgid "" +"Para el crear el impuesto accederemos a Contabilidad dentro del menú " +":menuselection:`Configuración --> Impuestos`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:439 +msgid "" +"Procedemos a crear un nuevo Impuesto con importe 0% considerando los " +"siguientes parámetros:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:444 +msgid "" +"El nombre del Impuesto puede ser definido a preferencia del usuario, sin " +"embargo el campo clave es **Grupo de Impuestos** dentro de Opciones " +"avanzadas, el cual debe ser: *bienes cubiertos* y el campo **Tipo de " +"Valor**: *IVA*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:452 +msgid "Actualización de descripción de Departamentos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:454 +msgid "" +"Es necesario actualizar la descripción de algunos departamentos, para lo " +"cual accederemos a módulo de Contactos y dentro del menú de " +":menuselection:`Configuración --> Provincias`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:460 +msgid "" +"Posteriormente, podemos agregar por País para identificar claramente las " +"provincias (Departamentos) de Colombia:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:466 +msgid "" +"Una vez agrupados buscar los siguientes departamentos para actualizarlos con" +" el valor indicado en la columna **Nombre actualizado**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:470 +msgid "Nombre de provincia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:470 +msgid "Código de Provincia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:470 +msgid "Nombre actualizado" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:472 +msgid "D.C." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:472 +msgid "DC" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:472 +msgid "Bogotá" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:474 +msgid "Quindio" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:474 +msgid "QUI" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:474 +msgid "Quindío" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:476 +msgid "Archipiélago de San Andrés, Providencia y Santa Catalina" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:476 +msgid "SAP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:476 +msgid "San Andrés y Providencia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:480 +msgid "Ejemplo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:486 +msgid "Verificación de Código postal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:488 +msgid "" +"Dentro del Anexo 1.7 se comienza a validar que el código postal de las " +"direcciones para contactos colombianos corresponda a las tablas oficiales " +"definidas por la DIAN, por lo que se debe verificar que este campo está " +"debidamente diligenciado de acuerdo a los definidos en la sigueinte fuente: " +"`Codigos_Postales_Nacionales.csv " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:495 +msgid "Consideraciones Operativas" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:500 +msgid "" +"Una vez que resgistro de Consumidor final ha sido creado este deberá ser " +"utilizado a demanda, generalmente será utilizado en las transacciones de " +"facturación del punto de punto de venta." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:503 +msgid "" +"El proceso de validación de la Factura será realizado de forma convencional " +"en Odoo y la factura será generada de la misma manera. Al detectar que el " +"número de identificación corresponde a consumidor Final, el XML que se envía" +" a Carvajal será generado con las consideraciones y secciones " +"correspondientes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:507 +msgid "" +"Contablemente todos los registros de Consumidor final quedarán asociados al " +"identificador generico:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:515 +msgid "" +"El 21 mayo del 2020 fue publicado el El Decreto 682 el cual establece " +"Excepción especial en el Impuesto sobre las ventas. El principal objetivo de" +" este decreto es reactivar la economía en Colombia por las bajas ventas " +"generadas a causa del COVID." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:520 +msgid "Fechas" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:522 +msgid "" +"Días de excención del impuesto sobre las ventas – IVA para bienes cubiertos " +"(3 días SIN IVA)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:524 +msgid "**Primer día**: 19 de junio de 2020" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:525 +msgid "**Segundo día**: 3 de Julio de 2020" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:526 +msgid "**Tercer día**: 19 de Julio de 2020" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:529 +msgid "Condiciones" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:531 +msgid "" +"Debido a que estas transacciones serán generadas de forma excepcional y que " +"se tiene una combinación de varios factores y condiciones, los productores " +"debera ser actualizados de forma manual en Odoo asignados temporalmente el " +"impuesto de venta *IVA exento - Bienes cubierto* en cada empresa según " +"corresponda." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:536 +msgid "" +"A continuación se mencionan algunas de las principales condiciones, sin " +"embargo, cabe mencionar que las empresas deben de verificar todos los " +"detalles en el `Decreto 682 " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:540 +msgid "Tipo de productos y precio Máximo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:543 +msgid "Tipo de Productos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:543 +msgid "Precio Máximo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:545 +msgid "Electrodomesticos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:545 +msgid "40 UVT: $1,4 millones." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:547 +msgid "Vestuario y complementos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:0 +msgid "3 UVT: $106.000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:0 +msgid "En el caso de los complementos es:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:0 +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:551 +msgid "10 UVT- $356.000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:551 +msgid "Elementos deportivos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:553 +msgid "Juguetes y Utiles Escolares" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:553 +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:555 +msgid "5 UVT - $178.035" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:555 +msgid "Utiles Escolares" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:557 +msgid "Bienes o servicios para el sector agropecuario" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:557 +msgid "80 UVT - $2.848.560" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:561 +msgid "Métodos de Pago:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:563 +msgid "" +"El pago debe realizarse por medios electrónico por ejemplo tarjetas de " +"crédito/débito o bien mecanismos de pago online." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:565 +msgid "Limite de unidades:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:567 +msgid "" +"Cada cliente puede adquirir únicamente 3 unidades como máximo de cada " +"producto." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:570 +msgid "Medidas en Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:572 +msgid "**Preparación de datos**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:574 +msgid "" +"Crear el Impuesto para Bienes cubiertos de acuerdo a lo indicado en este " +"punto: Datos maestros." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:575 +msgid "" +"Identificar los productos y transacciones a los cuales les aplicará la " +"Exclusión de IVA de acuerdo a las condiciones establecidas en el decreto " +"682. En caso de ser un porcentaje significativo de productos, se recomienda " +"actualizar el impuesto de forma temporal en Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:578 +msgid "" +"Exportar un listado con los productos que serán afectados incluyendo el " +"campo IVA Venta el cual será sustituido temporalmente por el IVA de Bienes " +"Cubiertos." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:580 +msgid "" +"Al finalizar las operaciones del día anterior a las fechas establecidas de " +"día sin IVA, se debe hacer la actualización temporal a IVA de Bienes " +"Cubiertos." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:586 +msgid "**Durante el día SIN IVA**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:588 +msgid "" +"Por defecto los productos previamente considerados con IVA de Bienes " +"cubiertos serán generados con este parámetro tanto en Órdenes de venta como " +"facturas creadas durante ese mismo día." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:594 +msgid "" +"Las órdenes de venta generadas con este impuesto deberán ser facturas el " +"mismo día." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:595 +msgid "" +"En caso de que alguna de las condiciones no sea cumplida (ejemplo el pago es" +" realizado en efectivo) el impuesto deberá ser actualizado manualmente al " +"momento de facturar." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:598 +msgid "**Posterior al día SIN IVA**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:600 +msgid "" +"Los productos que fueron actualizados deberá ser reconfigurados a su IVA " +"original." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia_ES.rst:601 +msgid "" +"En caso de que se detecte alguna Orden de venta facturar en la cual se " +"incluya IVA de Bienes Cubiertos, se deberá realizar actualización manual " +"correspondiente al IVA convencional." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:8 +#: ../../content/applications/finance/fiscal_localizations/india.rst:8 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:8 +msgid "Installation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egyptian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:19 +msgid ":guilabel:`Egypt - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:20 +msgid "``l10n_eg``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:21 +#: ../../content/applications/finance/fiscal_localizations/india.rst:21 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:22 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:19 +msgid "" +"Default :ref:`fiscal localization package `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:22 +msgid ":guilabel:`Egyptian E-invoice Integration`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:23 +msgid "``l10n_eg_edi_eta``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:24 +msgid "" +":ref:`Egyptian Tax Authority (ETA) e-invoicing integration " +"`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:29 +msgid "Egyptian e-invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:31 +msgid "" +"Odoo is compliant with the **Egyptian Tax Authority (ETA) e-invoicing** " +"requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:34 +msgid "" +"Egyptian e-invoicing is available from Odoo 15.0. If needed, :doc:`upgrade " +"` your database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:38 +msgid "" +"`Video: Egypt E-invoicing `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:39 +msgid ":doc:`/administration/upgrade`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:44 +msgid "Register Odoo on your ETA portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:46 +msgid "" +"You must register your Odoo ERP system on your ETA portal to get your API " +"credentials. You need these codes to :ref:`configure your Odoo Accounting " +"app `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:49 +msgid "" +"Access your company profile on the ETA portal by clicking on :guilabel:`View" +" Taxpayer Profile`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Clicking on \"View Taxpayer Profile\" on an ETA invoicing portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:55 +msgid "" +"Next, go to the :guilabel:`Representatives` section and then click on " +":guilabel:`Register ERP`. Fill out the :guilabel:`ERP Name` (e.g., ``Odoo``)" +" and leave the other fields empty." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Filling out of the form to register an ERP system on the ETA portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:62 +msgid "" +"Once successfully registered, the website displays your API credentials:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:64 +msgid "Client ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:65 +msgid "Client Secret 1" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:66 +msgid "Client Secret 2" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:69 +msgid "" +"ETA should give you a username and a password to access their online portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:70 +msgid "Ask ETA to provide you with preproduction portal access as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:71 +msgid "These codes are confidential and should be stored safely." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:76 +msgid "Configuration on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:78 +msgid "" +"To connect your Odoo database to your ETA portal account, go to " +":menuselection:`Accounting --> Configuration --> Settings --> ETA " +"E-Invoicing Settings`, and set the :guilabel:`ETA Client ID` and " +":guilabel:`ETA Secret` that you retrieved when you :ref:`registered Odoo on " +"your ETA portal `. Set an invoicing threshold " +"if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Configuration of the ETA E-Invoicing credentials in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:88 +msgid "" +"**Test on your preproduction portal** before starting to issue real invoices" +" on the production ETA portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:90 +msgid "" +"**Credentials** for preproduction and production environments are different." +" Make sure to update them on Odoo when you move from one environment to " +"another." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:92 +msgid "" +"If not done yet, fill out your company details with your company's full " +"address, country, and Tax ID." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:98 +msgid "ETA codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:100 +msgid "" +"E-invoicing works with a set of codes provided by the ETA. You can use the " +"`ETA documentation `_ to " +"code your business attributes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:103 +msgid "" +"Most of these codes are handled automatically by Odoo, provided that your " +":ref:`branches `, :ref:`customers " +"`, and :ref:`products ` are correctly configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:107 +msgid "Company Information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:109 +msgid "Company Tax ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "Branch ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "If you have only one branch, use ``0`` as the branch code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:112 +msgid "Activity type Code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:114 +msgid "Other Information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "Product Codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "" +"Your company's products should be coded and matched with their **GS1** or " +"**EGS** codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "Tax Codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "" +"Most of the taxes codes are already configured on Odoo in the :guilabel:`ETA" +" Code (Egypt)` field. We advise you to make sure these codes match your " +"company's taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:123 +msgid "" +"`Egyptian eInvoicing & eReceipt SDK - Code Tables " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:125 +msgid ":doc:`../accounting/taxes`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:130 +msgid "Branches" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:132 +msgid "" +"Create a contact and a journal for each branch of your company and configure" +" its ETA settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:134 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"then click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:137 +msgid "" +"Name the journal according to your company's branch and set the " +":guilabel:`Type` as :guilabel:`Sales`. Next, open the " +":menuselection:`Advanced Settings` tab and fill out the :guilabel:`Egyptian " +"ETA settings` section:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:141 +msgid "" +"In the :guilabel:`Branch` field, select the branch's contact or create it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:142 +msgid "Set the :guilabel:`ETA Activity Code`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:143 +msgid "" +"Set the :guilabel:`ETA Branch ID` (use ``0`` if you have one branch only)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Sales journal configuration of an Egyptian company's branch" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:150 +msgid "" +"The contact selected in the :guilabel:`Branch` field must be set as a " +":guilabel:`Company` (**not** as an :guilabel:`Individual`), and the " +":guilabel:`Address` and :guilabel:`Tax ID` fields must be filled out." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:157 +msgid "Customers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:159 +msgid "" +"Make sure your customers' contact forms are correctly filled out so your " +"e-invoices are valid:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:161 +msgid "contact type: :guilabel:`Individual`: or :guilabel:`Company`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:162 +msgid ":guilabel:`Country`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:163 +msgid "" +":guilabel:`Tax ID`: Tax ID or Company registry for companies. National ID " +"for individuals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:166 +msgid "" +"You can edit your customers' contact forms by going to " +":menuselection:`Accounting --> Customers --> Customers`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:378 +msgid "Products" +msgstr "Produkty" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:174 +msgid "" +"Make sure your products are correctly configured so your e-invoices are " +"valid:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:176 +msgid ":guilabel:`Product Type`: storable products, consumables, or services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:177 +msgid "" +":guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled" +" :doc:`Units of Measure " +"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:179 +msgid ":guilabel:`Barcode`: **GS1** or **EGS** barcode" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:180 +msgid "" +":guilabel:`ETA Item code` (under the :menuselection:`Accounting` tab): if " +"the barcode doesn't match your ETA item code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:184 +msgid "" +"You can edit your products by going to :menuselection:`Accounting --> " +"Customers --> Products`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:189 +msgid "USB authentication" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:191 +msgid "" +"Each person who needs to electronically sign invoices needs a specific USB " +"key to authenticate and send invoices to the ETA portal through an ERP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:195 +msgid "" +"You can contact the :abbr:`ETA (Egyptian Tax Authority)` or `Egypt Trust " +"`_ to get these USB keys." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:201 +msgid "Install Odoo as a local proxy on your computer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:203 +msgid "" +"An Odoo local server works as a bridge between your computer and your Odoo " +"database hosted online." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:205 +msgid "" +"Download the Odoo Community installer from the page " +"https://www.odoo.com/page/download and start the installation on your " +"computer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:208 +msgid "Select :guilabel:`Local Proxy Mode` as the type of install." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "" +"Selection of \"Local Proxy Mode\" during the installation of Odoo Community." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:215 +msgid "" +"This installation of Odoo only works as a server and does not install any " +"Odoo apps on your computer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:218 +msgid "" +"Once the installation is complete, the installer displays your **access " +"token** for the Odoo Local Proxy. Copy the token and save it in a safe place" +" for later use." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:222 +msgid "`Odoo: Download Odoo `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:223 +msgid ":doc:`/administration/install/install`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:228 +msgid "Configure the USB key" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:230 +msgid "" +"Once the local proxy server is installed on your computer, you can link it " +"with your Odoo database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:232 +msgid "" +"Go to :menuselection:`Accounting --> Configurations --> Thumb Drive` and " +"click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:234 +msgid "" +"Input a :guilabel:`Company` name, the :guilabel:`ETA USB Pin` given to you " +"by your USB key provider, and the :guilabel:`Access Token` provided at the " +"end of the :ref:`local proxy installation `, " +"then click on :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:237 +msgid "Click on :guilabel:`Get certificate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Creating a new thumb drive for the e-invoicing of an egyptian company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:3 +msgid "France" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:8 +msgid "FEC - Fichier des Écritures Comptables" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:10 +msgid "" +"An FEC :dfn:`Fichier des Écritures Comptables` audit file contains all the " +"accounting data and entries recorded in all the accounting journals for a " +"financial year. The entries in the file must be arranged in chronological " +"order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:14 +msgid "" +"Since January 1st, 2014, every French company is required to produce and " +"transmit this file upon request by the tax authorities for audit purposes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:18 +msgid "FEC Import" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:20 +msgid "" +"To make the onboarding of new users easier, Odoo Enterprise's French " +":ref:`fiscal localization package ` includes " +"the **FEC Import** feature (module name: ``l10n_fr_fec_import``), which " +"enables the import of existing FEC files from older software." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:24 +msgid "" +"To enable this feature, go to :menuselection:`Accounting --> Configuration " +"--> Settings --> Accounting Import`, enable **FEC Import**, and *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:27 +msgid "" +"Next, go to :menuselection:`Accounting --> Configuration --> FEC Import`, " +"upload your FEC file, and click on *Import*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"Importing FEC files from different year takes no particular action or " +"computation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"Should multiple files contain any \"Reports à Nouveaux\" (RAN) with the " +"starting balance of the year, you might need to cancel those entries in the " +"User Interface. Odoo makes those entries (RAN) useless." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:38 +msgid "File formats" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:40 +msgid "" +"FEC files can only be in CSV format, as the XML format is not supported." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:44 +msgid "" +"The FEC CSV file has a plain text format representing a data table, with the" +" first line being a header and defining the list of fields for each entry, " +"and each following line representing one accounting entry, in no " +"predetermined order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:48 +msgid "" +"Our module expects the files to meet the following technical specifications:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:50 +msgid "**Encoding**: UTF-8, UTF-8-SIG and iso8859_15." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:51 +msgid "**Separator**: any of these: `;` or `|` or `,` or `TAB`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:52 +msgid "" +"**Line terminators**: both CR+LF (`\\\\r\\\\n`) and LF (`\\\\n`) character " +"groups are supported." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:53 +msgid "**Date format**: `%Y%m%d`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:56 +msgid "Fields description and use" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "#" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "Field name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "Format" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "01" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "JournalCode" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "Journal Code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "`journal.code` and `journal.name` if `JournalLib` is not provided" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "Alphanumeric" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "02" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "JournalLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "Journal Label" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "`journal.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "03" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "EcritureNum" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "Numbering specific to each journal sequence number of the entry" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "`move.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +msgid "04" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +msgid "EcritureDate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +msgid "Accounting entry Date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "`move.date`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "Date (yyyyMMdd)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +msgid "05" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "CompteNum" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +msgid "Account Number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +msgid "`account.code`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "06" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "CompteLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "Account Label" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "`account.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "07" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "CompAuxNum" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "Secondary account Number (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "`partner.ref`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "08" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "CompAuxLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "Secondary account Label (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "`partner.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "09" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "PieceRef" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "Document Reference" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "`move.ref` and `move.name` if `EcritureNum` is not provided" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "PieceDate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "Document Date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "11" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "EcritureLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "Account entry Label" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "`move_line.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +msgid "Debit amount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +msgid "`move_line.debit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "Float" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "13" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +msgid "Credit amount (Field name \"Crédit\" is not allowed)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +msgid "`move_line.credit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "14" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "EcritureLet" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "Accounting entry cross reference (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "`move_line.fec_matching_number`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +msgid "DateLet" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +msgid "Accounting entry date (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "unused" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "16" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "ValidDate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "Accounting entry validation date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "17" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "Montantdevise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "Currency amount (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "`move_line.amount_currency`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "18" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "Idevise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "Currency identifier (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "`currency.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:108 +msgid "" +"These two fields can be found in place of the others in the sence above." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "Montant" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "Amount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "`move_line.debit` or `move_line.credit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "Sens" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "Can be \"C\" for Credit or \"D\" for Debit" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "determines `move_line.debit` or `move_line.credit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "Char" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:119 +msgid "Implementation details" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:121 +msgid "" +"The following accounting entities are imported from the FEC files: " +"**Accounts, Journals, Partners**, and **Moves**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:124 +msgid "" +"Our module determines the encoding, the line-terminator character, and the " +"separator that are used in the file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:127 +msgid "" +"A check is then performed to see if every line has the correct number of " +"fields corresponding to the header." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:130 +msgid "" +"If the check passes, then the file is read in full, kept in memory, and " +"scanned. Accounting entities are imported one type at a time, in the " +"following order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:134 +msgid "Accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:136 +msgid "" +"Every accounting entry is related to an account, which should be determined " +"by the field `CompteNum`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:140 +msgid "Code matching" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:142 +msgid "" +"Should a similar account code already be present in the system, the existing" +" one is used instead of creating a new one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:145 +msgid "" +"Accounts in Odoo generally have a number of digits that are default for the " +"fiscal localization. As the FEC module is related to the French " +"localization, the default number of relevant digits is 6." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:148 +msgid "" +"This means that the account codes the trailing zeroes are right-trimmed, and" +" that the comparison between the account codes in the FEC file and the ones " +"already existing in Odoo is performed only on the first six digits of the " +"codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:153 +msgid "" +"The account code `65800000` in the file is matched against an existing " +"`658000` account in Odoo, and that account is used instead of creating a new" +" one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:157 +msgid "Reconcilable flag" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:159 +msgid "" +"An account is technically flagged as *reconcilable* if the first line in " +"which it appears has the `EcritureLet` field filled out, as this flag means " +"that the accounting entry is going to be reconciled with another one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:165 +msgid "" +"In case the line somehow has this field not filled out, but the entry still " +"has to be reconciled with a payment that hasn't yet been recorded, this " +"isn't a problem anyway; the account is flagged as reconcilable as soon as " +"the import of the move lines requires it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:170 +msgid "Account type and Templates matching" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:172 +msgid "" +"As the **type** of the account is not specified in the FEC format, **new** " +"accounts are created with the default type *Current Assets* and then, at the" +" end of the import process, they are matched against the installed Chart of " +"Account templates. Also, the *reconcile* flag is also computed this way." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:177 +msgid "" +"The match is done with the left-most digits, starting by using all digits, " +"then 3, then 2." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:54 +msgid "Code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +msgid "Full comparison" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +msgid "3-digits comparison" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +msgid "2-digits comparison" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:61 +msgid "Template" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +msgid "`400000`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +msgid "`400`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "`40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "`40100000`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "`401`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:188 +msgid "**Result**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:188 +msgid "Match **found**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:191 +msgid "" +"The type of the account is then flagged as *payable* and *reconcilable* as " +"per the account template." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:196 +msgid "" +"Journals are also checked against those already existing in Odoo to avoid " +"duplicates, also in the case of multiple FEC files imports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:199 +msgid "" +"Should a similar journal code already be present in the system, the existing" +" one is used instead of creating a new one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:202 +msgid "New journals have their name prefixed by the string ``FEC-``." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:205 +msgid "`ACHATS` -> `FEC-ACHATS`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:207 +msgid "" +"The journals are *not* archived, the user is entitled to handle them as he " +"wishes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:210 +msgid "Journal type determination" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:212 +msgid "" +"The journal type is also not specified in the format (as per the accounts) " +"and therefore it is at first created with the default type `general`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:215 +msgid "" +"At the end of the import process, the type is determined as per these rules " +"regarding related moves and accounts:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`bank`: Moves in these journals always have a line (debit or credit) " +"impacting a liquidity account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`cash` / `bank` can be interchanged, so `bank` is set everywhere when this " +"condition is met." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`sale`: Moves in these journals mostly have debit lines on receivable " +"accounts and credit lines on tax income accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "Sale refund journal items are debit/credit inverted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`purchase`: Moves in these journals mostly have credit lines on payable " +"accounts and debit lines on expense accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "Purchase refund journal items are debit/credit inverted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "`general`: for everything else." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:231 +msgid "A minimum of three moves is necessary for journal type identification." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:232 +msgid "" +"A threshold of 70% of moves must correspond to a criteria for a journal type" +" to be determined." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:235 +msgid "Suppose we are analyzing the moves that share a certain `journal_id`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +#: ../../content/applications/finance/fiscal_localizations/france.rst:269 +msgid "Moves" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +msgid "Count" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +msgid "Percentage" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:240 +msgid "that have a sale account line and no purchase account line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +msgid "that have a purchase account line and no sale account line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +msgid "25%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +msgid "that have a liquidity account line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +msgid "3" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +msgid "**75%**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +msgid "**Total**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +msgid "4" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +msgid "100%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:249 +msgid "" +"The journal `type` would be `bank`, because the bank moves percentage (75%) " +"exceeds the threshold (70%)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:253 +msgid "Partners" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:255 +msgid "Each partner keeps its `Reference` from the field `CompAuxNum`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:259 +msgid "" +"These fields are searchable, in line with former FEC imports on the " +"accounting expert's side for fiscal/audit purposes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:264 +msgid "" +"Users can merge partners with the Data Cleaning App, where Vendors and " +"Customers or similar partner entries may be merged by the user, with " +"assistance from the system that groups them by similar entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:271 +msgid "" +"Entries are immediately posted and reconciled after submission, using the " +"`EcritureLet` field to do the matching between the entries themselves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:274 +msgid "" +"The `EcritureNum` field represents the name of the moves. We noticed that " +"sometimes it may not be filled out. In this case, the field `PieceRef` is " +"used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:278 +msgid "Rounding issues" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:280 +msgid "" +"There is a rounding tolerance with a currency-related precision on debit and" +" credit (i.e., 0.01 for EUR). Under this tolerance, a new line is added to " +"the move, named *Import rounding difference*, targeting the accounts:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:284 +msgid "`658000` Charges diverses de gestion courante, for added debits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:285 +msgid "`758000` Produits divers de gestion courante, for added credits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:288 +msgid "Missing move name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:290 +msgid "" +"Should the `EcritureNum` not be filled out, it may also happen that the " +"`PieceRef` field is also not suited to determine the move name (it may be " +"used as an accounting move line reference) leaving no way to actually find " +"which lines are to be grouped in a single move, and effectively impeding the" +" creation of balanced moves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:295 +msgid "" +"One last attempt is made, grouping all lines from the same journal and date " +"(`JournalLib`, `EcritureDate`). Should this grouping generate balanced moves" +" (sum(credit) - sum(debit) = 0), then each different combination of journal " +"and date creates a new move." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:300 +msgid "" +"`ACH` + `2021/05/01` --> new move on journal `ACH` with name `20210501`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:302 +msgid "" +"Should this attempt fail, the user is prompted an error message with all the" +" move lines that are supposedly unbalanced." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:306 +msgid "Partner information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:308 +msgid "" +"If a line has the partner information specified, the information is copied " +"to the accounting move itself if the targeted Journal is of type *payable* " +"or *receivable*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:312 +msgid "Export" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:314 +msgid "" +"If you have installed the French :ref:`fiscal localization package " +"`, you should be able to download the FEC. To" +" do so, go to :menuselection:`Accounting --> Reporting --> France --> FEC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:320 +msgid "" +"If you do not see the submenu **FEC**, go to :menuselection:`Apps`, remove " +"the *Apps* filter, then search for the module named **France-FEC** and make " +"sure it is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:325 +msgid "" +"`Official Technical Specification (fr) " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:327 +msgid "" +"`Test-Compta-Demat (Official FEC Testing tool) " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:331 +msgid "French Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:333 +msgid "" +"If you have installed the French Accounting, you will have access to some " +"accounting reports specific to France:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:336 +msgid "Bilan comptable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:337 +msgid "Compte de résultats" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:338 +msgid "Plan de Taxes France" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:341 +msgid "Get the VAT anti-fraud certification with Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:343 +msgid "" +"As of January 1st 2018, a new anti-fraud legislation comes into effect in " +"France and DOM-TOM. This new legislation stipulates certain criteria " +"concerning the inalterability, security, storage and archiving of sales " +"data. These legal requirements are implemented in Odoo, version 9 onward, " +"through a module and a certificate of conformity to download." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:350 +msgid "Is my company required to use anti-fraud software?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:352 +msgid "" +"Your company is required to use an anti-fraud cash register software like " +"Odoo (CGI art. 286, I. 3° bis) if:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:355 +msgid "You are taxable (not VAT exempt) in France or any DOM-TOM," +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:356 +msgid "Some of your customers are private individuals (B2C)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:358 +msgid "" +"This rule applies to any company size. Auto-entrepreneurs are exempted from " +"VAT and therefore are not affected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:362 +msgid "Get certified with Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:364 +msgid "Getting compliant with Odoo is very easy." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:366 +msgid "" +"Your company is requested by the tax administration to deliver a certificate" +" of conformity testifying that your software complies with the anti-fraud " +"legislation. This certificate is granted by Odoo SA to Odoo Enterprise users" +" `here `_. If you " +"use Odoo Community, you should :doc:`upgrade to Odoo Enterprise " +"` or contact your Odoo service " +"provider." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:373 +msgid "In case of non-conformity, your company risks a fine of €7,500." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:375 +msgid "To get the certification, just follow the following steps:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:377 +msgid "" +"If you use **Odoo Point of Sale**, :ref:`install ` the " +"**France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 " +"bis)** module by going to :menuselection:`Apps`, removing the *Apps* filter," +" then searching for *l10n_fr_pos_cert*, and installing the module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:381 +msgid "" +"Make sure a country is set on your company, otherwise your entries won’t be " +"encrypted for the inalterability check. To edit your company’s data, go to " +":menuselection:`Settings --> Users & Companies --> Companies`. Select a " +"country from the list; Do not create a new country." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:385 +msgid "" +"Download the mandatory certificate of conformity delivered by Odoo SA `here " +"`__." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:389 +msgid "" +"To install the module in any system created before December 18th 2017, you " +"should update the modules list. To do so, activate the :ref:`developer mode " +"`. Then go to the *Apps* menu and press *Update Modules " +"List* in the top-menu." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:393 +msgid "" +"In case you run Odoo on-premise, you need to update your installation and " +"restart your server beforehand." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:395 +msgid "" +"If you have installed the initial version of the anti-fraud module (prior to" +" December 18th 2017), you need to update it. The module's name was *France -" +" Accounting - Certified CGI 286 I-3 bis*. After an update of the modules " +"list, search for the updated module in *Apps*, select it and click " +"*Upgrade*. Finally, make sure the following module *l10n_fr_sale_closing* is" +" installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:404 +msgid "Anti-fraud features" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:406 +msgid "The anti-fraud module introduces the following features:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:408 +msgid "" +"**Inalterability**: deactivation of all the ways to cancel or modify key " +"data of POS orders, invoices and journal entries;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:410 +msgid "**Security**: chaining algorithm to verify the inalterability;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:411 +msgid "" +"**Storage**: automatic sales closings with computation of both period and " +"cumulative totals (daily, monthly, annually)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:415 +msgid "Inalterability" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:417 +msgid "" +"All the possible ways to cancel and modify key data of paid POS orders, " +"confirmed invoices and journal entries are deactivated, if the company is " +"located in France or in any DOM-TOM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:423 +msgid "" +"If you run a multi-companies environment, only the documents of such " +"companies are impacted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:426 +msgid "Security" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:428 +msgid "" +"To ensure inalterability, every order or journal entry is encrypted upon " +"validation. This number (or hash) is calculated from the key data of the " +"document as well as from the hash of the precedent documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:433 +msgid "" +"The module introduces an interface to test the data inalterability. If any " +"information is modified on a document after its validation, the test will " +"fail. The algorithm recomputes all the hashes and compares them against the " +"initial ones. In case of failure, the system points out the first corrupted " +"document recorded in the system." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:439 +msgid "" +"Users with *Manager* access rights can launch the inalterability check. For " +"POS orders, go to :menuselection:`Point of Sales --> Reporting --> French " +"Statements`. For invoices or journal entries, go to " +":menuselection:`Invoicing/Accounting --> Reporting --> French Statements`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:446 +msgid "Storage" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:448 +msgid "" +"The system also processes automatic sales closings on a daily, monthly and " +"annual basis. Such closings distinctly compute the sales total of the period" +" as well as the cumulative grand totals from the very first sales entry " +"recorded in the system." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:454 +msgid "" +"Closings can be found in the *French Statements* menu of Point of Sale, " +"Invoicing and Accounting apps." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:459 +msgid "" +"Closings compute the totals for journal entries of sales journals (Journal " +"Type = Sales)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:461 +msgid "" +"For multi-companies environments, such closings are performed by company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:463 +msgid "" +"POS orders are posted as journal entries at the closing of the POS session. " +"Closing a POS session can be done anytime. To prompt users to do it on a " +"daily basis, the module prevents from resuming a session opened more than 24" +" hours ago. Such a session must be closed before selling again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:469 +msgid "" +"A period’s total is computed from all the journal entries posted after the " +"previous closing of the same type, regardless of their posting date. If you " +"record a new sales transaction for a period already closed, it will be " +"counted in the very next closing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:476 +msgid "" +"For test & audit purposes such closings can be manually generated in the " +":ref:`developer mode `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:478 +msgid "" +"Then go to :menuselection:`Settings --> Technical --> Automation --> " +"Scheduled Actions`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:481 +msgid "Responsibilities" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:483 +msgid "" +"Do not uninstall the module! If you do so, the hashes will be reset and none" +" of your past data will be longer guaranteed as being inalterable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:486 +msgid "" +"Users remain responsible for their Odoo instance and must use it with due " +"diligence. It is not permitted to modify the source code which guarantees " +"the inalterability of data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:490 +msgid "" +"Odoo absolves itself of all and any responsibility in case of changes in the" +" module’s functions caused by 3rd party applications not certified by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:494 +msgid "More Information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:496 +msgid "" +"You can find more information about this legislation in the following " +"official documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:500 +msgid "" +"`Frequently Asked Questions " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:502 +msgid "" +"`Official Statement " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:504 +msgid "" +"`Item 88 of Finance Law 2016 " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:3 +msgid "Germany" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:6 +msgid "German Chart of Accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:8 +msgid "" +"The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can " +"choose the one you want by going in :menuselection:`Accounting --> " +"Configuration` then choose the package you want in the Fiscal Localization " +"section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:12 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:17 +msgid "" +"Be careful, you can only change the accounting package as long as you have " +"not created any accounting entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:16 +msgid "" +"When you create a new Odoo Online database, the SKR03 is installed by " +"default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:19 +msgid "German Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:21 +msgid "" +"Here is the list of German-specific reports available on Odoo Enterprise:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:25 +msgid "Tax Report (Umsatzsteuervoranmeldung)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:26 +msgid "Partner VAT Intra" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:29 +msgid "Export from Odoo to Datev" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:31 +msgid "" +"It is possible to export your accounting entries from Odoo to Datev. To be " +"able to use this feature, the german accounting localization needs to be " +"installed on your Odoo Enterprise database. Then you can go in " +":menuselection:`Accounting --> Reporting --> General Ledger` then click on " +"the **Export Datev (csv)** button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:39 +msgid "Point of Sale in Germany: Technical Security System" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:41 +msgid "" +"The **Kassensicherungsverordnung** (The Act on Protection against " +"Manipulation of Digital Records) requires that electronic record-keeping " +"systems - including the :doc:`point of sale " +"` systems - must be equipped with a " +"**Technical Security System** (also called **TSS** or **TSE**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:46 +msgid "" +"Odoo offers a service that is compliant with the help of `fiskaly " +"`_, a *cloud-based solution*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:50 +msgid "" +"Since this solution is cloud-based, a working internet connection is " +"required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:53 +msgid "" +"The only VAT rates allowed are given by fiskaly. You can check these rates " +"by consulting: `fiskaly DSFinV-K API: VAT Definition " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:63 +msgid "" +"If your database was created before June 2021, :ref:`upgrade " +"` your **Point of Sale** app (`point_of_sale`) and the " +"**Restaurant** module (`pos_restaurant`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:65 +msgid "" +":ref:`Install ` the **Germany - Certification for Point of " +"Sale** (`l10n_de_pos_cert`) and **Germany - Certification for Point of Sale " +"of type restaurant** (`l10n_de_pos_res_cert`) modules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:70 +msgid "" +"If these modules are not listed, :ref:`update the app list " +"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Upgrading Odoo Point of Sale from the Apps dashboard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:77 +msgid "Register your company at the financial authority" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:79 +msgid "" +"To register your company, go to :menuselection:`Settings --> General " +"Settings --> Companies --> Update Info`, fill out the following fields and " +"*Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:82 +msgid "**Company name**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:83 +msgid "Valid **address**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:84 +msgid "**VAT** number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:85 +msgid "" +"**St.-Nr** (Steuernummer): this number is assigned by the tax office to " +"every taxable natural or legal person. (e.g., `2893081508152`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:87 +msgid "" +"**W-IdNr** (Wirtschafts-Identifikationsnummer): this number is used as a " +"permanent identification number for economically active persons." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:90 +msgid "" +"You can then **register your company through fiskaly** by opening the " +"*fiskaly* tab and clicking on the *fiskaly Registration* button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Button to register a company through fiskaly in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:98 +msgid "" +"If you do not see the *fiskaly Registration* button, make sure that you " +"*saved* your company details and are not in *editing mode* anymore." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:101 +msgid "Once the registration has been finalized, new fields appear:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:103 +msgid "" +"**fiskaly organization ID** refers to the ID of your company at the fiskaly " +"side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:104 +msgid "" +"**fiskaly API key** and **secret** are the credentials the system uses to " +"access the services offered by fiskaly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "fiskaly keys as displayed on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:112 +msgid "" +"It is possible to request new credentials if there is any issue with the " +"current ones." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:115 +msgid "Create and link a Technical Security System to your PoS" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Create TSS option from a point of sale" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:121 +msgid "" +"To use your point of sale in Germany, you first have to create a :abbr:`TSS " +"(Technical Security System)` for it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:124 +msgid "" +"To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of" +" Sale`, open the point of sale you want to edit, then check the box next to " +"**Create TSS** and *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Example of TSS ID and Client ID from fiskaly in Odoo Point of Sale" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:131 +msgid "" +"Once the creation of the TSS is successful, you can find your **TSS ID** and" +" **Client ID** under the *fiskaly API* section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:134 +msgid "**TSS ID** refers to the ID of your TSS at fiskaly's side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:135 +msgid "**Client ID** refers to your PoS but at fiskaly's side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:138 +msgid "DSFinV-K" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Menu to export DSFinV-K" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:144 +msgid "" +"Whenever you close a PoS session, the orders' details are sent to the " +":abbr:`DSFinV-K (Digitale Schnittstelle der Finanzverwaltung für " +"Kassensysteme)` service of fiskaly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:147 +msgid "" +"In case of an audit, you can export the data sent to DSFinV-K by going to " +":menuselection:`Point of Sale --> Orders --> DSFinV-k exports`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:150 +msgid "These fields are mandatory:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:152 +msgid "**Name**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:153 +msgid "" +"**Start Datetime** (export data with dates larger than or equal to the given" +" start date)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:154 +msgid "" +"**End Datetime** (export data with dates smaller than or equal to the given " +"end date)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:156 +msgid "" +"Leave the **Point of Sale** field blank if you want to export the data of " +"all your points of sale. Specify a Point of Sale if you want to export this " +"specific PoS' data only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:159 +msgid "" +"The creation of a DSFinV-K export triggers on export at fiskaly's side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Pending DSFinV-K export on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:165 +msgid "" +"As you can see, the **State** is *Pending*. This means that the export has " +"been successfully triggered and is being processed. You have to click on " +"*Refresh State* to check if it is ready." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:171 +msgid "German Tax Accounting Standards: Odoo's guide to GoBD Compliance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:173 +msgid "" +"**GoBD** stands for `Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung" +" von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum" +" Datenzugriff " +"`_." +" In short, it is a **guideline for the proper management and storage of " +"books, records, and documents in electronic form, as well as for data " +"access**, that is relevant for the German tax authority, tax declaration, " +"and balance sheet." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:180 +msgid "" +"These principles have been written and published by the Federal Ministry of " +"Finance (BMF) in November 2014. Since January 2015, **they have become the " +"norm** and replace previously accepted practices linked to computer-based " +"accounting. Several changes have been made by the BMF in 2019 and January " +"2020 to specify some of the content and due to the development of digital " +"solutions (cloud hosting, paperless companies, etc.)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:187 +msgid "Odoo gives you **the means to be compliant with GoBD**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:190 +msgid "" +"What do you need to know about GoBD when relying on accounting software?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:193 +msgid "" +"If you can, the best way to understand GoBD is to Read the `Official GoBD " +"text " +"`_." +" It is a bit long but quite readable for non-experts. But in short, here is " +"what to expect:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:197 +msgid "" +"The **GoBD is binding for companies that have to present accounts, which " +"includes SMEs, freelancers, and entrepreneurs, to the financial " +"authorities**. As such, **the taxpayer himself is the sole responsible** for" +" the complete and exhaustive keeping of fiscal-relevant data (above-" +"mentioned financial and related data)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:202 +msgid "" +"Apart from software requirements, the user is required to ensure Internal " +"control systems (*in accordance with sec. 146 of the Fiscal Code*):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:205 +msgid "Access rights control;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:206 +msgid "Segregation of Duties, Functional separating;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:207 +msgid "Entry controls (error notifications, plausibility checks);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:208 +msgid "Reconciliation checks at data entry;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:209 +msgid "Processing controls;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:210 +msgid "" +"Measures to prevent intentional or unintentional manipulation of software, " +"data, or documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:212 +msgid "" +"The user must distribute tasks within its organization to the relevant " +"positions (*control*) and verify that the tasks are properly and completely " +"performed (*supervision*). The result of these controls must be recorded " +"(*documentation*), and should errors be found during these controls, " +"appropriate measures to correct the situation should be put into place " +"(*prevention*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:218 +msgid "What about data security?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:220 +msgid "" +"**The taxpayer must secure the system against any data loss due to " +"deletion, removal, or theft of any data**. If the entries are not " +"sufficiently secured, the bookkeeping will be regarded as not in accordance " +"with the GoBD guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:224 +msgid "" +"Once bookings have been finally posted, they can no longer be changed or " +"deleted via the application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:227 +msgid "" +"If Odoo is used in the cloud, regular backups are part of the Odoo Online " +"service. In addition, regular backups can be downloaded and backed up on " +"external systems." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:231 +msgid "" +"`Odoo Cloud Hosting - Service Level Agreement `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:233 +msgid "" +"If the server is operated locally, it is the responsibility of the user to " +"create the necessary backup infrastructure." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:237 +msgid "" +"In some cases, data has to be kept for ten years or more, so always have " +"backups saved. It is even more important if you decide to change software " +"provider." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:241 +msgid "Responsibility of the software editor" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:243 +msgid "" +"Considering GoBD only applies between the taxpayer and the financial " +"authority, **the software editor can by no means be held responsible for the" +" accurate and compliant documentation of financial transactional data of " +"their users**. It can merely provide the necessary tools for the user to " +"respect the software related guidelines described in the GoBD." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:249 +msgid "How can Odoo help you achieve Compliance?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:251 +msgid "" +"The key words, when it comes to GoBD, are: **traceable, verifiable, true, " +"clear, and continuous**. In short, you need to have audit-proof archiving in" +" place and Odoo provides you with the means to achieve all of these " +"objectives:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Traceability and verifiability**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"Each record in Odoo is stamped with the creator of the document, the " +"creation date, the modification date, and who modified it. In addition, " +"relevant fields are tracked thus it can be seen which value was changed by " +"whom in the chatter of the relevant object." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Completeness**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"All financial data must be recorded in the system, and there can be no gaps." +" Odoo ensures that there is no gap in the numbering of the financial " +"transactions. It is the responsibility of the user to encode all financial " +"data in the system. As most financial data in Odoo is generated " +"automatically, it remains the responsibility of the user to encode all " +"vendor bills and miscellaneous operations completely." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Accuracy**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"Odoo ensures with the correct configuration that the correct accounts are " +"used. In addition, the control mechanisms between purchase orders and sales " +"orders and their respective invoices reflect the business reality. It is the" +" responsibility of the user to scan and attach the paper-based vendor bill" +" to the respective record in Odoo. *Odoo Document helps you automate this " +"task*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Timely booking and record-keeping**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"As most financial data in Odoo is generated by the transactional objects " +"(for example, the invoice is booked at confirmation), Odoo ensures out-of-" +"the-box timely record-keeping. It is the responsibility of the user to " +"encode all incoming vendor bills in a timely manner, as well as the " +"miscellaneous operations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Order**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"Financial data stored in Odoo is per definition ordered and can be reordered" +" according to most fields present in the model. A specific ordering is not " +"enforced by the GoBD, but the system must ensure that a given financial " +"transaction can be quickly found by a third-party expert. Odoo ensures this " +"out-of-the-box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Inalterability**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"With the German Odoo localization, Odoo is in standard configured in such a " +"way that the inalterability clause can be adhered to without any further " +"customization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:286 +msgid "Do you need a GoBD-Export?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:288 +msgid "" +"In the case of fiscal control, the fiscal authority can request three levels" +" of access to the accounting system (Z1, Z2, Z3). These levels vary from " +"direct access to the interface to the handover of the financial data on a " +"storage device." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:292 +msgid "" +"In case of a handover of the financial data on a storage device, the format " +"is **not** enforced by the GoBD. It can be, for example, in XLS, CSV, XML, " +"Lotus 123, SAP-format, AS/400-format, or else. Odoo supports the CSV and " +"XLS-export of financial data out-of-the-box. The GoBD **recommends** the " +"export in a specific XML-based GoBD-format (see \"Ergänzende Informationen " +"zur Datenntträgerüberlassung\" §3) but it is not binding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:299 +msgid "What is the role and meaning of the compliance certification?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:301 +msgid "" +"The GoBD clearly states that due to the nature of a state of the art " +"accounting software, their configuration possibilities, changing nature, and" +" various forms of use, **no legally binding certification can be given**, " +"nor can the software be made liable towards a public authority. Third-party " +"certificates can indeed have **an informative value** for customers to make " +"software buying decisions but are by no means legally binding or of any " +"other legal value (A. 12, § 181)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:307 +msgid "" +"A GoBD certificate states nothing more than that if you use the software " +"according to its guidelines, the software will not refrain you from " +"respecting the GoBD. These certifications are very expensive in terms of " +"time and cost, and their value is very relative. Thus we focus our efforts " +"on ensuring GoBD compliance rather than pay for a marketing tool which does " +"not, however, offer our customer any legal certainty." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:314 +msgid "" +"The BMF actually states the following in the `Official GoBD text " +"`_:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:317 +msgid "" +"180. Positive attestations on the correctness of the bookkeeping - and thus " +"on the correctness of IT-based bookkeeping systems - are not issued either " +"in the context of a tax field audit or in the context of binding " +"information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:320 +msgid "" +"181. \"Certificates\" or \"attestations\" from third parties can serve as a " +"decision criterion for the company when selecting a software product, but " +"develop from the in margin no. 179 is not binding on the tax authorities." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:325 +msgid "" +"The previous content was `automatically translated from German with Google " +"Translate " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:330 +msgid "What happens if you are not compliant?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:332 +msgid "" +"In the event of an infringement, you can expect a fine but also a court " +"order demanding the implementation of specific measures." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:3 +msgid "India" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Indian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:19 +msgid ":guilabel:`Indian - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:20 +msgid "`l10n_in`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:22 +msgid ":guilabel:`Indian E-invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:23 +msgid "`l10n_in_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:24 +msgid ":ref:`Indian e-invoicing integration `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:25 +msgid ":guilabel:`Indian E-waybill`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:26 +msgid "`l10n_in_edi_ewaybill`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:27 +msgid ":ref:`Indian E-way bill integration `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:28 +msgid ":guilabel:`Indian - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:29 +msgid "`l10n_in_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:30 +msgid "Indian tax reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:31 +msgid ":guilabel:`Indian - Purchase Report(GST)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:32 +msgid "`l10n_in_purchase`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:33 +msgid "Indian GST Purchase report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:34 +msgid ":guilabel:`Indian - Sale Report(GST)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:35 +msgid "`l10n_in_sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:36 +msgid "Indian GST Sale report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:37 +msgid ":guilabel:`Indian - Stock Report(GST)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:38 +msgid "`l10n_in_stock`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:39 +msgid "Indian GST Stock report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Indian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:47 +msgid "e-Invoice system" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:49 +msgid "" +"Odoo is compliant with the **Indian Goods and Services Tax (GST) e-Invoice " +"system** requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:52 +msgid "" +"Indian e-invoicing is available from Odoo 15.0. If needed, :doc:`upgrade " +"` your database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:61 +msgid "NIC e-Invoice registration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:63 +msgid "" +"You must register on the :abbr:`NIC (National Informatics Centre)` e-Invoice" +" portal to get your **API credentials**. You need these credentials to " +":ref:`configure your Odoo Accounting app `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:67 +msgid "" +"Log in to the `NIC e-Invoice portal `_ by " +"clicking :guilabel:`Login` and entering your :guilabel:`Username` and " +":guilabel:`Password`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:71 +msgid "" +"If you are already registered on the NIC portal, you can use the same login " +"credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Register Odoo ERP system on e-invoice web portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:76 +msgid "" +"From the dashboard, go to :menuselection:`API Registration --> User " +"Credentials --> Create API User`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:78 +msgid "" +"After that, you should receive an :abbr:`OTP (one-time password)` code on " +"your registered mobile number. Enter the OTP code and click " +":guilabel:`Verify OTP`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:80 +msgid "" +"Select :guilabel:`Through GSP` for the API interface, set :guilabel:`Tera " +"Software Limited` as GSP, and type in a :guilabel:`Username` and " +":guilabel:`Password` for your API. Once it is done, click " +":guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Submit API specific Username and Password" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:90 +#: ../../content/applications/finance/fiscal_localizations/india.rst:233 +msgid "Configuration in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:92 +msgid "" +"To enable the e-Invoice service in Odoo, go to :menuselection:`Accounting " +"--> Configuration --> Settings --> Indian Electronic Invoicing`, and enter " +"the :guilabel:`Username` and :guilabel:`Password` previously set for the " +"API." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Setup e-invoice service" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:104 +msgid "" +"To automatically send e-Invoices to the NIC e-Invoice portal, you must first" +" configure your *sales* journal by going to :menuselection:`Accounting --> " +"Configuration --> Journals`, opening your *sales* journal, and in the " +":guilabel:`Advanced Settings` tab, under :guilabel:`Electronic Data " +"Interchange`, enable :guilabel:`E-Invoice (IN)` and save." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:119 +msgid "" +"Once an invoice is validated, a confirmation message is displayed at the " +"top. Odoo automatically uploads the JSON-signed file of validated invoices " +"to the NIC e-Invoice portal after some time. If you want to process the " +"invoice immediately, click :guilabel:`Process now`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Indian e-invoicing confirmation message" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:127 +#: ../../content/applications/finance/fiscal_localizations/india.rst:271 +msgid "" +"You can find the JSON-signed file in the attached files in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:128 +msgid "" +"You can check the document's :abbr:`EDI (electronic data interchange)` " +"status under the :guilabel:`EDI Document` tab or the :guilabel:`Electronic " +"invoicing` field of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:134 +#: ../../content/applications/finance/fiscal_localizations/india.rst:276 +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Invoice PDF report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:136 +msgid "" +"Once an invoice is validated and submitted, the invoice PDF report can be " +"printed. The report includes the :abbr:`IRN (Invoice Reference Number)`, " +":guilabel:`Ack. No` (acknowledgment number) and :guilabel:`Ack. Date` " +"(acknowledgment date), and QR code. These certify that the invoice is a " +"valid fiscal document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "IRN and QR code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:147 +msgid "e-Invoice cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:149 +msgid "" +"If you want to cancel an e-Invoice, go to the :guilabel:`Other info` tab of " +"the invoice and fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel" +" remarks` fields. Then, click :guilabel:`Request EDI cancellation`. The " +"status of the :guilabel:`Electronic invoicing` field changes to " +":guilabel:`To Cancel`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:155 +msgid "" +"Doing so cancels both the :ref:`e-Invoice ` and the " +":ref:`E-Way bill `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "cancel reason and remarks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:162 +msgid "" +"If you want to abort the cancellation before processing the invoice, then " +"click :guilabel:`Call Off EDI Cancellation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:164 +msgid "" +"Once you request to cancel the e-Invoice, Odoo automatically submits the " +"JSON-signed file to the NIC e-Invoice portal. You can click " +":guilabel:`Process now` if you want to process the invoice immediately." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:171 +msgid "GST e-Invoice verification" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:173 +msgid "" +"After submitting an e-Invoice, you can verify if the invoice is signed from " +"the GST e-Invoice system website itself." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:176 +msgid "" +"Download the JSON file from the attached files. It can be found in the " +"chatter of the related invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:178 +msgid "" +"Open the `NIC e-Invoice portal `_ and go to " +":menuselection:`Search --> Verify Signed Invoice`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:180 +msgid "Select the JSON file and submit it;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "select the JSON file for verify invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:185 +msgid "If the file is signed, a confirmation message is displayed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "verified e-invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:193 +msgid "E-Way bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:198 +msgid "" +"Odoo is compliant with the **Indian Goods and Services Tax (GST) E-waybill " +"system** requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:201 +msgid "" +"Indian E-waybill is available from Odoo 15.0. If needed, :doc:`upgrade " +"` your database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:207 +msgid "API registration on NIC E-Way bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:209 +msgid "" +"You must register on the :abbr:`NIC (National Informatics Centre)` E-Way " +"bill portal to create your **API credentials**. You need these credentials " +"to :ref:`configure your Odoo Accounting app `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:213 +msgid "" +"Log in to the `NIC E-Way bill portal `_ by " +"clicking :guilabel:`Login` and entering your :guilabel:`Username` and " +":guilabel:`Password`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:215 +msgid "From your dashboard, go to :menuselection:`Registration --> For GSP`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:216 +msgid "" +"Click :guilabel:`Send OTP`. Once you have received the code on your " +"registered mobile number, enter it and click :guilabel:`Verify OTP`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:218 +msgid "" +"Check if :guilabel:`Tera Software Limited` is already on the registered " +"GSP/ERP list. If so, use the username and password used to log in to the NIC" +" portal. Otherwise, follow the next steps;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "E-Way bill list of registered GSP/ERP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:224 +msgid "" +"Select :guilabel:`Add/New`, select :guilabel:`Tera Software Limited` as your" +" GSP Name, create a :guilabel:`Username` and a :guilabel:`Password` for your" +" API, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Submit GSP API registration details" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:235 +msgid "" +"To set up the E-Way bill service, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Indian Electronic WayBill --> Setup E-Way " +"bill`, and enter your :guilabel:`Username` and :guilabel:`Password`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "E-way bill setup odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:250 +msgid "Send an E-Way bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:252 +msgid "" +"You can manually send an E-Way bill by clicking :guilabel:`Send E-Way bill`." +" To send the E-Way bill automatically when an invoice or a bill is " +"confirmed, enable :guilabel:`E-Way bill (IN)` in your :ref:`Sales or " +"Purchase journal `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Send E-waybill button on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:264 +msgid "" +"Once an invoice has been issued and sent via :guilabel:`Send E-Way bill`, a " +"confirmation message is displayed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Indian e-Way bill confirmation message" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:272 +msgid "" +"Odoo automatically uploads the JSON-signed file to the government portal " +"after some time. Click :guilabel:`Process now` if you want to process the " +"invoice immediately." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:278 +msgid "" +"You can print the invoice PDF report once you have submitted the E-Way bill." +" The report includes the **E-Way bill number** and the **E-Way bill validity" +" date**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "E-way bill acknowledgment number and date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:287 +msgid "E-Way bill cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:289 +msgid "" +"If you want to cancel an E-Way bill, go to the :guilabel:`E-Way bill` tab of" +" the related invoice and fill out the :guilabel:`Cancel reason` and " +":guilabel:`Cancel remarks` fields. Then, click :guilabel:`Request EDI " +"Cancellation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:294 +msgid "" +"Doing so cancels both the :ref:`e-Invoice ` (if " +"applicable) and the :ref:`E-Way bill `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Cancel reason and remarks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:301 +msgid "" +"If you want to abort the cancellation before processing the invoice, click " +":guilabel:`Call Off EDI Cancellation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:303 +msgid "" +"Once you request to cancel the E-Way bill, Odoo automatically submits the " +"JSON-signed file to the government portal. You can click :guilabel:`Process " +"Now` if you want to process the invoice immediately." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:3 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:8 +msgid "E-Faktur Module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:10 +msgid "" +"The **E-Faktur Module** is installed by default with the Indonesian " +"localization module. It allows one to generate a CSV file for one tax " +"invoice or for a batch of tax invoices to upload to the **Tax Office " +"e-Faktur** application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:17 +msgid "NPWP/NIK settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "**Your Company**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "" +"This information is used in the FAPR line in the effect file format. You " +"need to set a VAT number on the related partner of your Odoo company. If you" +" don't, it won't be possible to create an e-Faktur from an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "**Your Clients**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "" +"You need to set the checkbox *ID PKP* to generate e-fakturs for a customer. " +"You can use the VAT field on the customer's contact to set the NPWP needed " +"to generate the e-Faktur file. If your customer does not have an NPWP, just " +"enter the NIK in the same VAT field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:39 +msgid "Generate Tax Invoice Serial Number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:41 +msgid "" +"Go to :menuselection:`Accounting --> Customers --> e-Faktur`. In order to be" +" able to export customer invoices as e-Faktur for the Indonesian government," +" you need to put here the ranges of numbers you were assigned by the " +"government. When you validate an invoice, a number will be assigned based on" +" these ranges. Afterwards, you can filter the invoices still to export in " +"the invoices list and click on *Action*, then on *Download e-Faktur*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:46 +msgid "" +"After receiving new serial numbers from the Indonesian Revenue Department, " +"you can create a set of tax invoice serial numbers group through this list " +"view. You only have to specify the Min and Max of each serial numbers' group" +" and Odoo will format the number automatically to a 13-digits number, as " +"requested by the Indonesia Tax Revenue Department." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:50 +msgid "" +"There is a counter to inform you how many unused numbers are left in that " +"group." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:58 +msgid "Generate e-faktur csv for a single invoice or a batch invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:60 +msgid "" +"Create an invoice from :menuselection:`Accounting --> Customers --> " +"Invoices`. If the invoice customer's country is Indonesia and the customer " +"is set as *ID PKP*, Odoo will allow you to create an e-Faktur." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:63 +msgid "" +"Set a Kode Transaksi for the e-Faktur. There are constraints related to the " +"Kode transaksi and the type of VAT applied to invoice lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:69 +msgid "" +"Odoo will automatically pick the next available serial number from the " +"e-Faktur number table (see the :ref:`section above " +"`) and generate the e-faktur number " +"as a concatenation of Kode Transaksi and serial number. You can see this " +"from the invoice form view under the page *Extra Info* in the box " +"*Electronic Tax*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:77 +msgid "" +"Once the invoice is posted, you can generate and download the e-Faktur from " +"the *Action* menu item *Download e-faktur*. The checkbox *CSV created* will " +"be set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:83 +msgid "" +"You can select multiple invoices in list view and generate a batch e-Faktur " +".csv." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:88 +msgid "Kode Transaksi FP (Transaction Code)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:90 +msgid "" +"The following codes are available when generating an e-Faktur. - 01 Kepada " +"Pihak yang Bukan Pemungut PPN (Customer Biasa) - 02 Kepada Pemungut " +"Bendaharawan (Dinas Kepemerintahan) - 03 Kepada Pemungut Selain Bendaharawan" +" (BUMN) - 04 DPP Nilai Lain (PPN 1%) - 06 Penyerahan Lainnya (Turis Asing) -" +" 07 Penyerahan yang PPN-nya Tidak Dipungut (Kawasan Ekonomi Khusus/ Batam) -" +" 08 Penyerahan yang PPN-nya Dibebaskan (Impor Barang Tertentu) - 09 " +"Penyerahan Aktiva (Pasal 16D UU PPN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:103 +msgid "" +"Correct an invoice that has been posted and downloaded: Replace Invoice " +"feature" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:105 +msgid "" +"Cancel the original wrong invoice in Odoo. For instance, we will change the " +"Kode Transakski from 01 to 03 for the INV/2020/0001." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:107 +msgid "" +"Create a new invoice and set the canceled invoice in the *Replace Invoice* " +"field. In this field, we can only select invoices in *Cancel* state from the" +" same customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:109 +msgid "" +"As you validate, Odoo will automatically use the same e-Faktur serial number" +" as the canceled and replaced invoice replacing the third digit of the " +"original serial number with *1* (as requested to upload a replacement " +"invoice in the e-Faktur app)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:120 +msgid "" +"Correct an invoice that has been posted but not downloaded yet: Reset " +"e-Faktur" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:122 +msgid "Reset the invoice to draft and cancel it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:123 +msgid "Click on the button *Reset e-Faktur* on the invoice form view." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:124 +msgid "" +"The serial number will be unassigned, and we will be able to reset the " +"invoice to draft, edit it and re-assign a new serial number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:3 +msgid "Italy" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Italian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:20 +msgid "Italy - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:21 +msgid "`l10n_it`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:23 +msgid "Italy - E-invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:24 +msgid "`l10n_it_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:25 +msgid "e-invoice implementation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:26 +msgid "Italy - E-invoicing (SdiCoop)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:27 +msgid "`l10n_it_edi_sdicoop`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:28 +msgid "Web service e-invoice implementation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:29 +msgid "Italy - Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:30 +msgid "`l10n_it_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:31 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:22 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:25 +msgid "Country-specific reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:32 +msgid "Italy - Stock DDT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:33 +msgid "`l10n_it_stock_ddt`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:34 +msgid "Transport documents - Documento di Trasporto (DDT)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:37 +msgid "" +"Once the `l10_it_edi_sdicoop` module is installed, sending invoices via PEC " +"mails is no longer possible." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Italian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:45 +msgid "Company information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:47 +msgid "" +"Configuring the company's information ensures your Accounting database is " +"properly set up. To add information, go to :menuselection:`Settings --> " +"General Settings`, and in the :guilabel:`Companies` section, click " +":guilabel:`Update info`. From here, fill out the fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:51 +msgid ":guilabel:`Address`: the address of the company;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:52 +msgid ":guilabel:`VAT`: VAT of the company;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:53 +msgid ":guilabel:`Codice Fiscale`: the fiscal code of the company;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:54 +msgid ":guilabel:`Tax System`: the tax system under which the company falls;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:55 +msgid "" +":guilabel:`PEC address email`: the certified email address of the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Company information to provide" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:62 +msgid "PEC mail" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:64 +msgid "" +"The **PEC email** is a specific type of **certified** email providing a " +"legal equivalent to the traditional registered mail. The **PEC email** of " +"the main company must be the same as the one registered by the **Agenzia " +"delle Entrate** authorities." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:69 +msgid "E-invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:71 +msgid "" +"The :abbr:`SdI (Sistema di Interscambio)` is the electronic invoicing system" +" used in Italy. It enables to send and receive electronic invoices to and " +"from customers. The documents must be in XML format and formally validated " +"by the system before being delivered." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:75 +msgid "" +"To be able to receive invoices and notifications, the :abbr:`SdI (Sistema di" +" Interscambio)` service must be notified that the user's files are to be " +"sent to **Odoo** and processed on their behalf. To so, you must set up " +"Odoo's :guilabel:`Codice Destinatario` on the **Agenzia Delle Entrate** " +"portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:80 +msgid "" +"Go to https://ivaservizi.agenziaentrate.gov.it/portale/ and authenticate;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:81 +msgid "Go to section :menuselection:`Fatture e Corrispettivi`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:82 +msgid "" +"Set the user as Legal Party for the VAT number you wish to configure the " +"electronic address;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:83 +msgid "" +"In :menuselection:`Servizi Disponibili --> Fatturazione Elettronica --> " +"Registrazione dell’indirizzo telematico dove ricevere tutte le fatture " +"elettroniche`, insert Odoo's :guilabel:`Codice Destinatario` `K95IV18`, and " +"confirm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:88 +msgid "Electronic Data Interchange (EDI)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:90 +msgid "" +"Odoo uses the **FatturaPA** :abbr:`EDI (Electronic Data Interchange)` format" +" for the Italian localization and is enabled on the default journals when " +"installed. When the **file processing authorization** has been set, all " +"**invoices** and **bills** are automatically sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:95 +msgid "" +"You can :ref:`enable electronic invoicing for other sales and purchase " +"journals ` than the default ones." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:98 +msgid "" +"You can check the current status of an invoice by the :guilabel:`Electronic " +"invoicing` field. The XML file can be found in the **chatter** of the " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Electronic invoicing status (waiting for confirmation)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:106 +msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:109 +msgid "File processing authorization (Odoo)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:111 +msgid "" +"Since the files are transmitted through Odoo's server before being sent to " +"the :abbr:`SdI (Sistema di Interscambio)` or received by your database, you " +"need to authorize Odoo to process your files from your database. To do so, " +"go to :menuselection:`Accounting --> Configuration --> Settings --> " +"Electronic Document Invoicing`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:116 +msgid "There are **three** modes available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:120 +msgid ":guilabel:`Demo`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:119 +msgid "" +"This mode simulates an environment in which invoices are sent to the " +"government. In this mode, invoices need to be *manually* downloaded as XML " +"files and uploaded to the **Agenzia delle Entrate**'s website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:124 +msgid ":guilabel:`Test (experimental)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:123 +msgid "" +"This mode sends invoices to a non-production (i.e., test) service made " +"available by the **Agenzia delle Entrate**. Saving this change directs all " +"companies on the database to use this configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:127 +msgid ":guilabel:`Official`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:127 +msgid "" +"This is a production mode that sends your invoices directly to the **Agenzia" +" delle Entrate**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:129 +msgid "" +"Once a mode is selected, you need to accept the **terms and conditions** by " +"ticking :guilabel:`Allow Odoo to process invoices`, and then " +":guilabel:`Save`. You can now record your transactions in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:134 +msgid "" +"Selecting either :guilabel:`Test (experimental)` or :guilabel:`Official` is " +"**irreversible**. Once in :guilabel:`Official` mode, it is not possible to " +"select :guilabel:`Test (experimental)` or :guilabel:`Demo`, and same for " +":guilabel:`Test (experimental)`. We recommend creating a separate database " +"for testing purposes only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:140 +msgid "" +"When in :guilabel:`Test (Experimental)` mode, all invoices sent *must* have " +"a partner using one of the following fake :guilabel:`Codice Destinatario` " +"given by the **Agenzia Delle Entrate**: `0803HR0` - `N8MIMM9` - `X9XX79Z`. " +"Any real production :guilabel:`Codice Destinario` of your customers will not" +" be recognized as valid by the test service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Italy's electronic document invoicing options" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:150 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Taxes configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:152 +msgid "" +"Many of the e-invoicing features are implemented using Odoo's tax system. As" +" such, it is very important that taxes are properly configured in order to " +"generate invoices correctly and handle other billing use cases. For example," +" specific configurations are required for the **reverse charge** type of " +"taxes. In case of a **reverse charge** tax, the seller does *not* charge the" +" customer for the VAT but, instead, the customer pays the VAT *themselves* " +"to their government. There are **two** main types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:159 +msgid ":ref:`external reverse charge `;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:160 +msgid ":ref:`internal reverse charge `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:165 +msgid "External reverse charge" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:168 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:399 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:212 +msgid "Invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:170 +msgid "" +"To make an export invoice, make sure that the invoice lines all use a tax " +"configured for **reverse charge**. The **Italian** localization contains an " +"**example** of a reverse charge tax for export in the EU to be used as " +"reference (`0% EU`, invoice label `00eu`), which can be found under " +":menuselection:`Accounting --> Configuration --> Taxes`. Exports are exempt " +"from VAT, and therefore **reverse charge** taxes require the :guilabel:`Has " +"exoneration of tax (Italy)` option ticked, with both the " +":guilabel:`Exoneration` kind and :guilabel:`Law Reference` filled in." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "External reverse charge settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:182 +msgid "" +"If you need to use a different kind of :guilabel:`Exoneration`, click " +":menuselection:`Action --> Duplicate` within the tax menu to create a copy " +"of an existing similar tax. Then, select another :guilabel:`Exoneration`, " +"and :guilabel:`Save`. Repeat this process as many times as you need " +"different kind of :guilabel:`Exoneration` taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:188 +msgid "" +"**Rename** your taxes in the :guilabel:`Name` field according to their " +":guilabel:`Exoneration` to differentiate them easily." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:191 +msgid "" +"On your invoice, select the corresponding tax you need in the " +":guilabel:`Taxes` field. You can find the following **additional info** by " +"opening the **XML** file of the issued invoice:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:194 +msgid "" +":guilabel:`SdI address (Codice Destinatario)`: must be filled for both " +"**EU** or **non-EU**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:195 +msgid "" +":guilabel:`Country Id`: must contain the country of the foreign seller in " +"the two-letter ISO (Alpha-2) code (ex., `IT` for 'Italy');" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:197 +msgid ":guilabel:`CAP`: must be filled with `00000`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:198 +msgid "" +":guilabel:`Partita Iva` (**VAT number**): must contain the **VAT** number " +"for **EU businesses** and `OO99999999999` (double 'O' **letter**, not " +"'zero') for **non-EU businesses**. In case of private customers without " +"**VAT** number, use `0000000`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:201 +msgid "" +":guilabel:`Fiscal Code`: for foreign entities without an actual **Codice " +"Fiscale**, any recognizable identifier is valid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:205 +msgid "Odoo does not support sending user-modified XML files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:207 +msgid "" +"For **invoices**, multiple configurations are technically identified by a " +":guilabel:`Tipo Documento` code:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:210 +msgid "`TD02` - Down payments;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:211 +msgid "`TDO7` - Simplified invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:212 +msgid "`TD08` - Simplified credit note;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:213 +msgid "`TD09` - Simplified debit note;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:214 +msgid "`TD24` - Deferred invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:218 +msgid "`TD02`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:220 +msgid "Down payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:222 +msgid "" +"**Down payment** invoices are imported/exported with a different " +":guilabel:`Tipo Documento` code `TDO2` than regular invoices. Upon import of" +" the invoice, it creates a regular vendor bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:226 +msgid "Odoo exports moves as `TD02` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:228 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:286 +msgid "Is an invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:229 +msgid "" +"All invoice lines are related to **sales order lines** that have the flag " +"`is_downpayment` set as `True`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:232 +msgid "`TD07`, `TD08`, and `TD09`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:234 +msgid "Simplified invoices, and credit/debit notes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:236 +msgid "" +"Simplified invoices and credit notes can be used to certify **domestic " +"transactions** under **400 EUR** (VAT included). Its status is the same as a" +" regular invoice, but with fewer information requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:240 +msgid "For a **simplified** invoice to be established, it must include:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:242 +msgid "" +":guilabel:`Customer Invoice` reference: **unique** numbering sequence with " +"**no gaps**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:243 +msgid ":guilabel:`Invoice Date`: issue **date** of the invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:244 +msgid "" +":guilabel:`Company Info`: the **seller**'s full credentials (VAT/TIN number," +" name, full address) under :menuselection:`General Settings --> Companies " +"(section)`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:246 +msgid "" +":guilabel:`VAT`: the **buyer**'s VAT/TIN number (on their profile card);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:247 +msgid ":guilabel:`Total`: the total **amount** (VAT included) of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:249 +msgid "" +"In the :abbr:`EDI (Electronic Data Interchange)`, Odoo exports invoices as " +"simplified if:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:251 +msgid "It is a **domestic** transaction (i.e., the partner is from Italy);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:252 +msgid "The buyer's data is **insufficient** for a regular invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:253 +msgid "" +"The **required fields** for a regular invoice (address, ZIP code, city, " +"country) are provided;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:255 +msgid "The total amount VAT included is **less** than **400 EUR**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:258 +msgid "" +"The 400 EUR threshold was defined in `the decree of the 10th of May 2019 in " +"the Gazzetta Ufficiale " +"`_. We " +"advise you to check the current official value." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:262 +msgid "`TD24`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:264 +msgid "Deferred invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:266 +msgid "" +"The **deferred invoice** is an invoice that is **issued at a later time** " +"than the sale of goods or the provision of services. A **deferred invoice** " +"has to be issued at the latest within the **15th day** of the month " +"following the delivery covered by the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:270 +msgid "" +"It usually is a **summary invoice** containing a list of multiple sales of " +"goods or services, carried out in the month. The business is allowed to " +"**group** the sales into **one invoice**, generally issued at the **end of " +"the month** for accounting purposes. Deferred invoices are default for " +"**wholesaler** having recurrent clients." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:275 +msgid "" +"If the goods are transported by a **carrier**, every delivery has an " +"associated **Documento di Transporto (DDT)**, or **Transport Document**. The" +" deferred invoice **must** indicate the details of all the **DDTs** " +"information for better tracing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:280 +msgid "" +"E-invoicing of deferred invoices requires the `l10n_it_stock_ddt` " +":ref:`module `. In this case, a dedicated :guilabel:`Tipo " +"Documento` `TD24` is used in the e-invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:284 +msgid "Odoo exports moves as `TD24` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:287 +msgid "" +"Is associated to deliveries whose **DDTs** have a **different** date than " +"the issuance date of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:293 +msgid "" +"Italian companies buying goods or services from EU countries (or services " +"from non-EU countries) must send the information contained within the bill " +"received to the **Agenzia delle Entrate**. This allows you to complete tax-" +"related information on your bill, and to send it. The seller must be set as " +":guilabel:`Cedente/Prestatore`, and the buyer as " +":guilabel:`Cessionario/Committente`. Contained within the **XML** document " +"for the vendor bill, the vendor's credentials show as " +":guilabel:`Cedente/Prestatore`, and your company's credentials as " +":guilabel:`Cessionario/Committente`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:302 +msgid "" +"Self-billing invoices or VAT invoice integrations must be issued and sent to" +" the tax agency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:304 +msgid "" +"When inputting taxes in a vendor bill, it is possible to select **reverse " +"charge** taxes. These are automatically activated in the Italian fiscal " +"position. By going to :menuselection:`Accounting --> Configuration --> " +"Taxes`, the `10%` and `22%` :guilabel:`Goods` and :guilabel:`Services` tax " +"scopes are activated and preconfigured with the correct tax grids. These are" +" set up automatically to ensure the correct booking of accounting entries " +"and display of the tax report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:310 +msgid "" +"For **vendor bills**, **three** types of configurations are technically " +"identified by a code called :guilabel:`Tipo Documento`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:313 +msgid "`TD17` - Buying services from **EU** and **non-EU** countries;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:314 +msgid "`TD18` - Buying **goods** from **EU**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:315 +msgid "" +"`TD19` - Buying **goods** from a **foreign** vendor, but the **goods** are " +"already in **Italy** in a **VAT deposit**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:320 +msgid "`TD17`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:322 +msgid "Buying **services** from **EU** and **non-EU** countries:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:324 +msgid "" +"The foreign *seller* invoices a service with a **VAT-excluded** price, as it" +" is not taxable in Italy. The VAT is paid by the *buyer* in Italy;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:327 +msgid "" +"Within EU: the *buyer* integrates the invoice received with the **VAT " +"information** due in Italy (i.e., **vendor bill tax integration**);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:329 +msgid "" +"Non-EU: the *buyer* sends themselves an invoice (i.e., **self-billing**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:331 +msgid "" +"Odoo exports a transaction as `TD17` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:333 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:347 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:363 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:423 +msgid "Is a vendor bill;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:334 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:348 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:424 +msgid "" +"At least one tax on the invoice lines targets the tax grids :ref:`VJ " +"`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:335 +msgid "" +"All invoice lines either have :guilabel:`Services` as **products**, or a tax" +" with the :guilabel:`Services` as **tax scope**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:338 +msgid "`TD18`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:340 +msgid "Buying **goods** from **EU**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:342 +msgid "" +"Invoices issued within the EU follow a **standard format**, therefore only " +"an integration of the existing invoice is required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:345 +msgid "" +"Odoo exports a transaction as `TD18` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:349 +msgid "" +"All invoice lines either have :guilabel:`Consumable` as **products**, or a " +"tax with the :guilabel:`Goods` as **tax scope**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:352 +msgid "`TD19`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:354 +msgid "" +"Buying **goods** from a **foreign** vendor, but the **goods** are already in" +" **Italy** in a **VAT deposit**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:357 +msgid "" +"From EU: the *buyer* integrates the invoice received with the **VAT " +"information** due in Italy (i.e., **vendor bill tax integration**);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:359 +msgid "" +"Non-EU: the *buyer* sends an invoice to *themselves* (i.e., **self-" +"billing**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:361 +msgid "Odoo exports a move as a `TD19` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:364 +msgid "" +"At least one tax on the invoice lines targets the tax grid :ref:`VJ3 " +"`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:365 +msgid "" +"All invoice lines either have :guilabel:`Consumable` products, or a tax with" +" :guilabel:`Goods` as tax scope." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:369 +msgid "" +"Odoo does not offer the `Conservazione Sostitutiva " +"`_ " +"requirements. Other providers and **Agenzia delle Entrate** supply free and " +"certified storage to meet the requested conditions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:377 +msgid "Internal reverse charge" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:380 +msgid "" +"Odoo currently does not support domestic **internal reverse charge** " +"processes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:385 +msgid "'Reverse Charge' tax grids" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:387 +msgid "" +"The Italian localization has a specific **tax grid** section for **reverse " +"charge** taxes. These tax grids are identifiable by the :ref:`VJ " +"` tag, and can be found under :menuselection:`Accounting --> " +"Reporting --> Audit Reports: Tax Report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Italian reverse charge tax grids" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:396 +msgid "San Marino" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:401 +msgid "" +"San Marino and Italy have special agreements on e-invoicing operations. As " +"such, **invoices** follow the regular **reverse charge** rules. Additional " +"requirements are not enforced by Odoo, however, the user is requested by the" +" **State** to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:405 +msgid "" +"Select a tax with the option :guilabel:`Has exoneration of tax (Italy)` " +"ticked, and the :guilabel:`Exoneration` set to `N3.3`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:407 +msgid "" +"Use the generic :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Codice " +"Destinatario` `2R4GT08`. The invoice is then routed by a dedicated office in" +" San Marino to the correct business." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:411 +msgid "Bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:413 +msgid "" +"When a **paper bill** is received from San Marino, any Italian company " +"**must** submit that invoice to the **Agenzia delle Entrate** by indicating " +"the e-invoice's :guilabel:`Tipo Documento` field with the special value " +"`TD28`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:419 +msgid "`TD28`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:421 +msgid "Odoo exports a move as `TD28` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:425 +msgid "The **country** of the partner is **San Marino**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:428 +msgid "Pubblica amministrazione (B2G)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:431 +msgid "" +"Odoo does **not** send invoices directly to the government as they need to " +"be signed. If we see that the codice destinatario is 6 digits, then it is " +"not sent to the PA automatically, but you can download the XML, sign it with" +" an external program and send it through the portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:436 +msgid "Digital qualified signature" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:438 +msgid "" +"For invoices and bills intended to the **Pubblica Amministrazione (B2G)**, a" +" **Digital Qualified Signature** is required for all files sent through the " +":abbr:`SdI (Sistema di Interscambio)`. The **XML** file must be certified " +"using a certificate that is either:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:442 +msgid "a **smart card**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:443 +msgid "a **USB token**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:444 +msgid "a **Hardware Security Module (HSM)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:447 +msgid "CIG, CUP, DatiOrdineAcquisto" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:449 +msgid "" +"To ensure the effective traceability of payments by public administrations, " +"electronic invoices issued to the public administrations must contain:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:452 +msgid "" +"The :abbr:`CIG (Codice Identificativo Gara)`, except in cases of exclusion " +"from traceability obligations provided by law n. 136 of August 13, 2010;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:454 +msgid "" +"The :abbr:`CUP (Codice Unico di Progetto)`, in case of invoices related to " +"public works." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:456 +msgid "" +"If the **XML** file requires it, the **Agenzia Delle Entrate** can *only* " +"proceed payments of electronic invoices when the **XML** file contains a " +":abbr:`CIG (Codice Identificativo Gara)` and :abbr:`CUP (Codice Unico di " +"Progetto)`. For each electronic invoice, it is **necessary** to indicate the" +" :abbr:`CUU (Codice Univoco Ufficio)`, which represents the unique " +"identifier code that allows the :abbr:`SdI (Sistema di Interscambio)` to " +"correctly deliver the electronic invoice to the recipient office." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:464 +msgid "" +"The :abbr:`Codice Unico di Progetto)` and the :abbr:`CIG (Codice " +"Identificativo Gara)` must be included in one of the **2.1.2** " +"(DatiOrdineAcquisto), **2.1.3** (Dati Contratto), **2.1.4** " +"(DatiConvenzione), **2.1.5** (Date Ricezione), or **2.1.6** (Dati Fatture " +"Collegate) information blocks. These correspond to the elements named " +":guilabel:`CodiceCUP` and :guilabel:`CodiceCIG` of the electronic invoice " +"**XML** file, whose table can be found on the government `website " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:470 +msgid "" +"The :abbr:`CUU (Codice Univoco Ufficio)` must be included in the electronic " +"invoice corresponding to the element **1.1.4** " +"(:guilabel:`CodiceDestinario`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:3 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Kenyan localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:19 +msgid ":guilabel:`Kenyan - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:20 +msgid "`l10n_ke`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:21 +msgid "" +"Installing this module grants you access to the list of accounts used in the" +" local GAAP and the list of common taxes (VAT, etc.)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:23 +msgid ":guilabel:`Kenyan - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:24 +msgid "`l10n_ke_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:25 +msgid "" +"Installing this module grants you access to improved accounting reports for " +"Kenya, such as Profit and Loss and Balance Sheets." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:28 +msgid "" +"You also have to install the **Kenya Tremol Device EDI Integration** package" +" to be able to report your taxes to the **Kenya Revenue Authority (KRA)** " +"using the Tremol G03 Control Unit:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:37 +msgid ":guilabel:`Kenya Tremol Device EDI Integration`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:38 +msgid "`l10n_ke_edi_tremol`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:39 +msgid "" +"Installing this module integrates with the Kenyan G03 Tremol control unit " +"device to report taxes to KRA through TIMS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst-1 +msgid "The three modules for the Kenya Fiscal Localization Package on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:47 +msgid "Kenyan TIMS integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:49 +msgid "" +"The Kenya Revenue Authority (KRA) has decided to go digital for tax " +"collection through the **Tax Invoice Management System (TIMS)**. As of " +"December 1st, 2022, all VAT-registered persons should comply with TIMS. The " +"goal is to reduce VAT fraud, increase tax revenue, and increase VAT " +"compliance through standardization, validation, and transmission of invoices" +" to KRA on a real-time or near real-time basis." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:55 +msgid "" +"All VAT-registered taxpayers should use a **compliant tax register**. Odoo " +"decided to develop the integration of the **Tremol G03 Control Unit (type " +"C)**, which can be run locally through USB. This device validates invoices " +"to ensure financial documents meet the new regulations and send the " +"validated tax invoices directly to KRA. Installing a proxy server that " +"provides a gateway between users and the internet is required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:62 +msgid "Installing the proxy server on a Windows device" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:64 +msgid "" +"Go to `odoo.com/download `_, fill out " +"the required information and click :guilabel:`Download`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst-1 +msgid "Install the Proxy Server on a Windows device" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:71 +msgid "" +"Once it is loaded on your computer, a wizard opens. You have to read and " +"agree with the terms of the agreement. On the next page, select the " +":guilabel:`type of install: Odoo IoT`. Then, click :guilabel:`Next` and " +":guilabel:`Install`. Once completed, click :guilabel:`Next`. Check the " +":guilabel:`Start Odoo` box to be redirected to Odoo automatically, and then " +"click :guilabel:`Finish`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:76 +msgid "" +"A new page opens, confirming your :doc:`IoT Box " +"<../../productivity/iot/config/connect>` is up and running. Connect your " +"physical device **Tremol G03 Control Unit (type C)** to your laptop via USB." +" In the :guilabel:`IoT Device` section, check that your Tremol G03 Control " +"Unit (type C) appears, confirming the connection between the device and your" +" computer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst-1 +msgid "Your IoT box is up and running" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:86 +msgid "" +"If the device is not detected, try to plug it in again or click on the " +":guilabel:`Restart` button in the top right corner." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:90 +msgid "" +":doc:`Connect an IoT box to your database " +"<../../productivity/iot/config/connect>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:93 +msgid "Sending the data to KRA using the Tremol G03 Control Unit" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:95 +msgid "" +"As a pre-requisite, check out that the :ref:`Kenyan Accounting modules " +"` are installed on your database. Then, go" +" to :menuselection:`Accounting --> Configuration --> Settings --> Kenya TIMS" +" Integration section`, and check that the :guilabel:`control Unit Proxy " +"Address` matches the address of the IoT box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:100 +msgid "" +"To send data to KRA, create a new invoice by going to " +":menuselection:`Accounting Dashboard --> Customer Invoice card` and clicking" +" :guilabel:`New Invoice`. Upon confirmation of a new invoice, the " +":guilabel:`Send invoice to Fiscal Device` button appears. Clicking on it " +"sends the invoice details to the device and from the device to the " +"government. The :guilabel:`CU Invoice Number` field is now completed in your" +" invoice, confirming the information has been sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:106 +msgid "" +"The :guilabel:`Tremol G03 Fiscal Device` tab contains fields that are " +"automatically completed once the invoice is sent to the government:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:109 +msgid "" +":guilabel:`CU QR Code`: Url from the KRA portal which reflects a QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:110 +msgid "" +":guilabel:`CU Serial Number`: reflects the serial number of the device." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:111 +msgid "" +":guilabel:`CU Signing Date and Time`: The date and time when the invoice has" +" been sent to KRA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:113 +msgid "" +"If you click on :guilabel:`Send and Print`, a .pdf of the invoice is " +"generated. The :guilabel:`Kenyan Fiscal Device Info` is mentioned on the " +"document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:117 +msgid "" +"To verify KRA has received the invoice information, take the :guilabel:`CU " +"Invoice Number` and and enter it in the :guilabel:`Invoice Number Checker` " +"section on `Kenya Revenue Authority website `_. Click :guilabel:`Validate` and find the invoice details." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:3 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:8 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Luxembourgish localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:17 +msgid ":guilabel:`Luxembourg - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:18 +msgid "`l10n_lu`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:20 +msgid ":guilabel:`Luxembourg - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:21 +msgid "`l10n_lu_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:23 +msgid ":guilabel:`Luxembourg - Annual VAT Report`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:24 +msgid "`l10n_lu_reports_annual_vat`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst-1 +msgid "" +"The three modules for the Luxembourgish Fiscal Localization Package on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:32 +msgid "" +"Installing the module :guilabel:`Luxembourg - Accounting Reports` installs " +"all three modules at once." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:36 +msgid "Standard Chart of Accounts - PCN 2020" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:38 +msgid "" +"Odoo's :ref:`fiscal localization package ` " +"for Luxembourg includes the current **Standard Chart of Accounts (PCN " +"2020)**, effective since January 2020." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:42 +msgid "eCDF tax return" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:44 +msgid "" +"Tax returns in Luxembourg require a specific XML file to upload on the eCDF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:46 +msgid "" +"To download it, go to :menuselection:`Accounting --> Report --> Audit " +"Reports --> Tax Report`, and click on :guilabel:`Export eCDF declaration`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:50 +msgid ":doc:`../accounting/reporting/tax_returns`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:51 +msgid "" +"`Platform for electronic gathering of financial data (eCDF) " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:54 +msgid "Annual tax report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:56 +msgid "" +"You can generate an XML file to electronically file your annual tax report " +"with the tax office." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:58 +msgid "" +"To do so, go to :menuselection:`Accounting --> Report --> Luxembourg --> " +"Annual Tax Report`, click on :guilabel:`Create`, then define the annual " +"period in the :guilabel:`Year` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:61 +msgid "" +"The **simplified annual declaration** is automatically generated. You can " +"manually add values in all the fields to get a **complete annual " +"declaration**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst-1 +msgid "" +"Odoo Accounting (Luxembourg localization) generates an annual tax " +"declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:68 +msgid "" +"To help you complete it, you can use the information provided on the " +":guilabel:`Tax Report`. To do so, go to :menuselection:`Accounting --> " +"Report --> Audit Reports --> Tax Report`, then click on the :guilabel:`Tax " +"Report` dropdown menu and select the type of report you want to display." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst-1 +msgid "Dropdown menu to select the type of Tax Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:76 +msgid "Finally, click on :guilabel:`Export XML` to download the XML file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:79 +msgid "" +"This feature requires the module :guilabel:`Luxembourg - Annual VAT Report` " +"to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:82 +msgid "FAIA (SAF-T)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:84 +msgid "" +"**FAIA (Fichier d’Audit Informatisé AED)** is a standardized and structured " +"file that facilitates the exchange of information between the taxpayers' " +"accounting system and the tax office. It is the Luxembourgish version of the" +" OECD-recommended SAF-T (Standard Audit File for Tax)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:88 +msgid "" +"Odoo can generate an XML file that contains all the content of an accounting" +" period according to the rules imposed by the Luxembourg tax authorities on " +"digital audit files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:92 +msgid "" +"This feature requires the module :guilabel:`Luxembourg - Accounting Reports`" +" to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:95 +msgid "Export FAIA file" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:97 +msgid "" +"Go to :menuselection:`Accounting --> Reporting --> Audit Reports --> " +"General Ledger`, then click on :guilabel:`FAIA`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:3 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:10 +msgid "`VIDEO WEBINAR OF A COMPLETE DEMO `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:15 +msgid "" +"Odoo Enterprise users in Mexico have free access to a set of modules that " +"allow them to issue electronic invoices according to the specifications of " +"the SAT for `version 3.3 of the CFDI " +"`_," +" a legal requirement as of January 1, 2018. These modules also add relevant " +"accounting reports (for example, the DIOT), and enable foreign trade, with " +"support for associated customs operations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:21 +msgid "" +"With the Mexican location in Odoo you will not only be able to comply with " +"the legal requirements to invoice in Mexico, but also use it as your " +"accounting system, satisfying the normal needs of the market. This makes " +"Odoo the perfect solution to manage your business in Mexico." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:26 +msgid "Pre requirements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:28 +msgid "" +"Before installing the modules and making the necessary configurations to " +"have the Mexican localization in Odoo, it is necessary to meet the following" +" requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:31 +msgid "Be registered with the SAT and have an RFC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:32 +msgid "" +"Have a `Certificate of Digital Seal `_ (CSD)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:34 +msgid "" +"Choose a PAC and purchase stamps. Currently the Mexican location in Odoo " +"works with the following PACs: `Solución Factible " +"`_, `Quadrum (formerly Finkok) " +"`_ and `SW Sapien - Smarter Web " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:37 +msgid "" +"Have knowledge and experience with billing, sales and accounting in Odoo. " +"This documentation contains only the information necessary to enable the use" +" of Odoo in a company based in Mexico." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:41 +msgid "Modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:43 +msgid "" +"To install the Mexican localization module, go to :menuselection:`Apps`, " +"then remove the default filter \"Apps\" and search for ``l10n_mx``." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Installation of the Mexican localization module in Odoo Apps" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:51 +msgid "" +"If you created the database from `www.odoo.com `_ and " +"chose \"Mexico\" as the country when creating your account, some of the " +"Mexican localization modules will have been installed automatically. In that" +" case we observe that some modules have a button that says \"Install\", " +"while others will instead have a label that says \"Installed\"." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:56 +msgid "" +"The following modules are necessary for all databases that require Mexican " +"localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "**Mexico - Accounting (l10n_mx)**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "" +"All the basic data to manage accounting, taxes and the chart of accounts. " +"The installed chart of accounts is based on `the SAT account grouping code " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "**EDI for Mexico (l10n_mx_edi & l10n_mx_edi_extended)**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "" +"Necessary for electronic transactions, CFDI 3.3, payment complement, and " +"addenda on invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "" +"**Odoo Mexican localization reports (l10n_mx_reports & " +"l10n_mx_reports_closing)**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "" +"All mandatory reports for electronic accounting. (Requires the accounting " +"application)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:67 +msgid "" +"The following modules are optional, and should be installed only if they " +"meet a specific organization requirement. Installing these modules is not " +"recommended unless you are sure they are needed as they add fields that can " +"unnecessarily complicate form filling." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "**Odoo Mexico Localization for Stock / Landing (l10n_mx_edi_landing)**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "" +"This module allows managing the requests as part of the shipping costs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "**Odoo Mexican XML Polizas Export (l10n_mx_xml_polizas)**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "" +"With this module, you will be able to export your Journal Entries in XML " +"ready to be uploaded to the SAT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:81 +msgid "Enable electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:83 +msgid "" +"Go to :menuselection:`Settings --> Accounting --> Customer Invoices`, and " +"make sure that the option **Mexican Electronic Invoicing** is enabled. With " +"this you will be able to generate the signed invoice and also generate the " +"signed payment complement, all automatically integrated into the normal " +"billing flow in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Steps to enable electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:95 +msgid "Enter legal information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:97 +msgid "" +"After verifying the general configuration, you must verify that the company " +"is configured with the correct data. To do so, go to " +":menuselection:`Settings --> General Settings --> Companies`, and click on " +"*Update information* under your company name." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Update the company's details in the Settings of Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:105 +msgid "" +"In the resulting form, put your full address (including zip code), RFC (VAT " +"number), and the rest of the data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:109 +msgid "" +"From a legal point of view, a Mexican company must use the local currency " +"(MXN). Therefore, Odoo does not provide features to manage an alternative " +"configuration. If you want to manage another currency, let MXN be the " +"default currency and use a :doc:`pricelist " +"` instead." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 +msgid "" +"Make sure that in the address, for the Country field, \"Mexico\" is chosen " +"from the list of countries that Odoo shows, because if it is entered " +"manually there is a risk of creating a \"new country\" in the system, which " +"it will result in errors later when the CFDIs are generated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "Company data information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:124 +msgid "" +"If you want to test the Mexican localization, you can configure the company " +"with a real address within Mexico (including all fields) and add " +"``EKU9003173C9`` as RFC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:128 +msgid "Set the fiscal regime of the company" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:130 +msgid "" +"The following is to indicate what is the fiscal regime of the company that " +"we are configuring, which is done through a pre-existing field in Odoo " +"called \"Fiscal Regime\"." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:133 +msgid "" +"Go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX) " +"--> Fiscal Regime`, and select the option that applies to your company from " +"the drop-down list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Set the Fiscal Regime in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:141 +msgid "" +"For the test environment: Select the option **General Law on Legal Persons**" +" from the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:145 +msgid "Contacts Configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:147 +msgid "" +"When creating a contact to be invoiced in Odoo, the following information " +"must be configured for invoice validation: **complete address** (including " +"postal code, city, state, country, etc.) and the **VAT** number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Contact form example" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:156 +msgid "Taxes Configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:158 +msgid "" +"A necessary configuration for electronic invoicing to work correctly in Odoo" +" is to add the factor type associated with sales taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:161 +msgid "" +"To make this configuration you first have to go to " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:164 +msgid "" +"Within the list of taxes that are pre-loaded, select the option *Sales* on " +"the filter, this is to see only taxes associated with sales, which are those" +" that are validated for the stamping of invoices. Open the form view of any " +"of the sales taxes, select the **Advanced Options** tab and within the field" +" **Factor Type** choose the option *Tasa*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:173 +msgid "" +"Do the same for all the sales taxes that the company needs, either those " +"that come by default in Odoo, or those that you add that are necessary for " +"your company bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:177 +msgid "" +"For the 0% VAT tax, select the option :guilabel:`Tasa` within the " +":guilabel:`Factor Type` field. For the 0% VAT **exempt** tax, select the " +"option :guilabel:`Exento` instead of :guilabel:`Tasa` within the " +":guilabel:`Factor Type` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:181 +msgid "" +"When registering a payment, Odoo will carry out the movement of taxes from " +"the **Cash Basis Transition Account** to the account set in the " +"**Definition** tab. For such movement, a tax base account will be used " +"(\"Base Imponible de Impuestos en Base a Flujo de Efectivo\" - **do not " +"eliminate this account**) in the Journal Entry when reclassifying taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Taxes accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:191 +msgid "Products Configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:193 +msgid "" +"All products to be sold need to have the SAT code associated with their " +"classification so that the invoices do not give an error when validating." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:196 +msgid "" +"To configure products, go to the **General Information** tab and in the " +"**UNSPSC Product Category** field select the category that represents that " +"product. The process can be done manually or through a bulk import." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Configure products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:205 +msgid "PAC Configuration to sign invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:207 +msgid "" +"Another important step to configure electronic invoicing in Odoo is to enter" +" the PAC which you are working with and the credentials. That way, " +"electronic invoicing will be enabled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:211 +msgid "" +"Remember that you must register directly with the PAC of your choice before " +"you start creating invoices from Odoo. We have the following PACs available:" +" `Quadrum `_, `Solución Factible " +"`_ and `SW Sapien - Smarter Web " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:216 +msgid "" +"You must process your **Private Key (CSD)** with the SAT institution before " +"following these steps. If you do not have this information, try with the " +"Test Credentials and return to this process when you have the SAT " +"Credentials for your production environment to work with real transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:221 +msgid "" +"To add the credentials, go to :menuselection:`Settings --> Accounting --> " +"Electronic Invoicing (MX)`. Under the **PAC MX** section, enter the name of " +"your PAC with your credentials (PAC username and PAC password)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "PAC credentials" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:230 +msgid "" +"If you check the checkbox **Test Environment**, it is not necessary to enter" +" a PAC username and/or password, but you must select a PAC from the drop-" +"down list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:233 +msgid "" +"Finally, upload the digital certificates of the company within the section " +"**MX Certificates**. Click on *Add a line*, a window will open, click on " +"*Create* and from there you can upload your digital certificate, your key " +"and your password. To finish, click on *Save and Close*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Certificate and key" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:242 +msgid "" +"If you still do not have one of the contracted PACs and you want to test " +"electronic invoicing you can use the following SAT test certificates:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:245 +msgid ":download:`Certificate `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:246 +msgid ":download:`Certificate Key `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:247 +msgid "**Password:** ``12345678a``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:249 +msgid "" +"You must also configure the company with a real address within Mexico " +"(including all fields) and add ``EKU9003173C9`` as the **VAT** number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:253 +msgid "Workflows" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:256 +msgid "Electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:258 +msgid "" +"The invoicing process in Odoo is based on `Annex 20 " +"`_" +" version 3.3 of electronic invoicing of the SAT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:262 +msgid "" +"To start invoicing from Odoo, an invoice must be created using the standard " +"invoicing flow, that is, either from a sales order or from the invoice menu " +"in the Accounting application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:265 +msgid "" +"The invoice will be stamped after clicking on *Validate*, before that the " +"status is still in draft mode and changes can be made to it. After " +"validating the invoice, you can verify that it was successfully stamped, as " +"it would look like this:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Creating an invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:273 +msgid "" +"The details of the invoice will be reflected in the Chatter, which is what " +"you see on the right of the invoice in the attached image. There you can " +"find your XML sent to the SAT and the status of the stamping, that is, if it" +" was validated or not." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:277 +msgid "" +"To send the stamped invoice to your client, you can send the XML together " +"with the PDF file directly from Odoo, by clicking the *Send and Print* " +"button. You can also download the PDF file directly to your computer by " +"clicking the *Print* button and selecting the desired option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:282 +msgid "" +"Depending on the size of the screen, the Chatter can be seen next to or " +"below the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:285 +msgid "Invoicing Special Cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:288 +msgid "Foreign Trade Invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:290 +msgid "" +"The foreign trade invoicing process in Odoo is based on the corresponding " +"`SAT regulation " +"`_." +" SAT electronic invoicing version is 3.3." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:295 +msgid "What do we mean when we talk about foreign trade?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:297 +msgid "" +"Since January 2018, the SAT requires a Foreign Trade Supplement in export " +"transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:300 +msgid "What is the Foreign Trade complement?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:302 +msgid "" +"It is an Annex to the electronic invoice that allows the identification of " +"exporters and importers, in addition to expanding the description of the " +"merchandise sold." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:306 +msgid "What information can be incorporated in this new complement?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:308 +msgid "Information on the operation type it covers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:309 +msgid "" +"Tax identification data of the issuer, receiver or recipient of the " +"merchandise." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:310 +msgid "Description of the goods to be exported." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:313 +msgid "Who is obliged to generate it?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:315 +msgid "Taxpayers who carry out export operations of A1 type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:318 +msgid "To which exports does the A1 type apply?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:320 +msgid "" +"Entry of goods of foreign origin to remain in national territory for an " +"unlimited time." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 +msgid "Exit of goods from the country to stay abroad for an unlimited time." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:322 +msgid "" +"Definitive importation of vehicles by diplomatic and consular missions and " +"offices of international organizations and their foreign personnel, in " +"accordance with the import of vehicles in diplomatic exemption." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:327 +msgid "Is Foreign Trade the same as Pedimentos?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:329 +msgid "" +"Not necessarily, the Pedimentos are directly related to the process of " +"Importing goods, while the Foreign Trade Complement is related to the " +"Exporting process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:333 +msgid "Required Modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:335 +msgid "" +"In order to generate foreign trade invoices, the following modules must be " +"installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:337 +msgid "EDI for Mexico (l10n_mx_edi)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "EDI para México" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:343 +msgid "EDI for Mexico (l10n_mx_edi_extended)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "EDI Advanced Features" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:350 +msgid "Company" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:352 +msgid "" +"Configure the company with a valid postal code, and if you have a colony " +"code, this should match with the corresponding Zip Code. At the same time, " +"remember to place the Tax Identification Number (VAT Number - RFC)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Contact address configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:361 +msgid "Receiving Client" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:363 +msgid "" +"Generally it will be a foreign client, in which you must verify that you " +"have at least the following fields completed with the corresponding " +"information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "External trade invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:371 +msgid "The customer's delivery address must also contain the zip code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:372 +msgid "" +"The format of the foreign VAT (Tax Identification Number) will be validated " +"as appropriate in each Country (Example: Colombia ``123456789-1``)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:374 +msgid "" +"In the XML, the VAT is automatically replaced by the Generic VAT for abroad " +"transactions: ``XEXX010101000``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:380 +msgid "" +"At the product level there must also configure some parameters in the " +"following fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "SAT product code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Tariff fraction" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:391 +msgid "" +"You must select the **UMT Aduana** (Unit of Measure) in *KG* since it is " +"only accepted by the SAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:392 +msgid "The weight refers to **the unit weight** of the product" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:393 +msgid "The tariff item must be from the code UoM of Kilograms (**UoM = 01**)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:395 +msgid "" +"Although the product is sold in pieces or in units, the value that must be " +"registered with customs in the tariff item must be reported in Kilograms." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:399 +msgid "Invoicing Flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:401 +msgid "" +"When creating the foreign sales invoice, you must select the **Incoterm** " +"corresponding and the **Need external trade?** checkbox must be checked. " +"With this configuration enabled, the **PDF** and the complement **XML** of " +"the invoice will have the necessary information to comply with the SAT " +"regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:407 +msgid "What is the certificate of origin and when is it used?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:409 +msgid "" +"The **Certificate Source** (or proof of origin) is the document that allows " +"an importer or exporter to prove the country or region from which a good is " +"considered to originate and serves to receive tariff preferences generally " +"agreed in trade agreements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Incoterm on invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "PDF external Trade" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:422 +msgid "Assign Pedimentos" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:424 +msgid "" +"If your company imports products and you need to add the **Pedimentos** " +"number in your invoices, you can also configure Odoo to record the process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:427 +msgid "" +"First, go to :menuselection:`Apps`, remove the \"Apps\" filter and search " +"for ``Mexico``, ``mx`` or ``l10n_mx``. Then, install **Odoo Mexico " +"Localization for Stock / Landing module (l10n_mx_edi_landing)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "MX stock module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:436 +msgid "" +"The l10n_mx_edi_landing module depends on the **Inventory** and **Sales** " +"apps, since the products must be entered into inventory to be able to add " +"their Pedimentos number to the corresponding receipt of products." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:440 +msgid "" +"Then, go to :menuselection:`Inventory --> Settings --> Settings`. Within the" +" options, activate **Landed Costs**. This option will allow adding the " +"Pedimentos number to the corresponding product receptions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Costos en destino" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:449 +msgid "" +"In order to use landed costs, the accounting configuration of the inventory " +"valuation of the products must be configured as *Automated* and its costing " +"method *Average* or *FIFO* (first in, first out)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:453 +msgid "" +"To associate the Pedimentos number indicated with an import (merchandise " +"reception) a new **Landed Cost** must be created. They can be accessed " +"through :menuselection:`Inventory --> Operations --> Landed Costs`. There " +"you will find the option to attach the Pedimentos number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Customs number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:462 +msgid "" +"You can only add the Pedimentos number once, so be careful when associating " +"the correct number with the transfer(s)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:466 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:469 +msgid "Payment Terms" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:471 +msgid "" +"The **Payment Terms** are already configured in Odoo when installing the " +"Mexican localization, this means that if you go to " +":menuselection:`Accounting --> Configuration --> Payment Terms`, you will " +"find the default list in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Payment terms" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:479 +msgid "" +"In Mexico you can have 2 types of payments: PPD or PUE. These are given by " +"the **Payment Term** chosen (or if there is no chosen payment term it will " +"be based on the due date of the invoice)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:483 +msgid "PPD Payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:485 +msgid "" +"To configure PPD payments (payment in installments or deferred) it is only " +"necessary to choose a date expiration date for your invoice and Odoo will " +"detect if it is after the first day of the following month (in this case no " +"payment term is set - with the payment term you can also stipulate if it " +"will be PPDo PUE)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:491 +msgid "PUE" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:493 +msgid "" +"To configure PUE payments (payment in a single payment) you must select an " +"invoice due date within the same month or choose a payment term that does " +"not imply changing the due month (immediate payment, 15 days, 21 days, all " +"falling within the current month)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:500 +msgid "" +"`According to the SAT documentation " +"`_, there may be 2 types of payments: **PUE** or **PPD**. In both " +"cases the payment process in Odoo is the same, the difference of whether the" +" payment is PUE or PPD lies in the payment term of the invoice - as " +"indicated in the previous point in the **Payment Terms**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:506 +msgid "" +"If the payment is a PPD type, Odoo will generate the corresponding payment " +"complement automatically when you *Confirm* it. If the payment is PUE, the " +"payment complement will not be generated. The type of payment is visible " +"from the invoice in the field called **Payment Policy** and takes the " +"invoice date and the due date as parameters." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Payment policy" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:515 +msgid "" +"When configuring the contacts that will be used when making payments, you " +"must configure the banks in the **Accounting** tab, place both the Bank, " +"Account Number and CLABE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Contact bank account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:523 +msgid "Register PPD Payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:525 +msgid "" +"If at the time of registering a payment it is of type PPD then a Payment " +"Complement (XML) will be generated with its details." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:528 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:573 +msgid "" +"The payment can be registered from the invoice and once it is confirmed, the" +" invoice will be paid and with its payment associated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "PPD payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "PPD payment information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:540 +msgid "" +"The journal will be the payment method where you receive or send the payment" +" from. You must also associate a **Payment Way** and a Recipient Bank " +"Account (this last one must be created within the contact associated with " +"the invoice)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:544 +msgid "" +"Once the payment is made, it will be associated with the corresponding " +"invoice and its status will be *In Payment* since the payment will be " +"effectively validated when it is bank reconciled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:548 +msgid ":doc:`../accounting/bank/reconciliation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "PPD payment created" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:555 +msgid "" +"The **Recipient Bank Account** is the one attached to the **Accounting** tab" +" in the contact associated with the invoice, it must be valid so that the " +"stamped payment complement can be created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:560 +msgid "" +"When making a payment in MXN for an invoice in USD, the payment must be " +"created using the :guilabel:`Register Payment` button **on the invoice " +"view** and not separately as a payment. Otherwise, the payment CFDI is not " +"correctly generated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:563 +msgid "" +"As such, a payment in MXN cannot be used to pay multiple invoices in USD. " +"Rather, the payment should be separated into multiple payments created using" +" the :guilabel:`Register Payment` button on the corresponding invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:568 +msgid "Register PUE Payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:570 +msgid "" +"If at the time of registering a payment it is of the PUE type then in this " +"case a Payment Complement (XML) will not be generated since it is not " +"necessary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "PUE payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "PUE payment information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "PUE payment created" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:589 +msgid "" +"In this case it is not created as a payment supplement by the nature of it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:592 +msgid "Down Payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:594 +msgid "" +"This is a special case in which we must receive an advance payment from a " +"client to later be applied to an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:598 +msgid "" +"`The official documentation for registration of down payments in Mexico " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:602 +msgid "Process to create advance in Mexico" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:604 +msgid "" +"Issuance of electronic invoicing with the amount of the advance payment " +"received." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:605 +msgid "" +"Issuance of the electronic invoice for the total value of the operation " +"(full invoice). (CFDI Origin: 07 | Advance invoice, point 1)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:607 +msgid "" +"Issuance of the electronic invoice with the *Egreso* type. (CFDI Origin: 07 " +"| Invoice_total, point 2)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:611 +msgid "Steps to follow in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:613 +msgid "Preparation: Create the product" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:614 +msgid "" +"Down Payment issuance of the electronic invoice for the amount of the " +"advance payment received" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:615 +msgid "" +"Issuance of the electronic invoice for the total value of the operation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:616 +msgid "Add a credit note from the down payment invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:619 +msgid "Preparation: Create the Product" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:621 +msgid "" +"The Down Payment product must be type *Service* and must use the **NSPSC " +"Product Category**: *84111506 Servicios de facturación*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Down payment product" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:628 +msgid "" +"Add the down payment product as default to be used from the Odoo " +"configurations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Down payment configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:635 +msgid "" +"Issuance of the electronic invoice for the value of the advance received" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:637 +msgid "" +"Create the Advance Payment Invoice: From the sales order, create an advance " +"payment invoice for the percentage of the purchase to be paid in advance (or" +" for a fixed amount)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Applying down payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:644 +msgid "Validate invoice with the down payment product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Confirm down payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Folio fiscal down payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:654 +msgid "Register Payment to the advance payment invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Down payment invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Down payment registered" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:665 +msgid "" +"Issuance of the electronic invoice for the total value of the operation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:667 +msgid "" +"From the sales order, create an invoice for the total, that is, for all the " +"order lines without discounting the advance." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Full invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:675 +msgid "Remove the check mark from the **Deduct down payments** field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:677 +msgid "" +"Add the original CFDI of the advance payment invoice by adding ``07 |`` at " +"the beginning + Folio Fiscal of the advance payment Invoice created in the " +"previous step." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:680 +msgid "Copy the Folio Fiscal of the following invoice following this example:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Folio full invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:686 +msgid "" +"And paste it in the draft invoice created from the Sales Order without " +"deducting the advances:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "CFDI origen folio" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:692 +msgid "" +"Validate and copy the Folio Fiscal for later (in the example the Folio " +"Fiscal copy is: 50E4FF06-4341-4006-A7C3-A7F653CBEFAE )" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:696 +msgid "Add credit note from invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:698 +msgid "" +"Create a **Credit Note** from the down payment invoice (the corrective " +"invoice must be edited prior to confirming it, see explanation below the 2 " +"following images)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Creation of a Credit Note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Matching down payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:709 +msgid "" +"Before you *Confirm* the Credit Note, edit the Origin CFDI with ``07 | XXX``" +" instead of the prefix ``01 | XXX``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Modify folio fiscal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "CFDI origen type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:720 +msgid "Now the invoice can be confirmed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Post credit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:726 +msgid "" +"Now the Credit Note (Advance Payment) must be applied to the total invoice, " +"this is added at the bottom below the amount owed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Add credit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Down payment applied" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:737 +msgid "" +"Register a payment for the difference of the down payment and the total of " +"the sale." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Residual amount payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:743 +msgid "" +"If you go to the XML of the invoice, you should see in CFDI related the type" +" of relationship 07 and the Folio Fiscal of the advance payment invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "XML down payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:751 +msgid "Discounts based on payment days" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:753 +msgid "" +"Cash discounts are incentives that you can offer to motivate customers to " +"pay within a specified time period. For example, you offer a 2% discount if " +"the customer pays you within the first 5 days of the invoice, when it is due" +" in 30 days. This approach can greatly improve your average customer " +"payments period." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:758 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:763 +msgid "Create and assign the corresponding Payment Term" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:759 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:782 +msgid "Register the Payment within the days of the discount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:760 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:808 +msgid "Create a credit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:765 +msgid "" +"To configure the discount for advance payment, go to " +":menuselection:`Accounting --> Configuration --> Payment Terms` and click on" +" *Create*. Add a Percentage type with a corresponding value (for example, " +"98% of the total price for a 2% discount) and the number of days for which " +"the offer is valid (for example 5 days). You can also change the balance due" +" type if necessary (in this example 30 days)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Discount payment term" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:775 +msgid "" +"Then when creating our Sales Order or Sales Invoice, assign the Payment Term" +" created previously." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "discount on invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:784 +msgid "" +"Register the payment within the days in which the application of the " +"discount was specified, in our case it is within 5 days after the creation " +"of the Sales Invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Discount payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:791 +msgid "" +"Then go to the bottom of the invoice where the totals are located and there " +"you will see 2 payments created, reset to draft and cancel the payment that " +"does not correspond - the one related to the discount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "See discount payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Mote to draft payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Cancel payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:810 +msgid "" +"Finally to close the cycle we must close the invoice, but as in this case we" +" apply a discount, to close it correctly we must create a credit note " +"specifying that the difference was given to the customer on a **Credit " +"Note**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Discount credit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Reason of credit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:822 +msgid "Adjust the amount to the remaining balance in the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Total credit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:828 +msgid "Add the Credit Note to the original invoice so that it is settled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Add credit note for discount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:835 +msgid "Cancellation of invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:838 +msgid "Before 72 Hours" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:840 +msgid "" +"If it is necessary to cancel an invoice validated and sent to the SAT in " +"less than 72 hours follow the steps below." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:843 +msgid "Request Cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "Cancel within 72 hours" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:849 +msgid "The status of the **Electronic invoicing** changes to *Cancelled*" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:850 +msgid "Click on *RESET TO DRAFT*" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "Invoice to draft" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:856 +msgid "Click on *CANCEL ENTRY*" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "Cancel journal entry" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:863 +msgid "After 72 Hours" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:865 +msgid "" +"If It is necessary to cancel an invoice validated and sent to the SAT more " +"than 72 hours, the client must be asked to accept the cancellation, for this" +" the following steps must be followed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:868 +msgid "" +"Click on *Request EDI Cancellation* to inform the SAT that you want to " +"cancel the invoice, in this case the client has to enter the SAT webpage and" +" approve it. (The status of the **Electronic invoicing** field in Odoo " +"changes to *To Cancel*)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:871 +msgid "" +"When the client (Receiver / Customer) approves the Cancellation in their SAT" +" portal it is now possible to Change the invoice to Draft and then click on " +"*Cancel entry*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:873 +msgid "" +"Odoo synchronizes with the SAT to update the status of the **Electronic " +"invoicing** with a scheduled action, Invoices canceled in the SAT will be " +"canceled in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Cancel after 72 hours" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:880 +msgid "" +"After clicking on **Request EDI cancellation**, the status of the " +"**Electronic invoicing** field will be *To Cancel* but the status of the SAT" +" will be the same to *Valid*, it will remain active until the end customer /" +" Recipient approves the cancellation in the SAT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Check estado del PAC" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:888 +msgid "" +"Once canceled in the SAT, Odoo will synchronize the status of the SAT " +"through scheduled actions that are executed every day to synchronize the " +"statuses of the SAT, Electronic invoicing and Odoo (this scheduled action " +"can be executed manually by entering with developer mode)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:892 +msgid "" +"If the invoice is canceled in the SAT, in Odoo it is also canceled, which " +"allows you to switch the invoice to draft and finally cancel the invoice " +"(*cancel entry*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "PAC scheduled action" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:900 +msgid "Cancel Paid Invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:902 +msgid "" +"If the invoice has already been paid, a credit note must be created from the" +" invoice so that the originating CFDI is recognized and later cancel the " +"original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Cancel paid invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Credit note to cancel" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:914 +msgid "Cancel Invoices from the previous period" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:917 +msgid "Problem" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:919 +msgid "" +"If the invoice is from the previous month and the period is closed, the " +"income has already been declared in Financial Reports and to the government." +" In Odoo, when canceling an invoice, the journal entry is eliminated as if " +"the income already reported had not existed, this represents a fiscal " +"problem because the income was already declared in the previous month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 +msgid "" +"The problem resides when the fiscal period has been closed, in the current " +"period you have to make the reverse entry and save the cancellation " +"information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:927 +msgid "Invoice to be canceled" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Previous period" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:933 +msgid "This is how the Balance Sheet looks like:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Previous BS" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:939 +msgid "" +"If the invoice is canceled, the journal entry and the Balance Sheet looks " +"like this after canceling:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "AR in BS" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:946 +msgid "Solution" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:948 +msgid "" +"Close the fiscal period every month (Best Practice Mexican Localization)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:949 +msgid "Cancel invoice in SAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:950 +msgid "Create a Manual Reversion entry (Journal Entry)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:951 +msgid "Reconcile the open invoice with the reversal entry (Journal Entry)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:952 +msgid "Change Electronic invoicing status to Cancelled with server action" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:955 +msgid "" +"Close accounting period each month (Best Practice Mexican Localization)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:957 +msgid "" +"If the accounting period is closed due to the blocking dates, Odoo will not " +"allow to modify or add accounting entries of a date corresponding to that " +"accounting period." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Closing fiscal period" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:965 +msgid "Cancel invoice in the SAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:967 +msgid "" +"If the accounting period is closed, and the invoice was canceled in the SAT," +" the status in Odoo will be published while the **Electronic invoicing** " +"status will be *Sent* and the SAT status is *Cancelled*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Cancel in SAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:976 +msgid "Create Manual Reversal Journal Entry" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:978 +msgid "" +"The solution is to create the reversal journal entry manually dated in the " +"current fiscal period and reconcile the open invoice with the reversion " +"created manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:981 +msgid "" +"It must be clearly indicated in the reference that it is a cancellation (you" +" can use a cancellation account for invoices from previous periods such as " +"**Other Income**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Manual reversal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:989 +msgid "Reconcile the open invoice with the reversal entry" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Reconcile open invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Open invoice paid" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:999 +msgid "" +"In the Balance Sheet and Trial balance they are now with the correct " +"balances." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "New BS" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Up to date BS" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Balanza de comprobación" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1014 +msgid "Change status of Electronic invoicing to Cancelled with server action" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1016 +msgid "" +"A server action can be created that modifies the status of the invoice to " +"*Cancelled* once it is reconciled with the reversal entry (You should check " +"this with support or with your Assigned Functional Consultant prior to " +"performing this action)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Scheduled action PAC status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Execute server action" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1029 +msgid "Electronic Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1031 +msgid "Accounting for Mexico in Odoo is composed of 3 reports:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1033 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1047 +msgid "Electronic Chart of Accounts (Called and displayed as COA)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1034 +msgid "Electronic Trial Balance." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1035 +msgid "DIOT report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1037 +msgid "" +"1. and 2. are considered electronic accounting, and DIOT is a report only " +"available in the context of accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1040 +msgid "" +"You can find all of those reports in :menuselection:`Accounting --> " +"Reporting --> Mexico`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "MX reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1049 +msgid "" +"Electronic invoicing has never been so easy, just go to " +":menuselection:`Accounting -> Reports -> Mexico -> COA` and click the button" +" **Export for SAT (XML)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "COA for SAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1057 +msgid "How to add new accounts ?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1059 +msgid "" +"If you add an account with the NNN.YY.ZZ encoding convention where NNN.YY is" +" a SAT encoding group, your account will be set up automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1062 +msgid "" +"Example to add an Account for a new Bank account go to " +":menuselection:`Accounting --> Settings --> Chart of Account` and then " +"create a new account in the «Create» button and try to create an account " +"with the number 102.01.99 once you change to establish the name you will see" +" an automatically configured label, the configured labels are the ones " +"chosen to be used in the COA in XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Create account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1073 +msgid "What is the meaning of the tags?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1075 +msgid "" +"To know all the possible labels, you can read `Annex 24 " +"`_" +" on the SAT website in the section called **Código agrupador de cuentas del " +"SAT**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1080 +msgid "" +"When you install the l10n_mx module and your chart of accounts depends on it" +" (this happens automatically when you install the configuration of Mexico as" +" a country in your database), it will have the most common labels by " +"default. If the tag you need is not created, you can create it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1086 +msgid "Trial Balance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1088 +msgid "" +"Exactly like the COA but with the credit and debit of the initial balance, " +"once you have correctly configured your COA, you can go to " +":menuselection:`Reports --> Trial Balance` this is automatically generated " +"and can be exported to XML using the button on the top **Export for SAT " +"(XML)** with the previous selection of the period you want to export." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Electronic verification balance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1097 +msgid "" +"All normal analysis and listed functions are available here as well as any " +"normal Odoo Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1100 +msgid "DIOT Report (Requires Accounting App)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1103 +msgid "What is DIOT and the importance of presenting it SAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1105 +msgid "" +"When it comes to procedures with the SAT Administration Service, we know " +"that we should not neglect what we present." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1108 +msgid "" +"The DIOT is the Informative Declaration of Operations with Third Parties " +"(DIOT), which is an additional obligation with VAT, where we must give the " +"status of our operations to third parties, or what is considered the same, " +"with our suppliers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1112 +msgid "" +"This applies to both individuals and Personas Morales, so if we have VAT to " +"present to the SAT and also deal with suppliers it is necessary to send the " +"DIOT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1116 +msgid "When to file the DIOT and in what format ?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1118 +msgid "" +"It is easy to present the DIOT, since, like all formats, you can obtain it " +"on the SAT page, it is the electronic form A-29 that you can find on the SAT" +" website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1121 +msgid "" +"Every month if you have operations with third parties, it is necessary to " +"present the DIOT, as we do with VAT, so if in January we have deals with " +"suppliers, by February we must present the information relevant to said " +"data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1126 +msgid "Where is DIOT presented?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1128 +msgid "" +"You can present DIOT in different ways, it is up to you which one you will " +"choose and which one will be more comfortable for you since you will present" +" it every month or every time you have dealings with suppliers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1132 +msgid "" +"The A-29 form is electronic so you can present it on the SAT page, but this " +"after having made up to 500 registrations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1135 +msgid "" +"Once these 500 records have been entered in the SAT, you must submit them to" +" the Local Taxpayer Services Administration (ALSC) with correspondence to " +"your tax address, these records can be submitted on a digital storage medium" +" such as a CD or USB, which a Once validated, they will return you, so do " +"not doubt that you will still have these discs and of course, your CD or " +"USB." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1141 +msgid "One more thing to know: batch loading?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1143 +msgid "" +"When reviewing the official SAT documents in DIOT, you will find the Batch " +"load, and of course the first thing we think is what is that ?, and " +"according to the SAT site it is:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1146 +msgid "" +"The \"batch load\" is the conversion of databases from records of " +"transactions with suppliers made by taxpayers in text files (.txt). These " +"files have the necessary structure for their application and import into the" +" Informative Declaration of Operations with third parties system, avoiding " +"direct capture and consequently, optimizing the time invested in their " +"integration for the presentation in time and form to the SAT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1152 +msgid "" +"You can use it to present the DIOT, since it is allowed, which will " +"facilitate this operation, so that it does not exist to avoid being in line " +"with the SAT in regards to the Informative Declaration of Operations with " +"Third Parties." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1157 +msgid "" +"`official information " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1161 +msgid "How to generate this report in Odoo?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1163 +msgid "" +"Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions " +"with third partied (DIOT)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "DIOT report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1170 +msgid "" +"A report view is displayed, select the last month to report the immediately " +"preceding month or leave the current month if it suits you." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "DIOT filter" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1177 +msgid "Click on *Export (XLSX)* or *Print (TXT)*" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Print DIOT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1183 +msgid "" +"Save the downloaded file in a safe place, go to the SAT website and follow " +"the necessary steps to declare it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1187 +msgid "Important considerations about your supplier and invoice data for DIOT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1189 +msgid "" +"All suppliers must have the fields configured in the accounting tab called " +"\"DIOT Information\", the L10N MX Nationality field is completed by simply " +"selecting the appropriate country in the address, not You need to do nothing" +" else there, but the l10n MX type of operation must be configured in all " +"your providers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "DIOT configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1198 +msgid "" +"There are 3 VAT options for this report, 16%, 0% and exempt, one invoice " +"line in Odoo is considered exempt if there is no tax on it, the other 2 " +"taxes are already configured correctly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1200 +msgid "" +"Remember that to pay an invoice that represents a prepayment, you must first" +" request the invoice and then pay it and properly reconcile the payment " +"following the standard Odoo procedure." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1202 +msgid "" +"You do not need to fill in all your partner data to try to generate the " +"supplier invoice, you can correct this information when you generate the " +"report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1204 +msgid "" +"Remember that this report only shows vendor invoices that were actually " +"paid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1206 +msgid "" +"If some of these considerations are not taken into account, a message like " +"this will appear when you generate the DIOT in TXT with all the partners you" +" need to verify this particular report, this is the reason why we recommend " +"to use this report not only for exporting your legal information. " +"obligation, but generate it before the end of the month and use it as your " +"auditory process to see that all your partners are configured correctly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "DIOT Error" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1217 +msgid "Closing Fiscal Period in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1219 +msgid "" +"Before proceeding to the close of the fiscal year, there are some steps that" +" you should normally take to ensure that your accounting is correct, updated" +" and accurate:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1222 +msgid "" +"Make sure that you have fully reconciled your bank account (s) through the " +"end of the year and confirm that the closing book balances match the " +"balances on your bank statements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1224 +msgid "Verify that all customer invoices have been entered and approved." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1225 +msgid "Confirm that you have entered and approved all vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1226 +msgid "Validate all expenses, ensuring their accuracy." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1227 +msgid "" +"Check that all payments received have been entered and recorded exactly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1232 +msgid "Run a **Tax Report**, and verify that your tax information is correct." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1233 +msgid "Reconcile all accounts on your **Balance Sheet**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1235 +msgid "" +"Compare your bank balances in Odoo against the current bank balances on your" +" statements. Use the report **Bank Reconciliation** to help you with this." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1237 +msgid "" +"Reconcile all cash and bank account transactions by running your **Old " +"Accounts Receivable** and **Old Accounts Payable** reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1239 +msgid "" +"Audit your accounts, making sure you fully understand the transactions that " +"affect them and the nature of the transactions, making sure to include loans" +" and fixed assets." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1242 +msgid "" +"Run the optional function **Payments Matching**, under the *More* drop-down " +"on the Journal options from the Accounting dashboard, validating any Vendor " +"Bill and Customer Invoices with its payments. This step is optional, however" +" it can assist the year-end process if all pending payments and invoices are" +" reconciled, and it can lead to finding errors or mistakes in the system." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1247 +msgid "" +"Your accountant will probably like to check your items in the balance sheet " +"and do some Journal Entries for:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1250 +msgid "" +"Manual year-end adjustments, using the **Journal Audit** report (For " +"example, the **Current Earnings for the Year** and **Retained Earnings " +"reports**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1253 +msgid "**Depreciation Journals**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1255 +msgid "**Tax Adjustments**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1257 +msgid "" +"If your accountant is on the year-end audit, they will want to have copies " +"of the balance sheet items (such as loans, bank accounts, prepayments, sales" +" tax reports, etc ...) to compare against. your balances in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1261 +msgid "" +"During this process, it is a good practice setting the **Closing Date for " +"Non-Advisers** to the last day of the preceding financial year, which is set" +" under the accounting settings. In this way, the accountant can trust that " +"no one else is changing the previous year's transactions while auditing the " +"books." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Fiscal year" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1271 +msgid "Accounting Closing Process" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1273 +msgid "" +"In Odoo there is no need to make a specific year-end entry to close the " +"reporting income accounts . The result of the exercise is automatically " +"calculated in the account type (Current Year Earnings) and the difference " +"between Income - Expenses will be accumulated to calculate it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1277 +msgid "" +"The reports are created in real-time, which means that the **Income Report**" +" corresponds directly to the closing date of the year that you specify in " +"Odoo. In addition, at any time that you generate the **Income Report**, the " +"start date will correspond to the start date of the **Fiscal Year** and the " +"account balances will all be 0." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1282 +msgid "" +"As of December 31, the Balance Sheet shows the earnings of the Current Year " +"that do not have been recognized (Account type Total Current Year " +"Unallocated Earnings in MX account 305.01.01 ['current year earnings' type])" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Balance sheet closing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1290 +msgid "" +"The accountant should create a Journal Entry to recognize the result of the " +"year in Accumulated Earnings from previous years on the account \"previous " +"years results\" account (304.01.01 in Mexico) - that is an equity account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1294 +msgid "" +"After posting the Journal Entry, click on *Mark as Closing Entry for the " +"Fiscal Year*. This step is important because it is linked to the Trial " +"Balance report. If this Journal Entry is not marked as a Closing Entry, the " +"Trial Balance won't be correct." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1298 +msgid "The simplified accounting entry would look like this:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Closing journal entry" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1304 +msgid "" +"Once the accountant has created the journal entry to locate the **Current " +"Earnings for the Year**, they must set the **Closing Date** to the last day " +"of the fiscal year. Making sure that before doing this, whether or not the " +"current gain of the year in the **Balance Sheet** is properly reporting a " +"balance 0." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Check BS closing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1314 +msgid "Extra Recommended features" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1317 +msgid "Contacts App (Free)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1319 +msgid "" +"If you want to properly manage your customers, suppliers and addresses, this" +" module, even if it is not a technical need, it is highly recommended to " +"install it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1323 +msgid "Multi-currency (Requires Accounting application)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1325 +msgid "" +"In Mexico, almost all companies send and receive payments in different " +"currencies. If you want to do this you can enable the use of multi-currency." +" You should also enable synchronization with the **Mexican Bank Service**, " +"as this would allow you to automatically have the exchange rate from the SAT" +" without having to manually create this information every day in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1330 +msgid "Go to settings and enable the multi-currency feature." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Multi currency configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1337 +msgid "" +"Enabling Explicit errors on the CFDI using the XSD local validator (CFDI " +"3.3)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1339 +msgid "" +"Frequently you want receive explicit errors from the fields incorrectly set " +"on the xml, those errors are better informed to the user if the check is " +"enable, to enable the Check with xsd feature follow the next steps (with the" +" :ref:`developer mode ` enabled)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1344 +msgid "" +"Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1345 +msgid "Look for the Action called \"Download XSD files to CFDI\"" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1346 +msgid "Click on button \"Create Contextual Action\"" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1347 +msgid "" +"Go to the company form :menuselection:`Settings --> Users&Companies --> " +"Companies`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1348 +msgid "Open any company you have." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1349 +msgid "Click on \"Action\" and then on \"Download XSD file to CFDI\"." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Download XSD files to CFDI from the Companies list view on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1355 +msgid "" +"Now you can make an invoice with any error (for example a product without " +"code which is pretty common) and an explicit error will be shown instead a " +"generic one with no explanation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1360 +msgid "If you see an error like this:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "``The cfdi generated is not valid``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "" +"``attribute decl. 'TipoRelacion', attribute 'type': The QName value " +"'{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_TipoRelacion' does " +"not resolve to a(n) simple type definition., line 36``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1367 +msgid "" +"This can be caused by a database backup restored in another server, or when " +"the XSD files are not correctly downloaded. Follow the same steps as above " +"but:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1371 +msgid "Go to the company in which the error occurs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1372 +msgid "Click on *Action* and then on *Download XSD file to CFDI*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1375 +msgid "Common problems and errors" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1377 +msgid "**Error messages** (Only applicable on CFDI 3.3):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1379 +msgid "" +"``9:0:ERROR:SCHEMASV:SCHEMAV_CVC_MINLENGTH_VALID: Element " +"'{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': " +"[facet 'minLength'] The value '' has a length of '0'; this underruns the " +"allowed minimum length of '1'.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1384 +msgid "" +"``9:0:ERROR:SCHEMASV:SCHEMAV_CVC_PATTERN_VALID: Element " +"'{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': " +"[facet 'pattern'] The value '' is not accepted by the pattern " +"'[^|]{1,100}'.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1388 +msgid "" +"**Solution**: You forgot to set the proper \"Reference\" field in the " +"product, please go to the product form and set your internal reference " +"properly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1392 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1433 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1464 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1485 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1493 +msgid "**Error messages**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1394 +msgid "" +"``6:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element " +"'{http://www.sat.gob.mx/cfd/3}RegimenFiscal': The attribute 'Regimen' is " +"required but missing.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1397 +msgid "" +"``5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element " +"'{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'RegimenFiscal' is " +"required but missing.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1400 +msgid "" +"**Solution**: You forgot to set the proper \"Fiscal Position\" on the " +"partner of the company. Go to customers, remove the customer filter and look" +" for the partner called as your company and set the proper fiscal position " +"which is the kind of business your company does related to SAT list of " +"possible values, another option can be that you forgot to follow the " +"considerations about fiscal positions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1407 +msgid "" +"You need to go to Fiscal Position settings and set the proper code (it is " +"the first 3 numbers of the name), for example, for the test, you need to set" +" 601, it will look like the picture." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "Fiscal position error" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1415 +msgid "" +"For testing purposes this value must be set to ``601 - General de Ley " +"Personas Morales`` which is the one required for the VAT demo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1418 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1450 +msgid "**Error message**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1420 +msgid "" +"``2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element " +"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'FormaPago': [facet " +"'enumeration'] The value '' is not an element of the set {'01', '02', '03', " +"'04', '05', '06', '08', '12', '13', '14', '15', '17', '23', '24', '25', " +"'26', '27', '28', '29', '30', '99'}``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1426 +msgid "**Solution**: The payment method is required on your invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Payment method error" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1435 +msgid "" +"``2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element " +"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': " +"[facet 'enumeration'] The value '' is not an element of the set {'00``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1438 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1452 +msgid "" +"``2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element " +"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' " +"is not a valid value of the atomic type " +"'{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1441 +msgid "" +"``5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element " +"'{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'Rfc' is required but " +"missing.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1444 +msgid "" +"**Solution**: You must configure your company address correctly, this is a " +"mandatory group of fields, you can go to your company configuration in " +":menuselection:`Settings --> Users & Companies --> Companies` and fill " +"complete all the mandatory fields for your address by following the steps in" +" this section: :ref:`mx-legal-info`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1457 +msgid "" +"**Solution**: The postal code of your company address is not valid for " +"Mexico, please correct it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "ZIP code error" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1466 +msgid "" +"``18:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element " +"'{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is " +"required but missing.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1469 +msgid "" +"``34:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element " +"'{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is " +"required but missing.\", '')``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1473 +msgid "" +"**Solution**: Set the Mexican name for the 0% and 16% tax in your system and" +" use it on the invoice. Your tax, which represents 16% VAT and 0%, must have" +" the **Factor Type** field set to *Tasa*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "Factor type error" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "Rate error" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "``CCE159``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "" +"``The XXXX attribute must be registered if the key of cce11: " +"ComercioExterior: TipoOperacion registered is '1' or '2'.``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1491 +msgid "**Solution**: It is necessary to specify the Incoterm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "``CCE209``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "" +"``The attribute cce11: Foreign Trade: Goods: Goods: Customs Unit must have " +"the value specified in the catalog catCFDI: c_FraccionArancelaria column " +"'UMT' when the attribute cce11: Foreign Trade: Goods: Me``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1500 +msgid "" +"**Solution**: The Tariff Fraction must have the code of the unit of measure " +"01, corresponding to Kilograms." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1504 +msgid "Glossary" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1506 +msgid "" +":abbr:`CFDI (Comprobante Fiscal Digital por Internet)`: Online Digital Tax " +"Receipt" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1507 +msgid ":abbr:`CSD (Certificado de Sello Digital)`: Digital Seal Certificate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1508 +msgid "" +":abbr:`PAC (Proveedores Autorizados de Certificación)`: Authorized " +"Certification Provider" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1509 +msgid "Stamp: Digital signature of the electronic invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1510 +msgid "" +"Addenda: Complement of information that can be attached to an Internet " +"Digital Tax Receipt (CFDI) normally required by certain companies in Mexico " +"such as Walmart, Tiendas Sorianas, etc." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1512 +msgid "" +":abbr:`UUID (Universally Unique Identifier)`: It is the acronym in English " +"of the Universally Unique Identifier. The UUID is the equivalent of Folio " +"Fiscal, it is composed of 32 hexadecimal digits, shown in 5 groups separated" +" by hyphens." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1515 +msgid "" +"LCO: List of Obliged Taxpayers (LCO) is a list issued by the SAT that " +"accounts for all the taxpayers whom it authorizes the issuance of invoices " +"and payroll receipts. This means that, to be able to electronically bill " +"your clients, you must be in this database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:3 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:6 +msgid "XAF Export" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:8 +msgid "" +"With the Dutch accounting localization installed, you will be able to export" +" all your accounting entries in XAF format. For this, you have to go in " +":menuselection:`Accounting --> Reporting --> General Ledger`, you define the" +" entries you want to export using the filters (period, journals, ...) and " +"then you click on the button **EXPORT (XAF)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:15 +msgid "Dutch Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:17 +msgid "" +"If you install the Dutch accounting localization, you will have access to " +"some reports that are specific to the Netherlands such as :" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:21 +msgid "Tax Report (Aangifte omzetbelasting)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:22 +msgid "Intrastat Report (ICP)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:3 +msgid "Peru" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:8 +msgid "" +"The Peruvian localization has been improved and extended, in this version " +"the next modules are available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:11 +msgid "" +"**l10n_pe**: Adds accounting features for the Peruvian localization, which " +"represent the minimal configuration required for a company to operate in " +"Peru and under the SUNAT regulations and guidelines. The main elements " +"included in this module are: Chart of account, taxes, document types." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:16 +msgid "" +"**l10n_pe_edi**: includes all technical and functional requirements to " +"generate and validate Electronic Invoice, based on the SUNAT specification " +"to create and process valid electronic documents, for more technical detail " +"you can access the `SUNAT EDI specifications " +"`_, that keeps track of new changes and " +"updates. The features of this module are based on the resolutions published " +"on the `SUNAT Legislation " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:28 +msgid "Install the Peruvian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:30 +msgid "" +"Go to *Apps* and search for Peru, then click Install in the module Peru EDI." +" This module has a dependency with *Peru - Accounting*. In case this last " +"one is not installed, Odoo installs it automatically within EDI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "The \"Module\" filter is set on \"Peru\"" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:39 +msgid "" +"When you install a database from scratch selecting Peru as country, Odoo " +"automatically installs the base module: Peru - Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:45 +msgid "" +"In addition to the basic information in the Company, we need to set Peru as " +"the Country, this is essential for the Electronic Invoice to work properly. " +"The field **Address Type Code** represents the establishment code assigned " +"by the SUNAT when companies register their RUC (Unique Contributor " +"Registration):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Company data for Peru including RUC and Address type code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:56 +msgid "" +"In case the Address type code is unknown, you can set it as the default " +"value: 0000. Be aware that if an incorrect value is entered, the Electronic " +"invoice validation might have errors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:60 +msgid "The NIF should be set following the RUC format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:64 +msgid "Chart of Account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:66 +msgid "" +"The chart of accounts is installed by default as part of the set of data " +"included in the localization module, the accounts are mapped automatically " +"in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:71 +msgid "Default Account Receivable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:73 +msgid "" +"The chart of accounts for Peru is based on the most updated version of the " +":abbr:`PCGE (Plan Contable General Empresarial)`, which is grouped in " +"several categories and is compatible with NIIF accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:78 +msgid "Accounting Settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:80 +msgid "" +"Once the modules are installed and the basic information of your company is " +"set, you need to configure the elements required for Electronic Invoice. For" +" this, go to :menuselection:`Accounting --> Settings --> Peruvian " +"Localization`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:85 +msgid "Basic Concepts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:87 +msgid "Here are some terms that are essential on the Peruvian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:89 +msgid "" +"**EDI**: Electronic Data Interchange, which in this refers to the Electronic" +" Invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:90 +msgid "" +"**SUNAT**: is the organization that enforces customs and taxation in Peru." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:91 +msgid "" +"**OSE**: Electronic Service Operator, `OSE SUNAT's definition " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:93 +msgid "**CDR**: Receipt certificate (Constancia de Recepción)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:94 +msgid "" +"**SOL Credentials**: Sunat Operaciones en Línea. User and password are " +"provided by the SUNAT and grant access to Online Operations systems." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:99 +msgid "Signature Provider" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:101 +msgid "" +"As part of the requirements for Electronic Invoice in Peru, your company " +"needs to select a Signature Provider that will take care of the document " +"signing process and manage the SUNAT validation response. Odoo offers three " +"options:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:105 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:112 +msgid "IAP (Odoo In-App Purchase)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:106 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:170 +msgid "Digiflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:107 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:186 +msgid "SUNAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:109 +msgid "" +"Please refer to the sections below to check the details and considerations " +"for each option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:114 +msgid "" +"This is the default and the suggested option, considering the digital " +"ceritificate is included as part of the service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "IAP option as signature providers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:122 +msgid "What is the IAP?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:124 +msgid "" +"This is a signature service offered directly by Odoo, the service takes care" +" of the next process:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:126 +msgid "" +"Provides the Electronic invoice Certificate, so you do not need to acquire " +"one by yourself." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:127 +msgid "Send the document to the OSE, in this case, Digiflow." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:128 +msgid "Receive the OSE validation and CDR." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:131 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:133 +msgid "" +"The service requires Credits in order to process your electronic documents. " +"Odoo provides 1000 credits for free in new databases. After these credits " +"are consumed, you need to buy a Credit Package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:138 +msgid "Credits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:138 +msgid "EUR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:140 +msgid "22" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:142 +msgid "5000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:142 +msgid "110" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:144 +msgid "10,000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:144 +msgid "220" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:146 +msgid "20,000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:146 +msgid "440" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:149 +msgid "The credits are consumed per each document that is sent to the OSE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:152 +msgid "" +"If you have a validation error and the document needs to be sent one more " +"time, one additional credit will be charged. Therefore, it is paramount that" +" you verify all information is correct before sending your document to the " +"OSE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:157 +msgid "What do you need to do?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:159 +msgid "" +"In Odoo, once your enterprise contract is activated and you start working in" +" Production, you need to buy credits once the first 1000 are consumed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:161 +msgid "" +"As Digiflow is the OSE used in the IAP, you need to affiliate it as the " +"official OSE for your company on the SUNAT website. This is a simple " +"process. For more information, please check `OSE Affiliation guide " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:165 +msgid "" +"Register Digiflow as the authorized PSE, please check `PSE Affiliation guide" +" " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:172 +msgid "" +"This option can be used as an alternative, instead of using the IAP services" +" you can send your document validation directly to Digiflow. In this case " +"you need to consider:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:175 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:192 +msgid "" +"Buy your own digital Certificate: For more detail regarding the official " +"vendor list, and the process to acquire it, please refer to `SUNAT Digital " +"Ceritifcates " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:178 +msgid "" +"Sign a service agreement directly with `Digiflow " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:179 +msgid "Provide your SOL credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:188 +msgid "" +"In case your company wants to sign directly with the SUNAT, it is possible " +"to select this option in your configuration. In this case you need to " +"consider: - Get the SUNAT Certification process accepted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:196 +msgid "Provide you SOL credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:199 +msgid "" +"When using direct connection with the SUNAT, the SOL User must be set with " +"the Company RUT + User Id. Example: ``20121888549JOHNSMITH``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:203 +msgid "Testing environment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:205 +msgid "" +"Odoo provides a testing environment that can be activated before your " +"company goes into production." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:207 +msgid "" +"When using the testing environment and the IAP signature, you don’t need to " +"buy testing credits for your transactions as all of them are validated by " +"default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:211 +msgid "" +"By default the databases are set to work on production, make sure to enable " +"the testing mode if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:217 +msgid "" +"In case you don’t use Odoo IAP, in order to generate the electronic invoice " +"signature, a digital certificate with the extension ``.pfx`` is required. " +"Proceed to this section and load your file and password." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "EDI Certificate wizard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:228 +msgid "" +"The official currency exchange rate in Peru is provided by the Bank of Peru." +" Odoo can connect directly to its services and get the currency rate either " +"automatically or manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Bank of Peru is displayed in Multicurrency Service option" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:235 +msgid "" +"Please refer to the next section in our documentation for more information " +"about :doc:`multicurrencies <../accounting/get_started/multi_currency>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:239 +msgid "Configure Master data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:244 +msgid "" +"As part of the localization module the taxes are created automatically with " +"their related financial account and electronic invoice configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "List of default taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:252 +msgid "EDI Configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:254 +msgid "" +"As part of the taxes configuration, there are three new fields required for " +"electronic invoice, the taxes created by default have this data included, " +"but in case you create new taxes make sure you fill in the fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Taxes EDI data for Peru" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:266 +msgid "" +"There are two main fiscal positions included by default when you install the" +" Peruvian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:268 +msgid "" +"**Extranjero - Exportación**: Set this fiscal position on customers for " +"Exportation transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:270 +msgid "**Local Peru**: Set this fiscal position on local customers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:275 +msgid "" +"In some Latin American countries, including Peru, some accounting " +"transactions like invoices and vendor bills are classified by document " +"types, defined by the government fiscal authorities, in this case by the " +"SUNAT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:279 +msgid "" +"Each document type can have a unique sequence per journal where it is " +"assigned. As part of the localization, the Document Type includes the " +"country on which the document is applicable;the data is created " +"automatically when the localization module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:283 +msgid "" +"The information required for the document types is included by default so " +"the user does not need to fill anything on this view:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Document Type list" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:291 +msgid "" +"Currently the documents supported on customer invoices are: Invoice, Boleta," +" Debit Note and Credit Note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:297 +msgid "" +"When creating Sales Journals, the following information must be filled, in " +"addition to the standard fields on the Journals:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:301 +msgid "Use Documents" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:303 +msgid "" +"This field is used to define if the journal uses Document Types. It is only " +"applicable to Purchase and Sales journals, which are the ones that can be " +"related to the different set of document types available in Peru. By " +"default, all the sales journals created use documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:308 +msgid "Electronic Data Interchange" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:310 +msgid "" +"This section indicates which EDI workflow is used in the invoice, for Peru " +"we must select “Peru UBL 2.1”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Journal EDI field" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:318 +msgid "" +"By default, the value Factur-X (FR) is always displayed, make sure you can " +"uncheck it manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:326 +msgid "" +"As part of the Peruvian localization, the identification types defined by " +"the SUNAT are now available on the Partner form, this information is " +"essential for most transactions either on the sender company and in the " +"customer, make sure you fill in this information in your records." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Partner identification type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:336 +msgid "Product" +msgstr "Produkt" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:338 +msgid "" +"Additional to the basic information in your products, for the Peruvian " +"localization, the UNSPC Code on the product is a required value to be " +"configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "UNSPC Code on products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:350 +msgid "Customer invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:353 +msgid "EDI Elements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:355 +msgid "" +"Once you have configured your master data, the invoices can be created from " +"your sales order or manually. Additional to the basic invoice information " +"described on :doc:`our page about the invoicing process " +"<../accounting/customer_invoices/overview>`, there are a couple of fields " +"required as part of the Peru EDI:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:360 +msgid "" +"**Document type**: The default value is “Factura Electronica” but you can " +"manually change the document type if needed and select Boleta for example." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Invoice document type field on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:367 +msgid "" +"**Operation type**: This value is required for Electronic Invoice and " +"indicates the transaction type, the default value is “Internal Sale” but " +"another value can be selected manually when needed, for example Export of " +"Goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Invoice operation type field on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:375 +msgid "" +"**EDI Affectation Reason**: In the invoice lines, additional to the Tax " +"there is a field “EDI Affectation Reason” that determines the tax scope " +"based on the SUNAT list that is displayed. All the taxes loaded by default " +"are associated with a default EDI affection reason, if needed you can " +"manually select another one when creating the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Tax affectation reason in invoice line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:387 +msgid "" +"Once you check all the information in your invoice is correct, you can " +"proceed to validate it. This action registers the account move and triggers " +"the Electronic invoice workflow to send it to the OSE and the SUNAT. The " +"following message is displayed at the top of the invoice:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Sending of EDI Invoice in blue" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:395 +msgid "" +"Asynchronous means that the document is not sent automatically after the " +"invoice has been posted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:398 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:492 +msgid "Electronic Invoice Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:400 +msgid "" +"**To be Sent**: To be sent: Indicates the document is ready to be sent to " +"the OSE, this can be done either automatically by Odoo with a *cron* that " +"runs every hour, or the user can send it immediately by clicking on the " +"button “Sent now”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Send EDI manually" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:408 +msgid "" +"**Sent**: Indicates the document was sent to the OSE and was successfully " +"validated. As part of the validation a ZIP file is downloaded and a message " +"is logged in the chatter indicating the correct Government validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Message on chatter when the invoice is valid" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:416 +msgid "" +"In case there is a validation error the Electronic Invoice status remains in" +" “To be sent” so the corrections can be made and the invoice can be sent " +"again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:420 +msgid "" +"One credit is consumed each time that you send a document for validation, in" +" this sense if an error is detected on an invoice and you send it one more " +"time, two credits are consumed in total." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:427 +msgid "" +"There are multiple reasons behind a rejection from the OSE or the SUNAT, " +"when this happens Odoo sends a message at the top of the invoice indicating " +"the error details and in the most common cases a hint to fix the issue." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:431 +msgid "If a validation error is received, you have two options:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:433 +msgid "" +"In case the error is related to master data on the partner, customer or " +"taxes, you can simply apply the change on the record (example customer " +"identification type) and once it is done click on the Retry button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:436 +msgid "" +"If the error is related to some data recorded on the invoice directly " +"(Operation type, missing data on the invoice lines), the correct solution is" +" to reset the invoice to Draft, apply the changes, and then send the invoice" +" again to the SUNAT for another validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "List of common errors on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:445 +msgid "" +"For more detail please refert to `Common errors in SUNAT " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:451 +msgid "" +"After the invoice is accepted and validated by the SUNAT, the invoice PDF " +"report can be printed. The report includes a QR code, indicating the invoice" +" is a valid fiscal document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:459 +msgid "IAP Credits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:461 +msgid "" +"Odoo’s Electronic IAP offers 1000 credits for free, after these credits are " +"consumed in your production database, your company must buy new credits in " +"order to process your transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:464 +msgid "" +"Once you run out of credits a red label is displayed at the top of the " +"invoice indicating that additional credits are required, you can easily buy " +"them by accessing the link provided in the message." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Buying credits in the IAP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:472 +msgid "" +"In the IAP service includes packages with different pricing based on the " +"number of credits. The price list in the IAP is always displayed in EUR." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:476 +msgid "Special Use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:479 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:515 +msgid "Cancellation process" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:481 +msgid "" +"Some scenarios require an invoice cancellation, for example, when an invoice" +" was created by mistake. If the invoice was already sent and validated by " +"the SUNAT, the correct way to proceed is by clicking on the button Request " +"Cancellation:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Request invoice cancellation button" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:489 +msgid "In order to cancel an invoice, please provide a cancellation Reason." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:494 +msgid "" +"**To Cancel**: Indicates the cancellation request is ready to be sent to " +"the OSE, this can be done either automatically by Odoo with a *cron* that " +"runs every hour, or the user can send it immediately by clicking on the " +"button “Send now”. Once it is sent, a cancellation ticket is created, as a " +"result the next message and CDR File are logged in the chatter:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Cancellation CDR sent by the SUNAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:503 +msgid "" +"**Cancelled**: Indicates the cancellation request was sent to the OSE and " +"was successfully validated. As part of the validation a ZIP file is " +"downloaded and a message is logged in the chatter indicating the correct " +"Government validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "nvoice after cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:512 +msgid "One credit is consumed on each cancellation request." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:517 +msgid "" +"When creating exportation invoices, take into account the next " +"considerations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:519 +msgid "The Identification type on your customer must be Foreign ID." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:520 +msgid "Operation type in your invoice must be an Exportation one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:521 +msgid "The taxes included in the invoice lines should be EXP taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Exportation invoices main data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:528 +msgid "Advance Payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:530 +msgid "Create the advance payment Invoice and apply its related payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:531 +msgid "Create the final invoice without considering the advance payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:532 +msgid "" +"Create a credit note for the Final invoice with the advance payment amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:533 +msgid "Reconcile the Credit note with the final invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:534 +msgid "" +"The remaining balance on the final invoice should be paid with a regular " +"payment transaction." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:537 +msgid "Detraction Invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:539 +msgid "" +"When creating invoices that is subject to Detractions, take into account the" +" next considerations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:541 +msgid "" +"All the products included in the invoice must have these fields configured:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Detraction fields on products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:547 +msgid "Operation type in your invoice must be ``1001``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Detraction code on invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:556 +msgid "" +"When a correction or refund is needed over a validated invoice, a credit " +"note must be generated, for this just click on the button “Add Credit Note”," +" a part of the Peruvian localization you need to prove a Credit Reason " +"selecting one of the options in the list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Add Credit Note from invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:565 +msgid "" +"When creating your first credit Note, select the Credit Method: Partial " +"Refund, this allows you to define the credit note sequence." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:568 +msgid "By default the Credit Note is set in the document type:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Credit Note document type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:574 +msgid "" +"To finish the workflow please follow the instructions on :doc:`our page " +"about Credit Notes <../accounting/customer_invoices/credit_notes>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:578 +msgid "" +"The EDI workflow for the Credit notes works in the same way as the invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:583 +msgid "" +"As part of the Peruvian localization, besides creating credit notes from an " +"existing document you can also create debit Notes. For this just use the " +"button “Add Debit Note”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:586 +msgid "By default the Debit Note is set in the document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:3 +msgid "Spain" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:6 +msgid "Spanish Chart of Accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:8 +msgid "" +"In Odoo, there are several Spanish Chart of Accounts that are available by " +"default:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:10 +msgid "PGCE PYMEs 2008" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:11 +msgid "PGCE Completo 2008" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:12 +msgid "PGCE Entitades" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:14 +msgid "" +"You can choose the one you want by going in :menuselection:`Accounting --> " +"Configuration` then choose the package you want in the **Fiscal " +"Localization** section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:20 +msgid "" +"When you create a new Odoo Online database, the PGCE PYMEs 2008 is installed" +" by default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:23 +msgid "Spanish Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:25 +msgid "" +"If the Spanish Accounting Localization is installed, you will have access to" +" accounting reports specific to Spain:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:28 +msgid "Tax Report (Modelo 111)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:29 +msgid "Tax Report (Modelo 115)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:30 +msgid "Tax Report (Modelo 303)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:3 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:6 +msgid "ISR (In-payment Slip with Reference number)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:8 +msgid "" +"The ISRs are payment slips used in Switzerland. You can print them directly " +"from Odoo. On the customer invoices, there is a new button called *Print " +"ISR*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:16 +msgid "" +"The button *Print ISR* only appears there is well a bank account defined on " +"the invoice. You can use CH6309000000250097798 as bank account number and " +"010391391 as CHF ISR reference." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:23 +msgid "Then you open a pdf with the ISR." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:28 +msgid "" +"There exists two layouts for ISR: one with, and one without the bank " +"coordinates. To choose which one to use, there is an option to print the " +"bank information on the ISR. To activate it, go in " +":menuselection:`Accounting --> Configuration --> Settings --> Customer " +"Invoices` and enable **Print bank on ISR**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:38 +msgid "ISR reference on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:40 +msgid "" +"To ease the reconciliation process, you can add your ISR reference as " +"**Payment Reference** on your invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:43 +msgid "" +"To do so, you need to configure the Journal you usually use to issue " +"invoices. Go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open the Journal you want to modify (By default, the Journal is named " +"*Customer Invoices*), click en *Edit*, and open the *Advanced Settings* tab." +" In the **Communication Standard** field, select *Switzerland*, and click on" +" *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst-1 +msgid "" +"Configure your Journal to display your ISR as payment reference on your " +"invoices in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:53 +msgid "Currency Rate Live Update" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:55 +msgid "" +"You can update automatically your currencies rates based on the Federal Tax " +"Administration from Switzerland. For this, go in :menuselection:`Accounting " +"--> Settings`, activate the multi-currencies setting and choose the service " +"you want." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:64 +msgid "Updated VAT for January 2018" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:66 +msgid "" +"Starting from the 1st January 2018, new reduced VAT rates will be applied in" +" Switzerland. The normal 8.0% rate will switch to 7.7% and the specific rate" +" for the hotel sector will switch from 3.8% to 3.7%." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:71 +msgid "" +"How to update your taxes in Odoo Enterprise (Odoo Online or On-premise)?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:73 +msgid "" +"If you have the V11.1 version, all the work is already been done, you don't " +"have to do anything." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:76 +msgid "" +"If you have started on an earlier version, you first have to update the " +"module \"Switzerland - Accounting Reports\". For this, you go in " +":menuselection:`Apps --> remove the filter \"Apps\" --> search for " +"\"Switzerland - Accounting Reports\" --> open the module --> click on " +"\"upgrade\"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:83 +msgid "" +"Once it has been done, you can work on creating new taxes for the updated " +"rates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:87 +msgid "" +"**Do not suppress or modify the existing taxes** (8.0% and 3.8%). You want " +"to keep them since you may have to use both rates for a short period of " +"time. Instead, remember to archive them once you have encoded all your 2017 " +"transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:92 +msgid "The creation of such taxes should be done in the following manner:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:94 +msgid "" +"**Purchase taxes**: copy the origin tax, change its name, label on invoice, " +"rate and tax group (effective from v10 only)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:97 +msgid "" +"**Sale taxes**: copy the origin tax, change its name, label on invoice, rate" +" and tax group (effective from v10 only). Since the vat report now shows the" +" details for old and new rates, you should also set the tags accordingly to" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:102 +msgid "" +"For 7.7% taxes: Switzerland VAT Form: grid 302 base, Switzerland VAT Form: " +"grid 302 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:105 +msgid "" +"For 3.7% taxes: Switzerland VAT Form: grid 342 base, Switzerland VAT Form: " +"grid 342 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:108 +msgid "" +"You'll find below, as examples, the correct configuration for all taxes " +"included in Odoo by default" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tax Name**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Rate**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Label on Invoice**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tax Group (effective from V10)**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tax Scope**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tag**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +msgid "TVA 7.7% sur achat B&S (TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "7.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +msgid "7.7% achat" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "TVA 7.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +msgid "Switzerland VAT Form: grid 400" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +msgid "TVA 7.7% sur achat B&S (Incl. TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +msgid "7.7% achat Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +msgid "TVA 7.7% sur invest. et autres ch. (TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +msgid "7.7% invest." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "Switzerland VAT Form: grid 405" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +msgid "TVA 7.7% sur invest. et autres ch. (Incl. TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +msgid "7.7% invest. Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +msgid "TVA 3.7% sur achat B&S (TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "3.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +msgid "3.7% achat" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "TVA 3.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +msgid "TVA 3.7% sur achat B&S (Incl. TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +msgid "3.7% achat Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +msgid "TVA 3.7% sur invest. et autres ch. (TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +msgid "3.7% invest" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "TVA 3.7% sur invest. et autres ch. (Incl. TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "3.7% invest Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +msgid "TVA due a 7.7% (TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "" +"Switzerland VAT Form: grid 302 base, Switzerland VAT Form: grid 302 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "TVA due à 7.7% (Incl. TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "7.7% Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +msgid "TVA due à 3.7% (TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "" +"Switzerland VAT Form: grid 342 base, Switzerland VAT Form: grid 342 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "TVA due a 3.7% (Incl. TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "3.7% Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:139 +msgid "" +"If you have questions or remarks, please contact our support using " +"odoo.com/help." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:143 +msgid "" +"Don't forget to update your fiscal positions. If you have a version 11.1 (or" +" higher), there is nothing to do. Otherwise, you will also have to update " +"your fiscal positions accordingly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:19 +msgid ":guilabel:`United Arab Emirates - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:20 +msgid "``l10n_ae``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:21 +msgid "" +"Default :doc:`fiscal localization package " +"`. Includes all accounts, taxes," +" and reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`U.A.E. - Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:24 +msgid "``l10n_ae_hr_payroll``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`U.A.E. - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:27 +msgid "``l10n_ae_hr_payroll_account``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:29 +msgid ":guilabel:`United Arab Emirates - Point of Sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:30 +msgid "``l10n_ae_pos``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:31 +msgid "Includes the UAE-compliant POS receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "Select the modules to install." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:40 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Chart of Accounts` to" +" view all default accounts available for the UAE localization package. You " +"can filter by :guilabel:`Code` using the numbers on the far left or by " +"clicking on :menuselection:`Group By --> Account Type`. You can " +":guilabel:`Enable`/:guilabel:`Disable` reconciliation or **configure** " +"specific accounts according to your needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:47 +msgid "" +"Always keep at least one **receivable account** and one **payable account** " +"active." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:48 +msgid "" +"It is also advised to **keep the accounts below active**, as they are used " +"either as transitory accounts by Odoo or are specific to the **UAE " +"localization package**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:55 +msgid "Account Name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:57 +msgid "102011" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:60 +msgid "102012" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:61 +msgid "Accounts Receivable (POS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:63 +msgid "201002" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:64 +msgid "Payables" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:66 +msgid "101004" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:69 +msgid "105001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:70 +msgid "Cash" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:72 +msgid "100001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:73 +msgid "Liquidity Transfer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:75 +msgid "101002" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:78 +msgid "101003" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:79 +msgid "Outstanding Payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:81 +msgid "104041" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:82 +msgid "VAT Input" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:84 +msgid "100103" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:85 +msgid "VAT Receivable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:87 +msgid "101001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:88 +msgid "Bank Suspense Account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:90 +msgid "201017" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:91 +msgid "VAT Output" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:93 +msgid "202001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:94 +msgid "End of Service Provision" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:96 +msgid "202003" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:97 +msgid "VAT Payable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:99 +msgid "999999" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:100 +msgid "Undistributed Profits/Losses" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:102 +msgid "400003" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:103 +msgid "Basic Salary" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:105 +msgid "400004" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:106 +msgid "Housing Allowance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:108 +msgid "400005" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:109 +msgid "Transportation Allowance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:111 +msgid "400008" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:112 +msgid "End of Service Indemnity" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:118 +msgid "" +"To access your taxes, go to :menuselection:`Accounting --> Configuration -->" +" Taxes`. Activate/deactivate, or :doc:`configure " +"` the taxes relevant to your " +"business by clicking on them. Remember to only set tax accounts on the " +"**5%** tax group, as other groups do not need closing. To do so, enable the " +":doc:`developer mode <../../general/developer_mode>` and go to " +":menuselection:`Configuration --> Tax Groups`. Then, set a :guilabel:`Tax " +"current account (payable)`, :guilabel:`Tax current account (receivable)`, " +"and an :guilabel:`Advance Tax payment account` for the **5%** group." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:127 +msgid "The :abbr:`RCM (Reverse Charge Mechanism)` is supported by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "Preview of the UAE localization package's taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:134 +msgid "Currency exchange rates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:136 +msgid "" +"To update the currency exchange rates, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies`. Click on the update button " +"(:guilabel:`🗘`) found next to the :guilabel:`Next Run` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:140 +msgid "" +"To launch the update automatically at set intervals, change the " +":guilabel:`Interval` from :guilabel:`Manually` to the desired frequency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:144 +msgid "" +"By default, the UAE Central Bank exchange rates web service is used. Several" +" other providers are available under the :guilabel:`Service` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:150 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:152 +msgid "" +"The :guilabel:`UAE - Payroll` module creates the necessary **salary rules** " +"in the Payroll app in compliance with the UAE rules and regulations. The " +"salary rules are linked to the corresponding accounts in the **chart of " +"accounts**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "The UAE Employee Payroll Structure." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:161 +msgid "Salary rules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:163 +msgid "" +"To apply these rules to an employee's contract, go to " +":menuselection:`Payroll --> Contracts --> Contracts` and select the " +"employee's contract. In the :guilabel:`Salary Structure Type` field, select " +":guilabel:`UAE Employee`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "Select the Salary Structure Type to apply to the contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:171 +msgid "" +"Under the :guilabel:`Salary Information` tab, you can find details such as " +"the:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:173 +msgid ":guilabel:`Wage`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:174 +msgid ":guilabel:`Housing Allowance`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:175 +msgid ":guilabel:`Transportation Allowance`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:176 +msgid ":guilabel:`Other Allowances`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:177 +msgid "" +":guilabel:`Number of Days`: used to calculate the :ref:`end of service " +"provision `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:181 +msgid "" +"**Leave deductions** are calculated using a salary rule linked to the " +"**unpaid leave** time-off type;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:183 +msgid "" +"Any other deductions or reimbursements are made *manually* using other " +"inputs;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:184 +msgid "" +"**Overtimes** are added *manually* by going to :menuselection:`Work Entries " +"--> Work Entries`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:185 +msgid "" +"**Salary attachments** are generated by going to :menuselection:`Contracts " +"--> Salary Attachments`. Then, :guilabel:`Create` an attachment and select " +"the :guilabel:`Employee` and the :guilabel:`Type (Attachment of Salary, " +"Assignment of Salary, Child Support)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:190 +msgid "" +"To prevent a rule from appearing on a paycheck, go to " +":menuselection:`Payroll --> Configuration --> Rules`. Click on " +":guilabel:`UAE Employee Payroll Structure`, select the rule to hide, and " +"uncheck :guilabel:`Appears on Payslip`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:197 +msgid "End of service provision" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:199 +msgid "" +"The provision is defined as the total monthly allowance *divided* by 30 and " +"then *multiplied* by the number of days set in the field :guilabel:`Number " +"of days` at the bottom of a contract's form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:202 +msgid "" +"The provision is then calculated via a salary rule associated with two " +"accounts: the **End Of Service Indemnity (Expense account)** and the **End " +"of Service Provision (Non-current Liabilities account)**. The latter is used" +" to pay off the **end of service amount** by settling it with the **payables" +" account**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:208 +msgid "" +"The end of service amount is calculated based on the gross salary and the " +"start and end dates of the employee’s contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:214 +msgid "" +"The UAE localization package allows the generation of invoices in English, " +"Arabic, or both. The localization also includes a line to display the **VAT " +"amount** per line." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:3 +msgid "United Kingdom" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:8 +msgid "" +":ref:`Install ` the :guilabel:`UK - Accounting` and the " +":guilabel:`UK - Accounting Reports` modules to get all the features of the " +"UK localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:17 +msgid ":guilabel:`UK - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:18 +msgid "`l10n_uk`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:19 +msgid "CT600-ready chart of accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:20 +msgid "VAT100-ready tax structure" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:21 +msgid "Infologic UK counties listing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:22 +msgid ":guilabel:`UK - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:23 +msgid "`l10n_uk_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:24 +msgid "Accounting reports for the UK" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:25 +msgid "Allows sending the tax report via the MTD-VAT API to HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst-1 +msgid "Odoo uk packages" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:32 +msgid "Only UK-based companies can submit reports to HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:33 +msgid "" +"Installing the module :guilabel:`UK - Accounting Reports` installs all two " +"modules at once." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:36 +msgid "" +"`HM Revenue & Customs `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:37 +msgid "" +"`Overview of Making Tax Digital " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:43 +msgid "" +"The UK chart of accounts is included in the :guilabel:`UK - Accounting` " +"module. Go to :menuselection:`Accounting --> Configuration --> Accounting: " +"Chart of Accounts` to access it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:46 +msgid "" +"Setup your :abbr:`CoA (chart of accounts)` by going to " +":menuselection:`Accounting --> Configuration --> Settings --> Accounting " +"Import section` and choose to :guilabel:`Review Manually` or " +":guilabel:`Import (recommended)` your initial balances." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:53 +msgid "" +"As part of the localization module, UK taxes are created automatically with " +"their related financial accounts and configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:56 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes` " +"to update the :guilabel:`Default Taxes`, the :guilabel:`Tax Return " +"Periodicity` or to :guilabel:`Configure your tax accounts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:60 +msgid "" +"To edit existing taxes or to :guilabel:`Create` a new tax, go to " +":menuselection:`Accounting --> Configuration --> Accounting: Taxes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:64 +msgid ":doc:`taxes <../accounting/taxes>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:65 +msgid "" +"Tutorial: `Tax report and return `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:69 +msgid "Making Tax Digital (MTD)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:71 +msgid "" +"In the UK, all VAT-registered businesses have to follow the MTD rules by " +"using software to submit their VAT returns." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:74 +msgid "" +"The **UK - Accounting Reports** module enables you to comply with the `HM " +"Revenue & Customs `_ requirements regarding `Making Tax Digital " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:80 +msgid "" +"If your periodic submission is more than three months late, it is no longer " +"possible to submit it through Odoo, as Odoo only retrieves open bonds from " +"the last three months. Your submission has to be done manually by contacting" +" HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:85 +msgid "Register your company to HMRC before the first submission" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:87 +msgid "" +"Go to :menuselection:`Accounting --> Reporting --> Tax report` and click on " +":guilabel:`Connect to HMRC`. Enter your company information on the HMRC " +"platform. You only need to do it once." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:92 +msgid "" +"When entering your VAT number, do not add the GB country code. Only the 9 " +"digits are required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:95 +msgid "Periodic submission to HMRC" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 +msgid "" +"Import your obligations HMRC, filter on the period you want to submit, and " +"send your tax report by clicking :guilabel:`Send to HMRC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:101 +msgid "Periodic submission to HMRC for multi-company" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:103 +msgid "" +"Only one company and one user can connect to HMRC simultaneously. If several" +" UK-based companies are on the same database, the user who submits the HMRC " +"report must follow these instructions before each submission:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:107 +msgid "Log into the company for which the submission has to be done." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:108 +msgid "" +"Go to :guilabel:`General Settings`, and in the :guilabel:`Users` section, " +"click :guilabel:`Manage Users`. Select the user who will submit the VAT " +"return." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:110 +msgid "" +"Go to the :guilabel:`UK HMRC Integration` tab and click :guilabel:`Reset " +"Authentication Credentials` or :guilabel:`Remove Authentication Credentials`" +" button. Then click again to create new credentials. It is now possible to " +"submit the tax report for this company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:113 +msgid "Repeat the steps for other companies' HMRC submissions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:116 +msgid "" +"During this process, the :guilabel:`Connect to HMRC` button no longer " +"appears for other UK-based companies." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:5 +msgid "Payment acquirers (credit cards, online payments)" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:21 +msgid "" +"Odoo embeds several **payment acquirers** that allow your customers to pay " +"on their *Customer Portals* or your *eCommerce website*. They can pay sales " +"orders, invoices, or subscriptions with recurring payments with their " +"favorite payment methods such as **Credit Cards**." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:25 +msgid "" +"Offering several payment methods increases the chances of getting paid in " +"time, or even immediately, as you make it more convenient for your customers" +" to pay with the payment method they prefer and trust." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst-1 +msgid "" +"Pay online in the customer portal and select which payment acquirer to use." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:34 +msgid "" +"Odoo apps delegate the handling of sensitive information to the certified " +"payment acquirer so that you don't ever have to worry about PCI compliance." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:37 +msgid "" +"This means that no sensitive information (such as credit card numbers) is " +"stored on Odoo servers or Odoo databases hosted elsewhere. Instead, Odoo " +"apps use a unique reference number to the data stored safely in the payment " +"acquirers' systems." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:44 +msgid "Supported payment acquirers" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:46 +msgid "" +"From an accounting perspective, we can distinguish two types of payment " +"acquirers: the payment acquirers that are third-party services and require " +"you to follow another accounting workflow, and the payments that go directly" +" on the bank account and follow the usual reconciliation workflow." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:53 +msgid "Online payment acquirers" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:61 +msgid "Payment flow from" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:62 +msgid ":ref:`Save cards for later `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:63 +msgid ":ref:`Manual capture `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:64 +msgid ":ref:`Refunds `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:65 +msgid ":doc:`Adyen `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:66 +#: ../../content/applications/finance/payment_acquirers.rst:76 +msgid "Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:67 +#: ../../content/applications/finance/payment_acquirers.rst:77 +#: ../../content/applications/finance/payment_acquirers.rst:92 +#: ../../content/applications/finance/payment_acquirers.rst:117 +msgid "|V|" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:69 +msgid "Full and partial" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:70 +msgid ":doc:`Alipay `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:71 +#: ../../content/applications/finance/payment_acquirers.rst:81 +#: ../../content/applications/finance/payment_acquirers.rst:86 +#: ../../content/applications/finance/payment_acquirers.rst:91 +#: ../../content/applications/finance/payment_acquirers.rst:96 +#: ../../content/applications/finance/payment_acquirers.rst:101 +#: ../../content/applications/finance/payment_acquirers.rst:106 +#: ../../content/applications/finance/payment_acquirers.rst:111 +#: ../../content/applications/finance/payment_acquirers.rst:116 +msgid "The acquirer website" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:75 +msgid ":doc:`Authorize.Net `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:78 +msgid "Full only" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:80 +msgid ":doc:`Buckaroo `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:85 +msgid ":doc:`Mollie `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:90 +msgid ":doc:`Ogone `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:95 +msgid ":doc:`PayPal `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:100 +msgid "PayU Latam" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:105 +msgid "PayUMoney" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:110 +msgid ":doc:`SIPS `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:115 +msgid ":doc:`Stripe `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:124 +msgid "" +"Some of these online payment providers can also be added as :doc:`bank " +"accounts <../finance/accounting/bank>`, but this is **not** the same process" +" as adding them as payment acquirers. Payment acquirers allow customers to " +"pay online, and bank accounts are added and configured on your Accounting " +"app to do a bank reconciliation, which is an accounting control process." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:133 +msgid "Bank payments" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:0 +msgid ":doc:`Wire Transfer `" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:0 +msgid "" +"When selected, Odoo displays your payment information with a payment " +"reference. You have to approve the payment manually once you have received " +"it on your bank account." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:0 +msgid ":doc:`SEPA Direct Debit <../finance/accounting/payments/batch_sdd>`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:0 +msgid "" +"Your customers can sign a SEPA Direct Debit mandate online and get their " +"bank account charged directly." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:145 +msgid "Additional features" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:147 +msgid "" +"Some payment acquirers support additional features for the payment flow. " +"Refer to the :ref:`table above ` to " +"check if your payment acquirer supports these features." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:154 +msgid "Save cards for later" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:156 +msgid "" +"If your payment acquirer supports this feature, customers can choose to save" +" their card details as a **payment token** in Odoo. When they do, they will " +"not have to enter their card details again when making a subsequent payment." +" This is particularly useful for the eCommerce conversion rate and for " +"subscriptions that use recurring payments." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:161 +msgid "" +"Enable this feature by navigating to the :guilabel:`Configuration` tab from " +"your payment acquirer and by ticking the :guilabel:`Allow Saving Payment " +"Methods` checkbox." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:165 +msgid "" +"You remain fully PCI-compliant when you enable this feature because Odoo " +"does not store the card details directly. Instead, it creates a payment " +"token that only holds a reference to the card details stored on the payment " +"acquirer's server." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:172 +msgid "Manual capture" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:174 +msgid "" +"If your payment acquirer supports this feature, you can authorize and " +"capture payments in two steps instead of one. When you authorize a payment, " +"the funds are reserved on the customer's payment method but they are not " +"immediately charged. The charge is only made when you manually capture the " +"payment later on. You can also void the authorization to release the " +"reserved funds; this is equivalent to a regular cancellation. Capturing " +"payments manually can prove itself useful in many situations:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:181 +msgid "" +"Receive the payment confirmation and wait until the order is shipped to " +"capture the payment." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:182 +msgid "" +"Review and verify that orders are legitimate before the payment is completed" +" and the fulfillment process starts." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:184 +msgid "" +"Avoid potentially high processing fees for cancelled payments: payment " +"acquirers will not charge you for voiding an authorization." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:186 +msgid "" +"Hold a security deposit to return later, minus any deductions (e.g., after a" +" damage)." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:188 +msgid "" +"Enable this feature by navigating to the :guilabel:`Configuration` tab from " +"your payment acquirer and by ticking the :guilabel:`Capture Amount Manually`" +" checkbox." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:191 +msgid "" +"To capture the payment after it was authorized, go to the related sales " +"order or invoice and click on the :guilabel:`CAPTURE TRANSACTION` button. To" +" release the funds, click on the :guilabel:`VOID TRANSACTION` button." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:196 +msgid "" +"Some payment acquirers support capturing only part of the authorized amount." +" The remaining amount can then be either captured or voided. These acquirers" +" have the value **Full and partial** in the :ref:`table above " +"`. The acquirers that only support " +"capturing or voiding the full amount have the value **Full only**." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:200 +msgid "" +"The funds are likely not reserved forever. After a certain time, they may be" +" automatically released back to the customer's payment method. Refer to your" +" payment acquirer's documentation for the exact reservation duration." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:203 +msgid "" +"Odoo does not support this feature for all payment acquirers but some allow " +"the manual capture from their website interface." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:209 +msgid "Refunds" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:211 +msgid "" +"If your payment acquirer supports this feature, you can refund payments " +"directly from Odoo. It does not need to be enabled first. To refund a " +"customer payment, navigate to it and click on the :guilabel:`REFUND` button." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:216 +msgid "" +"Some payment acquirers support refunding only part of the amount. The " +"remaining amount can then optionally be refunded too. These acquirers have " +"the value **Full and partial** in the :ref:`table above " +"`. The acquirers that only support " +"refunding the full amount have the value **Full only**." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:220 +msgid "" +"Odoo does not support this feature for all payment acquirers but some allow " +"to refund payments from their website interface." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:229 +msgid "" +"Each acquirer has its specific configuration flow, depending on :ref:`which " +"feature is available `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:235 +msgid "Add a new payment acquirer" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:237 +msgid "" +"To add a new payment acquirer and make it available to your customers, go to" +" :menuselection:`Accounting --> Configuration --> Payment Acquirers`, look " +"for your payment acquirer, install the related module, and activate it. To " +"do so, open the payment acquirer and change its state from *Disabled* to " +"*Enabled*." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst-1 +msgid "" +"Click on install, then on activate to make the payment acquirer available on" +" Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:247 +msgid "" +"We recommend using the *Test Mode* on a duplicated database or a test " +"database. The Test Mode is meant to be used with your test/sandbox " +"credentials, but Odoo generates Sales Orders and Invoices as usual. It isn't" +" always possible to cancel an invoice, and this could create some issues " +"with your invoices numbering if you were to test your payment acquirers on " +"your main database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:255 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:23 +#: ../../content/applications/finance/payment_acquirers/alipay.rst:15 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:15 +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:15 +#: ../../content/applications/finance/payment_acquirers/mollie.rst:14 +#: ../../content/applications/finance/payment_acquirers/sips.rst:15 +msgid "Credentials tab" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:257 +msgid "" +"If not done yet, go to the online payment provider website, create an " +"account, and make sure to have the credentials required for third-party use." +" Odoo requires these credentials to communicate with the payment acquirer." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:261 +msgid "" +"The form in this section is specific to the payment acquirer you are " +"configuring. Please refer to the related documentation for more information." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:267 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:38 +msgid "Configuration tab" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:269 +msgid "" +"You can change the payment acquirer's front-end appearance by modifying its " +"name under the **Displayed as** field and which credit card icons to display" +" under the **Supported Payment Icons** field." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:276 +msgid "Countries" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:278 +msgid "" +"Restrict the use of the payment acquirer to a selection of countries. Leave " +"this field blank to make the payment acquirer available to all countries." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:284 +msgid "Payment journal" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:286 +msgid "" +"The **Payment journal** selected for your payment acquirer must be a *Bank* " +"journal." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:291 +msgid "Accounting perspective" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:293 +msgid "" +"The **Bank Payments** that go directly to one of your bank accounts follow " +"their usual reconciliation workflows. However, payments recorded with " +"**Online Payment Providers** require you to consider how you want to record " +"your payments' journal entries. We recommend you to ask your accountant for " +"advice." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:298 +msgid "" +"You need to select a *Payment Journal* on your acquirer configuration to " +"record the payments, on a **Outstanding Account**. The Journal's **type** " +"must be *Bank Journal*." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:301 +msgid "" +"You can use a single journal for many payment methods. And for each payment " +"method, you can either:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:303 +msgid "" +"Define an **Accounting Account** to separate these payments from another " +"payment method." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:304 +msgid "" +"Leave blank to fallback on the default account, which you can see or change " +"in the settings." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst-1 +msgid "A bank journal in the \"Incoming Payments Tab\"." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:310 +msgid "" +"You can have the same bank account for the whole company, or for some " +"journals only, or a single payment method... What best suit your needs." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:314 +msgid ":doc:`payment_acquirers/wire_transfer`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:315 +msgid ":doc:`payment_acquirers/adyen`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:316 +msgid ":doc:`payment_acquirers/alipay`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:317 +msgid ":doc:`payment_acquirers/authorize`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:318 +msgid ":doc:`payment_acquirers/buckaroo`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:319 +msgid ":doc:`payment_acquirers/mollie`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:320 +msgid ":doc:`payment_acquirers/ogone`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:321 +msgid ":doc:`payment_acquirers/paypal`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:322 +msgid ":doc:`payment_acquirers/sips`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:323 +msgid ":doc:`payment_acquirers/stripe`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers.rst:324 +msgid ":doc:`../websites/ecommerce/shopper_experience/payment_acquirer`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:3 +msgid "Adyen" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:5 +msgid "" +"`Adyen `_ is a Dutch company that offers several " +"online payment possibilities." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:9 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:20 +#: ../../content/applications/finance/payment_acquirers/alipay.rst:12 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:12 +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:12 +#: ../../content/applications/finance/payment_acquirers/mollie.rst:11 +#: ../../content/applications/finance/payment_acquirers/ogone.rst:9 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:93 +#: ../../content/applications/finance/payment_acquirers/sips.rst:12 +#: ../../content/applications/finance/payment_acquirers/stripe.rst:12 +msgid ":ref:`payment_acquirers/add_new`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:10 +#: ../../content/applications/finance/payment_acquirers/adyen.rst:137 +#: ../../content/applications/finance/payment_acquirers/alipay.rst:36 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:51 +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:47 +#: ../../content/applications/finance/payment_acquirers/mollie.rst:31 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:162 +#: ../../content/applications/finance/payment_acquirers/sips.rst:32 +#: ../../content/applications/finance/payment_acquirers/stripe.rst:134 +msgid ":doc:`../payment_acquirers`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:13 +msgid "" +"Adyen works only with customers processing **more** than **10 million " +"annually** or invoicing a **minimum** of **1.000** transactions **per " +"month**." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:25 +msgid "" +"Odoo needs your **API Credentials** to connect with your Adyen account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:27 +msgid "" +"**Merchant Account**: The code of the merchant account to use with Adyen." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:28 +msgid "" +":ref:`API Key `: The API key of the webservice " +"user." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:29 +msgid "" +":ref:`Client Key `: The client key of the " +"webservice user." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:30 +msgid ":ref:`HMAC Key `: The HMAC key of the webhook." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:31 +msgid "" +":ref:`Checkout API URL `: The base URL for the Checkout API " +"endpoints." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:32 +msgid "" +":ref:`Recurring API URL `: The base URL for the Recurring API " +"endpoints." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:34 +msgid "" +"You can copy your credentials from your Adyen account, and paste them in the" +" related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:38 +msgid "" +"If you are trying Adyen as a test, with an Adyen *test account*, head to " +":menuselection:`Accounting --> Configuration --> Payment Acquirers`. There, " +"click on :guilabel:`Adyen`, enable :guilabel:`Test Mode` and enter your " +"credentials in the :guilabel:`Credentials` tab." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:46 +msgid "API Key and Client Key" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:48 +msgid "" +"In order to retrieve the API Key and the Client Key, log into your Adyen " +"account, go to :menuselection:`Developers --> API Credentials`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:51 +msgid "If you already have an API user, open it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:52 +msgid "If you don't have an API user yet, click on **Create new credential**." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:54 +msgid "" +"Go to :menuselection:`Server settings --> Authentification` and copy or " +"generate your **API Key**. Be careful to copy your API key as you'll not be " +"allowed to get it later without generating a new one." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:58 +msgid "" +"Now, head to :menuselection:`Client settings --> Authentification` and cody " +"or generate your **Client Key**. This is also the place where you can " +":ref:`allow payments to be made from your website `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:65 +msgid "HMAC key" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:67 +msgid "" +"In order to retrieve the HMAC Key, you'll need to configure a `Standard " +"Notification` webhook. For this, log into your Adyen account then go to " +":menuselection:`Developers --> Webhooks --> Add webhook --> Add Standard " +"notification`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst-1 +msgid "Configure a webhook." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:75 +msgid "" +"There, in :menuselection:`General --> Server configuration --> URL`, enter " +"your server address followed by `/payment/adyen/notification`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst-1 +msgid "Enter the notification URL." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:82 +msgid "" +"Then enter :menuselection:`Security --> HMAC Key --> Generate`. Be careful " +"to copy the key as you will not be allowed to do it later without generating" +" a new one." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst-1 +msgid "Generate a HMAC key and save it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:89 +msgid "You have to save the webhook to finalize its creation." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:94 +msgid "API URLs" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:96 +msgid "" +"All Adyen API URLs include a customer area-specific prefix generated by " +"Adyen. To configure the URLs, proceed as follows:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:99 +msgid "" +"Log into your Adyen account, then go to :menuselection:`Developers --> API " +"URLs`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:100 +msgid "" +"Copy the :guilabel:`Prefix` for your live Customer area (i.e., **data " +"center**) and save it for later." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:0 +msgid "Copy the prefix for the Adyen APIs" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:106 +msgid "" +"In Odoo, :ref:`navigate to the payment acquirer Adyen " +"`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:107 +msgid "" +"In the :guilabel:`Checkout API URL` field, enter the following URL and " +"replace `yourprefix` with the prefix you previously saved: " +"`https://yourprefix-checkout-live.adyenpayments.com/checkout`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:110 +msgid "" +"In the :guilabel:`Recurring API URL` field, enter the following URL and " +"replace `yourprefix` with the prefix you previously saved: " +"`https://yourprefix-pal-live.adyenpayments.com/pal/servlet/Recurring`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:115 +msgid "" +"If you are trying Adyen as a test, you can use the following URLs instead:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:117 +msgid ":guilabel:`Checkout API URL`: `https://checkout-test.adyen.com`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:118 +msgid "" +":guilabel:`Recurring API URL`: `https://pal-" +"test.adyen.com/pal/servlet/Recurring`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:121 +msgid "Adyen Account" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:126 +msgid "Allow payments from a specific origin" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst:128 +msgid "" +"To allow payment originated from your website, follow the steps in " +":ref:`adyen/api_and_client_keys` to navigate to your API user and go to " +":menuselection:`Add allowed origins`, then add the URLs from where payments " +"will be made (the URLs of the servers hosting your Odoo instances)." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/adyen.rst-1 +msgid "Allows payments originated from a specific domain." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:3 +msgid "Alipay" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:5 +msgid "" +"`Alipay `_ is an online payments platform " +"established in China by Alibaba Group." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:17 +msgid "" +"Odoo needs your **API Credentials** to connect with your Alipay account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:19 +msgid "" +"**Account**: Depending on where you are situated - `Express Checkout` if " +"your are a Chinese Merchant. - `Cross-border` if you are not." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:22 +msgid "" +"**Alipay Seller Email**: Your public Alipay partner email (for express " +"checkout only)." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:23 +msgid "" +"**Merchant Partner ID**: The public partner ID solely used to identify the " +"account with Alipay." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:24 +msgid "**MD5 Signature Key**: The signature key." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:26 +msgid "" +"You can copy your credentials from your Alipay account, and paste them in " +"the related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:29 +msgid "" +"To retrieve them, log into your Alipay account, they are on the front page." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/alipay.rst:32 +msgid "" +"If you are trying Alipay as a test, in the *sandbox*, change the **State** " +"to *Test Mode*. We recommend doing this on a test Odoo database, rather than" +" on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:3 +msgid "Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:5 +msgid "" +"`Authorize.Net `_ is a United States-based online" +" payment solution provider, allowing businesses to accept **credit cards**." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:17 +msgid "" +"Odoo needs your **API Credentials & Keys** to connect with your " +"Authorize.Net account, which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:20 +msgid "" +"**API Login ID**: The ID solely used to identify the account with " +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:21 +msgid "**API Transaction Key**" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:22 +msgid "**API Signature Key**" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:23 +msgid "**API Client Key**" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:25 +msgid "" +"To retrieve them, log into your Authorize.Net account, go to " +":menuselection:`Account --> Settings --> Security Settings --> API " +"Credentials & Keys`, generate your **Transaction Key** and **Signature " +"Key**, and paste them on the related fields in Odoo. Then, click on " +"**Generate Client Key**." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:31 +msgid "" +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:34 +msgid "" +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:41 +msgid "Place a hold on a card" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 +msgid "" +"With Authorize.Net, you can enable the :ref:`manual capture " +"`. If enabled, the funds are " +"reserved for 30 days on the customer's card, but not charged yet." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:48 +msgid "" +"After **30 days**, the transaction is **voided automatically** by " +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:54 +msgid "Import an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:57 +msgid "Export from Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:63 +msgid "" +"`Download the Excel import template " +"`_" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:65 +msgid "To export a statement:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:67 +msgid "Log in to Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:68 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:69 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:71 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:84 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:87 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:89 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:90 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:92 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:93 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:95 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:97 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template `. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:104 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:107 +msgid "Import into Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:109 +msgid "To import the data into Odoo:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:111 +msgid "Open the :ref:`Excel import template `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:112 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:114 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:117 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:118 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:120 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template ` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:125 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template ` for each invoice." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 +msgid "Chargeback description" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:133 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:135 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:137 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:139 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:141 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:143 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:148 +msgid "" +"List of `eCheck.Net return codes " +"`_" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:3 +msgid "Buckaroo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:5 +msgid "" +"`Buckaroo `_ is a Dutch-based company that offers " +"several online payment possibilities." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:17 +msgid "" +"Odoo needs your **API Credentials** to connect with your Buckaroo account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:19 +msgid "" +":ref:`Website Key `: The key solely used to identify " +"the website with Buckaroo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:21 +msgid "" +":ref:`Secret Key `: The secret key you entered on " +"Buckaroo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:23 +msgid "" +"You can copy your credentials from your Buckaroo account, and paste them in " +"the related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:29 +msgid "Website Key" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:31 +msgid "" +"In order to retrieve the Website Key, log into your Buckaroo account, go to " +":menuselection:`Configuration --> Templates --> Your Website`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:37 +msgid "Secret Key" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:39 +msgid "" +"In order to retrieve the Website Key, log into your Buckaroo account, go to " +":menuselection:`Configuration --> Security --> Secret Key`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/buckaroo.rst:43 +msgid "" +"If you are trying Buckaroo in a test account, change the **State** to *Test " +"Mode*. We recommend doing this on a test Odoo database, rather than on your " +"main database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/mollie.rst:3 +msgid "Mollie" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/mollie.rst:5 +msgid "" +"`Mollie `_ is an online payments platform " +"established in the Netherlands." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/mollie.rst:16 +msgid "" +"Odoo needs your **API Credentials** to connect with your Mollie account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/mollie.rst:18 +msgid "" +"**API Key**: The test or live API Key depending on the configuration of the " +"acquirer." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/mollie.rst:20 +msgid "" +"You can copy your credentials from your Mollie account, and paste them in " +"the related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/mollie.rst:23 +msgid "" +"To retrieve your API key, log into your Mollie account, go to " +":menuselection:`Developers --> API keys`, and copy your Test or Live **API " +"Key**." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/mollie.rst:27 +msgid "" +"If you are trying Mollie as a test, with the Test API key, change the " +"**State** to *Test Mode*. We recommend doing this on a test Odoo database, " +"rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:3 +msgid "Ogone" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:5 +msgid "" +"`Ogone `_, also known as **Ingenico Payment " +"Services** is a France-based company that provides the technology involved " +"in secure electronic transactions." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:10 +msgid "" +"`Ogone's documentation `_." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:13 +msgid "Settings in Ogone" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:16 +msgid "Create an API user" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:18 +msgid "" +"Log into your Ogone account and head to the :guilabel:`Configuration` tab." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:20 +msgid "" +"You need to create an **API user** to be used in the creation of " +"transactions from Odoo. While you can use your main account to do so, using " +"an **API user** ensures that if the credentials used in Odoo are leaked, no " +"access to your Ogone configuration is possible. Additionally, passwords for " +"**API users** do not need to be updated regularly, unlike normal users." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:25 +msgid "" +"To create an **API user**, go to :menuselection:`Configuration --> Users` " +"and click on :guilabel:`New User`. The following fields must be configured:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:30 +msgid ":guilabel:`UserID`: you can choose anything you want." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:31 +msgid "" +":guilabel:`User's Name, E-mail and Timezone`: you can enter the information " +"you want." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:32 +msgid ":guilabel:`Profile`: should be set to :guilabel:`Admin`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:33 +msgid ":guilabel:`Special user for API`: should be checked." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:35 +msgid "" +"After the creation of the user, you are required to generate a password. " +"Save the password and **UserID**, as they will be required later on during " +"the setup." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:39 +msgid "" +"If you already have an user set up, make sure it is activated without any " +"error. If not, simply click the :guilabel:`Activate(Errors)` button to reset" +" the user." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:43 +msgid "Set up Ogone for Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:45 +msgid "" +"Ogone must now be configured to accept payments from Odoo. Head to " +":menuselection:`Configuration --> Technical Information --> Global Security " +"Parameters`, select :guilabel:`SHA-1` as :guilabel:`Hash Algorithm` and " +":guilabel:`UTF-8` as :guilabel:`character encoding`. Then, go to the " +":guilabel:`Data and Origin verification` tab of the same page and leave the " +"URL field of the :guilabel:`e-Commerce and Alias Gateway` section blank." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:52 +msgid "" +"If you need to use another algorithm, such as `sha-256` or `sha-512`, within" +" Odoo, activate the :ref:`developer mode ` and go to " +":menuselection:`General Settings --> Technical --> System Parameters`. From " +"here, search for `payment_ogone.hash_function` and change the value line to " +"the desired algorithm (`sha-256` or `sha-512`)." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:57 +msgid "" +"You are now required to generate **SHA-IN** passphrases. **SHA-IN** and " +"**SHA-OUT** passphrases are used to digitally sign the transaction requests " +"and responses between Odoo and Ogone. By using these secret passphrases and " +"the `sha-1` algorithm, both systems can ensure that the information they " +"receive from the other was not altered or tampered with." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:62 +msgid "" +"Enter the same **SHA-IN** passphrase in both :guilabel:`Checks for " +"e-Commerce & Alias Gateway` and :guilabel:`Checks for DirectLink and Batch " +"(Automatic)`. You can leave the IP address field blank." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:65 +msgid "" +"Your **SHA-IN** and **SHA-OUT** passphrases should be different, and between" +" 16 and 32 characters long. Make sure to use the same **SHA-IN** and **SHA-" +"OUT** passphrases throughout the entire Ogone configuration, as Odoo only " +"allows a single **SHA-IN** and single **SHA-OUT** passphrase." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:69 +msgid "" +"In order to retrieve the **SHA-OUT** key, log into your Ogone account, go to" +" :menuselection:`Configuration --> Technical Information --> Transaction " +"feedback --> All transaction submission modes`, and get or generate your " +"**API Key** and **Client Key**. Be careful to copy your API key as you’ll " +"not be allowed to get it later without generating a new one." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:74 +msgid "" +"When done, head to :menuselection:`Configuration --> Technical Information " +"--> Transaction Feedback` and check the following options:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:77 +msgid "" +"The :guilabel:`URL` fields for :guilabel:`HTTP redirection in the browser` " +"can be left empty, as Odoo will specify these URLs for every transaction " +"request." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:79 +msgid "" +":guilabel:`I would like to receive transaction feedback parameters on the " +"redirection URLs`: should be checked." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:81 +msgid "" +":guilabel:`Direct HTTP server-to-server request`: should to be set to " +"`Online but switch to a deferred request when the online request fails`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:83 +msgid "" +"Both **URL** fields should contain the same following URL, with `` " +"replaced by your database: `https:///payment/ogone/return`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:86 +msgid "" +":guilabel:`Dynamic eCommerce Parameters` should contain the following " +"values: `ALIAS`, `AMOUNT`, `CARDNO`, `CN`, `CURRENCY`, `IP`, `NCERROR` " +"`ORDERID`, `PAYID`, `PM`, `STATUS`, `TRXDATE`. Other parameters can be " +"included (if you have another integration with Ogone that requires them), " +"but are not advised." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:90 +msgid "" +"In the :guilabel:`All transaction submission modes` section, fill out **SHA-" +"OUT** passphrase and disable `HTTP request for status change`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:93 +msgid "" +"To allow your customers to save their credit card credentials for future " +"use, head to :menuselection:`Configuration --> Alias --> My alias " +"information`. From this tab, you can configure how the user can have its " +"card details saved, for how long the information is saved, if a checkbox to " +"save the card information should be displayed, etc." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:99 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:90 +msgid "Settings in Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:101 +msgid "" +"To set up Ogone in Odoo, head to :menuselection:`Accounting --> " +"Configuration --> Payment Acquirers` and open the Ogone acquirer. In the " +":guilabel:`Credentials` tab, enter the **PSPID** of your Ogone account, and " +"fill out the other fields as configured in your :ref:`Ogone portal " +"`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:106 +msgid "" +"If you wish to run tests with Ogone, within the accounting app, go to " +":menuselection:`Configuration --> Payment Acquirers`. Click on " +":guilabel:`Ogone`, enable :guilabel:`Test Mode` and enter your credentials " +"in the :guilabel:`Credentials` tab. We recommend doing this on an Odoo test " +"database, rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:3 +msgid "PayPal" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:5 +msgid "" +"`Paypal `_ is an American online payment acquirer " +"available worldwide, and one of the few that does not charge a subscription " +"fee." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:9 +msgid "Settings in PayPal" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:11 +msgid "" +"To access your PayPal account settings, log into PayPal, open the " +":guilabel:`Account Settings`, and open the :guilabel:`Website payments` " +"menu." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst-1 +msgid "PayPal account menu" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:19 +msgid "" +"Note that for PayPal to work **in Odoo**, the options :ref:`Auto Return " +"`, :ref:`PDT `, and :ref:`IPN ` " +"**must** all be enabled." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:25 +msgid "Auto Return" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:27 +msgid "" +"The **Auto Return** feature automatically redirects customers to Odoo once " +"the payment is processed." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:29 +msgid "" +"From :guilabel:`Website payments`, go to :menuselection:`Website preferences" +" --> Update --> Auto return for website payments --> Auto return` and select" +" :guilabel:`On`. Enter the address of your Odoo database (e.g., " +"`https://yourcompany.odoo.com`) in the :guilabel:`Return URL` field, and " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:35 +msgid "" +"Any URL does the job. Odoo only needs the setting to be enabled since it " +"uses another URL." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:40 +msgid "Payment Data Transfer (PDT)" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:42 +msgid "" +":abbr:`PDT (Payment Data Transfer)` allows to receive payment confirmations," +" displays the payment status to the customers, and verifies the authenticity" +" of the payments. From :menuselection:`Website preferences --> Update`, " +"scroll down to :guilabel:`Payment data transfer` and select :guilabel:`On`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:47 +msgid "" +"PayPal displays your **PDT Identity Token** as soon as :ref:`Auto return " +"` and :ref:`Payment Data Transfer (PDT) ` " +"are enabled. If you need the **PDT Identity Token**, disable and re-enable " +":guilabel:`Payment data transfer` to display the token again." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:54 +msgid "Instant Payment Notification (IPN)" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:56 +msgid "" +":abbr:`IPN (Instant Payment Notifications)` is similar to **PDT**, but " +"allows for more notifications, such as chargeback notifications. To enable " +"**IPN**, go to :menuselection:`Website payments --> Instant payment " +"notifications --> Update` and click :guilabel:`Choose IPN settings`. Enter a" +" :guilabel:`Notification URL`, select :guilabel:`Receive IPN messages " +"(Enabled)`, and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:63 +msgid "PayPal Account Optional" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:65 +msgid "" +"We advise not to prompt customers to log in with a PayPal account upon " +"payment. It is better and more accessible for customers to pay with a " +"debit/credit card. To disable that prompt, go to :menuselection:`Account " +"Settings --> Website payments --> Update` and select :guilabel:`On` for " +":guilabel:`PayPal account optional`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:71 +msgid "Payment Messages Format" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:73 +msgid "" +"If you use accented characters (or anything other than primary Latin " +"characters) for customer names or addresses, then you **must** configure the" +" encoding format of the payment request sent by Odoo to PayPal. If you do " +"not, some transactions fail without notice." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:77 +msgid "" +"To do so, go to `your production account `_. Then, click " +":guilabel:`More Options` and set the two default encoding formats as " +":guilabel:`UTF-8`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:82 +msgid "" +"For Encrypted Website Payments & EWP_SETTINGS error, please check the " +"`Paypal documentation `_." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:85 +msgid "" +"Configure your :ref:`Paypal Sandbox account `, then follow " +"this `link `_ to configure the " +"encoding format in a test environment." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:96 +msgid "Credentials" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:98 +msgid "" +"Odoo needs your **API Credentials** to connect with your PayPal account. To " +"do so, go to :menuselection:`Accounting --> Configuration --> Payment " +"Acquirers` and :guilabel:`Activate` PayPal. Then, enter your PayPal account " +"credentials in the :guilabel:`Credentials` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:102 +msgid ":guilabel:`Email`: the login email address in Paypal;" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:103 +msgid "" +":guilabel:`PDT Identity Token`: the key used to verify the authenticity of " +"transactions;" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:104 +msgid ":guilabel:`Use IPN`: enable for PayPal to work properly in Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:107 +msgid "Save the :guilabel:`PDT Identity Token` for later use." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:109 +msgid "" +"To set the :guilabel:`PDT Identity Token`, switch to :ref:`developer mode " +"` and retrieve the token by following the configuration " +"steps at :ref:`paypal/pdt`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:113 +msgid "The PayPal **Merchant ID** is not required in Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:115 +msgid "" +"If you are trying PayPal as a test, using a :ref:`PayPal Sandbox account " +"`, change the :guilabel:`State` to :guilabel:`Test Mode`. We" +" recommend doing this on a test Odoo database rather than on your main " +"database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:120 +msgid "Extra fees" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:122 +msgid "" +"You can charge **extra fees** to customers choosing to pay with PayPal in " +"order to cover the transaction fees PayPal charges you. Once redirected to " +"Paypal, your customer sees an extra amount applied to the order amount." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:126 +msgid "" +"To activate this option, go to :menuselection:`Accounting --> Configuration " +"--> Payment Acquirers` and select :guilabel:`PayPal`. Then, go to the " +":guilabel:`Fees` tab and tick the :guilabel:`Add Extra Fees` box." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:131 +msgid "" +"You can refer to `Paypal Fees `_ to set up fees." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:133 +msgid "" +"`Traders in the EU " +"`_ are not allowed to charge extra fees for paying " +"with credit cards." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:138 +msgid "Test environment" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:143 +msgid "" +"Thanks to PayPal sandbox accounts, you can test the entire payment flow in " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:145 +msgid "" +"Log into the `Paypal Developer Site `_ using " +"your PayPal credentials, which creates two sandbox accounts:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:148 +msgid "" +"A business account (to use as merchants, e.g., " +"`pp.merch01-facilitator@example.com " +"`_);" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:150 +msgid "" +"A default personal account (to use as shoppers, e.g., " +"`pp.merch01-buyer@example.com `_)." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:153 +msgid "" +"Log into PayPal sandbox using the merchant account and follow the same " +"configuration instructions. Enter your sandbox credentials in Odoo " +"(:menuselection:`Accounting --> Configuration --> Payment Acquirer --> " +"PayPal` in the :guilabel:`Credentials` tab, and make sure the status is set " +"on :guilabel:`Test Mode`. We recommend doing this on a test Odoo database " +"rather than your main database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:159 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/sips.rst:3 +msgid "SIPS" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/sips.rst:5 +msgid "" +"`SIPS `_ is an online payments solution from " +"the multinational Worldline." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/sips.rst:17 +msgid "" +"Odoo needs your **API Credentials** to connect with your SIPS account, which" +" comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/sips.rst:19 +msgid "" +"**Merchant ID**: The ID solely used to identify the merchant account with " +"SIPS." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/sips.rst:20 +msgid "**Secret Key**: The key to sign the merchant account with SIPS." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/sips.rst:21 +msgid "**Secret Key Version**: The version of the key, pre-filled." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/sips.rst:22 +msgid "**Interface Version**: Pre-filled, don't change it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/sips.rst:24 +msgid "" +"You can copy your credentials from your SIPS environment info documentation," +" in the section **PROD**, and paste them in the related fields under the " +"**Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/sips.rst:28 +msgid "" +"If you are trying SIPS as a test, with the *TEST* credentials, change the " +"**State** to *Test Mode*. We recommend doing this on a test Odoo database, " +"rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:3 +msgid "Stripe" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:5 +msgid "" +"`Stripe `_ is a United States-based online payment " +"solution provider, allowing businesses to accept **credit cards** and other " +"payment methods." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:9 +msgid "Link your Stripe Account with Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:14 +msgid "The method to acquire your credentials depends on your hosting type:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:19 +#: ../../content/applications/finance/payment_acquirers/stripe.rst:35 +msgid "" +"Go to the **eCommerce** or the **Sales** app and click on the *Activate " +"Stripe* or the *Set payments* button on the onboarding banner." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:21 +#: ../../content/applications/finance/payment_acquirers/stripe.rst:37 +msgid "Fill in the requested information and submit the form." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:22 +#: ../../content/applications/finance/payment_acquirers/stripe.rst:38 +msgid "Confirm your email address when Stripe sends you a confirmation email." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:23 +msgid "" +"At the end of the process, you are redirected to Odoo. If you submitted all " +"the requested information, you are all set and your payment acquirer is " +"enabled." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:25 +msgid "Your can continue to :ref:`stripe/local-payment-methods`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:28 +msgid "" +"To use your own API keys, :ref:`activate the Developer mode ` and :ref:`enable Stripe manually `. You " +"can then :ref:`Fill in your credentials `, :ref:`generate a" +" webhook ` and enable the payment acquirer." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:33 +msgid "Odoo.sh or On-premise" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:39 +msgid "" +"At the end of the process, you are redirected to the payment acquirer " +"**Stripe** on Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:40 +msgid ":ref:`Fill in your credentials `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:41 +msgid ":ref:`Generate a webhook `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:42 +msgid "Enable the payment acquirer." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:43 +msgid "" +"You are all set and can continue to :ref:`stripe/local-payment-methods`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:46 +msgid "" +"To connect your Stripe account after the onboarding is already completed, go" +" to :menuselection:`Accounting --> Configuration --> Payment Acquirers --> " +"Stripe` and click on the *Connect Stripe* button." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:51 +msgid "" +"If you are testing Stripe (in **test mode**), change the **State** to *Test " +"Mode*. We recommend doing this on a test Odoo database rather than on your " +"main database." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:57 +msgid "Fill in your credentials" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:59 +msgid "" +"In case your **API Credentials** are required to connect with your Stripe " +"account, these are the credentials that must be completed:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:62 +msgid "" +":ref:`Publishable Key `: The key solely used to identify " +"the account with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:63 +msgid "" +":ref:`Secret Key `: The key to sign the merchant account " +"with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:64 +msgid "" +":ref:`Webhook Signing Secret `: When you enable your webhook" +" on your Stripe account, this signing secret must be set to authenticate the" +" messages sent from Stripe to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:67 +msgid "" +"To retrieve the publishable and secret keys, follow this `link to your API " +"keys `_, or log into your " +"Stripe dashboard and go to :menuselection:`Developers --> API Keys --> " +"Standard Keys`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:74 +msgid "Generate a webhook" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:76 +msgid "" +"In case your **Webhook Signing Secret** is required to connect with your " +"Stripe account, you can create a webhook either automatically or manually." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:80 +msgid "Create the webhook automatically" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:82 +msgid "" +"Make sure your :ref:`Publishable and Secret keys ` are " +"filled in, then click on the *Generate your Webhook* button." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:85 +msgid "Create the webhook manually" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:87 +msgid "" +"Visit the `webhooks page on Stripe " +"`_, or log into your Stripe dashboard" +" and go to :menuselection:`Developers --> Webhooks`. Then, click on **Add " +"endpoint** in your **Hosted endpoints** and insert the following data into " +"the pop-up form:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:0 +msgid "In the **Endpoint URL**, enter your Odoo database's URL followed by" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:0 +msgid "`/payment/stripe/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:0 +msgid "For example: `https://yourcompany.odoo.com/payment/stripe/webhook`" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:94 +msgid "" +"At the end of the form, you can **Select events** to listen to. Click on it " +"and, in the **Checkout** section, select **checkout.session.completed**." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:98 +msgid "" +"It is possible to select other events, but they are currently not processed " +"by Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:100 +msgid "" +"When you click on **Add endpoint**, your Webhook is configured. You can then" +" click on **reveal** to display your signing secret." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:106 +msgid "Enable local payment methods" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:108 +msgid "" +"Local payment methods are payment methods that are only available for " +"certain merchants and customers countries and currencies." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:111 +msgid "Odoo supports the following local payment methods:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:113 +msgid "Bancontact" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:114 +msgid "EPS" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:115 +msgid "giropay" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:116 +msgid "iDEAL" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:117 +msgid "Przelewy24 (P24)" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:119 +msgid "" +"To enable some of these local payment methods with Stripe, list them as " +"supported payment icons. To do so, go to :menuselection:`Payment Acquirers " +"--> Stripe --> Configuration` and add the desired payment methods in the " +"**Supported Payment Icons** field. If the desired payment method is already " +"listed, you don't have anything to do." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst-1 +msgid "Select and add icons of the payment methods you want to enable" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:129 +msgid "" +"If a payment icon record does not exist in the database and its related " +"local payment method is listed above, it is considered enabled with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:131 +msgid "" +"If a local payment method is not listed above, it is not supported and " +"cannot be enabled." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:3 +msgid "Wire transfers" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:5 +msgid "" +"The **Wire transfer** payment method allows you to provide payment " +"instructions to your customers, such as the bank details and communication. " +"They are displayed:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:8 +msgid "" +"at the end of the checkout process, once the customer has selected " +":guilabel:`Wire transfer` as a payment method and clicked the :guilabel:`Pay" +" now` button:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:0 +msgid "Payment instructions at checkout" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:14 +msgid "on the customer portal:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:0 +msgid "Payment instructions on the customer portal" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:20 +msgid "" +"While this method is very accessible and requires minimal setup, it is very " +"inefficient process-wise. We recommend setting up a :doc:`payment acquirer " +"<../payment_acquirers>` instead." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:22 +msgid "" +"Online orders remain in the :guilabel:`Quotation sent` (i.e., unpaid order) " +"stage until you receive the payment and :guilabel:`Confirm` the order." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:26 +msgid "" +"**Wire transfer** can be used as a template for other payment methods that " +"are processed manually, such as checks, by renaming or duplicating it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:32 +msgid "**Wire Transfer** is installed and enabled by default." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:34 +msgid "" +"To configure it, go to :menuselection:`Accounting / Website --> " +"Configuration --> Payment Acquirers`, and open the :guilabel:`Wire Transfer`" +" card. Then, in the :guilabel:`Configuration` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:38 +msgid "Select the :guilabel:`Communication` to be used;" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:40 +msgid ":guilabel:`Based on Document Reference`: sales order or invoice number" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:41 +msgid ":guilabel:`Based on Customer ID`: customer identifier" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:43 +msgid "" +"Tick the :guilabel:`Enable QR codes` check box to activate :doc:`QR code " +"payments <../accounting/customer_invoices/epc_qr_code>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:46 +msgid "Define the payment instructions in the :guilabel:`Messages` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst-1 +msgid "Define payment instructions" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:52 +msgid ":ref:`payment_acquirers/journal`" +msgstr "" + +#: ../../content/applications/finance/sign.rst:3 +msgid "Sign" +msgstr "" + +#: ../../content/applications/finance/sign.rst:5 +msgid "**Odoo Sign** allows you to send, sign and approve documents online." +msgstr "" + +#: ../../content/applications/finance/sign.rst:7 +msgid "" +"You can upload any PDF file and add drag-and-dropping fields on it. These " +"fields are automatically filled out with the user's detail if they are " +"logged in." +msgstr "" + +#: ../../content/applications/finance/sign.rst:11 +msgid "`Odoo Sign: product page `_" +msgstr "" + +#: ../../content/applications/finance/sign.rst:12 +msgid "`Odoo Tutorials: Sign `_" +msgstr "" + +#: ../../content/applications/finance/sign.rst:17 +msgid "Validity of electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:19 +msgid "" +"The legal validity of electronic signatures generated by Odoo depends on the" +" legislation of your country. Companies doing business abroad should " +"consider electronic signature laws of other countries as well." +msgstr "" + +#: ../../content/applications/finance/sign.rst:24 +msgid "In the European Union" +msgstr "" + +#: ../../content/applications/finance/sign.rst:26 +msgid "" +"The `eIDAS regulation `_ " +"establishes the framework for electronic signatures in all `27 member states" +" of the European Union `_." +msgstr "" + +#: ../../content/applications/finance/sign.rst:30 +msgid "It distinguishes three types of electronic signatures:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:32 +msgid "Electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:33 +msgid "Advanced electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:34 +msgid "Qualified electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:36 +msgid "" +"Odoo generates the first type, regular electronic signatures, and these " +"signatures can produce legal effects in the EU, as the regulation states " +"that “an electronic signature shall not be denied legal effect and " +"admissibility as evidence in legal proceedings solely on the grounds that it" +" is in an electronic form or that it does not meet the requirements for " +"qualified electronic signatures.”" +msgstr "" + +#: ../../content/applications/finance/sign.rst:41 +msgid "" +"Note that electronic signatures may not be automatically recognized as " +"valid. You may need to bring supporting evidence of a signature’s validity." +msgstr "" + +#: ../../content/applications/finance/sign.rst:45 +msgid "In the United States of America" +msgstr "" + +#: ../../content/applications/finance/sign.rst:47 +msgid "" +"The `ESIGN Act (Electronic Signatures in Global and National Commerce Act) " +"`_, at the " +"interstate and international levels, and the `UETA (Uniform Electronic " +"Transactions Act) `_," +" at the state level, provide the legal framework for electronic signatures. " +"Note that `Illinois " +"`_ and `New York " +"`_ have not " +"adopted the UETA, but similar acts instead." +msgstr "" + +#: ../../content/applications/finance/sign.rst:56 +msgid "" +"Overall, to be recognized as valid, electronic signatures have to meet five " +"criteria:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:58 +msgid "" +"A signer must show a clear intent to sign. For example, using a mouse to " +"draw a signature can show intent. The signer must also have the option to " +"opt-out of electronically signing a document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:61 +msgid "" +"A signer must first express or imply their consent to conduct business " +"electronically." +msgstr "" + +#: ../../content/applications/finance/sign.rst:62 +msgid "" +"The signature must be clearly attributed. In Odoo, metadata, such as the " +"signer’s IP address, is added to the signature, which can be used as " +"supporting evidence." +msgstr "" + +#: ../../content/applications/finance/sign.rst:64 +msgid "" +"The signature must be associated with the document being signed, for " +"example, by keeping a record detailing how the signature was captured." +msgstr "" + +#: ../../content/applications/finance/sign.rst:66 +msgid "" +"Electronically signed documents need to be retained and available for later " +"reference by all parties involved, for example, by providing the signer " +"either a fully-executed copy or the option to download a copy." +msgstr "" + +#: ../../content/applications/finance/sign.rst:71 +msgid "" +"The information provided here does not constitute legal advice; it is " +"provided for general informational purposes only. As laws governing " +"electronic signatures rapidly evolve, we cannot guarantee whether all " +"information is up to date or not. We advise contacting a local attorney for " +"legal advice regarding electronic signature compliance and validity." +msgstr "" + +#: ../../content/applications/finance/sign.rst:79 +msgid "Field Types" +msgstr "" + +#: ../../content/applications/finance/sign.rst:81 +msgid "" +"By configuring your own *Field Types*, also known as *Signature Item Types*," +" you can make the signing process even faster for your customers, partners, " +"and employees." +msgstr "" + +#: ../../content/applications/finance/sign.rst:84 +msgid "" +"To create and customize fields, activate the :ref:`developer mode " +"`. Then head to :menuselection:`Documents --> Configuration " +"--> Field Types` and click on *Create*." +msgstr "" + +#: ../../content/applications/finance/sign.rst:87 +msgid "" +"After giving your new field a name, select one of the six *Types* available:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:89 +msgid "" +"**Signature**: users are prompted to enter their signature either by drawing" +" it, automatically generating one based on their name, or uploading a local " +"file (usually an image). Each subsequent *Signature* field then reuses the " +"data entered in the first field." +msgstr "" + +#: ../../content/applications/finance/sign.rst:92 +msgid "" +"**Initial**: users are prompted to enter their initials, in a similar way to" +" the *Signature* field." +msgstr "" + +#: ../../content/applications/finance/sign.rst:94 +msgid "**Text**: users enter text on a single line." +msgstr "" + +#: ../../content/applications/finance/sign.rst:95 +msgid "**Multiline Text**: users enter text on multiple lines." +msgstr "" + +#: ../../content/applications/finance/sign.rst:96 +msgid "" +"**Checkbox**: users can tick a box (e.g.,to mark their approval or consent)." +msgstr "" + +#: ../../content/applications/finance/sign.rst:97 +msgid "**Selection**: users choose a single option from a variety of options." +msgstr "" + +#: ../../content/applications/finance/sign.rst:99 +msgid "" +"Next, you have the option to auto-complete fields for users based on their " +"Odoo profile information by using *Automatic Partner Field*. To this end, " +"the *Name*, *Email*, *Phone*, and *Company* fields are preconfigured in your" +" database." +msgstr "" + +#: ../../content/applications/finance/sign.rst:104 +msgid "Users can freely edit auto-completed fields." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Company field example in Odoo Sign" +msgstr "" + +#: ../../content/applications/finance/sign.rst:110 +msgid "" +"You can then change the size of the field by editing the *Default Width* and" +" *Default Height*. Both sizes are defined as a percentage of the full-page " +"expressed as a decimal, with 1 equalling the full-page's width or height. By" +" default, the width of new fields you create is set to 15% (0.150) of a " +"full-page's width, while their height is set to 1.5% (0.015) of a full-" +"page's height." +msgstr "" + +#: ../../content/applications/finance/sign.rst:115 +msgid "" +"Next, write a *Tip*. Tips are displayed inside arrows on the left-hand side " +"of the user's screen during the signing process. You can also use a " +"*Placeholder* text to be displayed inside the field before it is completed." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Tip and placeholder example in Odoo Sign" +msgstr "" diff --git a/locale/pl/LC_MESSAGES/general.po b/locale/pl/LC_MESSAGES/general.po new file mode 100644 index 000000000..0032ee2ab --- /dev/null +++ b/locale/pl/LC_MESSAGES/general.po @@ -0,0 +1,4616 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"PO-Revision-Date: 2021-11-02 08:47+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications/general.rst:3 +msgid "Miscellaneous" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:3 +msgid "Apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:5 +msgid "" +"You can :ref:`install `, :ref:`upgrade ` " +"and :ref:`uninstall ` all apps and modules from the " +":menuselection:`Apps` dashboard." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:8 +msgid "" +"By default, an *Apps* filter is applied. If you want to search for modules, " +"click on *Filters* and select *Extra*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst-1 +msgid "Add \"Extra\" filter in Odoo Apps" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:16 +msgid "" +"Odoo is *not a smartphone*, and its apps shouldn't be installed or " +"uninstalled carelessly. Apply caution when adding or removing apps and " +"modules on your database since this may impact your subscription costs." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "**Installing or uninstalling apps and managing users is up to you.**" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "" +"As the administrator of your database, you are responsible for its usage, as" +" you know best how your organization works." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "**Odoo apps have dependencies.**" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "" +"Installing some apps and features with dependencies may also install " +"additional apps and modules that are technically required, even if you won't" +" actively use them." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "**Test app installation/removal on a duplicate of your database.**" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "" +"This way, you can know what app dependencies may be required or what data " +"may be erased." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:32 +msgid "Install apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:34 +msgid "" +"Go to :menuselection:`Apps`, and click on the *Install* button of the app " +"you want to install." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:37 +msgid "" +"If the module you are looking for is not listed, you can **update the app " +"list**." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:39 +msgid "" +"To do so, activate the :ref:`developer mode `, then go to " +":menuselection:`Apps --> Update Apps List` and click on *Update*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:45 +msgid "Upgrade apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:47 +msgid "" +"On some occasions, new improvements or app features are added to " +":doc:`supported versions of Odoo " +"`. To be able to use them, you " +"must **upgrade** your app." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:51 +msgid "" +"Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you " +"want to upgrade, then on *Upgrade*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:57 +msgid "Uninstall apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:59 +msgid "" +"Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you " +"want to uninstall, then on *Uninstall*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:65 +msgid "" +"Some apps have dependencies, meaning that one app requires another. " +"Therefore, uninstalling one app may uninstall multiple apps and modules. " +"Odoo warns you which dependent apps and modules are affected by it." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:72 +msgid "To complete the uninstallation, click on *Confirm*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:75 +msgid "" +"Uninstalling an app also uninstalls all its dependencies and permanently " +"erases their data." +msgstr "" + +#: ../../content/applications/general/auth.rst:5 +msgid "Authentication" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:3 +msgid "Two-factor Authentication" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:5 +msgid "" +"Two-factor authentication (\"2FA\") is a good way to improve the security of" +" an account, to make it less likely that an other person will manage to log " +"in instead of you." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:9 +msgid "" +"Practically, it means storing a secret inside an *authenticator* (usually " +"your cell phone) and exchanging a code from the authenticator when you try " +"to log in." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:13 +msgid "" +"This means an attacker needs *both* to have guessed (or found) your password" +" and to access (or steal) your authenticator, a more difficult proposition " +"than either one or the other." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:18 +msgid "Requirements" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:20 +msgid "" +"These lists are just examples, they are not endorsements of any specific " +"software." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:23 +msgid "" +"If you don't already have one, you will need to choose an authenticator." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:26 +msgid "" +"Phone-based authenticators are the easiest and most common so we will assume" +" you'll pick and install one on your phone, examples include `Authy " +"`_, `FreeOTP `_, `Google " +"Authenticator `_, " +"`LastPass Authenticator `_, `Microsoft " +"Authenticator `_, ...; password managers also " +"commonly include :abbr:`2FA (two-factor authentication)` support e.g. " +"`1Password `_, `Bitwarden" +" `_, ..." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:39 +msgid "" +"For the sake of demonstration we will be using Google Authenticator (not " +"because it is any good but because it is quite common)." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:43 +msgid "Setting up two-factor authentication" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:45 +msgid "" +"Once you have your authenticator of choice, go to the Odoo instance you want" +" to setup :abbr:`2FA (two-factor authentication)`, then open " +":guilabel:`Preferences` (or :guilabel:`My Profile`):" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:52 +msgid "" +"Open the :guilabel:`Account Security` tab, then click the :guilabel:`Enable " +"two-factor authentication` button:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:58 +msgid "" +"Because this is a security-sensitive action, you will need to input your " +"password:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:64 +msgid "After which you will see this screen with a barcode:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:69 +msgid "" +"In most applications, you can simply *scan the barcode* via the " +"authenticator of your choice, the authenticator will then take care of all " +"the setup:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:78 +msgid "" +"If you can not scan the screen (e.g. because you are doing this set-up on " +"the same phone as the authenticator application), you can click the provided" +" link, or copy the secret to manually set-up your authenticator:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:89 +msgid "" +"Once this is done, the authenticator should display a *verification code* " +"with some useful identifying information (e.g. the domain and login for " +"which the code is):" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:96 +msgid "" +"You can now input the code into the :guilabel:`Verification Code` field, " +"then click the :guilabel:`Enable two-factor authentication` button." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:100 +msgid "" +"Congratulation, your account is now protected by two-factor authentication!" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:107 +msgid "Logging in" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:109 +msgid "You should now :guilabel:`Log out` to follow along." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:111 +msgid "" +"On the login page, input the username and password of the account for which " +"you set up :abbr:`2FA (two-factor authentication)`, rather than immediately " +"enter Odoo you will now get a second log-in screen:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:118 +msgid "" +"Get your authenticator, input the code it provides for the domain and " +"account, validate, and you're now in." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:121 +msgid "" +"And that's it. From now on, unless you disable :abbr:`2FA (two-factor " +"authentication)` you will have a two-step log-in process rather than the old" +" one-step process." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:125 +msgid "" +"Don't lose your authenticator, if you do, you will need an *Odoo " +"Administrator* to disable :abbr:`2FA (two-factor authentication)` on the " +"account." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:3 +msgid "Microsoft Azure sign-in authentication" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:5 +msgid "" +"Due to specific requirements in Azure's OAuth implementation, Microsoft " +"Azure OAuth identification is NOT compatible with Odoo at the moment." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:9 +msgid ":doc:`../../productivity/calendar/outlook`" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:10 +#: ../../content/applications/general/email_communication/email_servers.rst:67 +msgid ":doc:`/administration/maintain/azure_oauth`" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:3 +msgid "Google Sign-In Authentication" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:5 +msgid "" +"The *Google Sign-In Authentication* is a useful function that allows Odoo " +"users to sign in to their database with their Google account." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:8 +msgid "" +"This is particularly helpful if the organization uses Google Workspace, and " +"wants employees within the organization to connect to Odoo using their " +"Google Accounts." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:12 +msgid ":doc:`/applications/productivity/calendar/google`" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:13 +#: ../../content/applications/general/email_communication/email_servers.rst:66 +msgid ":doc:`/administration/maintain/google_oauth`" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:18 +#: ../../content/applications/general/voip/axivox.rst:16 +#: ../../content/applications/general/voip/onsip.rst:13 +msgid "Configuration" +msgstr "Konfiguracja" + +#: ../../content/applications/general/auth/google.rst:20 +msgid "" +"The integration of the Google sign-in function requires configuration both " +"on Google *and* Odoo." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:25 +msgid "Google API Dashboard" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:27 +msgid "" +"Go to the `Google API Dashboard `_." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:28 +msgid "" +"Make sure the right project is opened. If there isn't a project yet, click " +"on :guilabel:`Create Project`, fill out the project name and other details " +"of the company, and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Filling out the details of a new project." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:37 +msgid "Choose the name of the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:42 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:44 +msgid "On the left side menu, click on :menuselection:`OAuth consent screen`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Google OAuth consent selection menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:50 +msgid "" +"Choose one of the options (:guilabel:`Internal` / :guilabel:`External`), and" +" click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Choice of a user type in OAuth consent." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:58 +msgid "" +"*Personal* Gmail Accounts are only allowed to be **External** User Type, " +"which means Google may require an approval, or for *Scopes* to be added on. " +"However, using a *Google WorkSpace* account allows for **Internal** User " +"Type to be used." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:62 +msgid "" +"Note, as well, that while the API connection is in the *External* testing " +"mode, then no approval is necessary from Google. User limits in this testing" +" mode is set to 100 users." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:65 +msgid "" +"Fill out the required details and domain info, then click on :guilabel:`Save" +" and Continue`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:66 +msgid "" +"On the :menuselection:`Scopes` page, leave all fields as is, and click on " +":guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:68 +msgid "" +"Next, if continuing in testing mode (*External*), add the email addresses " +"being configured under the :guilabel:`Test users` step by clicking on " +":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " +"summary of the app registration appears." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:71 +msgid "" +"Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:76 +msgid "Credentials" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:78 +msgid "On the left side menu, click on :menuselection:`Credentials`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Credentials button menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:84 +msgid "" +"Click on :guilabel:`Create Credentials`, and select :guilabel:`OAuth client " +"ID`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "OAuth client id selection." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:90 +msgid "" +"Select :guilabel:`Web Application` as the :guilabel:`Application Type`. Now," +" configure the allowed pages on which Odoo will be redirected." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:93 +msgid "" +"In order to achieve this, in the :guilabel:`Authorized redirect URIs` field," +" enter the database's domain immediately followed by `/auth_oauth/signin`. " +"For example: `https://mydomain.odoo.com/auth_oauth/signin`, then click on " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:97 +msgid "" +"Now that the *OAuth client* has been created, a screen will appear with the " +":guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the " +":guilabel:`Client ID` for later, as it will be necessary for the " +"configuration in Odoo, which will be covered in the following steps." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:104 +msgid "Google Authentication on Odoo" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:109 +msgid "Retrieve the Client ID" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:111 +msgid "" +"Once the previous steps are complete, two keys are generated on the Google " +"API Dashboard: :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the" +" :guilabel:`Client ID`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst-1 +msgid "Google OAuth Client ID generated." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:121 +msgid "Odoo activation" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:123 +msgid "" +"Go to :menuselection:`Odoo General Settings --> Integrations` and activate " +":guilabel:`OAuth Authentication`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:127 +msgid "Odoo may prompt the user to log-in again after this step." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:129 +msgid "" +"Go back to :menuselection:`General Settings --> Integrations --> OAuth " +"Authentication`, activate the selection and :guilabel:`Save`. Next, return " +"to :menuselection:`General Settings --> Integrations --> Google " +"Authentication` and activate the selection. Then fill out the " +":guilabel:`Client ID` with the key from the Google API Dashboard, and " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Filling out the client id in Odoo settings." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:139 +msgid "" +"Google OAuth2 configuration can also be accessed by clicking on " +":guilabel:`OAuth Providers` under the :guilabel:`OAuth Authentication` " +"heading in :menuselection:`Integrations`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:145 +msgid "Log in to Odoo with Google" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:147 +msgid "" +"To link the Google account to the Odoo profile, click on :guilabel:`Log in " +"with Google` when first logging into Odoo." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Reset password screen with \"Log in with Google\" button." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:155 +msgid "" +"Existing users must :ref:`reset their password ` to " +"access the :menuselection:`Reset Password` page, while new users can " +"directly click on :guilabel:`Log in with Google`, instead of choosing a new " +"password." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:160 +msgid "" +"`Google Cloud Platform Console Help - Setting up OAuth 2.0 " +"`_" +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:3 +msgid "Sign in with LDAP" +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:5 +msgid "Install the LDAP module in General Settings." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:7 +msgid "Click on **Create** in Setup your LDAP Server." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:15 +msgid "Choose the company about to use the LDAP." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:20 +msgid "" +"In **Server Information**, enter the IP address of your server and the port " +"it listens to." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:22 +msgid "Tick **User TLS** if your server is compatible." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:27 +msgid "" +"In **Login Information**, enter ID and password of the account used to query" +" the server. If left empty, the server will be queried anonymously." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:32 +msgid "" +"In **Process Parameter**, enter the domain name of your LDAP server in LDAP " +"nomenclature (e.g. ``dc=example,dc=com``)." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:34 +msgid "In **LDAP filter**, enter ``uid=%s``" +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:39 +msgid "" +"In **User Information**, tick *Create User* if you want Odoo to create a " +"User profile the first time someone log in with LDAP." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:41 +msgid "" +"In **Template User**, indicate a template for the new profiles created. If " +"left blanked, the admin profile will be used as template." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:5 +msgid "Developer Mode (debug mode)" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:7 +msgid "" +"The developer mode (or debug mode) unlocks access to extra and advanced " +"tools in Odoo. There are several ways to activate the developer mode: " +"through the :ref:`settings `, the " +":ref:`browser extension `, through" +" the :ref:`command palette ` or the" +" :ref:`URL `." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:17 +msgid "Activate through the Settings" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:19 +msgid "" +"The debug mode can be activated in the Odoo database settings. Go to " +":menuselection:`Settings --> General Settings --> Developer Tools` and click" +" on :guilabel:`Activate the developer mode`. At least one application needs " +"to be installed for the :guilabel:`Developer Tools` section to appear in the" +" :guilabel:`Settings` module." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Overview of the debug options under settings in Odoo." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:29 +msgid "" +":guilabel:`Activate the developer mode (with assets)` is used by developers;" +" :guilabel:`Activate the developer mode (with tests assets)` is used by " +"developers and testers." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:32 +msgid "" +"Once activated, the :guilabel:`Deactivate the developer mode` option becomes" +" available." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:37 +msgid "Activate through the browser extension" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:39 +msgid "" +"Within a web browser, navigate to the browser settings and extensions and " +"search for the `Odoo Debug` extension. Once the extension is installed, a " +"new icon will be shown on the browser's toolbar." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:43 +msgid "" +"For the *Odoo Debug* extension, a single click enables a normal version of " +"the mode, while a double click enables it with assets. To deactivate it, use" +" a single click." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "View of Odoo's debug icon in a Google Chrome toolbar." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:53 +msgid "Activate through the command palette" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:55 +msgid "" +"In Odoo, the command palette tool has a command to activate the debug mode. " +"First, open the command palette tool with the keyboard shortcut `ctrl+k` and" +" then type `debug`. A command will show up to activate the debug mode." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Command palette with debug command." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:66 +msgid "Activate through the URL" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:68 +msgid "" +"The debug mode can also be activated by adding an extra query string to the " +"database's URL. In the URL, add `?debug=1` or `?debug=true` after `/web`. To" +" deactivate the debug mode, change the value to `?debug=0` instead." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Overview of a URL with the debug mode command added." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:77 +msgid "" +"Additional modes are available for developers: `?debug=assets` enables the " +":ref:`assets mode `, and " +"`?debug=tests` enables the :ref:`tests mode " +"`." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:84 +msgid "Locate the developer mode tools" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:86 +msgid "" +"Once developer mode is activated, the developer mode tools can be accessed " +"from the :guilabel:`Open Developer Tools` button, the bug icon located in " +"the header of the Odoo database." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Overview of a console page and the debug icon being shown in Odoo." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:93 +msgid "" +"This menu contains additional tools that are useful to understand or edit " +"technical data, such as the views or actions of a page. On a page that has " +"filters, actions, and view options, the developer mode tools contain some " +"useful menu items such as:" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:97 +msgid ":guilabel:`Edit Action`" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:98 +msgid ":guilabel:`Manage Filters`" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:99 +msgid "Edit the current view (e.g. Kanban, List, Graph, etc.)" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:100 +msgid "See the :guilabel:`Fields View Get`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:3 +msgid "Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:5 +msgid "" +"**Digest Emails** are periodic snapshots sent to your organization via email" +" that include high-level information about how your business is performing." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:8 +msgid "" +"Navigate to Digest Emails by going to :menuselection:`Settings --> General " +"Settings --> Statistics`, then activate the **Digest Emails** feature and " +"click on save." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst-1 +msgid "Digest Emails section inside General Settings." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:15 +msgid "You can control a variety of settings for your Digest Emails, such as:" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:17 +msgid "which KPIs are shared in the Digest" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:18 +msgid "how often Digest Emails are sent" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:19 +msgid "who in your organization receives Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:20 +msgid "creating custom Digest Email templates" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:21 +msgid "adding additional KPIs (Studio required)" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:24 +msgid "" +"By default, Digest Email is *enabled*, and *Your Odoo Periodic Digest* " +"serves as the primary template, which includes all KPI measurements across " +"your Odoo database and is sent daily to administrators." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:31 +msgid "Customize *Your Odoo Periodic Digest*" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:33 +msgid "" +"To customize the default Digest Email (*Your Odoo Periodic Digest*), go to " +":menuselection:`Settings --> General Settings --> Statistics --> Digest " +"Email`, select *Your Odoo Periodic Digest* and click on the *external link* " +"next to the dropdown selection." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:37 +msgid "" +"A popup window appears and presents a variety of editable settings, which " +"include:" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:39 +msgid "**Digest Title** - what you want your Digest Email to be called" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:40 +msgid "" +"**Periodicity** - control the regimen in how often Digest Emails are sent" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:41 +msgid "" +"**KPIs** - check/uncheck each calculated KPI that appears in Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:42 +msgid "**Recipients** - add/remove users who receive your Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:43 +msgid "**Custom** - add your own KPIs (Studio required)" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst-1 +msgid "Customize default Digest Email settings and custom KPIs." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:52 +msgid "Custom digest emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:54 +msgid "To do so, click on **Configure Digest Emails** and then **Create**." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:56 +msgid "" +"From there, give your Digest Email a title, specify periodicity, and choose " +"your desired KPIs and recipients fields as needed." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:59 +msgid "" +"After you click **Save**, your new custom Digest Email is available as a " +"selection in the **General Settings** dropdown menu." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:65 +msgid "Custom KPIs with Studio" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:67 +msgid "" +"For either *Your Odoo Periodic Digest* or your own custom Digest Email, you " +"can add your own KPIs by using Odoo Studio." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:70 +msgid "" +"To begin, click the **Toggle Studio** icon or click the **Recipients** tab " +"and then the ellipses :menuselection:`… icon --> Add Custom Field` to edit " +"the template or add additional fields." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:73 +msgid "" +"In order to create additional fields, you must create two fields on the " +"digest object:" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:75 +msgid "" +"create a boolean field called `kpi_myfield` and display it in the KPIs tab" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:76 +msgid "" +"create a computed field called `kpi_myfield_value` that computes your " +"customized KPI" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:77 +msgid "select your KPI(s) in the KPIs tab." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:80 +msgid "Computed values reference table" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:83 +msgid "LABEL" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:83 +msgid "VALUE" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:85 +msgid "Connected Users" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:85 +msgid "`kpi_res_users_connected_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:87 +msgid "Messages Sent" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:87 +msgid "`kpi_mail_message_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:89 +msgid "New Leads" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:89 +msgid "`kpi_crm_lead_created_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:91 +msgid "Opportunities Won" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:91 +msgid "`kpi_crm_opportunities_won_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:93 +msgid "Open Tasks" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:93 +msgid "`kpi_project_task_opened_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:95 +msgid "Tickets Closed" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:95 +msgid "`kpi_helpdesk_tickets_closed_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:97 +msgid "% of Happiness" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:97 +msgid "`kpi_livechat_rating_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:99 +msgid "Conversations handled" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:99 +msgid "`kpi_livechat_conversations_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:101 +msgid "Time to answer (sec)" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:101 +msgid "`kpi_livechat_response_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:103 +msgid "All Sales" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:103 +msgid "`kpi_all_sale_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:105 +msgid "eCommerce Sales" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:105 +msgid "`kpi_website_sale_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:107 +msgid "Revenue" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:107 +msgid "`kpi_account_total_revenue_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:109 +msgid "Bank & Cash Moves" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:109 +msgid "`kpi_account_bank_cash_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:111 +msgid "POS Sales" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:111 +msgid "`kpi_pos_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:113 +msgid "New Employees" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:113 +msgid "`kpi_hr_recruitment_new_colleagues_value`" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:5 +msgid "Email Communication" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:3 +msgid "Configure DNS records to send emails in Odoo" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:6 +msgid "SPAM labels overview" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:8 +msgid "" +"Sometimes, emails from Odoo are misclassified by the different email " +"providers and end up in spam folders. At the moment, some settings are out " +"of Odoo's control, notably the way the different email providers classify " +"Odoo's emails according to their own restriction policy and/or limitations." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:12 +msgid "" +"It is standard in Odoo that emails are received from ``\"name of the " +"author\" ``. In other words this can be " +"translated to: ``\"name of the author\" " +"<{ICP.mail.from.filter}@{mail.catchall.domain}>``. In this case ICP stands " +"for `ir.config.parameters`, which are the System Parameters. Deliverability " +"is greatly improved with the :ref:`notifications configuration " +"`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:18 +msgid "" +"In order for servers to accept emails from Odoo on a more regular basis, one" +" of the solutions is for customers to create rules within their own mailbox." +" A filter can be added to the email inbox so that when email is received " +"from Odoo (`notifications@mycompany.odoo.com`) it is moved to the inbox. It " +"is also possible to add the Odoo database domain onto a safe senders list or" +" whitelist on the receiving domain." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:24 +msgid "" +"If an Odoo email server appears on a blacklist, notify Odoo via a `new help " +"ticket `_ and the support team will work to get " +"the servers removed from the blacklist." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:28 +msgid "" +"Should the Odoo database be using a custom domain for sending emails from " +"Odoo there are three records that should be implemented on the custom " +"domain's DNS to ensure deliverability of email. This includes setting " +"records for :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys " +"Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, " +"Reporting, & Conformance)`. Ultimately though, it is up to the discretion of" +" the final receiving mailbox." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:38 +msgid "Be SPF compliant" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:40 +msgid "" +"The Sender Policy Framework (SPF) protocol allows the owner of a domain name" +" to specify which servers are allowed to send emails from that domain. When " +"a server receives an incoming email, it checks whether the IP address of the" +" sending server is on the list of allowed IPs according to the sender's " +":abbr:`SPF (Sender Policy Framework)` record." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:46 +msgid "" +"The :abbr:`SPF (Sender Policy Framework)` verification is performed on the " +"domain mentioned in the `Return-Path` field of the email. In the case of an " +"email sent by Odoo, this domain corresponds to the value of the " +"`mail.catchall.domain` key in the database system parameters." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:50 +msgid "" +"The :abbr:`SPF (Sender Policy Framework)` policy of a domain is set using a " +"TXT record. The way to create or modify a TXT record depends on the provider" +" hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. In " +"order for the verification to work properly, each domain can only have one " +":abbr:`SPF (Sender Policy Framework)` record." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:55 +msgid "" +"If the domain name does not yet have a :abbr:`SPF (Sender Policy Framework)`" +" record, create one using the following input: `v=spf1 include:_spf.odoo.com" +" ~all`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:58 +msgid "" +"If the domain name already has a :abbr:`SPF (Sender Policy Framework)` " +"record, the record must be updated (and do not create a new one)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:63 +msgid "" +"If the TXT record is `v=spf1 include:_spf.google.com ~all`, edit it to add " +"`include:_spf.odoo.com`: `v=spf1 include:_spf.odoo.com " +"include:_spf.google.com ~all`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:66 +msgid "" +"Check if the :abbr:`SPF (Sender Policy Framework)` record is valid with a " +"free tool like `MXToolbox SPF `_." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:72 +msgid "Enable DKIM" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:74 +msgid "" +"The DomainKeys Identified Mail (DKIM) allows a user to authenticate emails " +"with a digital signature." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:77 +msgid "" +"When sending an email, the Odoo server includes a unique :abbr:`DKIM " +"(DomainKeys Identified Mail)` signature in the headers. The recipient's " +"server decrypts this signature using the :abbr:`DKIM (DomainKeys Identified " +"Mail)` record in the database's domain name. If the signature and the key " +"contained in the record match, this guarantees that the message is authentic" +" and has not been altered during transport." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:83 +msgid "" +"To enable :abbr:`DKIM (DomainKeys Identified Mail)`, add a :abbr:`CNAME " +"(Canonical Name)` record to the :abbr:`DNS (Domain Name System)` zone of the" +" domain name:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:86 +msgid "`odoo._domainkey IN CNAME odoo._domainkey.odoo.com.`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:89 +msgid "" +"If the domain name is `mycompany.com`, make sure to create a subdomain " +"`odoo._domainkey.mycompany.com` whose canonical name is " +"`odoo._domainkey.odoo.com.`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:92 +msgid "" +"The way to create or modify a :abbr:`CNAME (Canonical Name)` record depends " +"on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the " +"domain name. The most common providers are :ref:`listed below " +"`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:96 +msgid "" +"Check if the :abbr:`DKIM (DomainKeys Identified Mail)` record is valid with " +"a free tool like `DKIM Core `_. If a selector " +"is asked, enter `odoo`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:100 +msgid "Check the DMARC policy" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:102 +msgid "" +"The Domain-based Message Authentication, Reporting, & Conformance (DMARC) " +"record is a protocol that unifies :abbr:`SPF (Sender Policy Framework)` and " +":abbr:`DKIM (DomainKeys Identified Mail)`. The instructions contained in the" +" :abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` record of a domain name tell the destination server what to do" +" with an incoming email that fails the :abbr:`SPF (Sender Policy Framework)`" +" and/or :abbr:`DKIM (DomainKeys Identified Mail)` check." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:110 +msgid "DMARC: TXT record" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:112 +msgid "`v=DMARC1; p=none;`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:114 +msgid "" +"There are three :abbr:`DMARC (Domain-based Message Authentication, " +"Reporting, & Conformance)` policies:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:117 +msgid "`p=none`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:118 +#: ../../content/applications/general/email_communication/email_domain.rst:171 +msgid "`p=quarantine`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:119 +msgid "`p=reject`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:121 +msgid "" +"`p=quarantine` and `p=reject` instruct the server that receives an email to " +"quarantine that email or ignore it if the :abbr:`SPF (Sender Policy " +"Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check fails." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:125 +msgid "" +"If the domain name uses :abbr:`DMARC (Domain-based Message Authentication, " +"Reporting, & Conformance)` and has defined one of these policies, the domain" +" must be :abbr:`SPF (Sender Policy Framework)` compliant or enable " +":abbr:`DKIM (DomainKeys Identified Mail)`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:130 +msgid "" +"Yahoo or AOL are examples of email providers with a :abbr:`DMARC (Domain-" +"based Message Authentication, Reporting, & Conformance)` policy set to " +"`p=reject`. Odoo strongly advises against using an *@yahoo.com* or " +"*@aol.com* address for the database users. These emails will never reach " +"their recipient." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:135 +msgid "" +"`p=none` is used for the domain owner to receive reports about entities " +"using their domain. It should not impact the deliverability if the " +":abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` check fails." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:139 +msgid "" +":abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` records are comprised of tags in the form of :abbr:`DNS " +"(Domain Name System)` records. These tags/parameters allow for reporting, " +"such as :abbr:`RUA (Reporting URI of aggregate reports)` and :abbr:`RUF " +"(Reporting URI for forensic reports)`, along with more precise specification" +" like :abbr:`PCT (Percentage of messages subjected to filtering)`, :abbr:`P " +"(Policy for organizational domain)`, :abbr:`SP (Policy for subdomains of the" +" OD)` :abbr:`ADKIM (Alignment mode for DKIM)` & :abbr:`ASPF (Alignment mode " +"for SPF)`. For best practice, the the :abbr:`DMARC (Domain-based Message " +"Authentication, Reporting, & Conformance)` policy should not start out being" +" too restrictive." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:148 +msgid "The following chart displays available tags:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:154 +msgid "Tag Name" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:155 +msgid "Purpose" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:156 +msgid "Example" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:157 +msgid "v" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:158 +msgid "Protocol version" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:159 +msgid "`v=DMARC1`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:160 +msgid "pct" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:161 +msgid "Percentage of messages subjected to filtering" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:162 +msgid "`pct=20`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:163 +msgid "ruf" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:164 +msgid "Reporting URI for forensic reports" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:165 +msgid "`ruf=mailto:authfail@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:166 +msgid "rua" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:167 +msgid "Reporting URI of aggregate reports" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:168 +msgid "`rua=mailto:aggrep@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:169 +msgid "p" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:170 +msgid "Policy for organizational domain" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:172 +msgid "sp" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:173 +msgid "Policy for subdomains of the OD" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:174 +msgid "`sp=reject`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:175 +msgid "adkim" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:176 +msgid "Alignment mode for DKIM" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:177 +msgid "`adkim=s`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:178 +msgid "aspf" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:179 +msgid "Alignment mode for SPF" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:180 +msgid "`aspf=r`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:182 +msgid "" +"Check the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` record of a domain name with a tool like `MXToolbox DMARC " +"`_." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:186 +msgid "" +"`DMARC.org is another great resource to learn about DMARC records. " +"`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:192 +msgid "SPF, DKIM & DMARC documentation of common providers" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:194 +msgid "" +"`OVH DNS " +"`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:195 +msgid "" +"`OVH SPF `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:196 +msgid "" +"`GoDaddy TXT record `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:197 +msgid "`GoDaddy SPF `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:198 +msgid "" +"`GoDaddy DKIM `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:199 +msgid "" +"`NameCheap " +"`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:201 +msgid "" +"`CloudFlare DNS `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:202 +msgid "" +"`Google Domains `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:203 +msgid "" +"`Azure DNS `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:205 +msgid "" +"To fully test the configuration, use the `Mail-Tester `_ tool, which gives a full overview of the content and " +"configuration in one sent email. Mail-Tester can also be used to configure " +"records for other, lesser-known providers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:210 +msgid "" +"`Using Mail-Tester to set SPF Records for specific carriers " +"`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:3 +msgid "Send and receive emails in Odoo with an email server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:6 +msgid "Odoo Online or Odoo.sh users" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:8 +msgid "" +"Since **Odoo sets up its own mail servers for the database**, outgoing and " +"incoming emails already work out-of-the-box. So for **Odoo Online** and " +"**Odoo.sh** customers, nothing needs to be configured!" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:12 +msgid "" +"Unless an external mail server is required to send large batches of mass " +"emails, simply use the standard online Odoo database normally since it has " +"already been pre-configured to send email." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:16 +msgid "" +"The Odoo server is subject to a daily email limit to prevent abuse. The " +"default limit is 200 emails sent per day for databases with an " +"**Enterprise** subscription. This limit can be increased under certain " +"conditions. See the :doc:`FAQ ` or contact support for more " +"information." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:22 +msgid "Scope of this documentation" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:24 +msgid "" +"This document is **mainly dedicated to Odoo on-premise databases** who don't" +" benefit from an out-of-the-box solution to send and receive emails in Odoo," +" unlike `Odoo Online `_ and `Odoo.sh " +"`_. Incoming and outgoing servers must be configured " +"for on-premise databases." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:29 +msgid "" +"The following sections below contain information on how to integrate an " +"external email server with Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:33 +msgid "" +"If no one in the company is employed to manage email servers, Odoo Online " +"and Odoo.sh are strongly recommended. In these Odoo hosting types email " +"sending and receiving works instantly and is monitored by professionals. " +"Nevertheless, a company can use their own email server if they want to " +"manage the email server's reputation themselves. For more information see " +":doc:`Configure DNS records to send emails in Odoo `" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:42 +msgid "Default notifications system" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:44 +msgid "" +"Documents in Odoo (such as a CRM opportunity, a sales order, an invoice, " +"etc.) have a discussion thread, called *chatter*." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:47 +msgid "" +"When a database user posts a message in the chatter, this message is sent by" +" email to the followers of the document as a notification (except to the " +"sender). If a follower replies to the message, the reply updates the " +"chatter, and Odoo relays another reply to the followers as a notification. " +"Messages sent back to the chatter from users or external users will appear " +"in the chatter from their respective email, or as the name listed in their " +"*Contacts* record." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:53 +msgid "" +"These notifications are sent using a default from address. For more " +"information see :ref:`Use a default email address " +"`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:57 +msgid "Manage outbound messages" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:59 +msgid "" +"As a system admin, go to :menuselection:`Settings --> General Settings --> " +"Discuss` in Odoo, and enable the :guilabel:`Custom Email Servers` option. " +"Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers`" +" and click :guilabel:`Create` to create a new outgoing mail server record in" +" Odoo. Reference the SMTP data of the external email server. Once all the " +"information has been filled out, click :guilabel:`Test Connection`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:70 +msgid "" +"Ensuring the outgoing domain has :abbr:`SPF (Sender Policy Framework)`, " +":abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based " +"Message Authentication, Reporting, & Conformance)` set up on the :abbr:`DNS " +"(Domain Name System)` will improve deliverability. For more information see " +":doc:`email_domain`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:78 +msgid "Port restriction" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:80 +msgid "" +"Note that port 25 is blocked for security reasons on the Odoo Online and " +"Odoo.sh platforms. Try using ports 465, 587, or 2525 instead." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:86 +msgid "Use a default \"From\" email address" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:88 +msgid "" +"Sometimes, an email's \"From\" (outgoing) address can belong to a different " +"domain, and that can be a problem." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:91 +msgid "" +"For example, if a customer with the email address " +"`mary\\@customer.example.com` responds to a message, Odoo will try to " +"redistribute that same email to the other subscribers in the thread. " +"However, if the domain `customer.example.com` forbids that kind of usage for" +" security, the email that Odoo is trying to redistribute would get rejected " +"by some recipients' email servers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:96 +msgid "" +"To avoid that problem, Odoo sends all emails using a \"From\" address from " +"the same authorized domain." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:99 +msgid "" +"Access the :guilabel:`System Parameters` by activating :ref:`developer mode " +"` and going to :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` menu." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:102 +msgid "" +"To force the email address from which emails are sent, a combination of the " +"following keys needs to be set in the system parameters of the database:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:105 +msgid "" +"`mail.default.from`: accepts the local part or a complete email address as " +"value" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:106 +msgid "" +"`mail.default.from_filter`: accepts a domain name or a full email address as" +" value" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:109 +msgid "" +"The `mail.default.from_filter` works only for `odoo-bin` configurations or " +"the default Odoo email server, otherwise this parameter can be set using the" +" `from_filter` field on `ir.mail_server`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:112 +msgid "" +"The field can be a domain name or an entire email address, or it can remain " +"empty. If the sender's email address does not match this set filter, then " +"the email will be encapsulated using a combination of the two system " +"parameters: `mail.default.from` and `mail.catchall.domain`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:117 +msgid "" +"In the following example, the from email address is replaced with the " +"combination of the the two system parameters (`mail.default.from` and " +"`mail.catchall.domain`). This is the default\\ notifications configuration " +"in Odoo: ``“Admin” `` => ``“Admin” " +"``." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:122 +msgid "" +"In other words if the email address of the author does not match " +"`mail.default.from_filter`, the email address is replaced by " +"`mail.default.from` (if it contains a full email address) or a combination " +"of `mail.default.from` and `mail.catchall.domain`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:126 +msgid "" +"If the `from_filter` contains a full email address, and if the " +"`mail.default.from` is the same as this address, then all of the email " +"addresses that are different from `mail.default.from` will be encapsulated " +"in `mail.default.from`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:133 +msgid "Utilizing the \"From\" filter on an outgoing email server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:135 +msgid "" +"The :guilabel:`FROM Filtering` field allows for the use of a specific " +"outgoing email server depending on the :guilabel:`From` email address or " +"domain that Odoo is sending on behalf of. This setting can be used to " +"improve the deliverability or sending success rate of emails sent from the " +"database. Setting the :guilabel:`FROM Filtering` field can also be used to " +"send from different domains in a multi-company environment. Access this " +"field in Odoo by navigating to :menuselection:`Settings --> Discuss --> " +"Custom Mail Servers --> Outgoing Mail Servers --> New`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst-1 +msgid "Outgoing email server settings and the FROM filter settings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:146 +msgid "" +"When an email is sent from Odoo while the :guilabel:`FROM Filtering` field " +"is set, an email server is chosen in the following sequence:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:149 +msgid "" +"First, Odoo searches for an email server that has the same :guilabel:`FROM " +"Filtering` value as the :guilabel:`From` value (email address) defined in " +"the outgoing email. For example, if the :guilabel:`From` value (email " +"address) is `test\\@example.com`, only the email servers that have the " +":guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:153 +msgid "" +"However, if no email servers are found that use the :guilabel:`From` value, " +"then Odoo searches for an email server that has the same *domain* as the " +":guilabel:`From` value (email address) defined in the outgoing email. For " +"example, if the :guilabel:`From` email address is `test\\@example.com`, only" +" the email servers that have the :guilabel:`FROM Filtering` value equal to " +"`example.com` are returned." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:159 +msgid "" +"If no email servers are found after checking for the domain, then Odoo " +"returns all email servers that do not have any :guilabel:`FROM Filtering` " +"value(s) set." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:162 +msgid "" +"Should this query return no results, then Odoo performs a search for an " +"email server using the system parameter: `mail.default.from`. First, the " +"email address listed attempts to match an email server, and then the domain " +"attempts to find a match. If no email server is found, Odoo returns the " +"first outgoing email server (sorted by priority)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:168 +msgid "" +"If several email servers are found, then Odoo uses the first one according " +"to its priority. For example, if there are two email servers, one with a " +"priority of `10` and the other with a priority of `20`, then the email " +"server with a priority of `10` is used first." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:175 +msgid "Set up different dedicated servers for transactional and mass emails" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:177 +msgid "" +"In Odoo a separate email server can be used for transactional emails and " +"mass mailings. Example: Use Postmark or SendinBlue for transactional emails," +" and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet " +"` for mass mailings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:182 +msgid "" +"A default outgoing email server is already configured. Do not create an " +"alternative one unless a specific external outgoing email server is needed " +"for technical reasons." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:185 +msgid "" +"To do this, first activate the :ref:`developer mode `, and " +"then go to :menuselection:`Settings --> Technical --> Outgoing` email " +"servers. There, create two outgoing email server settings; one for the " +"transactional emails and one for the mass mailing server. Make sure to give " +"priority to the transactional server over the mass mailing server by " +"providing a lower priority number for the transactional email server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:191 +msgid "" +"Now, go to :menuselection:`Email Marketing --> Settings` and enable " +":guilabel:`Dedicated Server`. Choose the appropriate email server. With " +"these settings, Odoo uses the server with the lower priority for " +"transactional emails, and the server here selected for mass mails. Note that" +" in this case, the domain's Sender Policy Framework (SPF) records must be " +"set to include both transactional and mass mail servers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:198 +msgid ":doc:`email_domain`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:203 +msgid "Manage inbound messages" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:205 +msgid "Odoo relies on generic email aliases to fetch incoming messages." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:207 +msgid "" +"**Reply messages** of messages sent from Odoo are routed to their original " +"discussion thread (and to the inbox of all its followers) by the alias of " +"the model if there is any or by the catchall alias (**catchall@**). Replies " +"to messages of models that don't have a custom alias will use the catchall " +"alias (`catchall@mycompany.odoo.com`). The catchall address, however, does " +"not have another action attached to it like other aliases might, it is only " +"used to collect replies." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:212 +msgid "" +"**Bounced messages** are used as a Return-Path. One example this is " +"especially useful for is in `Odoo Email Marketing " +"`__. In this case bounces are " +"opt-out based on if the email bounced too many times (5) in the last month " +"and the bounces are separated by one week. This is done to avoid " +"blacklisting someone because of a mail server error. If these circumstances " +"are met then the email is considered invalid and is blacklisted. A log note " +"is added on the contact under :guilabel:`Blacklisted Email Addresses` on the" +" :guilabel:`Email Marketing Configuration Menu`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:220 +msgid "" +"Messages that bounce in the chatter (outside of Email Marketing) will " +"populate a red envelope indicating the failed delivery. This can be helpful " +"to know that a Sales Order or an Invoice did not reach its final " +"destination." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:223 +msgid "" +"**Original messages**: several business objects have their own alias to " +"create new records in Odoo from incoming emails:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:226 +msgid "" +"Sales channel (to create *Leads* or *Opportunities* in `Odoo CRM " +"`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:228 +msgid "" +"Support channel (to create *Tickets* in `Odoo Helpdesk " +"`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:229 +msgid "" +"Projects (to create new *Tasks* in `Odoo Project `_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:231 +msgid "" +"Job positions (to create *Applicants* in `Odoo Recruitment " +"`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:234 +msgid "" +"Depending on the mail server, there might be several methods to fetch " +"emails. The easiest and most recommended method is to manage one email " +"address per Odoo alias in the mail server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:237 +msgid "" +"Create the corresponding email addresses in the mail server (**catchall@**, " +"**bounce@**, **sales@**, etc.)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:239 +msgid "" +"Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> " +"General Settings --> Discuss`. Changing the :guilabel:`Alias Domain` will " +"change the catchall's domain for the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:242 +msgid "" +"If the database's hosting type is Odoo on-premise, create an " +":guilabel:`Incoming Mail Server` in Odoo for each alias. To create a new " +"incoming server go to: :menuselection:`Settings --> Discuss --> Custom Mail " +"Servers --> Incoming Mail Servers --> New` Fill out the form according to " +"the email provider's settings. Leave the :guilabel:`Actions to Perform on " +"Incoming Mails` field blank. Once all the information has been filled out, " +"click on :guilabel:`TEST & CONFIRM`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:0 +msgid "Incoming mail server configuration on Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:252 +msgid "" +"If the database's hosting type is Odoo Online or Odoo.sh, redirecting or " +"forwarding incoming messages to Odoo's domain name instead of the external " +"email server is recommended. That way, incoming messages can be received " +"without delay. Redirections for all email addresses should be set to Odoo's " +"domain name in the email server (e.g. `catchall\\@mydomain.ext` to " +"`catchall\\@mycompany.odoo.com`)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:258 +msgid "" +"All the aliases are customizable in Odoo. Object aliases can be edited from " +"their respective configuration view by navigating to " +":menuselection:`Settings --> Technical Menu --> Email --> Aliases`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:262 +msgid "" +"To edit catchall and bounce aliases, first activate the :ref:`developer mode" +" `. Then, go to :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` to customize the aliases " +"(`mail.catchall.alias` & `mail.bounce.alias`). These types of changes should" +" be completed prior to the database going live. If a customer replies after " +"a change is made then the system will not recognize the old alias and the " +"reply won't be received." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:268 +msgid "" +"By default, inbound messages are fetched every 5 minutes for on-premise " +"databases." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:271 +msgid "" +"This value can be changed in :ref:`developer mode `. Go to " +":menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`" +" and look for :guilabel:`Mail: Fetchmail Service`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:3 +msgid "Email Templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:5 +msgid "" +"We all know writing good emails is vital to get a high response rate, but " +"you do not want to rewrite the same structure every time, do you? That is " +"where email templates come in. Without the need to rewrite the entire email " +"structure every time, you save time to focus on the content. Multiple " +"templates also let you deliver the right message to the right audience, " +"improving their overall experience with the company." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:12 +msgid "" +"The email templates use QWeb. The composer allows you to edit emails in " +"their final rendering, making customizations more robust as you don’t have " +"to edit code." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:16 +msgid "Defining a default reply to on your mail template" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:18 +msgid "" +"Although the field *reply to* is available within the mail templates, **this" +" field is only used for mass mailing** mode (this means when sending " +"templates on what we call bulk emailing). You can send emails in bulk in " +"almost every app that has a list view. Select the records you want and click" +" on the action button. If you have an option to send an email, you will see " +"a mail composer with possible values to define:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Composer in mass mailing mode after selecting multiple quotations." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:28 +msgid "You can also define them by default on the template:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Reply-to field on template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:34 +msgid "" +"Because of this, setting a value in this field is useless as the value " +"defined will be totally ignored. The default *reply-to* value is the default" +" catchall email address to ensure a communication between your customer and " +"your Odoo database. For more information about the way the catchall works, " +"please check :ref:`how to manage inbound messages " +"`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:40 +msgid "Transactional emails and corresponding URL for each company" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:42 +msgid "" +"When using Odoo, multiple events trigger the sending of automated emails. " +"These emails are known as transactional emails and sometimes contain links " +"pointing to your Odoo database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:45 +msgid "" +"By default, links generated by the database use the dynamic web.base.url key" +" defined in the system parameters. More information about this " +":ref:`parameter `." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:48 +msgid "" +"If the website application isn't installed, the web.base.url key will always" +" be the default parameter used to generate all the links." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:51 +msgid "" +"It’s important to know that this key can only have a single value, meaning " +"that in a multi-website/company database environment, even if you have a " +"specific domain name for each website, the links generated to share a " +"document or within a transactional email might remain the same, whatever the" +" website/company related to the sending of the email/document." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:56 +msgid "" +"This is not always the case as some Odoo applications have a link " +"established in the database with the website application, meaning that in " +"this case, if a specific domain is defined for the websites, the URL " +"generated in the email template will use the domain defined on the " +"corresponding website of the company." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:62 +msgid "" +"A document shared using the documents application will always use the " +"web.base.url key, as the document shared isn't associated with any " +"particular website. Meaning that the URL will always be the same (the " +"web.base.url key value), whatever the company it's shared from, this is a " +"known limitation!" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:67 +msgid "" +"On the other hand, sales orders made by a customer on one of your Odoo " +"e-commerce websites have a link established with the website from which the " +"order was made. As a result, the e-mail sent for the sales orders uses the " +"domain name defined for the corresponding website to generate the links." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:71 +msgid "" +"For more information about how to configure your domains, we invite you to " +"check :doc:`our domain name documentation " +"`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:75 +msgid "Updating translations within email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:77 +msgid "" +"Email templates are automatically translated. Changing the translations " +"shouldn’t be necessary. However, if for a specific reason you’d like to " +"change some of the translations, this can be done." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:80 +msgid "" +"Like any modification in the code, keep in mind that modifications that " +"aren’t done correctly (for example modifications leading to bad syntax) can " +"break the template, as a result, the template will appear blank." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:84 +msgid "" +"In order to edit your translations, follow these steps from the template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:86 +msgid "Click on the edit button, then on the language button" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:0 +msgid "Edit the language of a template" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:92 +msgid "" +"A pop-up window with the different languages installed on the database will " +"be displayed. From here, editing the translations will be possible. Don't " +"forget to hit the save button to preserve your changes." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:0 +msgid "" +"Translation of the body of the Application template in the different " +"languages installed." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:3 +msgid "FAQ" +msgstr "FAQ" + +#: ../../content/applications/general/email_communication/faq.rst:5 +msgid "" +"This document contains an explanation of the most recurring mailing " +"concerns." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:7 +msgid "" +"We will start by addressing issues of outgoing emails (ex: my client has not" +" received my email), and then, of incoming emails (ex: I do not receive " +"responses from my customers in the database)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:11 +msgid "Outgoing emails" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:16 +msgid "What do you have to check if your email is not sent?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:18 +msgid "" +"The first indicator showing you that the email has not been sent is the red " +"envelope next to the date and time of the message." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Red envelope displayed in chatter" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:26 +msgid "Common error messages" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:31 +msgid "You reached your daily limit:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Warning in Odoo upon email limit reached" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:37 +msgid "" +"Each email service provider has its own email sending limits. The limits may" +" be daily, hourly, and sometimes even per minute. This is the same for Odoo," +" we have to limit our customers to prevent our e-mail servers from being " +"blacklisted." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:41 +msgid "Here are the default limits for new databases:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:43 +msgid "" +"200 emails/day for Odoo Online and Odoo.sh databases with an active " +"subscription," +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:45 +msgid "50 emails/day for one-app free and trial databases," +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:47 +msgid "" +"in case of migration, your daily limit might be reset to 50 emails a day." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:49 +msgid "In case you hit the limit, you can:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:51 +msgid "" +"Ask our support team to increase your daily limit. We will analyze the " +"situation of your database depending on (non-exhaustive list):" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:54 +msgid "How many users in your database," +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:55 +msgid "Which apps are installed," +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:56 +msgid "" +"Your bounce rate: the percentage of email addresses that did not receive " +"your emails because it was returned by a mail server on its way to the final" +" recipient. You can contact the `support `_." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:60 +msgid "" +"Use your own outgoing email server to be independent of Odoo’s mail limit " +"(please refer to :doc:`the corresponding documentation " +"`)," +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:62 +msgid "" +"Wait until 11pm UTC for the reset and click on the retry button: The " +":ref:`Developer mode ` must be activated. Then, go to " +":menuselection:`Settings --> Technical --> Emails`" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Retry button of an emails" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:70 +msgid "" +"The daily limit is global to your database and can rise quickly! By default " +"an internal message, a notification, a note, etc. counts as an email in your" +" daily limit if it notifies someone." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:73 +msgid "" +"You can mitigate this by receiving your :ref:`notifications in Odoo " +"` instead of by emails." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:77 +msgid "SMTP Error" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:79 +msgid "" +"You can find out why an email wasn't transmitted successfully by reviewing " +"the Simple Mail Transport Protocol (SMTP) error messages. SMTP is a protocol" +" to describe the email structure and transmit it over the Internet, and the " +"error messages generated by email services are helpful tools to diagnose and" +" troubleshoot email problems." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:85 +msgid "No Error" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:87 +msgid "" +"Odoo is not always capable of providing information for the reason it " +"failed. The different providers implement a personalized policy of the " +"bounce emails and it is not always possible for Odoo to interpret it " +"correctly." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:91 +msgid "" +"If you have this problem on a recurring basis with the same client or the " +"same domain, please do not hesitate to contact `Odoo Support " +"`_ for help in finding a reason." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:94 +msgid "" +"Note: in such case, one of the most common reasons is related to :ref:`SPF " +"` and/or :ref:`DKIM " +"` configuration." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:98 +msgid "Why is my email sent late?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:100 +msgid "" +"It may happen that you schedule an email campaign but it is not sent on " +"time. We know that we use a delayed job to send emails that we consider as " +"not urgent (Newsletters concept such as mass mailing, marketing automation, " +"events). The system utility **cron** can be used to schedule programs to run" +" automatically at predetermined intervals. We use that policy in order to " +"avoid cluttering the mail servers and prioritize the communication." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:106 +msgid "" +"The emails considered urgent (communication from one person to another one " +"such as Sales Orders, Invoices, Purchase Orders, etc.) are sent directly." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Email scheduled to be sent later." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:113 +msgid "" +"By default, the Mass Mailing cron runs every 60 minutes. So, you should wait" +" maximum an hour before the campaign is actually sent." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:117 +msgid "Incoming emails" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:119 +msgid "" +"When you have an issue with incoming emails, there might not be an " +"indication per se in Odoo. This is the client who tries to contact a " +"database who will get a bounce (most of the time 550: mailbox unavailable)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:124 +msgid "Emails are not received" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:126 +msgid "Depending on the platform you are using:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:128 +msgid "" +"The **Odoo.sh** users can find their live logs on the folder " +":file:`~/logs/`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:130 +msgid "" +"The folder :file:`~/logs/` (preferably accessed by the command line) of an " +"Odoo.sh contains a list of files containing the logs of the database. The " +"log files are created everyday at 5:00 AM UTC. The two last days are not " +"compressed, while the older ones are, in order to gain space. The naming of " +"the files for Today and Yesterday are :file:`odoo.log` and " +":file:`odoo.log.1`. For the following, they are named with their dates and " +"compressed. See the Odoo.sh documentation about :ref:`logs `. " +"Use the command ``grep`` and ``zgrep`` (for the compressed ones) to search " +"through the files." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:138 +msgid "" +"**Odoo Online** users won’t have access to their logs. However you can still" +" contact `Odoo Support `_ , if you have a " +"recurring issue with the same client or domain." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:143 +msgid "Get help from support" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:145 +msgid "" +"In order to get helped efficiently, please provide as much information as " +"possible. Here is a list of what can be helpful:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:148 +msgid "" +"The **EML** of the email, stating for *Electronic Mail*, is the file format " +"containing all the technical information required for an investigation. The " +"documentation of your own email provider might help you on how to get your " +"EML files. Once you get the EML of the email, adding it in the attachment of" +" your ticket is the most efficient way for us to investigate. The support " +"will mainly focus on redundant issues." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:155 +msgid "`Gmail documentation `_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:157 +msgid "" +"`Outlook documentation `_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:160 +msgid "" +"The exact flow you are following in order to normally receive those emails " +"in Odoo. Here are examples of questions whose answers can be useful:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:163 +msgid "Is this simply a reply from an email going out from Odoo ?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:165 +msgid "Are you using an incoming email server or somehow redirecting?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:167 +msgid "" +"Can you provide us with an example of an email that has been correctly " +"forwarded ?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:169 +msgid "Providing answers to the following questions:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:171 +msgid "" +"Is it a generic issue or is it specific to a use case? If yes, which one " +"exactly?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:173 +msgid "" +"Is it working as expected? In case the email is sent using Odoo, the bounce " +"email should reach the Odoo database and display the :ref:`red envelope " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:8 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:10 +msgid "" +"When working with a database, it sometimes is necessary to export your data " +"in a distinct file. Doing so can help to do reporting over your activities " +"(even if Odoo offers a precise and easy reporting tool with each available " +"application)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:14 +msgid "" +"With Odoo, you can export the values from any field in any record. To do so," +" activate the list view on the items that need to be exported, click on " +"*Action*, and, then, on *Export*." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst-1 +msgid "view of the different things to enable/click to export data" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:22 +msgid "" +"Pretty simple, this action still comes with some specificities. In fact, " +"when clicking on *Export*, a pop-up window appears with several options for " +"the data to export:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst-1 +msgid "" +"overview of all the options to take into account when exporting data in Odoo" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:30 +msgid "" +"With the *I want to update data* option ticked, the system only shows the " +"fields which can be imported. This is very helpful in case you want to " +"update existing records. Basically, this works like a filter. Leaving the " +"box unticked gives way more field options because it shows all the fields, " +"not just the ones which can be imported." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:36 +msgid "" +"When exporting, you can choose between two formats: .csv and .xls. With " +".csv, items are separated with a comma, while .xls holds information about " +"all the worksheets in a file, including both content and formatting." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:39 +msgid "" +"Those are the items you may want to export. Use the arrows to display more " +"sub-field options. Of course, you can use the search bar to find specific " +"fields more easily. To use the search option more efficiently, display all " +"the fields by clicking on all the arrows!" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:44 +msgid "The + button is there to add fields to the \"to export\" list." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:45 +msgid "" +"The \"handles\" next to the selected fields allow you to move the fields up " +"and down to change the order in which they must be displayed in the exported" +" file." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:48 +msgid "The trashcan is there if you need to remove fields." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:49 +msgid "" +"For recurring reports, it might be interesting to save export presets. " +"Select all the needed ones and click on the template bar. There, click on " +"*New template* and give a name to yours. The next time you need to export " +"the same list, simply select the related template." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:56 +msgid "" +"It’s good to keep the field’s external identifier in mind. For example, " +"*Related Company* is equal to *parent_id*. Doing so helps export only what " +"you would like to import next." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:63 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:66 +msgid "How to start" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:68 +msgid "" +"You can import data on any Odoo's business object using either Excel (.xlsx)" +" or CSV (.csv) formats: contacts, products, bank statements, journal entries" +" and even orders!" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:72 +msgid "" +"Open the view of the object you want to populate and click on " +":menuselection:`Favorites --> Import records`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:78 +msgid "" +"There you are provided with templates you can easily populate with your own " +"data. Such templates can be imported in one click; The data mapping is " +"already done." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:83 +msgid "How to adapt the template" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:85 +msgid "Add, remove and sort columns to fit at best your data structure." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:86 +msgid "We advise to not remove the **ID** one (see why in the next section)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:87 +#: ../../content/applications/general/export_import_data.rst:376 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:92 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field in Odoo. Don't worry! You can map new " +"columns manually when you test the import. Search the list for the " +"corresponding field." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:100 +msgid "" +"Then, use this field's label in your file in order to make it work straight " +"on the very next time." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:104 +msgid "How to import from another application" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:106 +msgid "" +"In order to re-create relationships between different records, you should " +"use the unique identifier from the original application and map it to the " +"**ID** (External ID) column in Odoo. When you import another record that " +"links to the first one, use **XXX/ID** (XXX/External ID) to the original " +"unique identifier. You can also find this record using its name but you will" +" be stuck if at least 2 records have the same name." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:114 +msgid "" +"The **ID** will also be used to update the original import if you need to " +"re-import modified data later, it's thus good practice to specify it " +"whenever possible." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:120 +msgid "I cannot find the field I want to map my column to" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:122 +msgid "" +"Odoo tries to find with some heuristic, based on the first ten lines of the " +"files, the type of field for each column inside your file. For example if " +"you have a column only containing numbers, only the fields that are of type " +"*Integer* will be displayed for you to choose from. While this behavior " +"might be good and easy for most cases, it is also possible that it goes " +"wrong or that you want to map your column to a field that is not proposed by" +" default." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:131 +msgid "" +"If that happens, you just have to check the ** Show fields of relation " +"fields (advanced)** option, you will then be able to choose from the " +"complete list of fields for each column." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:139 +msgid "Where can I change the date import format?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:141 +msgid "" +"Odoo can automatically detect if a column is a date, and it will try to " +"guess the date format from a set of most commonly used date formats. While " +"this process can work for many date formats, some date formats will not be " +"recognized. This can cause confusion due to day-month inversions; it is " +"difficult to guess which part of a date format is the day and which part is " +"the month in a date such as '01-03-2016'." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:147 +msgid "" +"To view which date format Odoo has found from your file you can check the " +"**Date Format** that is shown when clicking on **Options** under the file " +"selector. If this format is incorrect you can change it to your liking using" +" the *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:152 +msgid "" +"If you are importing an excel (.xls, .xlsx) file, you can use date cells to " +"store dates as the display of dates in excel is different from the way it is" +" stored. That way you will be sure that the date format is correct in Odoo " +"whatever your locale date format is." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:157 +msgid "Can I import numbers with currency sign (e.g.: $32.00)?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:159 +msgid "" +"Yes, we fully support numbers with parenthesis to represent negative sign as" +" well as numbers with currency sign attached to them. Odoo also " +"automatically detect which thousand/decimal separator you use (you can " +"change those under **options**). If you use a currency symbol that is not " +"known to Odoo, it might not be recognized as a number though and it will " +"crash." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:164 +msgid "" +"Examples of supported numbers (using thirty-two thousands as an example):" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:166 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:167 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:168 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:169 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:170 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:171 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:172 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:174 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:176 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:177 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:180 +msgid "What can I do when the Import preview table isn't displayed correctly?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:182 +msgid "" +"By default the Import preview is set on commas as field separators and " +"quotation marks as text delimiters. If your csv file does not have these " +"settings, you can modify the File Format Options (displayed under the Browse" +" CSV file bar after you select your file)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:186 +msgid "" +"Note that if your CSV file has a tabulation as separator, Odoo will not " +"detect the separations. You will need to change the file format options in " +"your spreadsheet application. See the following question." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:191 +msgid "" +"How can I change the CSV file format options when saving in my spreadsheet " +"application?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:193 +msgid "" +"If you edit and save CSV files in spreadsheet applications, your computer's " +"regional settings will be applied for the separator and delimiter. We " +"suggest you use OpenOffice or LibreOffice Calc as they will allow you to " +"modify all three options (in :menuselection:`'Save As' dialog box --> Check " +"the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:198 +msgid "" +"Microsoft Excel will allow you to modify only the encoding when saving (in " +":menuselection:`'Save As' dialog box --> click 'Tools' dropdown list --> " +"Encoding tab`)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:202 +msgid "What's the difference between Database ID and External ID?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:204 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When you" +" want to import such fields, Odoo will have to recreate links between the " +"different records. To help you import such fields, Odoo provides three " +"mechanisms. You must use one and only one mechanism per field you want to " +"import." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:209 +msgid "" +"For example, to reference the country of a contact, Odoo proposes you 3 " +"different fields to import:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:211 +msgid "Country: the name or code of the country" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:212 +msgid "" +"Country/Database ID: the unique Odoo ID for a record, defined by the ID " +"postgresql column" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:213 +msgid "" +"Country/External ID: the ID of this record referenced in another application" +" (or the .XML file that imported it)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:216 +msgid "For the country Belgium, you can use one of these 3 ways to import:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:218 +msgid "Country: Belgium" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:219 +msgid "Country/Database ID: 21" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:220 +msgid "Country/External ID: base.be" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:222 +msgid "" +"According to your need, you should use one of these 3 ways to reference " +"records in relations. Here is when you should use one or the other, " +"according to your need:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:225 +msgid "" +"Use Country: This is the easiest way when your data come from CSV files that" +" have been created manually." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:227 +msgid "" +"Use Country/Database ID: You should rarely use this notation. It's mostly " +"used by developers as it's main advantage is to never have conflicts (you " +"may have several records with the same name, but they always have a unique " +"Database ID)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:230 +msgid "" +"Use Country/External ID: Use External ID when you import data from a third " +"party application." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:232 +msgid "" +"When you use External IDs, you can import CSV files with the \"External ID\"" +" column to define the External ID of each record you import. Then, you will " +"be able to make a reference to that record with columns like " +"\"Field/External ID\". The following two CSV files give you an example for " +"Products and their Categories." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:237 +msgid "" +":download:`CSV file for categories " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:240 +msgid "" +":download:`CSV file for Products " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:244 +msgid "What can I do if I have multiple matches for a field?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:246 +msgid "" +"If for example you have two product categories with the child name " +"\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other " +"Products/Sellable\"), your validation is halted but you may still import " +"your data. However, we recommend you do not import the data because they " +"will all be linked to the first 'Sellable' category found in the Product " +"Category list (\"Misc. Products/Sellable\"). We recommend you modify one of " +"the duplicates' values or your product category hierarchy." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:252 +msgid "" +"However if you do not wish to change your configuration of product " +"categories, we recommend you use make use of the external ID for this field " +"'Category'." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:256 +msgid "" +"How can I import a many2many relationship field (e.g. a customer that has " +"multiple tags)?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:258 +msgid "" +"The tags should be separated by a comma without any spacing. For example, if" +" you want your customer to be linked to both tags 'Manufacturer' and " +"'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column" +" of your CSV file." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:262 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:266 +msgid "" +"How can I import a one2many relationship (e.g. several Order Lines of a " +"Sales Order)?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:268 +msgid "" +"If you want to import sales order having several order lines; for each order" +" line, you need to reserve a specific row in the CSV file. The first order " +"line will be imported on the same row as the information relative to order. " +"Any additional lines will need an additional row that does not have any " +"information in the fields relative to the order. As an example, here is " +"``purchase.order_functional_error_line_cant_adpat.CSV`` file of some " +"quotations you can import, based on demo data." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:275 +msgid "" +":download:`File for some Quotations " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:277 +msgid "" +"The following CSV file shows how to import purchase orders with their " +"respective purchase order lines:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:280 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:282 +msgid "" +"The following CSV file shows how to import customers and their respective " +"contacts:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:284 +msgid "" +":download:`Customers and their respective contacts " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:287 +msgid "Can I import several times the same record?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:289 +msgid "" +"If you import a file that contains one of the column \"External ID\" or " +"\"Database ID\", records that have already been imported will be modified " +"instead of being created. This is very useful as it allows you to import " +"several times the same CSV file while having made some changes in between " +"two imports. Odoo will take care of creating or modifying each record " +"depending if it's new or not." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:294 +msgid "" +"This feature allows you to use the Import/Export tool of Odoo to modify a " +"batch of records in your favorite spreadsheet application." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:298 +msgid "What happens if I do not provide a value for a specific field?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:300 +msgid "" +"If you do not set all fields in your CSV file, Odoo will assign the default " +"value for every non defined fields. But if you set fields with empty values " +"in your CSV file, Odoo will set the EMPTY value in the field, instead of " +"assigning the default value." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:305 +msgid "How to export/import different tables from an SQL application to Odoo?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:307 +msgid "" +"If you need to import data from different tables, you will have to recreate " +"relations between records belonging to different tables. (e.g. if you import" +" companies and persons, you will have to recreate the link between each " +"person and the company they work for)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:311 +msgid "" +"To manage relations between tables, you can use the \"External ID\" " +"facilities of Odoo. The \"External ID\" of a record is the unique identifier" +" of this record in another application. This \"External ID\" must be unique " +"across all the records of all objects, so it's a good practice to prefix " +"this \"External ID\" with the name of the application or table. (like " +"'company_1', 'person_1' instead of '1')" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:317 +msgid "" +"As an example, suppose you have a SQL database with two tables you want to " +"import: companies and persons. Each person belong to one company, so you " +"will have to recreate the link between a person and the company he work for." +" (If you want to test this example, here is a :download:`dump of such a " +"PostgreSQL database `)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:322 +msgid "" +"We will first export all companies and their \"External ID\". In PSQL, write" +" the following command:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:328 +msgid "This SQL command will create the following CSV file:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:337 +msgid "" +"To create the CSV file for persons, linked to companies, we will use the " +"following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:343 +msgid "It will produce the following CSV file:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:353 +msgid "" +"As you can see in this file, Fabien and Laurence are working for the Bigees " +"company (company_1) and Eric is working for the Organi company. The relation" +" between persons and companies is done using the External ID of the " +"companies. We had to prefix the \"External ID\" by the name of the table to " +"avoid a conflict of ID between persons and companies (person_1 and company_1" +" who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:359 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two CSV files, you will have 4 " +"contacts and 3 companies. (the firsts two contacts are linked to the first " +"company). You must first import the companies and then the persons." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:364 +msgid "How to adapt an import template" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:366 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). You can open them with " +"any spreadsheets software (Microsoft Office, OpenOffice, Google Drive, " +"etc.)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:372 +msgid "How to customize the file" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:374 +msgid "" +"Remove columns you don't need. We advise to not remove the *ID* one (see why" +" here below)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:381 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field of the system. If so, find the " +"corresponding field using the search." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:388 +msgid "" +"Then, use the label you found in your import template in order to make it " +"work straight away the very next time you try to import." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:392 +msgid "Why an “ID” column" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:394 +msgid "" +"The **ID** (External ID) is an unique identifier for the line item. Feel " +"free to use the one of your previous software to ease the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:397 +msgid "" +"Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:399 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates;" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:400 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:403 +msgid "How to import relation fields" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:405 +msgid "" +"An Odoo object is always related to many other objects (e.g. a product is " +"linked to product categories, attributes, vendors, etc.). To import those " +"relations you need to import the records of the related object first from " +"their own list menu." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:409 +msgid "" +"You can do it using either the name of the related record or its ID. The ID " +"is expected when two records have the same name. In such a case add \" / " +"ID\" at the end of the column title (e.g. for product attributes: Product " +"Attributes / Attribute / ID)." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:3 +msgid "In-App Purchase (IAP)" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:5 +msgid "" +"In-App Purchases (IAP) gives access to additional services through Odoo. For" +" instance, it allows you to send SMS Text Messages or to send Invoices by " +"post directly from my database." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:9 +msgid "Buying Credits" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:11 +msgid "" +"Each IAP Service relies on prepaid credits to work and has its own pricing. " +"To consult my current balance or to recharge my account, go to " +":menuselection:`Settings --> Odoo IAP --> View my Services`." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:19 +msgid "" +"If I am on Odoo Online and have the Enterprise version, I benefit from free " +"credits to test our IAP features." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:23 +msgid "IAP accounts" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:25 +msgid "" +"Credits to use IAP services are stored on IAP accounts, which are specific " +"to each service and database. By default, IAP accounts are common to all " +"companies, but can be restricted to specific ones. Activate the " +":ref:`developer mode `, then go to :menuselection:`Technical" +" Settings --> IAP Account`." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:34 +msgid "IAP Portal" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:36 +msgid "" +"The IAP Portal is a platform regrouping my IAP Services. It is accessible " +"from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From " +"there, I can view my current balance, recharge my credits, review my " +"consumption and set a reminder to when credits are low." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:44 +msgid "Get notified when credits are low" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:46 +msgid "" +"To be notified when it’s time to recharge my credits, I’ll go to my IAP " +"Portal through :menuselection:`Settings app --> Odoo IAP --> View my " +"Services`, unfold a service and mark the Receive threshold warning option. " +"Then, I’ll provide a minimum amount of credits and email addresses. Now, " +"every time that the limit is reached, an automatic reminder will be sent to " +"by email!" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:56 +msgid "IAP services available" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:58 +msgid "" +"Different services are available depending on the hosting type of your " +"Database:" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:60 +msgid "" +"*Odoo Online*: only the IAP services provided by Odoo can be used (i.e. the " +"SMS, Snailmail, Reveal and Partner Autocomplete features);" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:62 +msgid "" +"*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by " +"Odoo and by third-party apps can be used." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:66 +msgid "Offering my own services" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:68 +msgid "" +"I am more than welcome to offer my own IAP services through Odoo Apps! It is" +" the perfect opportunity to get recurring revenue for an ongoing service use" +" rather than — and possibly instead of — a sole initial purchase. Please, " +"find more information at: :doc:`/developer/howtos/provide_iap_services`." +msgstr "" + +#: ../../content/applications/general/users.rst:5 +msgid "Users and companies" +msgstr "" + +#: ../../content/applications/general/users.rst:7 +msgid "" +"Odoo defines a *user* as someone who has access to a database to perform " +"daily tasks. You can add as many users as you need and, in order to restrict" +" the type of information each user can access, rules can be applied. Users " +"and access rights can be added and changed at any point." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:3 +msgid "Access Rights" +msgstr "Prawa dostępu" + +#: ../../content/applications/general/users/access_rights.rst:5 +msgid "" +"Activate the :ref:`developer mode `, then go to " +":menuselection:`Settings --> Users & Companies --> Groups`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:9 +msgid "Groups" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:14 +msgid "" +"When choosing the groups the user can have access under :ref:`Access Rights " +"`, details of the rules and inheritances of that group" +" are not shown, so this is when the menu *Groups* comes along. *Groups* are " +"created to define rules to models within an application." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:16 +msgid "" +"Under *Users*, have a list of the current ones. The ones with administrative" +" rights are shown in black." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab users in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:22 +msgid "" +"*Inherited* means that users added to this application group are " +"automatically added to the following ones. In the example below, users who " +"have access to the group *Administrator* of *Sales* also have access to " +"*Website/Restricted Editor* and *Sales/User: All Documents*." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab inherited in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:32 +msgid "" +"Remember to always test the settings being changed in order to ensure that " +"they are being applied to the needed and right users." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:35 +msgid "" +"The *Menus* tab is where you define which menus (models) the user can have " +"access to." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab menus in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:42 +msgid "" +"*Access Rights* rules are the first level of rights. The field is composed " +"of the object name, which is the technical name given to a model. For each " +"model, enable the following options as appropriate:" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:45 +msgid "*Read*: the values of that object can be only seen by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:46 +msgid "*Write*: the values of that object can be edited by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:47 +msgid "*Create*: values for that object can be created by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:48 +msgid "*Delete*: the values of that object can be deleted by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab access rights in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:55 +msgid "" +"As a second layer of editing and visibility rules, *Record Rules* can be " +"formed. They overwrite, or refine, the *Access Rights*." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:58 +msgid "" +"A record rule is written using a *Domain*. Domains are conditions used to " +"filter or searching data. Therefore, a domain expression is a list of " +"conditions. For each rule, choose among the following options: *Read*, " +"*Write*, *Create* and *Delete* values." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab record rules in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:65 +msgid "" +"Making changes in access rights can have a big impact on the database. For " +"this reason, we recommend you to contact your Odoo Business Analyst or our " +"Support Team, unless you have knowledge about Domains in Odoo." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:3 +msgid "Companies" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:5 +msgid "" +"A centralized management environment allows you to select multiple companies" +" simultaneously and set their specific warehouses, customers, equipment, and" +" contacts. It provides you the ability to generate reports of aggregated " +"figures without switching interfaces, which facilitates daily tasks and the " +"overall management process." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:11 +msgid "Manage companies and records" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:13 +msgid "" +"Go to :menuselection:`Settings --> Manage Companies` and fill in the form " +"with your company’s information. If a *Parent Company* is selected, records " +"are shared between the two companies (as long as both environments are " +"active)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "Overview of a new company's form in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:22 +msgid "" +"Activate the :ref:`developer mode ` to choose a *Favicon* " +"for each of your companies, and easily identify them by the browser tabs. " +"Set your favicons’ files size to 16x16 or 32x32 pixels. JPG, PNG, GIF, and " +"ICO are extensions accepted." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:0 +msgid "" +"View of a web browser and the favicon for a specific company chosen in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:31 +msgid "" +"Switch between or select multiple companies by enabling their selection " +"boxes to activate them. The grayed company is the one which environment is " +"in use. To switch environments, click on the company’s name. In the example " +"below, the user has access to three companies, two are activated, and the " +"environment in use is of *JS Store US*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "View of the companies menu through the main dashboard in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:40 +msgid "" +"Data such as Products, Contacts, and Equipment can be shared or set to be " +"shown for a specific company only. To do so, on their forms, choose between:" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:43 +msgid "*A blank field*: the record is shared within all companies." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:44 +msgid "" +"*Adding a company*: the record is visible to users logged in to that " +"specific company." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "View of a product's form emphasizing the company field in Odoo Sales" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:51 +msgid "Employees' access" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:53 +msgid "" +"Once companies are created, manage your employees' :doc:`Access Rights " +"` for *Multi Companies*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of an user form emphasizing the multi companies field under the access rights tabs\n" +"in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:62 +msgid "" +"If a user has multiple companies *activated* on his database, and he is " +"**editing** a record, the editing happens on the record's related company." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:65 +msgid "" +"Example: if editing a sale order issued under JS Store US while working on " +"the JS Store Belgium environment, the changes are applied under JS Store US " +"(the company from which the sale order was issued)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:66 +msgid "When **creating** a record, the company taken into account is:" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:68 +msgid "The current company (the one active) or," +msgstr "" + +#: ../../content/applications/general/users/companies.rst:69 +msgid "No company is set (on products and contacts’ forms for example) or," +msgstr "" + +#: ../../content/applications/general/users/companies.rst:70 +msgid "" +"The company set is the one linked to the document (the same as if a record " +"is being edited)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:73 +msgid "Documents’ format" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:75 +msgid "" +"To set documents' formats according to each company, *activate* and *select*" +" the respective one and, under *Settings*, click on *Configure Document " +"Layout*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of the settings page emphasizing the document layout field in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:83 +msgid "Inter-Company Transactions" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:85 +msgid "" +"First, make sure each one of your companies is properly set in relation to:" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:87 +msgid "" +":doc:`Chart of Accounts " +"<../../finance/accounting/get_started/chart_of_accounts>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:88 +msgid ":doc:`Taxes <../../finance/accounting/taxes>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:89 +msgid "" +":doc:`Fiscal Positions <../../finance/accounting/taxes/fiscal_positions>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:90 +msgid ":doc:`Journals <../../finance/accounting/bank>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:91 +msgid ":doc:`Fiscal Localizations <../../finance/fiscal_localizations>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:92 +msgid ":doc:`Pricelists <../../sales/sales/products_prices/prices/pricing>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:94 +msgid "" +"Now, activate the *Inter-Company Transactions* option under *Settings*. With" +" the respective company *activated* and *selected*, choose if you would like" +" operations between companies to be synchronized at an invoice/bills level " +"or at a sales/purchase orders level." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of the settings page emphasizing the inter company transaction field in" +" Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:102 +msgid "" +"**Synchronize invoice/bills**: generates a bill/invoice when a company " +"confirms a bill/invoice for the selected company." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:105 +msgid "" +"*Example:* an invoice posted on JS Store Belgium, for JS Store US, " +"automatically creates a vendor bill on the JS Store US, from the JS Store " +"Belgium." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:112 +msgid "" +"**Synchronize sales/purchase order**: generates a drafted purchase/sales " +"order using the selected company warehouse when a sales/purchase order is " +"confirmed for the selected company. If instead of a drafted purchase/sales " +"order you rather have it validated, enable *Automatic Validation*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:116 +msgid "" +"*Example:* when a sale order for JS Store US is confirmed on JS Store " +"Belgium, a purchase order on JS Store Belgium is automatically created (and " +"confirmed if the *Automatic Validation* feature was enabled)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of the purchase created on JS Store US from JS Store Belgium in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:125 +msgid "" +"Products have to be configured as *Can be sold* and must be shared between " +"the companies." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:128 +msgid "" +"Remember to test all workflows as an user other than the administrator." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:131 +msgid ":doc:`Multi-company Guidelines `" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:132 +msgid ":doc:`../../finance/accounting/get_started/multi_currency`" +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:3 +msgid "Deleting an Odoo.com Account" +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:5 +msgid "" +"To delete your Odoo.com account, access the delete option by clicking on the" +" user icon. The delete option can be accessed by going to :menuselection:`My" +" Account --> Edit Security Settings --> Delete Account`. It can also be " +"accessed by going to https://www.odoo.com/my/home." +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:10 +msgid "" +"Deleting an Odoo account is irreversible. Take caution when performing this " +"action as the Odoo.com account will not be retrievable." +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:13 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window will " +"appear, asking you to confirm the account deletion." +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/applications/general/users/delete_account.rst:20 +msgid "" +"Confirm the deletion by entering the :guilabel:`password` and the " +":guilabel:`login` for the account being deleted. Click the :guilabel:`Delete" +" Account` button to confirm the deletion." +msgstr "" + +#: ../../content/applications/general/users/language.rst:3 +msgid "Change language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:5 +msgid "" +"Odoo provides you with the option to manage Odoo in different languages, and" +" each user can use Odoo in his own language ." +msgstr "" + +#: ../../content/applications/general/users/language.rst:9 +msgid "Load your desired language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:11 +msgid "" +"The first thing to do is to load your desired language on your Odoo " +"instance." +msgstr "" + +#: ../../content/applications/general/users/language.rst:14 +msgid "" +"From the general dashboard click on the **Settings** app; on the top left of" +" the page select :menuselection:`Translations --> Load a Translation`, " +"select a language to install and click on **LOAD.**" +msgstr "" + +#: ../../content/applications/general/users/language.rst:23 +msgid "" +"If you check the \"Websites to translate\" checkbox you will have the option" +" to change the navigation language on your website." +msgstr "" + +#: ../../content/applications/general/users/language.rst:27 +msgid "Change your language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:29 +msgid "" +"You can change the language to the installed language by going to the drop-" +"down menu at the top right side of the screen, choose **Preferences**." +msgstr "" + +#: ../../content/applications/general/users/language.rst:36 +msgid "" +"Then change the Language setting to your installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../content/applications/general/users/language.rst:42 +msgid "Open a new menu to view the changes." +msgstr "" + +#: ../../content/applications/general/users/language.rst:45 +msgid "Change another user's language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:47 +msgid "" +"Odoo also gives you the possibility for each user to choose his preferred " +"language." +msgstr "" + +#: ../../content/applications/general/users/language.rst:50 +msgid "" +"To change the language for a different user, choose :menuselection:`Users " +"--> Users` from the Settings app. Here you have a list of all users and you " +"can choose the user who you'd like to change the language for. Select the " +"user and click on **Edit** in the top left corner. Under Preferences you can" +" change the Language to any previously installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../content/applications/general/users/language.rst:61 +msgid ":doc:`../../websites/website/configuration/translate`" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:3 +msgid "Manage users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:5 +msgid "" +"Odoo defines a **user** as someone who has access to a database to perform " +"daily tasks. You can add as many users as you need and, in order to restrict" +" the type of information each user can access, rules can be applied. Users " +"and access rights can be added and changed at any point." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:10 +msgid ":doc:`language`" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:11 +msgid ":doc:`access_rights`" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:16 +msgid "Add individual users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:18 +msgid "" +"Go to :menuselection:`Settings --> Manage Users` and click on *Create*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "View of the settings page emphasizing the manage users field in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:27 +msgid "" +"Fill in the form with the needed information. Under the tab :doc:`Access " +"Rights ` choose the group within each application the user " +"can have access to." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:28 +msgid "" +"The list of applications shown is based on the applications installed on the" +" database." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "View of a user’s form emphasizing the access rights tab in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:34 +msgid "" +"When you are done editing the page and have *Saved* it, an invitation email " +"is automatically sent to the user. The user must click on it to accept the " +"invitation and create a login." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "" +"View of a user’s form with a notification that the invitation email has been" +" sent in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:42 +msgid "" +"Remember that subscription prices follow the number of users. Refer to our " +"`pricing page `_ for more information." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:46 +msgid "" +"With the :ref:`developer mode ` activated, *User Types* can " +"be selected." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "" +"View of a user’s form in developer mode emphasizing the user type field in " +"Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:53 +msgid "" +"The *Portal* and *Public* options do not allow you to choose access rights. " +"Members have specific ones (such as record rules and restricted menus) and " +"usually do not belong to the usual Odoo groups." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:60 +msgid "Deactivate users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:62 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users`, open the " +"user you want to deactivate, click on *Action*, and then on *Archive*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:66 +msgid "**Never** deactivate the main user (*admin*)." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:71 +msgid "Passwords management" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:76 +msgid "Reset passwords" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:81 +msgid "Enable password resets from login page" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:83 +msgid "It is possible to enable password resets directly from the login page." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:85 +msgid "" +"To do so, go to :menuselection:`Settings --> Permissions`, activate " +"**Password Reset** and *Save*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "Enabling Password Reset in Odoo Settings" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:94 +msgid "Send reset instructions to users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:96 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users`, select the " +"user out of the list and click on *Send Password Reset Instructions* on its " +"user form. An email is automatically sent to them." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:101 +msgid "" +"The *Send Password Reset Instructions* button only appears if the Odoo " +"invitation email has already been confirmed by the user." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:104 +msgid "" +"This email contains all the instructions needed to reset the password, along" +" with a link redirecting the user to an Odoo login page." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "Example of an email with a password reset link for an Odoo account" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:114 +msgid "Change users’ passwords" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:116 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users` and select " +"a user to access its form. Click on the *Action* button and select *Change " +"Password*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "Change another user's password on Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:123 +msgid "Enter a new password and confirm by clicking on *Change Password*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:126 +msgid "" +"This operation only modifies the password of the users locally and does not " +"affect their odoo.com account. If you want to change the odoo.com password, " +"you can :ref:`send the password reset instructions `." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:130 +msgid "" +"Click on *Change Password* one more time. You are then redirected to an Odoo" +" login page where you can reaccess your database using your new password." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:136 +msgid "Multi Companies" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:138 +msgid "" +"The *Multi Companies* field allows you to set to which of the multiple " +"companies database you hold the user can have access." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:142 +msgid "" +"Note that if not handled correctly, it may be the source of a lot of " +"inconsistent multi-company behaviors. Therefore, a good knowledge of Odoo is" +" required. For technical explanations refer to :doc:`this " +"` documentation." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "View of a user’s form emphasizing the multi companies field in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:152 +msgid ":doc:`companies`" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:3 +msgid "Portal access" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:5 +msgid "" +"Portal access is given to users who need the ability to view certain " +"documents or information within an Odoo database." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:8 +msgid "" +"Some common use cases for providing portal access include allowing customers" +" to read/view any or all of the following in Odoo:" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:11 +msgid "leads/opportunities" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:12 +msgid "quotations/sales orders" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:13 +msgid "purchase orders" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:14 +msgid "invoices & bills" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:15 +msgid "projects" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:16 +msgid "tasks" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:17 +msgid "timesheets" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:18 +msgid "tickets" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:19 +msgid "signatures" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:20 +msgid "subscriptions" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:23 +msgid "" +"Portal users only have read/view access, and will not be able to edit any " +"documents in the database." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:27 +msgid "Provide portal access to customers" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:29 +msgid "" +"From the main Odoo dashboard, select the :guilabel:`Contacts` application. " +"If the contact is not yet created in the database, click on the " +":guilabel:`Create` button, enter the details of the contact, and then click " +":guilabel:`Save`. Otherwise, choose an existing contact, and then click on " +"the :guilabel:`Action` drop-down menu located at the top-center of the " +"interface." +msgstr "" + +#: ../../content/applications/general/users/portal.rst-1 +msgid "Use the Contacts application to give portal access to users" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:38 +msgid "" +"Then select :guilabel:`Grant portal access`. A pop-up window appears, " +"listing three fields:" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:40 +msgid "" +":guilabel:`Contact`: the recorded name of the contact in the Odoo database" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:41 +msgid "" +":guilabel:`Email`: the contact's email address that they will use to log " +"into the portal" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:42 +msgid ":guilabel:`In Portal`: whether or not the user has portal access" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:44 +msgid "" +"To grant portal access, first enter the contact's :guilabel:`Email` they " +"will use to log into the portal. Then, check the box under the :guilabel:`In" +" Portal` column. Optionally, add text to the invitation message the contact " +"will receive. Then click :guilabel:`Apply` to finish." +msgstr "" + +#: ../../content/applications/general/users/portal.rst-1 +msgid "" +"An email address and corresponding checkbox for the contact need to be filled in before\n" +"sending a portal invitation." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:53 +msgid "" +"An email will be sent to the specified email address, indicating that the " +"contact is now a portal user for that Odoo database." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:57 +msgid "" +"To grant portal access to multiple users at once, navigate to a company " +"contact, then click :menuselection:`Action --> Grant portal access` to view " +"a list of all of the company's related contacts. Check the box under the " +":guilabel:`In Portal` column for all the contacts that need portal access, " +"then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:63 +msgid "" +"At any time, portal access can be revoked by navigating to the contact, " +"clicking :menuselection:`Action --> Grant portal access`, and then " +"unselecting the checkbox under the :guilabel:`In Portal` column and clicking" +" :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/voip.rst:5 +msgid "VoIP (Voice over Internet Protocol)" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:3 +msgid "Configure your VoIP Asterisk server for Odoo" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:6 +msgid "Installing Asterisk server" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:9 +msgid "Dependencies" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:11 +msgid "" +"Before installing Asterisk you need to install the following dependencies:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:13 +msgid "wget" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:14 +msgid "gcc" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:15 +msgid "g++" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:16 +msgid "ncurses-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:17 +msgid "libxml2-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:18 +msgid "sqlite-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:19 +msgid "libsrtp-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:20 +msgid "libuuid-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:21 +msgid "openssl-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:22 +msgid "pkg-config" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:24 +msgid "In order to install libsrtp, follow the instructions below:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:35 +msgid "" +"You also need to install PJSIP, you can download the source `here " +"`_. Once the source directory is " +"extracted:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:38 +msgid "**Change to the pjproject source directory:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:44 +msgid "**run:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:50 +msgid "**Build and install pjproject:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:58 +msgid "**Update shared library links:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:64 +msgid "**Verify that pjproject is installed:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:70 +msgid "**The result should be:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:87 +msgid "Asterisk" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:89 +msgid "" +"In order to install Asterisk 13.7.0, you can download the source directly " +"`there `_." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:92 +msgid "Extract Asterisk:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:98 +msgid "Enter the Asterisk directory:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:104 +msgid "Run the Asterisk configure script:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:110 +msgid "Run the Asterisk menuselect tool:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:116 +msgid "" +"In the menuselect, go to the resources option and ensure that res_srtp is " +"enabled. If there are 3 x’s next to res_srtp, there is a problem with the " +"srtp library and you must reinstall it. Save the configuration (press x). " +"You should also see stars in front of the res_pjsip lines." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:120 +msgid "Compile and install Asterisk:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:126 +msgid "" +"If you need the sample configs you can run 'make samples' to install the " +"sample configs. If you need to install the Asterisk startup script you can " +"run 'make config'." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:130 +msgid "DTLS Certificates" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:132 +msgid "After you need to setup the DTLS certificates." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:138 +msgid "Enter the Asterisk scripts directory:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:144 +msgid "" +"Create the DTLS certificates (replace pbx.mycompany.com with your ip address" +" or dns name, replace My Super Company with your company name):" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:152 +msgid "Configure Asterisk server" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:154 +msgid "" +"For WebRTC, a lot of the settings that are needed MUST be in the peer " +"settings. The global settings do not flow down into the peer settings very " +"well. By default, Asterisk config files are located in /etc/asterisk/. Start" +" by editing http.conf and make sure that the following lines are " +"uncommented:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:166 +msgid "" +"Next, edit sip.conf. The WebRTC peer requires encryption, avpf, and " +"icesupport to be enabled. In most cases, directmedia should be disabled. " +"Also under the WebRTC client, the transport needs to be listed as ‘ws’ to " +"allow websocket connections. All of these config lines should be under the " +"peer itself; setting these config lines globally might not work:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:197 +msgid "" +"In the sip.conf and rtp.conf files you also need to add or uncomment the " +"lines:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:204 +msgid "Lastly, set up extensions.conf:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:213 +msgid "Configure Odoo VOIP" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:215 +msgid "In Odoo, the configuration should be done in the user's preferences." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:221 +msgid "" +"The SIP Login/Browser's Extension is the number you configured previously in" +" the sip.conf file (in our example: 1060)." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:224 +msgid "The SIP Password is the secret you chose in the sip.conf file." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:226 +msgid "" +"The extension of your office's phone is not a required field but it is used " +"if you want to transfer your call from Odoo to an external phone also " +"configured in the sip.conf file." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:230 +msgid "" +"The configuration should also be done in the General Settings under the " +"\"Integrations\" section." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:235 +msgid "" +"The PBX Server IP should be the same as the IP you define in the http.conf " +"file." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:237 +msgid "" +"The WebSocket should be: ws://localhost:XXXX/ws where \"localhost\" needs to" +" be the same as the IP defined previously and \"XXXX\" needs to be the port " +"defined in the http.conf file." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:3 +msgid "Use VoIP services in Odoo with Axivox" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:6 +#: ../../content/applications/general/voip/onsip.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:8 +msgid "" +"Odoo VoIP can be set up to work together with `Axivox " +"`_. In that case, an :doc:`Asterisk server " +"` is not necessary as the infrastructure is hosted and managed by " +"Axivox." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:12 +msgid "" +"To use this service, `contact Axivox `_ to " +"open an account. Before doing so, verify that Axivox covers your area and " +"the areas you wish to call." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:18 +msgid "Go to :menuselection:`Apps` and install the **VoIP Module**." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "VoIP module installation on an Odoo database" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:24 +msgid "" +"Go to :menuselection:`Settings --> General Settings --> Integrations`, and " +"fill out the **Asterisk (VoIP)** field:" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:27 +msgid "" +"**PBX Server IP**: set the domain created by Axivox for your account (e.g., " +"*yourcompany.axivox.com*)" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:29 +msgid "**WebSocket**: type in ``wss://pabx.axivox.com:3443``" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:30 +msgid "**VoIP Environment**: set as *Production*" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "Integration of Axivox as VoIP provider in an Odoo database" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:37 +msgid "Configure the VOIP user in the Odoo's user" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:39 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users`, then open " +"the user's form you want to configure. Under the **Preferences** tab, fill " +"out the section **PBX Configuration**:" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:42 +msgid "**SIP Login / Browser's Extension**: the Axivox *username*" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:43 +msgid "**SIP Password**: the Axivox *SIP Password*" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "Integration of Axivox user in the Odoo user preference" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:50 +msgid "" +"You can find all this information by logging in at " +"https://manage.axivox.com/, selecting the user you want to configure, and " +"referring to the fields as pictured below." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "SIP credentials in the Axivox manager" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:58 +msgid "Phone Calls" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:60 +msgid "" +"You can make phone calls by clicking on the phone icon in the navigation " +"bar." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:62 +msgid "" +"You can also receive phone calls. Odoo rings and displays a notification." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:65 +msgid "Your number is the one provided by Axivox." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "Incoming VoIP call in Odoo" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:72 +msgid "" +"If you see a *Missing Parameter* message in the **Odoo softphone**, refresh " +"your Odoo window and try again." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "\"Missing Parameter\" error message in the Odoo softphone" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:80 +msgid "" +"If you see an *Incorrect Number* message in the Odoo softphone, make sure to" +" use the international format, leading with the plus (+) sign followed by " +"the international country code. E.g., +16506913277 (where +1 is the " +"international prefix for the United States)." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "\"Incorrect Number\" error message in the Odoo softphone" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:3 +msgid "Use VoIP services in Odoo with OnSIP" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:8 +msgid "" +"Odoo VoIP can be set up to work together with OnSIP (www.onsip.com). In that" +" case, the installation and setup of an Asterisk server is not necessary as " +"the whole infrastructure is hosted and managed by OnSIP." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:10 +msgid "" +"You will need to open an account with OnSIP to use this service. Before " +"doing so, make sure that your area and the areas you wish to call are " +"covered by the service. After opening an OnSIP account, follow the " +"configuration procedure below." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:15 +msgid "Go to Apps and install the module **VoIP OnSIP**." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:20 +msgid "" +"Go to Settings/General Settings. In the section Integrations/Asterisk " +"(VoIP), fill in the 3 fields:" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:22 +msgid "" +"**OnSIP Domain** is the domain you chose when creating an account on " +"www.onsip.com. If you don't know it, log in to https://admin.onsip.com/ and " +"you will see it in the top right corner of the screen." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:23 +msgid "**WebSocket** should contain wss://edge.sip.onsip.com" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:24 +msgid "**Mode** should be Production" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:29 +msgid "" +"Go to **Settings/Users**. In the form view of each VoIP user, in the " +"Preferences tab, fill in the section **PBX Configuration**:" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:31 +msgid "**SIP Login / Browser's Extension**: the OnSIP 'Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:32 +msgid "**OnSIP authorization User**: the OnSIP 'Auth Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:33 +msgid "**SIP Password**: the OnSIP 'SIP Password'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:34 +msgid "**Handset Extension**: the OnSIP 'Extension'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:36 +msgid "" +"You can find all this information by logging in at " +"https://admin.onsip.com/users, then select the user you want to configure " +"and refer to the fields as pictured below." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:41 +msgid "" +"You can now make phone calls by clicking the phone icon in the top right " +"corner of Odoo (make sure you are logged in as a user properly configured in" +" Odoo and in OnSIP)." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:45 +msgid "" +"If you see a *Missing Parameters* message in the Odoo softphone, make sure " +"to refresh your Odoo window and try again." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:52 +msgid "" +"If you see an *Incorrect Number* message in the Odoo softphone, make sure to" +" use the international format, leading with the plus (+) sign followed by " +"the international country code. E.g.: +16506913277 (where +1 is the " +"international prefix for the United States)." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:57 +msgid "" +"You can now also receive phone calls. Your number is the one provided by " +"OnSIP. Odoo will ring and display a notification." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:63 +msgid "OnSIP on Your Cell Phone" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:65 +msgid "" +"In order to make and receive phone calls when you are not in front of your " +"computer, you can use a softphone app on your cell phone in parallel of Odoo" +" VoIP. This is useful for on-the-go calls, but also to make sure to hear " +"incoming calls, or simply for convenience. Any SIP softphone will work." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:67 +msgid "" +"On Android and iOS, OnSIP has been successfully tested with `Grandstream " +"Wave `_." +" When creating an account, select OnSIP in the list of carriers. You will " +"then have to configure it as follows:" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:69 +msgid "**Account name**: OnSIP" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:70 +msgid "**SIP Server**: the OnSIP 'Domain'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:71 +msgid "**SIP User ID**: the OnSIP 'Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:72 +msgid "**SIP Authentication ID**: the OnSIP 'Auth Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:73 +msgid "**Password**: the OnSIP 'SIP Password'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:75 +msgid "" +"Aside from initiating calls from Grandstream Wave on your phone, you can " +"also initiate calls by clicking phone numbers in your browser on your PC. " +"This will make Grandstream Wave ring and route the call via your phone to " +"the other party. This approach is useful to avoid wasting time dialing phone" +" numbers. In order to do so, you will need the Chrome extension `OnSIP Call " +"Assistant `_." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:79 +msgid "" +"The downside of using a softphone on your cell phone is that your calls will" +" not be logged in Odoo as the softphone acts as an independent separate app." +msgstr "" diff --git a/locale/pl/LC_MESSAGES/index.po b/locale/pl/LC_MESSAGES/index.po new file mode 100644 index 000000000..1480f6fbc --- /dev/null +++ b/locale/pl/LC_MESSAGES/index.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-11-02 09:24+0000\n" +"PO-Revision-Date: 2021-11-02 09:27+0000\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/index.rst:5 +msgid "Odoo Documentation" +msgstr "" diff --git a/locale/pl/LC_MESSAGES/inventory_and_mrp.po b/locale/pl/LC_MESSAGES/inventory_and_mrp.po new file mode 100644 index 000000000..3618d7da6 --- /dev/null +++ b/locale/pl/LC_MESSAGES/inventory_and_mrp.po @@ -0,0 +1,13062 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"PO-Revision-Date: 2021-11-02 08:48+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications/inventory_and_mrp.rst:5 +msgid "Inventory & MRP" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:8 +msgid "Inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:10 +msgid "" +"**Odoo Inventory** is both an inventory application and a warehouse " +"management system, with an advanced barcode scanner app. Learn how to manage" +" lead times, automate replenishments, and configure advanced routes like " +"drop-shipping, cross-docks, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:15 +msgid "" +"`Odoo Tutorials: Inventory `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:16 +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:16 +msgid "" +"`Odoo Tutorials: Barcode Scanner `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode.rst:5 +msgid "Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations.rst:5 +msgid "Daily Operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:3 +msgid "Process to an Inventory Adjustment with Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:5 +msgid "" +"To process an inventory adjustment by using barcodes, you first need to open" +" the *Barcode* app. Then, from the application, click on *Inventory " +"Adjustments*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:13 +msgid "" +"If you want to fully work with barcodes, you can download the sheet " +"*Commands for Inventory*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:16 +msgid "" +"Once you have clicked on *Inventory Adjustments*, Odoo will automatically " +"create one. Note that, if you work with multi-location, you first need to " +"specify in which location the inventory adjustment takes place." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:24 +msgid "" +"If you don’t work with multi-location, you will be able to scan the " +"different products you want to include in the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:31 +msgid "" +"If you have 5 identical articles, scan it 5 times or use the keyboard to set" +" the quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:34 +msgid "" +"Besides using the barcode scanner, you can also manually add a product if " +"necessary. To do so, click on *Add Product* and fill the information in " +"manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:44 +msgid "" +"When you have scanned all the items of the location, validate the inventory " +"manually or scan the *Validate* barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:6 +msgid "Overview" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:5 +msgid "" +"There are different situations in which barcode nomenclatures can be useful." +" A well-known use case is the one of a point of sale which sells products in" +" bulk, in which the customers will scale their products themselves and get " +"the printed barcode to stick on the product. This barcode will contain the " +"weight of the product and help compute the price accordingly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:13 +msgid "Create a Barcode Nomenclature" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:15 +msgid "" +"Odoo supports Barcode Nomenclatures, which determine the mapping and " +"interpretation of the encoded information. You can configure your barcode " +"nomenclature being in :ref:`developer mode `. To do so, go " +"to :menuselection:`Inventory --> Configuration --> Barcode Nomenclature`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:20 +msgid "" +"You can create a barcode nomenclature from there, and then add a line to " +"create your first rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:26 +msgid "" +"The first step is to specify the **rule name**, for example Weight Barcode " +"with 3 Decimals. You then have to specify the type for barcode nomenclature," +" in our case it will be Weighted Product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:33 +msgid "" +"The Barcode Pattern is a regular expression that defines the structure of " +"the barcode. In this example 21 defines the products on which the rule will " +"be applied, those are the numbers by which the product barcode should start." +" The 5 “dots” are the following numbers of the product barcode and are there" +" simply to identify the product in question. The “N” define a number and the" +" “D” define the decimals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:40 +msgid "" +"The encoding allows to specify the barcode encoding on which the rule should" +" be applied." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:44 +msgid "" +"You can define different rules and order their priority thanks to the " +"sequence. The first rule which matches the scanned barcode will be applied." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:49 +msgid "Configure your Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:51 +msgid "The barcode of the product should start by “21”;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:52 +msgid "" +"The 5 “dots” are the other numbers of your product barcode, allowing to " +"identify the product;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:53 +msgid "" +"The barcode should contain 0’s where you did defined D’s or N’s. In our case" +" we need to set 5 zeros because we configured “21…..{NNDDD}”;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:54 +msgid "" +"In EAN-13, the last number is a check number, use an EAN13 generator to know" +" which digit it should be in your case." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:59 +msgid "" +"In case you weight 1,5 Kg of pasta, the balance will print you the following" +" barcode 2112345015002. If you scan this barcode in your POS or when " +"receiving products in your barcode application, Odoo will automatically " +"create a new line for the Pasta product for a quantity of 1.5 Kg. For the " +"point of sale, a price depending on the quantity will also be computed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:70 +msgid "Rule Types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:72 +msgid "" +"**Priced Product**: allows you to identify the product and specify its " +"price, used in POS." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:73 +msgid "" +"**Discounted Product**: allows you to create one barcode per applied " +"discount. You can then scan your product in the POS and then scan the " +"discount barcode, discount will be applied on the normal price of the " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:74 +msgid "" +"**Weighted Product**: allows you to identify the product and specify its " +"weight, used in both POS (in which the price is computed based on the " +"weight) and in inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:75 +msgid "" +"**Client**: allows you to identify the customer, for example used with " +"loyalty program." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:76 +msgid "**Cashier**: allows you to identify the cashier when entering the POS." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:77 +msgid "" +"**Location**: allows you to identify the location on a transfer when multi-" +"location is activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:78 +msgid "" +"**Package**: allows you to identify packages on a transfer when packages are" +" activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:79 +msgid "" +"**Credit Card**: doesn’t need manual modification, exists for data from the " +"Mercury module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:80 +msgid "" +"**Unit Product**: allows you to identify a product for both POS and " +"transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/barcode_nomenclature.rst:83 +msgid "" +"When the barcode pattern contains .*, it means that it can contain any " +"number of characters, those characters being any number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:3 +msgid "Process to Transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:6 +msgid "Simple Transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:8 +msgid "" +"To process a transfer from the *Barcode* app, the first step is to go to " +"*Operations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:14 +msgid "" +"Then, you have the choice to either enter an existing transfer, by going to " +"the corresponding operation type and manually selecting the one you want to " +"enter, or by scanning the barcode of the transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:24 +msgid "" +"From there, you will be able to scan the products that are part of the " +"existing transfer and/or add new products to this transfer. Once all the " +"products have been scanned, you can validate the transfer to proceed with " +"the stock moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:33 +msgid "" +"If you have different storage locations in your warehouse, you can add " +"additional steps for the different operation types." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:37 +msgid "Receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:39 +msgid "" +"When receiving a product in stock, you need to scan its barcode in order to " +"identify it in the system. Once done, you can either make it enter the main " +"location of the transfer, for example WH/Stock, or scan a location barcode " +"to make it enter a sub-location of the main location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:48 +msgid "" +"If you want the product to enter WH/Stock in our example, you can simply " +"scan the next product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:52 +msgid "Delivery Orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:54 +msgid "" +"When delivering a product, you have to scan the source location if it is " +"different than the one initially set on the transfer. Then, you can start " +"scanning the products that are delivered from this specific location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:62 +msgid "" +"Once the different products have been scanned, you have the possibility to " +"scan another location, such as WH/Stock, and another page will be added to " +"your delivery order. You can move from one to the other thanks to the " +"*Previous* and *Next* buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:70 +msgid "" +"Now, you can validate your transfer. To do so, click on *Next* until you " +"reach the last page of the transfer. There, you will be able to validate it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:78 +msgid "Internal Transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:80 +msgid "" +"When realizing an internal transfer with multi-location, you first have to " +"scan the source location of the product. Then, you can scan the product in " +"itself, before having to scan the barcode of the destination location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:85 +msgid "" +"If the source and destination of the internal transfers are already correct," +" you don’t need to scan them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:89 +msgid "Transfers with Tracked Products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:91 +msgid "" +"If you work with products tracked by lot/serial numbers, you have two ways " +"of working:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:94 +msgid "" +"If you work with serial/lot numbers taking all products into consideration, " +"you can scan the barcode of the lot/serial number and Odoo will increase the" +" quantity of the product, setting its lot/serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:99 +msgid "" +"If you have the same lot/serial number for different products, you can work " +"by scanning the product barcode first, and then the barcode of the " +"lot/serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/transfers_scratch.rst:3 +msgid "Create a Transfer from Scratch" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/transfers_scratch.rst:5 +msgid "" +"To create a transfer from the *Barcode* application, you first need to print" +" the operation type barcodes. To do so, you can download the *Stock barcode " +"sheet* from the home page of the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/transfers_scratch.rst:12 +msgid "" +"Once done, you can scan the one for which you want to create a new document." +" Then, an empty document will be created and you will be able to scan your " +"products to populate it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup.rst:5 +msgid "Setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:3 +msgid "Set up your barcode scanner" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:5 +msgid "" +"Getting started with barcode scanning in Odoo is fairly easy. Yet, a good " +"user experience relies on an appropriate hardware setup. This guide will " +"help you through the task of choosing and configuring the barcode scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:11 +msgid "Find the barcode scanner that suits your needs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:13 +msgid "" +"The 3 recommended type of barcode scanners to work with the Odoo " +"**Inventory** and **Barcode Scanning** apps are the **USB scanner**, **the " +"bluetooth scanner** and the **mobile computer scanner**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:20 +msgid "" +"If you scan products at a computer location, the **USB scanner** is the way " +"to go. Simply plug it in the computer to start scanning. Just make sure when" +" you buy it that the scanner is compatible with your keyboard layout or can " +"be configured to be so." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:25 +msgid "" +"The **bluetooth scanner** can be paired with a smartphone or a tablet and is" +" a good choice if you want to be mobile but don't need a big investment. An " +"approach is to log in Odoo on you smartphone, pair the bluetooth scanner " +"with the smartphone and work in the warehouse with the possibility to check " +"your smartphone from time to time and use the software 'manually'." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:32 +msgid "" +"For heavy use, the **mobile computer scanner** is the handiest solution. It " +"consists of a small computer with a built-in barcode scanner. This one can " +"turn out to be a very productive solution, however you need to make sure " +"that is is capable of running Odoo smoothly. The most recent models using " +"Android + Google Chrome or Windows + Internet Explorer Mobile should do the " +"job. However, due to the variety of models and configurations on the market," +" it is essential to test it first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:42 +msgid "Configure your barcode scanner" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:45 +msgid "Keyboard layout" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:50 +msgid "" +"An USB barcode scanner needs to be configured to use the same keyboard " +"layout as your operating system. Otherwise, your scanner won't translate " +"characters correctly (replacing a 'A' with a 'Q' for example). Most scanners" +" are configured by scanning the appropriate barcode in the user manual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:57 +msgid "Automatic carriage return" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/hardware.rst:59 +msgid "" +"By default, Odoo has a 50 milliseconds delay between each successive scan " +"(it helps avoid accidental double scanning). If you want to suppress this " +"delay, you can configure your scanner to insert a carriage return at the end" +" of each barcode. This is usually the default configuration and can be " +"explicitly configured by scanning a specific barcode in the user manual ('CR" +" suffix ON', 'Apply Enter for suffix', etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:3 +msgid "Activate the Barcodes in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:5 +msgid "" +"The barcode scanning features can save you a lot of time usually lost " +"switching between the keyboard, the mouse and the scanner. Properly " +"attributing barcodes to products, pickings locations, etc. allows you to " +"work more efficiently by controlling the software almost exclusively with " +"the barcode scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:13 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:13 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:14 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:9 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15 +msgid "Configuration" +msgstr "Konfiguracja" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:14 +msgid "" +"To use this feature, you first need to activate the *Barcode* functionality " +"via :menuselection:`Inventory --> Settings --> Barcode Scanner`. Once you " +"have ticked the feature, you can hit save." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:22 +msgid "Set Product Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:24 +msgid "" +"You can easily assign barcodes to your different products via the " +"*Inventory* app. To do so, go to :menuselection:`Settings --> Configure " +"Products Barcodes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:30 +msgid "" +"Then, you have the possibility to assign barcodes to your products directly " +"at creation on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:40 +msgid "" +"Be careful to add barcodes directly on the product variants and not on the " +"template product. Otherwise, you won’t be able to differentiate them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:45 +msgid "Set Locations Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:47 +msgid "" +"If you manage multiple locations, you will find useful to attribute a " +"barcode to each location and stick it on the location. You can configure the" +" locations barcodes in :menuselection:`Inventory --> Configuration --> " +"Locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:58 +msgid "" +"You can easily print the barcode you allocate to the locations via the " +"*Print* menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:62 +msgid "Barcode Formats" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:64 +msgid "" +"Most retail products use EAN-13 barcodes. They cannot be made up without " +"proper authorization. You must pay the International Article Numbering " +"Association a fee in exchange for an EAN code sequence." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:68 +msgid "" +"Still, as Odoo supports any string as a barcode, you can always define your " +"own barcode format for internal use." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management.rst:5 +msgid "Warehouse Management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:3 +msgid "Inventory adjustments" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:5 +msgid "" +"In any warehouse management system, the recorded inventory counts in the " +"database might not always match the actual inventory counts in the " +"warehouse. The discrepancy between the two counts can be due to theft, " +"damages, human errors, or other factors. As such, inventory adjustments must" +" be made to reconcile the differences, and ensure that the recorded counts " +"in the database match the actual counts in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:11 +msgid "" +"In Odoo, inventory adjustments can be accessed through " +":menuselection:`Inventory --> Operations --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:14 +msgid "" +"The :guilabel:`Inventory Adjustments` page shows all products that are " +"currently in stock. Each line contains the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:17 +msgid ":guilabel:`Product`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:18 +msgid ":guilabel:`Lot/Serial Number`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:19 +msgid ":guilabel:`On Hand Quantity`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:22 +msgid "Add a new line" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:24 +msgid "" +"To add an inventory adjustment line, click :guilabel:`Create` and fill in " +"the :guilabel:`Product` and :guilabel:`Counted Quantity` fields. Then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:27 +msgid "" +"At this stage, the count is recorded but not yet *applied*. Meaning the " +"quantity on hand is not yet updated to match the new :guilabel:`Counted " +"Quantity`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:30 +msgid "" +"To apply the new :guilabel:`Counted Quantity`, click :guilabel:`Apply` on " +"the line or the :guilabel:`Apply All` button on the top of the page. If " +":guilabel:`Apply All` is clicked, a reference or reason can be entered " +"before clicking :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst-1 +msgid "" +"Apply all option applies the inventory adjustment once a reason is " +"specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:40 +msgid "Count products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:42 +msgid "" +"Counting products is a recurring activity in a warehouse. Once a count is " +"complete, go to :menuselection:`Inventory --> Operations --> Inventory " +"Adjustments` to update the :guilabel:`Counted Quantity` column for each " +"product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:46 +msgid "" +"If a count matches the :guilabel:`On Hand Quantity` recorded in the " +"database, click on :guilabel:`Set`, which will copy the value in the " +":guilabel:`On Hand Quantity` field and paste it in the :guilabel:`Counted " +"Quantity` field. A move with `0.00` :guilabel:`Quantity Done` will be " +"recorded in the product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:51 +msgid "" +"If a count does *not* match the :guilabel:`On Hand Quantity` recorded in the" +" database, record the count in the :guilabel:`Counted Quantity` field. When " +":guilabel:`Apply` is clicked, a move with the difference between the " +":guilabel:`On Hand Quantity` and :guilabel:`Counted Quantity` will be " +"recorded in the product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst-1 +msgid "" +"Inventory Adjustments History dashboard detailing a list of prior product " +"moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:61 +msgid "" +"Sometimes a count occurs, but can not be applied in the database right away." +" In the time between the actual count and applying the inventory adjustment," +" product moves can occur. In that case, the :guilabel:`On Hand Quantity` in " +"the database can change and will not be consistent with the counted " +"quantity. As an extra caution measure, Odoo will ask for confirmation before" +" applying the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:68 +msgid "Plan counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:70 +msgid "Each inventory adjustment line contains the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:72 +msgid ":guilabel:`Scheduled Date`: the date at which a count should be made." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:73 +msgid ":guilabel:`User`: the person in charge of the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:74 +msgid "" +":guilabel:`Accounting Date`: the date at which the adjustments will be " +"accounted. The column is hidden by default, but can be made visible by " +"opening the column options icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:78 +msgid "" +"In the Barcode app, users can only view counts assigned to them that are " +"scheduled for today or earlier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:81 +msgid "" +"To plan big counts, select the desired product lines on the " +":guilabel:`Inventory Adjustments` page. Then, click :guilabel:`Request a " +"Count` and fill in the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:84 +msgid ":guilabel:`Inventory Date`: the planned date of the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:85 +msgid ":guilabel:`User`: the user responsible for the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:86 +msgid "" +":guilabel:`Accounting Date`: the date at which the inventory adjustment will" +" be accounted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:87 +msgid "" +":guilabel:`Count`: to leave the :guilabel:`On Hand Quantity` of each product" +" line blank, select :guilabel:`Leave Empty`. To prefill the :guilabel:`On " +"Hand Quantity` of each product line with the current value recorded in the " +"database, select :guilabel:`Set Current Value`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:91 +msgid "Finally, click :guilabel:`Confirm` to request the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst:93 +msgid "" +"By default, after an inventory adjustment is applied, the scheduled date for" +" the next count is the 31st of December of the current year. To modify the " +"default scheduled date, go to :menuselection:`Inventory --> Configuration " +"--> Settings --> Operations` and change the date in the :guilabel:`Annual " +"Inventory Day and Month` setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst-1 +msgid "" +"Adjust the next inventory count date with the Annual Inventory Day and Month" +" setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:3 +msgid "Cycle counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:5 +msgid "" +"In most companies, the stock is only counted once a year. That's why by " +"default, after making an inventory adjustment in Odoo, the scheduled date " +"for the next count is set on the 31st of December. However, for some " +"businesses it's crucial to have an accurate inventory count at all times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:10 +msgid "" +"The goal of cycle counts is to keep critical stock levels accurate by " +"counting more often at key locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:16 +msgid "" +"In Odoo, cycle counts are location-based. The frequency of the counts is " +"defined by the storage location. To activate storage locations, go to " +":menuselection:`Inventory --> Configuration --> Settings --> Warehouse` and " +"activate the :guilabel:`Storage Locations` setting. Next, click " +":guilabel:`Save` to apply the setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst-1 +msgid "Enable Storage Locations in Odoo settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:26 +msgid "Change the inventory frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:28 +msgid "" +"To change a location's inventory frequency, first, go to the locations by " +"clicking :menuselection:`Inventory --> Configuration --> Locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:31 +msgid "" +"Then, click on a location to open the location settings. Next, click on " +":guilabel:`Edit`. In the :guilabel:`Inventory Frequency (Days)` field, set " +"the number of days. For example, a location that needs an inventory count " +"every 30 days would set the :guilabel:`Inventory Frequency (Days)` value to " +"`30`. Once the value is entered, click :guilabel:`Save` to apply the setting" +" to the location. Now, once an inventory adjustment is applied to this " +"location, the next scheduled count date will be automatically set based on " +"the number of days in the :guilabel:`Inventory Frequency (Days)` setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst-1 +msgid "Edit a location to change the inventory frequency." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers.rst:5 +msgid "Lots and Serial Numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:3 +msgid "What's the difference between lots and serial numbers?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:20 +msgid "When to use" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:34 +msgid "When not to use" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:46 +msgid ":doc:`serial_numbers`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst:47 +msgid ":doc:`lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:3 +msgid "Expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:5 +msgid "" +"In Odoo, *expiration dates* can be used to manage and track the lifecycles " +"of perishable products, from purchase to sale. Using expiration dates " +"reduces product loss due to unexpected expiry, and helps to avoid sending " +"expired products to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:9 +msgid "" +"In Odoo, only products that are tracked using *lots* and *serial numbers* " +"can be assigned expiration information. Once a lot or serial number has been" +" assigned, an expiration date can be set. This is especially helpful for " +"companies (such as food manufacturers) that consistently, or exclusively, " +"buy and sell perishable products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:17 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:19 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:19 +msgid "Enable expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:21 +msgid "" +"To enable the use of *expiration dates*, go to :menuselection:`Inventory app" +" --> Configuration --> Settings`, and scroll down to the " +":guilabel:`Traceability` section. Then, click the checkbox to enable the " +":guilabel:`Lots & Serial Numbers` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:25 +msgid "" +"Once that feature is activated, a new option will appear to enable " +":guilabel:`Expiration Dates`. Click that checkbox to enable the feature, and" +" be sure to :guilabel:`Save` changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 +msgid "Enabled lots and serial numbers and expiration dates settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:33 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` feature is activated, additional " +"features appear to :guilabel:`Display Lots & Serial Numbers on Delivery " +"Slips`; to :guilabel:`Display Lots & Serial Numbers on Invoices`; and to " +":guilabel:`Display Expiration Dates on Delivery Slips`. Activating these " +"features helps with end-to-end traceability, making it easier to manage " +"product recalls, identify \"bad\" batches of products, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:40 +msgid "Configure expiration dates on products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:42 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` and :guilabel:`Expiration Dates` " +"features have been enabled in the settings of the *Inventory* app, " +"expiration information can be configured on individual products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:46 +msgid "" +"To do so, go to :menuselection:`Inventory app --> Products --> Products`, " +"and select a product to edit. Selecting a product reveals the product form " +"for that particular item. Once on the product form, click :guilabel:`Edit` " +"in the upper-left corner to make changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:51 +msgid "" +"To be tracked using lots or serial numbers, or to configure expiration " +"information, products *must* have their :guilabel:`Product Type` set as " +":guilabel:`Storable Product` under the :guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:55 +msgid "" +"Then, click the :guilabel:`Inventory` tab, and scroll down to the " +":guilabel:`Traceability` section. From here, make sure that either " +":guilabel:`By Unique Serial Number` or :guilabel:`By Lots` is checked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:59 +msgid "" +"Once it is, a new :guilabel:`Expiration Date` checkbox appears that must " +"also be clicked. When both are enabled, a new :guilabel:`Dates` field " +"appears to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:63 +msgid "" +"If a product has stock on-hand prior to activating tracking by lots or " +"serial numbers, an inventory adjustment might need to be performed in order " +"to assign lot numbers to the existing stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:68 +msgid "" +"For processing large quantities of products on receipts or deliveries, it is" +" recommended to track using lots, so multiple products can be traced back to" +" the same lot, if any issues arise." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 +msgid "Expiration dates configuration on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:75 +msgid "" +"Under the :guilabel:`Dates` field, there are four categories of expiration " +"information to configure for the product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:78 +msgid "" +":guilabel:`Expiration Time`: the number of days after receiving products " +"(either from a vendor or in stock after production) in which goods may " +"become dangerous and should not be used or consumed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:80 +msgid "" +":guilabel:`Best Before Time`: the number of days before the expiration date " +"in which the goods start deteriorating, **without** necessarily being " +"dangerous yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:82 +msgid "" +":guilabel:`Removal Time`: the number of days before the expiration date in " +"which the goods should be removed from stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:84 +msgid "" +":guilabel:`Alert Time`: the number of days before the expiration date in " +"which an alert should be raised on goods in a particular lot or containing a" +" particular serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:88 +msgid "" +"The values entered into these fields automatically compute the expiration " +"date for goods entered into stock, whether purchased from a vendor or " +"manufactured in-house." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:91 +msgid "" +"Once all the expiration information has been configured, click " +":guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:94 +msgid "" +"If the :guilabel:`Dates` field is not populated with any values for " +"expiration information, dates (and lots) can be manually assigned upon " +"receipts and deliveries in and out of the warehouse. Even when assigned, " +"they can still be overwritten and changed manually if needed, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:99 +msgid "Set expiration dates on receipts with lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:101 +msgid "" +"Generating expiration dates for **incoming** goods can be done directly from" +" the purchase order. To create a purchase order, go to the " +":menuselection:`Purchase` app and click :guilabel:`Create` to create a new " +"request for quotation (RFQ)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:105 +msgid "" +"Then, fill out the information by adding a :guilabel:`Vendor`, and add " +"products to the :guilabel:`Product` lines by clicking :guilabel:`Add a " +"product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:108 +msgid "" +"Choose the desired quantity to order by changing the number in the " +":guilabel:`Quantity` column, and click :guilabel:`Confirm Order`. This " +"converts the :abbr:`RFQ (request for quotation)` into a purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:112 +msgid "" +"Click the :guilabel:`Receipt` smart button at the top of the purchase order " +"to be taken to the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:116 +msgid "" +"Clicking :guilabel:`Validate` before assigning a serial number to the " +"ordered product quantities causes a :guilabel:`User Error` popup to appear. " +"The popup requires entry of a lot or serial number for the ordered products." +" The :abbr:`RFQ (request for quotation)` cannot be validated without an " +"assigned lot or serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:0 +msgid "User error popup when validating an order with no lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:125 +msgid "" +"From here, click the :guilabel:`Additional Options` menu (hamburger) icon " +"located on the far-right of the product line. When clicked, a " +":guilabel:`Detailed Operations` pop-up will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:128 +msgid "" +"In this pop-up, click :guilabel:`Add a line`, and assign a lot or serial " +"number under the :guilabel:`Lot/Serial Number Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:131 +msgid "" +"An expiration date automatically populates, based on the configuration on " +"the product form (if previously configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:135 +msgid "" +"If the :guilabel:`Dates` field on the product form has not been configured, " +"this date can be manually entered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:138 +msgid "" +"After the expiration date has been established, mark the :guilabel:`Done` " +"quantities, and click :guilabel:`Confirm` to close the pop-up. Finally, " +"click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 +msgid "" +"Detailed operations popup showing expiration dates for ordered products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:145 +msgid "" +"A :guilabel:`Traceability` smart button will appear upon validating the " +"receipt. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document; the :guilabel:`Product` being traced; the :guilabel:`Lot/Serial " +"#`; and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:151 +msgid "Set expiration dates on manufactured products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:153 +msgid "" +"Expiration dates can also be generated for products manufactured in-house. " +"To assign expiration dates to manufactured products, a manufacturing order " +"(MO) needs to be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:156 +msgid "" +"To create a :abbr:`MO (manufacturing order)`, go to " +":menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, " +"and click :guilabel:`Create`. Choose a product to manufacture from the " +":guilabel:`Product` field drop-down menu, then select the " +":guilabel:`Quantity` to produce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 +msgid "Manufacturing order for product with expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:165 +msgid "" +"To manufacture a product, there must be materials to consume in the lines in" +" the :guilabel:`Product` column. This can be achieved either by creating a " +":guilabel:`Bill of Material` for the :guilabel:`Product`, or manually adding" +" materials to consume by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:170 +msgid "Once ready, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:172 +msgid "" +"Next to :guilabel:`Lot/Serial Number`, either select an existing lot number " +"from the drop-down menu, or click the green :guilabel:`+` sign to " +"automatically assign a new lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:175 +msgid "" +"Then, select a number of units for the :guilabel:`Quantity` field, and click" +" :guilabel:`Mark as Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:178 +msgid "" +"Click on the :guilabel:`External Link` icon in the assigned " +":guilabel:`Lot/Serial Number` field. A pop-up appears, revealing a detail " +"form for that specific number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:181 +msgid "" +"On that pop-up, under the :guilabel:`Dates` tab, all expiration information " +"that was previously configured for the product is displayed. That same " +"information is also available on the detail form for that specific product, " +"or by going to :menuselection:`Inventory app --> Products --> Lots/Serial " +"Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 +msgid "Dates tab with expiration information for specific lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:191 +msgid "Sell products with expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:193 +msgid "" +"Selling perishable products with expiration dates is done the same as any " +"other type of product. The first step in selling perishable products is to " +"create a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:196 +msgid "" +"To do that, go to :menuselection:`Sales app --> Create` to create a new " +"quotation, and fill out the information on the sales order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:199 +msgid "" +"Add a :guilabel:`Customer`, click :guilabel:`Add a product` to add the " +"desired products to the :guilabel:`Product` lines, and set a " +":guilabel:`Quantity` for the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:202 +msgid "" +"Then, click the :guilabel:`Other Info` tab. Under the :guilabel:`Delivery` " +"section, change the :guilabel:`Delivery Date` to a date after the expected " +"date, and click the :guilabel:`green checkmark` icon to confirm the date. " +"Finally, click :guilabel:`Confirm` to confirm the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:206 +msgid "" +"Next, click the :guilabel:`Delivery` smart button at the top of the sales " +"order to see the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:209 +msgid "" +"On the warehouse receipt form, click :guilabel:`Validate`, and then " +":guilabel:`Apply` in the accompanying pop-up window, to automatically " +"process all :guilabel:`Done` quantities, and deliver the products to the " +"customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:213 +msgid "" +"If the products are delivered before the :guilabel:`Alert Date` set on the " +"product form, then no alerts will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:217 +msgid "" +"To sell perishable products with expiration dates, the :guilabel:`Removal " +"Strategy` for the :guilabel:`Location` the products are stored in must be " +"set to :abbr:`FEFO (First Expiry, First Out)`. If there is not enough stock " +"of perishable products in one lot, Odoo will automatically take the " +"remaining quantity required from a second lot with the next-soonest " +"expiration date. Removal strategies can also be set on :guilabel:`Product " +"Categories`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:224 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:209 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/routes/strategies/removal`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:227 +msgid "View expiration dates for lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:229 +msgid "" +"To view (and/or group) all products with expiration dates by lot number, go " +"to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:232 +msgid "" +"Once there, remove any default search filters from the :guilabel:`Search...`" +" bar. Then, click :guilabel:`Group By`, choose :guilabel:`Add Custom Group`," +" and select the :guilabel:`Expiration Date` parameter from the drop-down " +"menu. Finally, click :guilabel:`Apply` to apply the filter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:236 +msgid "" +"Doing so breaks down all perishable products, their expiration dates, and " +"the assigned lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 +msgid "Group by expiration dates on lots and serial numbers page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:243 +msgid "Expiration alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:245 +msgid "" +"To see expiration alerts, go to :menuselection:`Inventory app --> Products " +"--> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:247 +msgid "" +"Then, click into a :guilabel:`Lot/Serial Number` with perishable products. " +"Doing so reveals the serial number detail form. On the serial number detail " +"form, click the :guilabel:`Dates` tab to see all expiration information " +"related to the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:251 +msgid "" +"To edit the form, click :guilabel:`Edit` in the upper-left corner of the " +"form, then change the :guilabel:`Expiration Date` to today's date (or " +"earlier), and click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:255 +msgid "" +"After saving, the lot number form displays a red :guilabel:`Expiration " +"Alert` at the top of the form to indicate that the products in this lot are " +"either expired or expiring soon. From here, click back to the " +":guilabel:`Lots/Serial Numbers` page (via the breadcrumbs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:259 +msgid "" +"To see the new expiration alert, or any expiration alerts for products that " +"are expired (or will expire soon), remove all of the search filters from the" +" :guilabel:`Search...` bar on the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:263 +msgid "" +"Then, click :guilabel:`Filters`, and choose :guilabel:`Expiration Alerts`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst-1 +msgid "Expiration alert for product past the expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:3 +msgid "Use lots to manage groups of products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:5 +msgid "" +"*Lots* are one of the two ways to identify and track products in Odoo. A lot" +" usually indicates a specific batch of an item that was received, is " +"currently stored, or was shipped from a warehouse, but can also pertain to a" +" batch of products manufactured in-house, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:9 +msgid "" +"Manufacturers assign lot numbers to groups of products that have common " +"properties; this can lead to multiple goods sharing the same lot number. " +"This helps to identify a number of products in a single group, and allows " +"for end-to-end traceability of these products through each step in their " +"lifecycles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:14 +msgid "" +"Lots are useful for products that are manufactured or received in large " +"quantities (such as clothes or food), and can be used to trace a product " +"back to a group. This is especially useful when managing product recalls or " +"expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:20 +msgid "Enable lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:24 +msgid "" +"To track products using lots, the *Lots & Serial Numbers* feature must be " +"enabled. Go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`, scroll down to the :guilabel:`Traceability` section, and click " +"the box next to :guilabel:`Lots & Serial Numbers`. Then, click the " +":guilabel:`Save` button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 +msgid "Enabled lots and serial numbers feature in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:34 +msgid "Track products by lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:36 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` setting has been activated, " +"individual products can now be configured to be tracked using lots. To do " +"this, go to the :menuselection:`Inventory app --> Products --> Products`, " +"and choose a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:40 +msgid "" +"Once on the product form, click :guilabel:`Edit` to make changes to the " +"form. Then, click the :guilabel:`Inventory` tab. In the " +":guilabel:`Traceability` section, click :guilabel:`By Lots`. Then, click " +":guilabel:`Save` to save changes. Existing or new lot numbers can now be " +"assigned to newly-received or manufactured batches of this product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:46 +msgid "" +"If a product has stock on-hand prior to activating tracking by lots or " +"serial numbers, an inventory adjustment might need to be performed to assign" +" lot numbers to the existing stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 +msgid "Enabled tracking by lots feature on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:54 +msgid "Create new lots for products already in stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:56 +msgid "" +"New lots can be created for products already in stock with no assigned lot " +"number. To do this, go to the :menuselection:`Inventory app --> Products -->" +" Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a " +"separate page where a new :guilabel:`Lot/Serial Number` is generated " +"automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:62 +msgid "" +"While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to " +"follow the most recent number, it can be edited and changed to any desired " +"number, by clicking the line under the :guilabel:`Lot/Serial Number` field, " +"and changing the generated number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:66 +msgid "" +"Once the new :guilabel:`Lot/Serial Number` is generated, click the blank " +"field next to :guilabel:`Product` to reveal a drop-down menu. From this " +"menu, select the product to which this new number will be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:70 +msgid "" +"This form also provides the option to adjust the :guilabel:`Quantity`, " +"assign a unique :guilabel:`Internal Reference` number (for traceability " +"purposes), and assign this specific lot or serial number configuration to a " +"specific website in the :guilabel:`Website` field (if working in a multi-" +"website environment)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:75 +msgid "" +"A detailed description of this specific lot or serial number can also be " +"added in the :guilabel:`Description` tab below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:79 +msgid "" +"When all desired configurations are complete, click the :guilabel:`Save` " +"button to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 +msgid "New lot number creation form with assigned product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:84 +msgid "" +"After a new lot number has been created, saved, and assigned to the desired " +"product, navigate back to the product form in the :menuselection:`Inventory`" +" app, by going to :menuselection:`Products --> Products`, and selecting the " +"product to which this newly-created lot number was just assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:88 +msgid "" +"On that product's detail form, click the :guilabel:`Lot/Serial Numbers` " +"smart button to view the new lot number. When additional quantity of this " +"product is received or manufactured, this new lot number can be selected and" +" assigned to it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:93 +msgid "Manage lots for shipping and receiving" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:95 +msgid "" +"Lot numbers can be assigned for both **incoming** and **outgoing** goods. " +"For incoming goods, lot numbers are assigned directly on the purchase order " +"form. For outgoing goods, lot numbers are assigned directly on the sales " +"order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:100 +msgid "Manage lots on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:102 +msgid "" +"Assigning lot numbers to **incoming** goods can be done directly from the " +"purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:104 +msgid "" +"To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app " +"--> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:107 +msgid "" +"On this :abbr:`RFQ (request for quotation)`, fill out the necessary " +"information by adding a :guilabel:`Vendor`, and adding the desired products " +"to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` " +"(under the :guilabel:`Products` tab)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:111 +msgid "" +"Choose the desired quantity of the product to order by changing the number " +"in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:114 +msgid "" +"Once the :abbr:`RFQ (request for quotation)` has been filled out, click " +":guilabel:`Confirm Order`. When the :abbr:`RFQ (request for quotation)` is " +"confirmed, it becomes a :guilabel:`Purchase Order`, and a " +":guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` " +"smart button to be taken to the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:120 +msgid "" +"Clicking :guilabel:`Validate` before assigning a lot number to the ordered " +"product quantities will result in a :guilabel:`User Error` pop-up. The pop-" +"up requires entry of a lot or serial number for the ordered products. The " +":abbr:`RFQ (request for quotation)` **cannot** be validated without a lot " +"number being assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 +msgid "Add lot/serial number user error popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:129 +msgid "" +"From here, click the :guilabel:`Additional Options` menu, represented by a " +":guilabel:`hamburger (four horizontal lines)` icon, located to the right of " +"the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). " +"Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:133 +msgid "" +"In this pop-up, configure a number of different fields, including the " +"assignation of a lot number, under the :guilabel:`Lot/Serial Number Name` " +"column, located at the bottom of the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:136 +msgid "" +"There are two ways to assign lot numbers: **manually** and **copy/paste**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:138 +msgid "" +"**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the" +" location the products will be stored in under the :guilabel:`To` column. " +"Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` " +"quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:0 +msgid "Assign lot number detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:147 +msgid "" +"If quantities should be processed in multiple locations and lots, click " +":guilabel:`Add a line` and type a new :guilabel:`Lot Number Name` for " +"additional quantities. Repeat until the :guilabel:`Quantity Done` matches " +"the :guilabel:`Demand`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:151 +msgid "" +"**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with " +"all of the lot numbers received from the supplier (or manually chosen to " +"assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial" +" Number Name` column. Odoo will automatically create the necessary number of" +" lines based on the amount of numbers pasted in the column. From here, the " +":guilabel:`To` locations and :guilabel:`Done` quantities can be manually " +"entered in each of the lot number lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:0 +msgid "List of lot numbers copied on excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:161 +msgid "" +"Once all product quantities have been assigned a lot number, click " +":guilabel:`Confirm` to close the pop-up. Then, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:164 +msgid "" +"A :guilabel:`Traceability` smart button appears upon validating the receipt." +" Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`" +" assigned, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:170 +msgid "Manage lots on delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:172 +msgid "" +"Assigning lot numbers to **outgoing** goods can be done directly from the " +"sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:174 +msgid "" +"To create an :abbr:`SO (sales order)`, go to the :menuselection:`Sales app " +"--> Create`. Doing so reveals a new, blank quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:177 +msgid "" +"On this blank quotation form, fill out the necessary information by adding a" +" :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines " +"(in the :guilabel:`Order Lines` tab) by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:181 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:219 +msgid "" +"Then, choose the desired quantity to sell by changing the number in the " +":guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:183 +msgid "" +"Once the quotation has been filled out, click the :guilabel:`Confirm` button" +" to confirm the quotation. When the quotation is confirmed, it becomes an " +":abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:187 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:225 +msgid "" +"Click the :guilabel:`Delivery` smart button to view the warehouse receipt " +"form for that specific :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:190 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:228 +msgid "" +"From here, click the :guilabel:`Additional Options` menu, represented by a " +"`hamburger` icon (four horizontal lines, located to the right of the " +":guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). " +"Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:194 +msgid "" +"In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, " +"with the full :guilabel:`Reserved` quantity taken from that specific lot (if" +" there is enough stock in that particular lot)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:198 +msgid "" +"If there is insufficient stock in that lot, or if partial quantities of the " +":guilabel:`Demand` should be taken from multiple lots, change the quantity " +"in the :guilabel:`Done` column to only include that specific part of the " +"total quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:203 +msgid "" +"The lot automatically chosen for delivery orders varies, depending on the " +"selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO " +"(Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will " +"also depend on the quantity ordered, and if there is enough quantity in one " +"lot to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:211 +msgid "" +"Then, click :guilabel:`Add a line`, select an additional (different) " +":guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` " +"quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click" +" the :guilabel:`Validate` button to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 +msgid "Detailed operations popup for source lot number on sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:219 +msgid "" +"Upon validating the delivery order, a :guilabel:`Traceability` smart button " +"appears. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and " +"the :guilabel:`Lot/Serial #` assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:224 +msgid "" +"The :guilabel:`Traceability Report` can also include a :guilabel:`Reference`" +" receipt from the previous purchase order, if the product quantities shared " +"the same lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:228 +msgid "Manage lots for different operations types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:230 +msgid "" +"In Odoo, the creation of new lots is only allowed upon **receiving** " +"products from a purchase order, by default. **Existing** lot numbers cannot " +"be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:233 +msgid "" +"For sales orders, the opposite is true: new lot numbers cannot be created on" +" the delivery order, only existing lot numbers can be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:236 +msgid "" +"To change the ability to use new (or existing) lot numbers on any operation " +"type, go to the :menuselection:`Inventory app --> Configuration --> " +"Operations Types`, and select the desired :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:240 +msgid "" +"For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` " +"page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be " +"enabled, by clicking :guilabel:`Edit`, and then clicking the checkbox beside" +" the :guilabel:`Use Existing Lots/Serial Numbers` option (in the " +":guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button" +" to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:245 +msgid "" +"For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial " +"Numbers` option can be enabled, by clicking :guilabel:`Edit`, and clicking " +"the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option. " +"Be sure to click the :guilabel:`Save` button to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 +msgid "Enabled traceability setting on operations type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:254 +msgid "" +"For inter-warehouse transfers involving products tracked by lots, it can be " +"useful to enable the :guilabel:`Use Existing Lots/Serial Numbers` option for" +" warehouse receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:258 +msgid "Lots traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:260 +msgid "" +"Manufacturers and companies can refer to traceability reports to see the " +"entire lifecycle of a product: where (and when) it came from, where it was " +"stored, and who (and when) it went to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:263 +msgid "" +"To see the full traceability of a product, or group by lots, go to the " +":menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing " +"so reveals the :menuselection:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:267 +msgid "" +"From here, products with lot numbers assigned to them will be listed by " +"default, and can be expanded to show the lot numbers those products have " +"assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:270 +msgid "" +"To group by lots (or serial numbers), begin by removing any filters in the " +"search bar. Then, click the :guilabel:`Group By` drop-down, select " +":guilabel:`Add Custom Group`, and select :guilabel:`Lot/Serial Number` from " +"the drop-down menu. Then, click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:274 +msgid "" +"Doing so displays all existing lots and serial numbers, and can be expanded " +"to show all quantities of products with that assigned number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst-1 +msgid "Lots and serial numbers traceability report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:282 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:317 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:3 +msgid "Use serial numbers to track products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:5 +msgid "" +"*Serial numbers* are one of the two ways to identify and track products in " +"Odoo. A serial number is a unique identifier assigned incrementally (or " +"sequentially) to an item or product, used to distinguish it from other items" +" and products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:9 +msgid "" +"Serial numbers can consist of many different types of characters: they can " +"be strictly numerical, they can contain letters and other typographical " +"symbols, or they can be a mix of all of the above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:12 +msgid "" +"The goal of assigning serial numbers to individual products is to make sure " +"that every item's history is identifiable when it travels through the supply" +" chain. This can be especially useful for manufacturers that provide after-" +"sales services to products that they sell and deliver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:22 +msgid "" +"To track products using serial numbers, the :guilabel:`Lots & Serial " +"Numbers` feature must be enabled. To enable this, go to " +":menuselection:`Inventory app --> Configuration --> Settings`, scroll down " +"to the :guilabel:`Traceability` section, and click the box next to " +":guilabel:`Lots & Serial Numbers`. Remember to click the :guilabel:`Save` " +"button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst-1 +msgid "Enabled lots and serial numbers setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:32 +msgid "Configure serial number tracking on products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:34 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` setting has been activated, " +"individual products can now be tracked using serial numbers. To configure " +"this, go to :menuselection:`Inventory app --> Products --> Products`, and " +"choose a desired product to track." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:38 +msgid "" +"Once on the product form, click :guilabel:`Edit`, and click the " +":guilabel:`Inventory` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:40 +msgid "" +"Once on the product form, click :guilabel:`Edit`, navigate to the " +":guilabel:`Inventory` tab, and scroll to the :guilabel:`Traceability` " +"section. Then, select the :guilabel:`By Unique Serial Number` option, and " +"click :guilabel:`Save` to save the changes. Existing or new serial numbers " +"can now be selected and assigned to newly-received or manufactured batches " +"of this product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst-1 +msgid "Enabled serial number tracking on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:50 +msgid "" +"If a product doesn't have a serial number assigned to it, a user error pop-" +"up window will appear. The error message states that the product(s) in stock" +" have no lot/serial number. However, a lot/serial number can be assigned to " +"the product by making an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:55 +msgid "Create new serial numbers for products already in stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:57 +msgid "" +"New serial numbers can be created for products already in stock with no " +"assigned serial number. To do this, go to :menuselection:`Inventory --> " +"Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so " +"reveals a blank lots/serial numbers form. On this form, a new " +":guilabel:`Lot/Serial Number` is generated automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:63 +msgid "" +"While Odoo automatically generates a new lot/serial number to follow the " +"most recent number, it can be edited and changed to any desired number, by " +"clicking the line under the :guilabel:`Lot/Serial Number` field, and " +"changing the generated number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:67 +msgid "" +"Once the :guilabel:`Lot/Serial Number` is generated, click the blank field " +"next to :guilabel:`Product` to reveal a drop-down menu. From this menu, " +"select the product to which this new number will be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:71 +msgid "" +"This form also provides the option to adjust the :guilabel:`Quantity`, to " +"assign a unique :guilabel:`Internal Reference` number (for traceability " +"purposes), and to assign this specific lot/serial number configuration to a " +"specific website in the :guilabel:`Website` field (if working in a multi-" +"website environment)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:76 +msgid "" +"A detailed description of this specific lot/serial number can also be added " +"in the :guilabel:`Description` tab below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst-1 +msgid "New serial number created for existing product stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:85 +msgid "" +"After a new serial number has been created, assigned to the desired product," +" and saved, navigate back to the product form, by going to " +":menuselection:`Products --> Products`, and selecting the product that this " +"newly-created serial number was just assigned to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:89 +msgid "" +"On that product's detail form, click the :guilabel:`Lot/Serial Numbers` " +"smart button to view the new serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:93 +msgid "Manage serial numbers for shipping and receiving" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:95 +msgid "" +"Serial numbers can be assigned for both **incoming** and **outgoing** goods." +" For incoming goods, serial numbers are assigned directly on the purchase " +"order form. For outgoing goods, serial numbers are assigned directly on the " +"sales order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:100 +msgid "Manage serial numbers on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:102 +msgid "" +"Assigning serial numbers to **incoming** goods can be done directly from the" +" purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:104 +msgid "" +"To create a :abbr:`PO (purchase order)`, go to the :menuselection:`Purchase " +"app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:107 +msgid "" +"On this :abbr:`RFQ (request for quotation)` form, fill out the necessary " +"information, by adding a :guilabel:`Vendor`, and by adding the desired " +"products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a " +"product`, under the :guilabel:`Products` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:111 +msgid "" +"Choose the desired quantity of the product to order, by changing the number " +"in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:114 +msgid "" +"When the necessary configurations are complete, click :guilabel:`Confirm " +"Order`. This will convert the :abbr:`RFQ (request for quotation)` to a " +"purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:117 +msgid "" +"Then, click the :guilabel:`Receipt` smart button to be taken to the " +"warehouse receipt form page for that specific :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:121 +msgid "" +"Clicking :guilabel:`Validate` before assigning a serial number to the " +"ordered product quantities will cause a :guilabel:`User Error` pop-up to " +"appear. The pop-up requires entry of a lot or serial number for the ordered " +"products. The :abbr:`RFQ (request for quotation)` **cannot** be validated " +"without a serial number being assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst-1 +msgid "User error popup prompting serial number entry." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:134 +msgid "" +"In this pop-up, configure a number of different fields, including the " +"assignation of a serial number (or serial numbers) under the " +":guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-" +"up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:138 +msgid "" +"There are three ways to do this: manually assigning serial numbers, " +"automatically assigning serial numbers, and copy/pasting serial numbers from" +" a spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:142 +msgid "Assign serial numbers manually" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:144 +msgid "" +"To assign serial numbers manually, click :guilabel:`Add a line` from the " +":guilabel:`Detailed Operations` pop-up, and first choose the location where " +"the product will be stored under the :guilabel:`To` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:148 +msgid "" +"Then, type a new :guilabel:`Serial Number Name`, and set the " +":guilabel:`Done` quantity in the appropriate columns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:151 +msgid "" +"Repeat this process for the quantity of products shown in the " +":guilabel:`Demand` field, and until the :guilabel:`Quantity Done` field " +"displays the correct (matching) number of products processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:155 +msgid "Assign serial numbers automatically" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:157 +msgid "" +"If a large quantity of products need individual serial numbers assigned to " +"them, Odoo can automatically generate and assign serial numbers to each of " +"the individual products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:160 +msgid "" +"To accomplish this, start with the :guilabel:`First SN` field in the " +":guilabel:`Detailed Operations` pop-up window, and type the first serial " +"number in the desired order to be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:163 +msgid "" +"Then, in the :guilabel:`Number of SN` field, type the total number of items " +"that need newly-generated unique serial numbers assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:166 +msgid "" +"Finally, click :guilabel:`Assign Serial Numbers`, and a list will populate " +"with new serial numbers matching the ordered quantity of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst-1 +msgid "Automatic serial number assignment in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:174 +msgid "Copy/paste serial numbers from a spreadsheet" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:176 +msgid "" +"To copy and paste serial numbers from an existing spreadsheet, first " +"populate a spreadsheet with all of the serial numbers received from the " +"supplier (or manually chosen upon receipt). Then, copy and paste them in the" +" :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create " +"the necessary number of lines based on the amount of numbers pasted in the " +"column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:181 +msgid "" +"From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can " +"be manually entered in each of the serial number lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst-1 +msgid "List of serial numbers copied in Excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:189 +msgid "" +"For purchase orders that include large quantities of products to receive, " +"the best method of serial number assignment is to automatically assign " +"serial numbers using the :guilabel:`Assign Serial Numbers` button located on" +" the :abbr:`PO (purchase order)`. This prevents any serial numbers from " +"being reused or duplicated, and improves traceability reporting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:194 +msgid "" +"Once all product quantities have been assigned a serial number, click the " +":guilabel:`Confirm` button to close the pop-up. Then, click " +":guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:197 +msgid "" +"A :guilabel:`Traceability` smart button appears upon validating the receipt." +" Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial " +"#`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:202 +msgid "" +"Once all product quantities have been assigned a serial number, click " +":guilabel:`Confirm` to close the popup, and click :guilabel:`Validate`. A " +":guilabel:`Traceability` smart button will appear upon validating the " +"receipt. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial " +"#`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:209 +msgid "Manage serial numbers on delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:211 +msgid "" +"Assigning serial numbers to **outgoing** goods can be done directly from the" +" sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:213 +msgid "" +"To create an :abbr:`SO (sales order)`, navigate to the " +":menuselection:`Sales` app, and click the :guilabel:`Create` button. Doing " +"so reveals a new, blank quotation form. On this blank quotation form, fill " +"out the necessary information, by adding a :guilabel:`Customer`, and adding " +"products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` " +"tab), by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:221 +msgid "" +"Once the quotation has been filled out, click the :guilabel:`Confirm` button" +" to confirm the quotation. When the quotation is confirmed, the quotation " +"becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button" +" appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:232 +msgid "" +"In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, " +"with each product of the total :guilabel:`Reserved` quantity listed with " +"their unique serial numbers (most likely listed in sequential order)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:236 +msgid "" +"To manually change a product's serial number, click the drop-down menu under" +" :guilabel:`Lot/Serial Number`, and choose (or type) the desired serial " +"number. Then, mark the :guilabel:`Done` quantities, and click " +":guilabel:`Confirm` to close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:240 +msgid "" +"Finally, click the :guilabel:`Validate` button to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst-1 +msgid "Serial numbers listed in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:246 +msgid "" +"Upon validating the delivery order, a :guilabel:`Traceability` smart button " +"appears. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and " +"the :guilabel:`Lot/Serial #` assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:251 +msgid "" +"The :guilabel:`Traceability Report` can also include a :guilabel:`Reference`" +" receipt from the previous purchase order (PO), if any of the product " +"quantities shared a serial number assigned during receipt of that specific " +":abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:256 +msgid "Manage serial numbers for different operations types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:258 +msgid "" +"By default in Odoo, the creation of new serial numbers is only allowed upon " +"**receiving** products from a purchase order. **Existing** serial numbers " +"cannot be used. For sales orders, the opposite is true: new serial numbers " +"cannot be created on the delivery order, only existing serial numbers can be" +" used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:263 +msgid "" +"To change the ability to use new (or existing) serial numbers on any " +"operation type, go to :menuselection:`Inventory app --> Configuration --> " +"Operations Types`, and select the desired :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:267 +msgid "" +"For the :guilabel:`Receipts` operation type, found on the " +":guilabel:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial " +"Numbers` option can be enabled, by selecting :guilabel:`Receipts` from the " +":guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and then " +"clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial " +"Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the" +" :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:273 +msgid "" +"For the :guilabel:`Delivery Orders` operation type, located on the " +":guilabel:`Operations Types` page, the :guilabel:`Create New Lots/Serial " +"Numbers` option can be enabled, by selecting :guilabel:`Delivery Orders` " +"from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and " +"clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` " +"option (in the :guilabel:`Traceability` section). Be sure to click " +":guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst-1 +msgid "Enabled traceability setting in operations type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:284 +msgid "Serial number traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:286 +msgid "" +"Manufacturers and companies can refer to the traceability reports to see the" +" entire lifecycle of a product: where it came from (and when), where it was " +"stored, and who it went to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:289 +msgid "" +"To see the full traceability of a product, or group by serial numbers, go to" +" :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing " +"so reveals the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:293 +msgid "" +"From here, products with serial numbers assigned to them will be listed by " +"default, and can be expanded to show what serial numbers have been " +"specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:296 +msgid "" +"To group by serial numbers (or lots), first remove any default filters from " +"the search bar in the upper-right corner. Then, click :guilabel:`Group By`, " +"and select :guilabel:`Add Custom Group`, which reveals a mini drop-down " +"menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, " +"and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:301 +msgid "" +"Doing so reveals all existing serial numbers and lots, and can be expanded " +"to show all quantities of products with that assigned number. For unique " +"serial numbers that are not reused, there should be just one product per " +"serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst-1 +msgid "Serial numbers reporting page with drop-down lists." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:310 +msgid "" +"For additional information regarding an individual serial number (or lot " +"number), click the line item for the serial number to reveal that specific " +"serial number's :guilabel:`Serial Number` form. From this form, click the " +":guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all " +"stock on-hand using that serial number, and any operations made using that " +"serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc.rst:5 +msgid "Miscellaneous Operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:3 +msgid "Process Batch Transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:5 +msgid "" +"Batch picking allows a single picker to handle a batch of orders, reducing " +"the number of times he must visit the same location. In Odoo, it means you " +"can regroup several transfers into the same batch transfer, then process it," +" either via the barcode application or in the form view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:11 +msgid "Create a Batch Transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:13 +msgid "" +"To activate the batch picking option, go to :menuselection:`Inventory --> " +"Configuration --> Configuration` and enable *Batch Pickings*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "" +"View of the inventory settings. Process to enable the batch pickings option " +"in the Odoo Inventory app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:20 +msgid "" +"Then, go to :menuselection:`Inventory --> Operations --> Batch Transfers` " +"and hit the create button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "View of the new menu, Batch Transfers, under operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:27 +msgid "" +"Now, determine the batch transfer responsible and the type of transfers you " +"want to include in the batch. To add the types of transfers, click on *Add a" +" line*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "View of a Batch Transfers form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:34 +msgid "" +"In the example below, a filter was applied to only see the transfers that " +"are in the *Pick* step. After that, the different transfers that needed to " +"be included in the batch transfer were selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "" +"View of the list of transfers to choose for a single batch transfer and how to add them\n" +"to the batch transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:42 +msgid "" +"To see the products to pick for the different transfers, click on *Select*. " +"If *Multi-locations* has been activated, the document also shows the " +"locations they have been reserved from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "" +"View of a batch transfer list. Products to pick with their source and target" +" locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:51 +msgid "Create a Batch Transfer from the Transfers List View" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:53 +msgid "" +"From the *Transfers List View*, select transfers that should be included in " +"the Batch. Then, select *Add to batch* from the *Action* list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "" +"View of the process to add transfers to a batch transfer from the transfers " +"list view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:61 +msgid "" +"Next, determine if you want to add the transfers to an existing draft batch " +"transfer or create a new one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "Option to add a responsible to a batch transfer so it can be confirmed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:69 +msgid "Process a Batch Transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:71 +msgid "" +"While gathering the products, you can edit the batch transfer and update the" +" *Quantity done* for each product. Once everything has been picked, select " +"*Validate* so the different transfers contained in the batch are validated " +"too." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "View of an in progress batch transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:80 +msgid "" +"In case all the products cannot be picked, you can create backorders for " +"each individual transfer which couldn’t be completely processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "" +"How to handle batch transfers with unavailable products. Creation of a backorder inside\n" +"of a batch transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "View of how backorders are handled in Odoo's batch transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:93 +msgid "Process a Batch Transfer from the Barcode app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:95 +msgid "Enter the *Barcode* application, select the *Batch Transfers* menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "View of the Odoo Barcode app dashboard" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:101 +msgid "" +"Then, you can enter the batch transfer on which you want to work. Batch " +"transfers can easily be grouped per responsible if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "View of the batch transfers dashboard inside of the Barcode app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:108 +msgid "" +"In the batch transfer, products are classified per location. The source " +"document is visible on each line and a color-code helps differentiate them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "" +"View of an in progress batch transfer with the Odoo Barcode application" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:116 +msgid "" +"To see the products to pick from another location, click on the *Next* " +"button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst-1 +msgid "" +"View of a ready and completed batch transfer inside of the Odoo Barcode " +"application" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/batch_transfers.rst:123 +msgid "" +"Once all the products have been picked, click on *Validate* (on the last " +"page) to mark the batch transfer as done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:3 +msgid "Consignment: buy and sell stock without owning it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:5 +msgid "" +"Most of the time, products stored in a company's warehouse are either " +"purchased from suppliers, or are manufactured in-house. However, suppliers " +"will sometimes let companies store and sell products in the company's " +"warehouse, without having to buy those items up-front. This is called " +"*consignment*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:10 +msgid "" +"Consignment is a useful method for suppliers to launch new products, and " +"easily deliver to their customers. It's also a great way for the company " +"storing the products (the consignee) to earn something back for their " +"efforts. Consignees can even charge a fee for the convenience of storing " +"products they don't actually own." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:16 +msgid "Enable the consignment setting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:18 +msgid "" +"To receive, store, and sell consignment stock, the feature needs to be " +"enabled in the settings. To do this, go to :menuselection:`Inventory --> " +"Configuration --> Settings`, and under the :guilabel:`Traceability` section," +" check the box next to :guilabel:`Consignment`, and then click " +":guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst-1 +msgid "Enabled Consignment setting in Inventory configuration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:28 +msgid "Receive (and store) consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:30 +msgid "" +"With the feature enabled in Odoo, consignment stock can now be received into" +" a warehouse. From the main :menuselection:`Inventory` dashboard, click into" +" the :guilabel:`Receipts` section. Then, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:35 +msgid "" +"Consignment stock is not actually purchased from the vendor; it is simply " +"received and stored. Because of this, there are no quotations or purchase " +"orders involved in receiving consignment stock. So, *every* receipt of " +"consignment stock will start by creating manual receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:39 +msgid "" +"Choose a vendor to enter in the :guilabel:`Receive From` field, and then " +"choose the same vendor to enter in the :guilabel:`Assign Owner` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:43 +msgid "" +"Since the products received from the vendor will be owned by the same " +"vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields " +"must match." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:46 +msgid "" +"Once the vendor-related fields are set, enter products into the " +":guilabel:`Product` lines, and set the quantities to be received into the " +"warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of " +"Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be " +"changed, as well. Once all the consignment stock has been received, " +":guilabel:`Validate` the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst-1 +msgid "Matching vendor fields in consignment Receipt creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:56 +msgid "Sell and deliver consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:58 +msgid "" +"Once consignment stock has been received into the warehouse, it can be sold " +"the same as any other in-stock product that has the :guilabel:`Can Be Sold` " +"option enabled on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:61 +msgid "" +"To create a sales order, navigate to the :menuselection:`Sales` app, and " +"from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, " +"choose a customer to enter into the :guilabel:`Customer` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:66 +msgid "" +"The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` " +"that supplied the consignment stock received (and stored) in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:69 +msgid "" +"Add the consignment product under the :guilabel:`Product` column in the " +"order lines, set the :guilabel:`Quantity`, and fill out any other pertinent " +"product details on the form. Once the quotation is complete, click " +":guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst-1 +msgid "Sales order of consignment stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:77 +msgid "" +"Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will " +"become a sales order. From here, the products can be delivered by clicking " +"on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate`" +" to validate the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:82 +msgid "Traceability and reporting of consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:84 +msgid "" +"Although consignment stock is owned by the vendor who supplied it, and not " +"by the company storing it in their warehouse, consignment products will " +"*still* appear in certain inventory reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:87 +msgid "" +"To find inventory reports, go to :menuselection:`Inventory --> Reporting`, " +"and choose a report to view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:91 +msgid "" +"Since the consignee does not actually own consigment stock, these products " +"are *not* reflected in the :guilabel:`Stock Valuation` report, and have no " +"impact on the consignee's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:96 +msgid "Product moves report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:98 +msgid "" +"To view all information about on-hand stock moves, navigate to the the " +":guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory " +"--> Reporting --> Product Moves`. For consignment products, the information " +"in this report is the same as any other product: the history of its product " +"moves can be reviewed; the :guilabel:`Quantity Done` and " +":guilabel:`Reference` document are available; and its :guilabel:`Locations` " +"are available, as well. The consignment stock will originate from " +":guilabel:`Partner Location/Vendors`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:106 +msgid "" +"To view a consignment product's moves by ownership, select the " +":guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` " +"parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to " +"finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst-1 +msgid "Consignment stock moves history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:115 +msgid "" +"To see forecasted units of consignment stock, go to " +":menuselection:`Inventory --> Reporting --> Forecasted Inventory`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:119 +msgid "Stock on hand report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/owned_stock.rst:121 +msgid "" +"View the :guilabel:`Stock On Hand` dashboard by navigating to " +":menuselection:`Inventory --> Reporting --> Inventory Report`. From this " +"report, the :guilabel:`Locations` of all stock on-hand are displayed, in " +"addition to the quantities per location. For consigment products, the " +":guilabel:`Owner` column will be populated with the owner of those products," +" or the original vendor who supplied the products in the first place." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:3 +msgid "Process wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:5 +msgid "" +"While a batch transfer is a group of several pickings, a **wave transfer** " +"only contains some parts of different pickings. Both methods are used to " +"pick orders in a warehouse, and depending on the situation, one method may " +"be a better fit than the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:9 +msgid "" +"To handle orders of a specific product category, or fetch products that are " +"at the same location, wave transfers are the ideal method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:12 +msgid "" +"In Odoo, wave transfers are actually batch transfers with an extra step: " +"transfers are split before being grouped in a batch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:18 +msgid "" +"Before a wave transfer can be created, the :guilabel:`Batch Transfers` and " +":guilabel:`Wave Transfers` options must be activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:21 +msgid "" +"First, go to :menuselection:`Inventory --> Configuration --> Settings`. In " +"the :guilabel:`Operations` section, enable :guilabel:`Batch Transfers` and " +":guilabel:`Wave Transfers`. Then, click :guilabel:`Save` to apply the " +"settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst-1 +msgid "" +"View of Odoo Inventory app settings to enable the wave transfers option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:30 +msgid "Add products to a wave" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:32 +msgid "" +"Now that the settings are activated, start a wave transfer by adding " +"products to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:34 +msgid "" +"Wave transfers can only contain product lines from transfers of the same " +"operation type. To view all the transfers and product lines in a specific " +"operation, first go to the :guilabel:`Inventory` dashboard and locate the " +"desired operation type's card. Then, open the options menu (the three dots " +"icon in the corner of the operation type's card) and click " +":guilabel:`Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst-1 +msgid "How to get an operation type's list of operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:43 +msgid "" +"On the operations page, select the product lines you want to add in a new or" +" existing wave. Then, click :guilabel:`Add to Wave`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst-1 +msgid "Select lines to add to the wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:51 +msgid "" +"Use the :guilabel:`Filters` in the search bar to group lines with the same " +"product, location, carrier, etc..." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:54 +msgid "After that, a pop-up box appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:56 +msgid "" +"To add the selected lines to an existing wave transfer, select the " +":guilabel:`an existing wave transfer` option and select the existing wave " +"transfer from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:59 +msgid "" +"To create a new wave transfer, select the :guilabel:`a new wave transfer` " +"option. If creating a new wave transfer, an employee can also be set in the " +"optional :guilabel:`Responsible` field. Once the desired options are " +"selected, click :guilabel:`Confirm` to add the product lines to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:64 +msgid "View wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:66 +msgid "" +"To view all wave transfers and their statuses, go to " +":menuselection:`Inventory --> Operations --> Wave Transfers`. Wave transfers" +" can also be viewed in the :guilabel:`Barcode` app by going to " +":menuselection:`Barcode --> Batch Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning.rst:5 +msgid "Planning" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:3 +msgid "How is the Scheduled Delivery Date Computed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:5 +msgid "" +"Providing the best possible service to customers is vital for business. It " +"implies planning every move: manufacturing orders, deliveries, receptions, " +"and so on. To do so, you need to configure lead time properly and coordinate" +" scheduled dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:9 +msgid "" +"By using lead times, Odoo provides end dates, the **Commitment Date**, for " +"each process. On a sales order, for example, this is the date your customer " +"will get the products he ordered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:13 +msgid "" +"From the customers’ side, the commitment date is important because it gives " +"them an estimation of when they will receive their products. The dates take " +"all other lead times, such as manufacturing, delivery, or suppliers, into " +"account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:19 +msgid "How are Lead Times Calculated?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:27 +msgid "" +"As said above, there are several types of lead times. Each is calculated " +"based on various indicators. Before going through the configuration, here is" +" a brief summary of how lead times are calculated and what they are:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:32 +msgid "" +"**Customer Lead Time**: the customer lead time is the default duration you " +"set. Therefore, the expected date on the sales orders is today + customer " +"lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:36 +msgid "" +"**Sales Security Lead Time**: the purpose is to be ready shipping that many " +"days before the actual commitment taken with the customer. Then, the default" +" scheduled date on the delivery order is **SO delivery date - Security Lead " +"Time**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:41 +msgid "" +"**Purchase Security Lead Time**: margin 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." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:46 +msgid "" +"**Purchase Delivery Lead Time**: this is the expected time between a PO " +"being confirmed and the receipt of the ordered products. The **Receipt " +"scheduled date - Vendor delivery date** is the default *PO Order By* date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:51 +msgid "" +"**Days to Purchase**: number of days the purchasing department takes to " +"validate a PO. If another RFQ to the same vendor is already opened, Odoo " +"adds the line to the RFQ instead of creating a new one. Then, the specific " +"date is set on the line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:56 +msgid "" +"**Manufacturing Lead Time**: this is the expected time it takes to " +"manufacture a product. This lead time is independent of the quantity to " +"produce and does not take the routing time into account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:61 +msgid "" +"**Manufacturing Security Lead Time**: additional time to mitigate the risk " +"of a manufacturing delay. In case of a *Replenish to Order*, the **Delivery " +"Order scheduled date - Manufacturing Lead Time - Manufacturing Security Lead" +" Time** is the default *Manufacturing Order* planned date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:68 +msgid "Sales - Lead Times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:70 +msgid "" +"In the *Sales* app, there is an option called *Delivery Date*. It allows " +"seeing an additional field on the sales orders, *Expected Date*. This one is" +" automatically computed based on the different lead times previously " +"configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst-1 +msgid "" +"View of the delivery settings to have the delivery lead time taken into " +"account" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:79 +msgid "" +"If the set up *Delivery Date* is earlier than the the *Expected Date*, a " +"warning message is displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst-1 +msgid "" +"View of the error that occurs when trying to choose an earlier date than what calculated\n" +"by Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:87 +msgid "" +"But, for all of this properly working, it is still necessary to configure " +"all the lead times that could occur." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:91 +msgid "Customer Lead Time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:93 +msgid "" +"The *Customer Lead Time* is the time needed for your product to go from your" +" warehouse to the customer place. It can be configured on any product by " +"going to :menuselection:`Sales --> Products --> Products`. There, open your " +"product form, go in the inventory tab, and add your *Customer Lead Time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst-1 +msgid "View of the customer lead time configuration from the product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:103 +msgid "" +"For example, product B is ordered on the 2nd of April but the *Customer Lead" +" Time* is two days. In that case, the expected delivery date is the 4th of " +"April." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:217 +msgid "Security Lead Time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:110 +msgid "" +"In sales, *Security Lead Time* corresponds to backup days to ensure you are " +"able to deliver the products in time. The purpose is to be ready shipping " +"earlier in order to arrive on time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:114 +msgid "" +"The number of security days is subtracted from the calculation to compute a " +"scheduled date earlier than the one promised to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:117 +msgid "" +"To set this up, go to :menuselection:`Inventory --> Configuration --> " +"Settings` and enable the feature *Security Lead Time for Sales*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst-1 +msgid "" +"View of the security lead time for sales configuration from the sales " +"settings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:124 +msgid "" +"For example, product B is scheduled to be delivered on the 6th of April but " +"the *Security Lead Time* is one day. In that case, the scheduled date for " +"the delivery order is the 5th of April." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:129 +msgid "Deliver several products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:131 +msgid "" +"In many cases, customers order several products at the same time. Those can " +"have different lead times but still need to be delivered, at once or " +"separately. Fortunately, Odoo can help you handle these cases easily." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:135 +msgid "" +"From the *Other Info* tab of your *Sale Order*, you can choose between *When" +" all products are ready* and *As soon as possible*. The first one is to " +"deliver products at once, while the second is to deliver them separately." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:140 +msgid "" +"For example, products A and B are ordered at the same time. A has 8 lead " +"days and B has 5. With the first option, the *Expected Date* is calculated " +"based on the product with the most lead days, here A. If the order is " +"confirmed on the 2nd of April, then the *Expected Date* is on the 10th of " +"April." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:146 +msgid "" +"With the second option, the *Expected Date* is calculated based on the " +"product with the least customer lead days. In this example, B is the product" +" with the least lead days. So, the *Expected Date* is on the 7th of April." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:152 +msgid "Purchase - Lead Times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:155 +msgid "Supplier Lead Time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:157 +msgid "" +"The *Supplier Lead Time* is the time needed for a product you purchased to " +"be delivered. To configure it, open a product from :menuselection:`Purchase " +"--> Products --> Products` and add a vendor under the *Purchase* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst-1 +msgid "View of the way to add vendors to products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:166 +msgid "" +"By clicking on *Add a line*, a new window is displayed. You can specify the " +"*Delivery Lead Time* there. If done so, the delivery day for every purchase " +"of that product is now equal to *Date of the Purchase Order + Delivery Lead " +"Time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst-1 +msgid "View of the delivery lead time configuration from a vendor form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:176 +msgid "" +"It is possible to add different vendors and, thus, different lead times " +"depending on the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:182 +msgid "" +"The *Security Lead Time* for purchase follows the same logic as the one for " +"*Sales*, except that you are the customer. Then, it is the margin of error " +"for your supplier to deliver your order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:186 +msgid "" +"To set up *Security Lead Time* for purchase, go to :menuselection:`Inventory" +" --> Configuration --> Settings` and enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst-1 +msgid "" +"View of the security lead time for purchase from the inventory settings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:194 +msgid "" +"Doing so, every time the system generates purchase orders, those are " +"scheduled that many days earlier to cope with unexpected vendor delays." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:198 +msgid "Manufacturing - Lead Times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:201 +msgid "Manufacturing Lead Time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:203 +msgid "" +"The *Manufacturing Lead Time* is the time needed to manufacture the product." +" To specify it, open the *Inventory* tab of your product form and add the " +"number of days the manufacturing takes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst-1 +msgid "" +"View of the manufacturing lead time configuration from the product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:211 +msgid "" +"When working with *Manufacturing Lead Times*, the *Deadline Start* of the " +"*MO* is **Commitment Date - Manufacturing Lead Time**. For example, the MO’s" +" deadline start date for an order having a commitment date on the 10th of " +"July is June 27th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:219 +msgid "" +"The *Security Lead Time* for manufacturing allows generating manufacturing " +"orders earlier to cope with the risk of manufacturing delays." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:223 +msgid "" +"To enable it, go to :menuselection:`Manufacturing --> Configuration --> " +"Settings` and tick *Security Lead Time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst-1 +msgid "" +"View of the security lead time for manufacturing from the manufacturing app " +"settings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:230 +msgid "" +"For example, a customer orders B with a delivery date scheduled on the 20th " +"of June. The *Manufacturing Lead Time* is 14 days and the *Security Lead " +"Time* is 3 days, so the manufacturing of B needs to start at the latest on " +"the 3rd of June, which is the MO’s planned date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:236 +msgid "Global Example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:238 +msgid "Here is a configuration:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:240 +msgid "1 day of security lead time for Sales" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:241 +msgid "2 days of security lead time for Manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:242 +msgid "3 days of manufacturing lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:243 +msgid "1 day of security lead time for Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:244 +msgid "4 days of supplier lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:246 +msgid "" +"Let’s say that a customer orders B on the 1st of September and the delivery " +"date is planned to be within 20 days (September 20th). In such a scenario, " +"here is when all the various steps are triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:250 +msgid "**September 1st**: the sales order is created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:251 +msgid "" +"**September 10th**: the deadline to order components from the supplier " +"because of the manufacturing process (4 days of supplier lead time)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:254 +msgid "" +"**September 13th**: the reception of the product from the supplier (1 day of" +" security lead time for Purchase)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:256 +msgid "" +"**September 14th**: the deadline start date for the manufacturing (19th - 3 " +"days of manufacturing lead time - 2 days of security lead time for " +"Manufacturing)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:259 +msgid "" +"**September 19th**: the expected date on the delivery order form (1 day of " +"security lead time for sales)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products.rst:5 +#: ../../content/applications/inventory_and_mrp/purchase/products.rst:5 +msgid "Products" +msgstr "Produkty" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:3 +msgid "Replenish on order (MTO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:9 +msgid "" +"*Replenish on order*, also known as *MTO* (make to order), is a " +"replenishment strategy that creates a draft order for a product every time a" +" sales order is created for it. For products that are purchased from a " +"vendor, a request for quotation (RFQ) is created, while a sales order for a " +"product manufactured in-house triggers the creation of a manufacturing " +"order. The creation of a |RFQ| or manufacturing order occurs every time a " +"sales order is created, regardless of the current stock level of the product" +" being ordered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:17 +msgid "Unarchive the Replenish on Order (MTO) route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:19 +msgid "" +"By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| " +"is a somewhat niche workflow that is only used by certain companies. " +"However, it is easy to unarchive the route in just a few simple steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:23 +msgid "" +"To do so, begin by navigating to :menuselection:`Inventory --> Configuration" +" --> Routes`. On the :guilabel:`Routes` page, click the :guilabel:`Filters` " +"button and select the :guilabel:`Archived` option. This shows all routes " +"that are currently archived." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst-1 +msgid "The archived filter on the Routes page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:31 +msgid "" +"Enable the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click" +" the :guilabel:`Action` button to reveal a drop-down menu. From the drop-" +"down menu, select :guilabel:`Unarchive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst-1 +msgid "The unarchive action on the Routes page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:38 +msgid "" +"Finally, remove the :guilabel:`Archived` filter from the " +":guilabel:`Search...` bar. The :guilabel:`Routes` page will now show all " +"available routes, including :guilabel:`Replenish on Order (MTO)`, which is " +"now selectable on the inventory tab of each product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst-1 +msgid "The MTO route appears on the Routes page after unarchiving it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:47 +msgid "Configure a product to use the MTO route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:49 +msgid "" +"With the |MTO| route unarchived, products can now be properly configured to " +"use replenish on order. To do so, begin by going to " +":menuselection:`Inventory --> Products --> Products`, then select an " +"existing product, or click :guilabel:`Create` to configure a new one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:53 +msgid "" +"On the product page, select the :guilabel:`Inventory` tab and enable the " +":guilabel:`Replenish on Order (MTO)` route in the :guilabel:`Routes` " +"section, along with one other route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:57 +msgid "" +"The :guilabel:`Replenish on Order (MTO)` route **does not** work unless " +"another route is selected as well. This is because Odoo needs to know how to" +" replenish the product when an order is placed for it (buy it, manufacture " +"it, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst-1 +msgid "Select the MTO route and a second route on the Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:65 +msgid "" +"If the product is purchased from a vendor to fulfill sales orders, enable " +"the :guilabel:`Can be Purchased` checkbox under the product name. Doing so " +"makes the :guilabel:`Purchase` tab appear alongside the other settings tabs " +"below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:69 +msgid "" +"Select the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the" +" :guilabel:`Price` they sell the product for." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst-1 +msgid "Enable \"Can be Purchased\" and specify a vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:76 +msgid "" +"If the product is manufactured, make sure that it has a bill of materials " +"(BOM) configured for it. To do so, click the :guilabel:`Bill of Materials` " +"smart button at the top of the screen, then click :guilabel:`Create` on the " +":guilabel:`Bill of Materials` page to configure a new |BOM| for the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:81 +msgid "" +"On the blank |BOM| form, add the components used to manufacture the product " +"on the :guilabel:`Components` tab, along with the operations required for " +"the manufacturing workflow on the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:85 +msgid "Finally, click :guilabel:`Save` to save the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:88 +msgid "Fulfill a sales order using the MTO route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:90 +msgid "" +"After configuring a product to use the |MTO| route, a replenishment order is" +" created for it every time a sales order including the product is confirmed." +" The type of order created depends on the second route selected in addition " +"to |MTO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:94 +msgid "" +"For example, if *Buy* was the second route selected, then a purchase order " +"is created upon confirmation of a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:98 +msgid "" +"When the |MTO| route is enabled for a product, a replenishment order is " +"always created upon confirmation of a sales order. This is the case even if " +"there is enough stock of the product on-hand to fulfill the sales order, " +"without buying or manufacturing additional units of it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:102 +msgid "" +"While the |MTO| route can be used in unison with a variety of other routes, " +"the *Buy* route is used as the example for this workflow. Begin by " +"navigating to the :menuselection:`Sales` app, then click :guilabel:`Create`," +" which opens a blank quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:106 +msgid "" +"On the blank quotation form, add a :guilabel:`Customer`, then click " +":guilabel:`Add a product` under the :guilabel:`Order Lines` tab, and enter a" +" product that has been configured to use the *MTO* and *Buy* routes. Click " +":guilabel:`Confirm` and the quotation is turned into a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:110 +msgid "" +"A :guilabel:`Purchase` smart button now appears in the top-right corner of " +"the sales order. Clicking it opens the |RFQ| associated with the sales " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:113 +msgid "" +"Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a " +"purchase order. A green :guilabel:`Receive Products` button now appears at " +"the top of the purchase order. Once the products are received, click " +":guilabel:`Receive Products` to register them into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:117 +msgid "" +"Return to the sales order by clicking the :guilabel:`SO` breadcrumb, or by " +"navigating to :menuselection:`Sales --> Orders --> Orders`, and selecting " +"the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:120 +msgid "" +"Finally, click the :guilabel:`Delivery` smart button in the top-right of the" +" order to be taken to the delivery order. Once the products have been " +"shipped to the customer, click :guilabel:`Validate` to confirm the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:3 +msgid "Reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:5 +msgid "" +"Reordering rules are used to keep forecasted stock levels above a certain " +"threshold without exceeding a specified upper limit. This is accomplished by" +" specifying a minimum quantity that stock should not fall below and a " +"maximum quantity that stock should not exceed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:9 +msgid "" +"Reordering rules can be configured for each product based on the route used " +"to replenish it. If a product uses the *Buy* route, then a Request for " +"Quotation (RFQ) is created when the reordering rule is triggered. If a " +"product uses the *Manufacture* route, then a Manufacturing Order (MO) is " +"created instead. This is the case regardless of the selected replenishment " +"route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:15 +msgid "Configure products for reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:17 +msgid "" +"In order to use reordering rules for a product, it must first be correctly " +"configured. Begin by navigating to :guilabel:`Inventory --> Products --> " +"Products`, then select an existing product, or create a new one by clicking " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:21 +msgid "" +"First, on the :guilabel:`General Information` tab, make sure that the " +":guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is " +"necessary because Odoo only tracks stock quantities for storable products, " +"and this number is used to trigger reordering rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst-1 +msgid "Set the Product Type as Storable." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:29 +msgid "" +"Next, click on the :guilabel:`Inventory` tab and select one or more routes " +"from the :guilabel:`Routes` section. Doing so tells Odoo which route to use " +"to replenish the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst-1 +msgid "Select one or more routes on the Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:36 +msgid "" +"If the product is reordered using the :guilabel:`Buy` route, confirm that " +"the :guilabel:`Can be Purchased` checkbox is enabled under the product name." +" This makes the :guilabel:`Purchase` tab appear. Click on the " +":guilabel:`Purchase` tab, and specify at least one vendor, and the price " +"that they sell the product for, so that Odoo knows which company the product" +" should be purchased from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst-1 +msgid "Specify a vendor and price on the Purchase tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:45 +msgid "" +"If the product is replenished using the :guilabel:`Manufacture` route, it " +"needs to have at least one Bill of Materials (BoM) associated with it. This " +"is necessary because Odoo only creates manufacturing orders for products " +"with a :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:49 +msgid "" +"If a :abbr:`BoM (Bill of Materials)` does not already exist for the product," +" select the :guilabel:`Bill of Materials` smart button at the top of the " +"product form, then click :guilabel:`Create` to configure a new :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst-1 +msgid "The Bill of Materials smart button on a product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:58 +msgid "Create new reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:60 +msgid "" +"To create a new reordering rule, navigate to :menuselection:`Inventory --> " +"Configuration --> Reordering Rules`, then click :guilabel:`Create`, and fill" +" out the new line as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:63 +msgid ":guilabel:`Product`: The product that is replenished by the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:64 +msgid ":guilabel:`Location`: The location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:65 +msgid "" +":guilabel:`Min Quantity`: The minimum quantity that can be forecasted " +"without the rule being triggered. When forecasted stock falls below this " +"number, a replenishment order for the product is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:68 +msgid "" +":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up " +"to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:69 +msgid "" +":guilabel:`Multiple Quantity`: Specify if the product should be replenished " +"in batches of a certain quantity (e.g., a product could be replenished in " +"batches of 20)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:71 +msgid "" +":guilabel:`UoM`: The unit of measure used for reordering the product. This " +"value can simply be `Units` or a specific unit of measurement for weight, " +"length, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst-1 +msgid "The form for creating a new reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:79 +msgid "" +"Reordering rules can also be created from each product form. To do so, " +"navigate to :menuselection:`Inventory --> Products --> Products`, then " +"select a product. Click on :menuselection:`Reordering Rules --> Create`, " +"then fill out the new line as detailed above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:83 +msgid "" +"Once a reordering rule has been created for a product, if its forecasted " +"quantity is below the rule's minimum quantity when the scheduler runs, a " +"replenishment order for the product is automatically generated. By default, " +"the scheduler runs once each day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:88 +msgid "" +"To manually trigger a reordering rule before the scheduler runs, select " +":menuselection:`Inventory --> Operations --> Run Scheduler`. Then, select " +"the green :guilabel:`Run Scheduler` button on the pop-up that appears. Be " +"aware that this also triggers any other scheduled actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:92 +msgid "" +"If the :guilabel:`Buy` route is selected, then an :abbr:`RFQ (Request for " +"Quotation)` is generated. To view and manage :abbr:`RFQs (Requests for " +"Quotation)`, navigate to :menuselection:`Purchase --> Orders --> Requests " +"for Quotation`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:96 +msgid "" +"If the :guilabel:`Manufacture` route is selected, then an :abbr:`MO " +"(Manufacturing Order)` is generated. To view and manage :abbr:`MOs " +"(Manufacturing Orders)`, navigate to :menuselection:`Manufacturing --> " +"Operations --> Manufacturing Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:101 +msgid "Set a preferred route for reordering" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:103 +msgid "" +"Odoo allows for multiple routes to be selected under the " +":guilabel:`Inventory` tab on each product form. For instance, it is possible" +" to select both :guilabel:`Buy` and :guilabel:`Manufacture`, thus enabling " +"the functionality of both routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:107 +msgid "" +"Odoo also enables users to set a preferred route for a product's reordering " +"rule. This is the route that the rule defaults to if multiple are selected. " +"To select a preferred route, begin by navigating to " +":menuselection:`Inventory --> Configuration --> Reordering Rules`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:111 +msgid "" +"By default, the :guilabel:`Preferred Route` column is hidden on the " +":guilabel:`Reordering Rules` page. Enable it by selecting the :guilabel:`⋮ " +"(three-dot)` option button on the right side of the page and checking the " +":guilabel:`Preferred Route` checkbox. Doing so reveals the " +":guilabel:`Preferred Route` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:116 +msgid "" +"Click inside of the column on the row of a reordering rule and a drop-down " +"menu shows all available routes for that rule. Select one to set it as the " +"preferred route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst-1 +msgid "Select a preferred route from the drop-down." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:124 +msgid "" +"If multiple routes are enabled for a product but no preferred route is set " +"for its reordering rule, the product is reordered using the selected route " +"that is listed first on the :guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:3 +msgid "Selecting a replenishment strategy" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:10 +msgid "" +"In Odoo, there are two strategies for automatically replenishing inventory: " +"*reordering rules* and the *make to order (MTO)* route. Although these " +"strategies differ slightly, they both have similar consequences: triggering " +"the automatic creation of a |PO| or |MO|. The choice of which strategy to " +"use depends on the business's manufacturing and delivery processes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:6 +msgid "Terminology" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:54 +msgid "Replenishment report and reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:21 +msgid "" +"The replenishment report is a list of all products that have a negative " +"forecast quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:23 +msgid "" +"*Reordering rules* are used to ensure there's always a minimum amount of a " +"product in-stock, in order to manufacture products and/or fulfill sales " +"orders. When the stock level of a product reaches its minimum, Odoo " +"automatically generates a purchase order with the quantity needed to reach " +"the maximum stock level." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:28 +msgid "" +"Reordering rules can be created and managed in the replenishment report, or " +"from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:31 +msgid "Make to order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:33 +msgid "" +"*Make to order (MTO)* is a procurement route that creates a draft purchase " +"order (or manufacturing order) each time a sales order is confirmed, " +"**regardless of the current stock level**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:36 +msgid "" +"Unlike products replenished using reordering rules, Odoo automatically links" +" the sales order to the |PO| or |MO| generated by the |MTO| route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:39 +msgid "" +"Another difference between reordering rules and |MTO| is, with |MTO|, Odoo " +"generates a draft |PO| or |MO| immediately after the |SO| is confirmed. With" +" reordering rules, Odoo generates a draft |PO| or |MO| when the product's " +"forecasted stock falls below the set minimum quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:43 +msgid "" +"In addition, Odoo automatically adds quantities to the |PO| or |MO| as the " +"forecast changes, so long as the |PO| or |MO| is not confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:46 +msgid "" +"The |MTO| route is the best replenishment strategy for products that are " +"customized, and/or for products that have no stock kept on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:56 +msgid "" +"To access the replenishment report, go to :menuselection:`Inventory app --> " +"Operations --> Replenishment.`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:59 +msgid "" +"By default, the replenishment report dashboard shows every product that " +"needs to be manually reordered. If there is no specific rule for a product, " +"Odoo assumes the :guilabel:`Min Quantity` and :guilabel:`Max Quantity` stock" +" are both `0.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:64 +msgid "" +"For products that don't have a set reordering rule, Odoo calculates the " +"forecast based on confirmed sales orders, deliveries, and receipts. For " +"products that have a set reordering rule, Odoo calculates the forecast " +"normally, but also takes into account the purchase/manufacturing lead time " +"and security lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:70 +msgid "" +"Before creating a new reordering rule, make sure the product has a *vendor* " +"or a *bill of materials* configured on the product form. To check this, go " +"to :menuselection:`Inventory app --> Products --> Products`, and select the " +"product to open its product form. The vendor, if configured, is listed in " +"the :guilabel:`Purchase` tab, and the bill on materials, if configured, is " +"found in the :guilabel:`Bill of Materials` smart button at the top of the " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:76 +msgid "" +"The :guilabel:`Product Type`, located in the :guilabel:`General Information`" +" tab on the product form, **must** be set to :guilabel:`Storable Product`. " +"By definition, a consumable product does not have its inventory levels " +"tracked, so Odoo cannot account for a consumable product in the " +"replenishment report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst-1 +msgid "" +"Replenishment report listing all items needing to be purchased to meet " +"current needs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:85 +msgid "" +"To create a new reordering rule from the replenishment report, go to " +":menuselection:`Inventory app --> Operations --> Replenishment`, click " +":guilabel:`Create`, and select the desired product from the drop-down menu " +"in the :guilabel:`Product` column. If necessary, a :guilabel:`Min Quantity` " +"and a :guilabel:`Max Quantity` can be configured in the corresponding " +"columns on the :guilabel:`Replenishment` report page, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:91 +msgid "" +"To create a new reordering rule from the product form, go to " +":menuselection:`Inventory app --> Products --> Products`, and select a " +"product to open its product form. Click the :guilabel:`Reordering Rules` " +"smart button, click :guilabel:`Create`, and fill out the fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:96 +msgid "Replenishment report fields" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:98 +msgid "" +"The following fields are on the :guilabel:`Replenishment` report. If any of " +"these fields are not visible, click the :guilabel:`⋮ (additional options)` " +"icon on the far right side of the report, then click the checkbox next to a " +"field to make it visible." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:102 +msgid ":guilabel:`Product`: the product that requires a replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:103 +msgid "" +":guilabel:`Location`: the specific location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:104 +msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:105 +msgid ":guilabel:`On Hand`: the amount of product currently available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:106 +msgid "" +":guilabel:`Forecast`: the amount of product available after all current " +"orders (sales, manufacturing, purchase, etc.) are taken into account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:108 +msgid "" +":guilabel:`Preferred Route`: how the product is procured, either " +":guilabel:`Buy`, :guilabel:`Manufactured`, :guilabel:`Dropship`, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:110 +msgid ":guilabel:`Vendor`: the company from which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:111 +msgid "" +":guilabel:`Bill of Materials`: the bill of materials for the product (if one" +" is configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:112 +msgid "" +":guilabel:`Trigger`: how the replenishment is created, either " +":guilabel:`Auto` (automatically, once the :guilabel:`On Hand` quantity goes " +"below the :guilabel:`Min Quantity`) or :guilabel:`Manual` (only when the " +"replenishment is requested)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:115 +msgid "" +":guilabel:`Procurement Group`: the reference number for how the product is " +"being acquired, such as a sales order, purchase order, or manufacturing " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:117 +msgid "" +":guilabel:`Min Quantity`: the minimum amount of product that should be " +"available. When inventory levels goes below this number, the replenishment " +"is triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:119 +msgid "" +":guilabel:`Max Quantity`: the amount of product that should be available " +"after replenishing the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:121 +msgid "" +":guilabel:`Multiple Quantity`: if the product should be ordered in specific " +"quantities, enter the number that should be ordered. For example, if the " +":guilabel:`Multiple Quantity` is set to `5`, and only 3 are needed, 5 " +"products are replenished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:124 +msgid "" +":guilabel:`To Order`: the amount of product that is currently needed, and " +"will be ordered, if the :guilabel:`Order Once` or :guilabel:`Automate " +"Orders` button is clicked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:126 +msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:127 +msgid ":guilabel:`Company`: the company for which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:129 +msgid "" +"By default, the quantity in the :guilabel:`To Order` field is the quantity " +"required to reach the set :guilabel:`Max Quantity`. However, the " +":guilabel:`To Order` quantity can be adjusted by clicking on the field and " +"changing the value. To replenish a product manually, click :guilabel:`Order " +"Once`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:133 +msgid "" +"To automate a replenishment from the :guilabel:`Replenishment` page, click " +":guilabel:`Automate Orders` on the right-side of the line, represented by a " +":guilabel:`🔄 (circular arrow)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:136 +msgid "" +"When this button is clicked, Odoo will automatically generate a draft " +"|PO|/|MO| every time the forecasted stock level falls below the set " +":guilabel:`Min Quantity` of the reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:139 +msgid "" +"On the :guilabel:`Replenishment` page, a reordering rule or manual " +"replenishment can be temporarily deactivated for a given period, by clicking" +" the :guilabel:`🔕 (snooze)` icon on the far-right of the line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst-1 +msgid "" +"Snooze options to turn off notifications for reordering for a period of " +"time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:147 +msgid "" +"A |PO| or |MO| created by a manual replenishment has a " +":guilabel:`Replenishment Report` as the source document. A |PO| or |MO| " +"created by an automated reordering rule has the |SO| reference number(s) " +"that triggered the rule as the source document." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst-1 +msgid "" +"Quote request list shows which quotes are directly from the replenishment " +"report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:156 +msgid "Make to order (MTO) route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:158 +msgid "" +"Since the |MTO| route is recommended for customized products, the route is " +"hidden by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:167 +msgid "To activate the |MTO| route in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:161 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:162 +msgid "" +"Activate the :guilabel:`Multi-Step Routes` setting, located under the " +":guilabel:`Warehouse` section, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:164 +msgid "" +"Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:165 +msgid "" +"Click on :menuselection:`Filters --> Archived` to show archived routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:166 +msgid "" +"Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click " +"on :menuselection:`Action --> Unarchive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:170 +msgid "" +"Activating the :guilabel:`Multi-Step Routes` setting also activates " +":guilabel:`Storage Locations`. If these features aren't applicable to the " +"warehouse, disable these settings after unarchiving the |MTO| route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:174 +msgid "" +"To set a product's procurement route to |MTO|, go to " +":menuselection:`Inventory app --> Products --> Products`, and click on the " +"desired product to open its product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:177 +msgid "" +"Then, click the :guilabel:`Inventory` tab, and in the :guilabel:`Routes` " +"section of options, select :guilabel:`Replenish on Order (MTO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:180 +msgid "" +"For products purchased directly from a vendor, make sure the :guilabel:`Buy`" +" route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` " +"route. Also, make sure a vendor is configured in the :guilabel:`Purchase` " +"tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:184 +msgid "" +"For products manufactured in-house, make sure the :guilabel:`Manufacture` " +"route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` " +"route. Also, make sure a bill of materials is configured for the product, " +"which is accessible via the :guilabel:`Bill of Materials` smart button on " +"the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:189 +msgid "Finally, when all configurations are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:192 +msgid "" +"The |MTO| route cannot be selected alone. |MTO| **only** works if the " +":guilabel:`Manufacture` or :guilabel:`Buy` route is also selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst-1 +msgid "Replenish on Order selected on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:3 +msgid "Use different units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:5 +msgid "" +"In some cases, handling products in different units of measure is necessary." +" For example, a business can buy products from a country that uses the " +"metric system, and then sell those products in a country that uses the " +"imperial system, so the business needs to convert the units. Another case " +"for unit conversion is when a business buys products in a big pack from a " +"supplier and then sells those products in individual units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:11 +msgid "Odoo can be set up to use different units of measure for one product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:16 +msgid "" +"To use different units of measure in Odoo, first go to " +":menuselection:`Inventory --> Configuration --> Settings --> Products` and " +"activate the :guilabel:`Units of Measure` setting. Then, click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst-1 +msgid "Enable Units of Measure in the Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:25 +msgid "Units of measure categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:27 +msgid "" +"After enabling the units of measure setting, view the default units of " +"measure categories in :menuselection:`Inventory --> Configuration --> Units " +"of Measures --> UoM Categories`. The category is important for unit " +"conversion, Odoo can only convert a product's units from one unit to another" +" only if both units belong to the same category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst-1 +msgid "Set units of measure categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:36 +msgid "" +"Each units of measure category has a reference unit. The reference unit is " +"highlighted in blue in the :guilabel:`Uom` column of the :guilabel:`Units of" +" Measure Categories` page. Odoo uses the reference unit as a base for any " +"new units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:40 +msgid "" +"To create a new unit, first select the correct category. For example, to " +"sell a product in a box of six units, click on the :guilabel:`Unit` category" +" line. Next, click :guilabel:`Edit`. After that, click :guilabel:`Add a " +"line`. Then, in the :guilabel:`Unit of Measure` field, title the new unit " +"`Box of 6`. In the :guilabel:`Type` field, select :guilabel:`Bigger than the" +" reference Unit of Measure`. In the :guilabel:`Ratio` field, enter `6.00000`" +" since a box of six is six times bigger than the reference unit (`1.00000`)." +" Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:47 +msgid "Click on the :guilabel:`Unit` category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:49 +msgid "" +"Click :guilabel:`Add a line`. As an example, we will create a Box of 6 units" +" that we will use for the Egg product. The box of 6 is 6 times bigger than " +"the reference unit of measure for the category which is “Units” here." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst-1 +msgid "" +"Convert products from one unit to another as long as they belong to the same" +" category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:58 +msgid "Specify a product's units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:60 +msgid "" +"To set units of measure on a product, first go to :menuselection:`Inventory " +"--> Products --> Products` and click on a product to open its settings. " +"Then, click on :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:63 +msgid "" +"In the :guilabel:`General Information` tab, edit the :guilabel:`Unit of " +"Measure` field to specify the unit of measure that the product is sold in. " +"The specified unit will also be the unit used to keep track of the product's" +" inventory and internal transfers. Edit the :guilabel:`Purchase UoM` field " +"to specify the unit of measure that the product is purchased in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:69 +msgid "Unit conversion" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:72 +msgid "Buy products in the Purchase UoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:74 +msgid "" +"When creating a new request for quotation (RFQ) in the Purchase app, Odoo " +"automatically uses the product's specified purchase unit of measure. " +"However, if needed, the :guilabel:`UoM` can be manually edited on the RFQ." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:78 +msgid "" +"After the RFQ is confirmed into a purchase order (PO), click on the " +":guilabel:`Receipt` smart button at the top right corner of the PO. Odoo " +"automatically converts the purchase unit of measure into the product's " +"sales/inventory unit of measure, so the :guilabel:`Demand` column of the " +"delivery receipt shows the converted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:83 +msgid "" +"For example, if the product's purchase UoM is `Box of 6` and its " +"sales/inventory unit of measure is `Units`, the PO shows the quantity in " +"boxes of six, and the delivery receipt shows the quantity in units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:88 +msgid "Replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:90 +msgid "" +"A request for quotation for a product can also be generated directly from " +"the product form using the :guilabel:`Replenish` button. After clicking " +":guilabel:`Replenish`, a replenish assistant box pops up. The purchase unit " +"of measure can be manually edited here if needed. Then, click " +":guilabel:`Confirm` to create the RFQ." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:95 +msgid "" +"Next, click the :guilabel:`Units Forecasted` smart button on the product " +"form and scroll down to :menuselection:`Forecasted Inventory --> Requests " +"for quotation`. Click on the RFQ reference number to open the draft RFQ. The" +" purchase UoM can also be edited here if needed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:100 +msgid "Sell in a different UoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:102 +msgid "" +"When creating a new quotation in the Sales app, Odoo automatically uses the " +"product's specified unit of measure. However, if needed, the :guilabel:`UoM`" +" can be manually edited on the quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:105 +msgid "" +"After the quotation is sent to the customer and confirmed into a sales order" +" (SO), click on the :guilabel:`Delivery` smart button at the top right " +"corner of the SO. Odoo automatically converts the unit of measure into the " +"product's inventory unit of measure, so the :guilabel:`Demand` column of the" +" delivery shows the converted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:110 +msgid "" +"For example, if the product's UoM on the SO was changed to `Box of 6`, but " +"its inventory unit of measure is `Units`, the SO shows the quantity in boxes" +" of six, and the delivery shows the quantity in units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:3 +msgid "When Should you Use Packages, Units of Measure or Special Packaging?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:6 +msgid "Units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:8 +msgid "" +"Units of measure specify the unit used to handle a product. In Odoo, you " +"have the possibility to specify the unit of measure in which you manage your" +" stock and the one which is used when purchasing the product to your " +"supplier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst-1 +msgid "" +"Specify unit of measure for handling a product vs. when it's purchased." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:16 +msgid "" +"Once a product has a :guilabel:`Unit of Measure` and a :guilabel:`Purchase " +"UoM` set on the product form, Odoo can automatically convert the different " +"units in the product's purchase/sales orders and the orders' respective " +"delivery orders/receipts. The only condition is that all the units have to " +"be in the *same category* (Unit, Weight, Volume, Length, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:21 +msgid "" +"For example, a product can have its :guilabel:`Unit of Measure` set to `feet" +" (ft)` and its :guilabel:`Purchase UoM` set to `centimeters (cm)`. When a " +"purchase order (PO) is created for that product, it will list the quantity " +"in centimeters. Then, when the PO is confirmed, Odoo automatically generates" +" a receipt and converts the centimeters to feet. The receipt will list the " +"quantity in feet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:28 +msgid "Packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:30 +msgid "" +"A package refers to the physical container that holds one or several " +"products from a picking. For example, when a product is ready for delivery, " +"its quantities can be separated into two different packages. In Odoo, the " +"quantity of products in each package can be recorded in the database. Make " +"sure the :guilabel:`Packages` option is enabled in :menuselection:`Inventory" +" --> Configuration --> Settings --> Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:36 +msgid "" +"On a delivery order, separate the products into different packages by " +"setting the :guilabel:`Done` quantity to the desired quantity in the first " +"package. Then, click :guilabel:`Put in Pack` to record the first package. " +"Repeat for each package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst-1 +msgid "Separate delivery into different packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst-1 +msgid "Separate delivery package details" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:49 +msgid "Packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:51 +msgid "" +"Packaging refers to a standard container that holds several unit of a " +"product. For example, cans of soda can be in a 6-pack, 15-pack, or even a " +"pallet for the packaging." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:54 +msgid "" +"In Odoo, packagings are used for indicative purposes on sales/purchase " +"orders and inventory transfers. The main difference between packagings and " +"units of measure is that packagings are defined at the product level while " +"UoMs are generic." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst-1 +msgid "Different product packaging examples." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst-1 +msgid "Package field on purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:67 +msgid "" +"Packaging is also useful during product reception. When scanning the barcode" +" of the packaging, Odoo automatically adds the number of units contained in " +"the packing on the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/usage.rst:71 +msgid ":doc:`uom`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting.rst:5 +msgid "Valuation Methods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:3 +msgid "Integrating additional costs to products (landed costs)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:5 +msgid "" +"The landed cost feature in Odoo allows the user to include additional costs " +"(shipment, insurance, customs duties, etc.) into the cost of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:11 +msgid "" +"First, go to :menuselection:`Inventory --> Configuration --> Settings --> " +"Valuation` and activate the :guilabel:`Landed Costs` feature. Odoo also " +"gives the option to set a :guilabel:`Default Journal` in which the landed " +"costs accounting entries will be recorded." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst-1 +msgid "Activate the landed cost feature in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:20 +msgid "Add costs to products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:23 +msgid "Receive the vendor bill" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:25 +msgid "" +"After a vendor fulfills a purchase order and sends a bill, click " +":guilabel:`Create Bill` on the purchase order to create a vendor bill in " +"Odoo. If the vendor bill includes landed costs, such as custom duties, tick " +"the box in the :guilabel:`Landed Costs` column on the vendor bill invoice " +"line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst-1 +msgid "Enable Landed Costs option on vendor bill line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:33 +msgid "" +"For charges that are always landed costs, create a landed cost product in " +"Odoo. That way, the landed cost product can be quickly added to the vendor " +"bill as an invoice line instead of manually entering the landed cost " +"information every time a vendor bill comes in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:37 +msgid "" +"First, create a new product in :menuselection:`Inventory --> Products --> " +"Products --> Create`. Next, name the landed cost product. Then, set the " +":guilabel:`Product Type` to :guilabel:`Service`. A landed cost product must " +"always be a service product type. After that, go to the :guilabel:`Purchase`" +" tab and check the box next to :guilabel:`Is a Landed Cost`. Finally, click " +":guilabel:`Save` to finish creating the landed cost product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:43 +msgid "" +"If this product is always a landed cost, you can also define it on the " +"product and avoid having to tick the box on each vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst-1 +msgid "Option to define a product as a landed cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:50 +msgid "" +"Once the landed cost is added to the vendor bill (either by checking the " +":guilabel:`Landed Cost` option on the invoice line or adding a landed cost " +"product to the bill), click the :guilabel:`Create Landed Costs` button at " +"the top of the bill. Odoo automatically creates a landed cost record with " +"the set landed cost pre-filled in the :guilabel:`Additional Costs` product " +"lines. From here, decide which picking the additional costs apply to by " +"clicking :guilabel:`Edit` and selecting the picking reference number from " +"the :guilabel:`Transfers` drop-down menu. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst-1 +msgid "" +"Use a warehouse transfer to cover a landed cost in the accounting journal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:62 +msgid "" +"After setting the picking, click :guilabel:`Compute` on the landed cost " +"record. Then, go to the :guilabel:`Valuation Adjustments` tab to see the " +"impact of the landed costs. Finally, click :guilabel:`Validate` to post the " +"landed cost entry to the accounting journal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:66 +msgid "" +"The user can access the journal entry that has been created by the landed " +"cost by clicking on the :guilabel:`Journal Entry`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:70 +msgid "" +"The product that the landed cost is applied to must have a product category " +"set to a :abbr:`FIFO (First In, First Out)` or an :abbr:`AVCO (Average " +"Costing)` method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst-1 +msgid "Landed cost journal entry" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:78 +msgid "" +"Landed cost records can also be directly created in " +":menuselection:`Inventory --> Operations --> Landed Costs`, it is not " +"necessary to create a landed cost record from the vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:3 +msgid "Inventory valuation configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:7 +msgid "" +"All of a company's stock on-hand contributes to the valuation of its " +"inventory. That value should be reflected in the company's accounting " +"records to accurately show the value of the company and all of its assets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:11 +msgid "" +"By default, Odoo uses a periodic inventory valuation (also known as manual " +"inventory valuation). This method implies that the accounting team posts " +"journal entries based on the physical inventory of the company, and that " +"warehouse employees take the time to count the stock. In Odoo, this method " +"is reflected inside each product category, where the :guilabel:`Costing " +"Method` field will be set to `Standard Price` by default, and the " +":guilabel:`Inventory Valuation` field will be set to `Manual`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst-1 +msgid "" +"The Inventory Valuation fields are located on the Product Categories form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:22 +msgid "" +"Alternatively, automated inventory valuation is an integrated valuation " +"method that updates the inventory value in real-time by creating journal " +"entries whenever there are stock moves initiated between locations in a " +"company's inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:27 +msgid "" +"Automated inventory valuation is a method recommended for expert " +"accountants, given the extra steps involved in journal entry configuration. " +"Even after the initial setup, the method will need to be periodically " +"checked to ensure accuracy, and adjustments may be needed on an ongoing " +"basis depending on the needs and priorities of the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:33 +msgid "Types of accounting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:35 +msgid "" +"Accounting entries will depend on the accounting mode: *Continental* or " +"*Anglo-Saxon*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:38 +msgid "" +"Verify the accounting mode by activating the :ref:`developer-mode` and " +"navigating to :menuselection:`Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:41 +msgid "" +"In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported " +"when products are sold or delivered. This means that the cost of a good is " +"only recorded as an expense when a customer is invoiced for a product. " +"*Interim Stock Accounts* are used for the input and output accounts, and are" +" both *Asset Accounts* in the balance sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:46 +msgid "" +"In *Continental* accounting, the cost of a good is reported as soon as a " +"product is received into stock. Additionally, a single *Expense* account is " +"used for both input and output accounts in the balance sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:51 +msgid "Costing methods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:53 +msgid "" +"Below are the three costing methods that can be used in Odoo for inventory " +"valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:55 +msgid "" +"**Standard Price**: is the default costing method in Odoo. The cost of the " +"product is manually defined on the product form, and this cost is used to " +"compute the valuation. Even if the purchase price on a purchase order " +"differs, the valuation will still use the cost defined on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:59 +msgid "" +"**Average Cost (AVCO)**: calculates the valuation of a product based on the " +"average cost of that product, divided by the total number of available stock" +" on-hand. With this costing method, inventory valuation is *dynamic*, and " +"constantly adjusts based on the purchase price of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:62 +msgid "" +"**First In First Out (FIFO)**: tracks the costs of incoming and outgoing " +"items in real-time and uses the real price of the products to change the " +"valuation. The oldest purchase price is used as the cost for the next good " +"sold until an entire lot of that product is sold. When the next inventory " +"lot moves up in the queue, an updated product cost is used based on the " +"valuation of that specific lot. This method is arguably the most accurate " +"inventory valuation method for a variety of reasons, however, it's highly " +"sensitive to input data and human error." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:70 +msgid "" +"Changing the costing method greatly impacts inventory valuation. It's highly" +" recommended to consult an accountant first before making any adjustments " +"here." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:74 +msgid "Configure automated inventory valuation in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:76 +msgid "" +"Make changes to inventory valuation options by navigating to " +":menuselection:`Inventory --> Configuration --> Product Categories`, and " +"choose the category/categories where the automated valuation method should " +"apply." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:81 +msgid "" +"It is possible to use different valuation settings for different product " +"categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:83 +msgid "" +"Under the :guilabel:`Inventory Valuation` heading are two labels: " +":guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the " +"desired :guilabel:`Costing Method` using the drop-down menu (e.g. " +":guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First " +"In First Out (FIFO)`) and switch the :guilabel:`Inventory Valuation` to " +":guilabel:`Automated`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:89 +msgid "" +":doc:`Using the inventory valuation " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:93 +msgid "" +"When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing " +"Method`, changing the numerical value in the :guilabel:`Cost` field for " +"products in the respective product category creates a new record in the " +"*Inventory Valuation* report to adjust the value of the product. The " +":guilabel:`Cost` amount will then automatically update based on the average " +"purchase price both of inventory on hand and the costs accumulated from " +"validated purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:99 +msgid "" +"When the :guilabel:`Costing Method` is changed, products already in stock " +"that were using the :guilabel:`Standard` costing method **do not** change " +"value; rather, the existing units keep their value, and any product moves " +"from then on affect the average cost, and the cost of the product will " +"change. If the value in the :guilabel:`Cost` field on a product form is " +"changed manually, Odoo will generate a corresponding record in the " +"*Inventory Valuation* report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:105 +msgid "" +"On the same screen, the :guilabel:`Account Stock Properties` fields will " +"appear, as they are now required fields given the change to automated " +"inventory valuation. These accounts are defined as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:109 +msgid "" +":guilabel:`Stock Valuation Account`: when automated inventory valuation is " +"enabled on a product, this account will hold the current value of the " +"products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:111 +msgid "" +":guilabel:`Stock Input Account`: counterpart journal items for all incoming " +"stock moves will be posted in this account, unless there is a specific " +"valuation account set on the source location. This is the default value for " +"all products in a given category, and can also be set directly on each " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:115 +msgid "" +":guilabel:`Stock Output Account`: counterpart journal items for all outgoing" +" stock moves will be posted in this account, unless there is a specific " +"valuation account set on the destination location. This is the default value" +" for all products in a given category, and can also be set directly on each " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:121 +msgid "Access reporting data generated by inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:123 +msgid "" +"To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`." +" At the top of the dashboard, change the :guilabel:`As of` field value to " +":guilabel:`Today`, and adjust the filtering :guilabel:`Options` to " +":guilabel:`Unfold All` in order to see all of the latest data displayed, all" +" at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:128 +msgid "" +"Under the parent :guilabel:`Current Assets` line item, look for the nested " +":guilabel:`Stock Valuation Account` line item, where the total valuation of " +"all of the inventory on hand is displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:132 +msgid "" +"Access more specific information with the :guilabel:`Stock Valuation " +"Account` drop-down menu, by selecting either the :guilabel:`General Ledger` " +"to see an itemized view of all of the journal entries, or by selecting " +":guilabel:`Journal Items` to review all of the individualized journal " +"entries that were submitted to the account. As well, annotations to the " +":guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, " +"filling in the text box, and clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst-1 +msgid "See the full inventory valuation breakdown in Odoo Accounting app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:3 +msgid "Using inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:5 +msgid "" +"*Inventory valuation* is a quintessential accounting procedure that " +"calculates the value of on-hand stock. Once determined, the inventory " +"valuation amount is then incorporated into a company's overall value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:9 +msgid "" +"In Odoo, this process can be conducted manually— by warehouse employees " +"physically counting the products— or automatically through the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:13 +msgid "" +":ref:`Inventory valuation configuration " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:16 +msgid "Understand the basics of inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:18 +msgid "" +"In order to understand how moving products in and out of stock affects the " +"company's overall value, consider the following product and stock moves " +"scenario below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:22 +msgid "Receive a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:24 +msgid "" +"For example, consider an physical product, a simple *table*, which is " +"categorized as `Office Furniture` in the product form's :guilabel:`Product " +"Category` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:27 +msgid "" +"Navigate to the the product category itself by going to " +":menuselection:`Inventory app --> Configuration --> Product Categories`, and" +" on the form, set the :guilabel:`Costing Method` as `First In First Out " +"(FIFO)` and the :guilabel:`Inventory Valuation` field as `Automated`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:32 +msgid "" +"Alternatively access the :guilabel:`Product Categories` dashboard by " +"clicking on the :guilabel:`internal link` arrow on the individual product's " +"form, by hovering over the :guilabel:`Product Category` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:36 +msgid "" +"Next, assume 10 tables are purchased at a price of $10.00, each. The " +":abbr:`PO (Purchase Order)` for those tables will show the subtotal of the " +"purchase as $100, plus any additional costs or taxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst-1 +msgid "Purchase order with 10 tables products valued at $10 each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:43 +msgid "" +"After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, use" +" the :guilabel:`Valuation` smart button to view how the value of inventory " +"was impacted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst-1 +msgid "Valuation smart button on a receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:51 +msgid "" +":ref:`Developer mode ` must be turned on to see the " +"*Valuation* smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:54 +msgid "" +"The :doc:`consignment " +"` " +"feature allows ownership to items in stock. Thus, products owned by other " +"companies are not accounted for in the host company's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:58 +msgid "" +"The :guilabel:`Stock Valuation` dashboard then displays valuation of all " +"products in the shipment, along with their quantities and valuation. In the " +"example of 10 tables being purchased, the :guilabel:`Total Value` column of " +"the dashboard would display a calculated valuation of $100." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst-1 +msgid "Stock valuation page depicting the products within a shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:66 +msgid "" +"In Odoo, automatic inventory valuation records are also recorded in the " +"*Accounting* app. To access these accounting entries, navigate to " +":menuselection:`Accounting --> Journal Entries`, and look for inventory " +"valuation entries with the `STJ` prefix in the :guilabel:`Journal` and " +":guilabel:`Number` columns, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst-1 +msgid "Accounting entry for the inventory valuation of 10 tables." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:76 +msgid "Deliver a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:78 +msgid "" +"In the same logic, when a table is shipped to a customer and leaves the " +"warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart " +"button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock " +"valuation record as it does on a :abbr:`PO (Purchase Order)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst-1 +msgid "Decreased stock valuation after a product is shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:87 +msgid "The inventory valuation report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:89 +msgid "" +"To view the current value of all products in the warehouse, go to " +":menuselection:`Inventory app --> Reporting --> Inventory Valuation`. The " +"records in the table are organized by product, and selecting a product's " +"drop-down menu displays detailed records with the :guilabel:`Date`, " +":guilabel:`Quantity`, and :guilabel:`Total Value` of the inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst-1 +msgid "Inventory valuation report showing multiple products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:99 +msgid "" +"The :guilabel:`Inventory At Date` button, located in the top-left corner of " +"the :guilabel:`Stock Valuation` dashboard, shows the inventory valuation of " +"products available during a prior specified date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:104 +msgid "Update product unit price" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:106 +msgid "" +"For any company: lead times, supply chain failures, and other risk factors " +"can contribute to invisible costs. Although Odoo attempts to accurately " +"represent the stock value, *manual valuation* serves as an additional tool " +"to update the unit price of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:111 +msgid "" +"Manual valuation is intended for products that can be purchased and received" +" for a cost greater than 0, or have product categories set with " +":guilabel:`Costing Method` set as either `Average Cost (AVCO)` or `First In " +"First Out (FIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst-1 +msgid "Add manual valuation of stock value to a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:119 +msgid "" +"Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard" +" by first navigating to :menuselection:`Inventory app --> Reporting --> " +"Inventory Valuation`, and then click the little gray drop-down icon to the " +"left of a product's name, to then reveal stock valuation line items below as" +" well as a teal :guilabel:`+ (plus)` button on the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:124 +msgid "" +"Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product" +" Revaluation` form, where updates to the calculation of inventory valuation " +"can be made, by increasing or decreasing the unit price of each product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst-1 +msgid "" +"Product revaluation form adding a value of $1.00 with the reason being " +"inflation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:6 +msgid "Incoming shipments and delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:8 +msgid "" +"There are several ways to handle how a warehouse receives products " +"(receipts) and ships products (deliveries). Depending on several factors, " +"such as the type of products stocked and sold, warehouse size, and the " +"amount of daily confirmed receipts and delivery orders, the way products are" +" handled when coming in and out of the warehouse can vary a lot. Different " +"settings can be configured for receipts and deliveries; they do not have to " +"be configured to have the same number of steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:15 +msgid "" +"`Using Routes (eLearning Tutorial) `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:16 +msgid "" +"`Push & Pull Rules (eLearning Tutorial) " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:20 +msgid "Choosing the right inventory flow to handle receipts and deliveries" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:22 +msgid "" +"By default, Odoo handles shipping and receiving in three different ways: in " +"one, two, or three steps. The simplest configuration is one step, which is " +"the default. Each additional step required for a warehouse for either the " +"receiving or shipping process will add an additional layer of operations to " +"perform before a product is either received or shipped. These configurations" +" depend entirely on the requirements for the products stored, such as " +"performing quality checks on received products, or using special packaging " +"on shipped products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:30 +msgid "One-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:32 +msgid "" +"The receiving and shipping rules for a one-step configuration are as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:34 +msgid "" +"**Receipt**: Receive products directly into stock. No intermediate steps " +"between receipt and stock occur, such as a transfer to a quality control " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:36 +msgid "" +"**Shipping**: Ship products directly from stock. No intermediate steps " +"between stock and shipping occur, such as a transfer to a packing location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:38 +msgid "" +"Can only be used if not using :abbr:`FIFO (First In, First Out)`, " +":abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First " +"Out)` removal strategies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:40 +msgid "Receipts and/or deliveries are handled quickly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:41 +msgid "" +"Recommended for small warehouses with low stock levels, and for non-" +"perishable items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:42 +msgid "Items are received or shipped directly into/from stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:45 +msgid "" +":ref:`Process receipts and deliveries in one step " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:48 +msgid "Two-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:50 +msgid "" +"The receiving and shipping rules for a two-step configuration are as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:52 +msgid "" +"**Input + stock**: Bring products to an input location *before* moving into " +"stock. Products can be organized by different internal storage locations, " +"such as various shelves, freezers, and locked areas, before being stocked in" +" the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:55 +msgid "" +"**Pick + ship**: Bring products to an output location before shipping. " +"Packages can be organized by different carriers or shipping docks before " +"being shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:57 +msgid "" +"Minimum requirement to use lot numbers or serial numbers to track products " +"with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`" +" or :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:60 +msgid "" +"Recommended for larger warehouses with high stock levels, or when stocking " +"large items (such as mattresses, large furniture, heavy machinery, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:83 +msgid "" +"Products received will not be available for manufacturing, shipping, etc., " +"until they are transferred into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:66 +msgid "" +":ref:`Process receipts and deliveries in two steps " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:69 +msgid "Three-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:71 +msgid "" +"The receiving and shipping rules for a three-step configuration are as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:73 +msgid "" +"**Input + quality + stock**: Receive products at the input location, " +"transfer them to a quality control area, and move the ones that pass " +"inspection into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:75 +msgid "" +"**Pick + pack + ship**: Pick products according to their removal strategy, " +"pack them in a dedicated packing area, and bring them to an output location " +"for shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:77 +msgid "" +"Can be used when tracking products by lot or serial numbers when using a " +":abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or " +":abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:80 +msgid "Recommended for very large warehouses with very high stock levels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:81 +msgid "" +"Required for any warehouse needing to perform quality control inspections " +"before receiving items into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:87 +msgid "" +":ref:`Process receipts in three steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:88 +msgid "" +":ref:`Process deliveries in three steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:91 +msgid "Inventory flow table of contents" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:3 +msgid "Process deliveries in three steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:7 +msgid "" +"Some companies process large amounts of deliveries every day, many of which " +"include multiple products or require special packaging. To make this " +"efficient, a packing step is needed before shipping out products. For this, " +"Odoo has a three step process for delivering goods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:11 +msgid "" +"In the default three-step delivery process, products that are part of a " +"delivery order are picked in the warehouse according to their removal " +"strategy, and brought to a packing zone. After the items have been packed " +"into the different shipments in the packing zone, they are brought to an " +"output location before being shipped. These steps can be modified if they do" +" not fit the needs of the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:20 +msgid "" +"Odoo is configured by default to :ref:`receive and deliver goods in one step" +" `, so the settings need to be changed" +" in order to utilize three step deliveries. First, make sure the *Multi-Step" +" Routes* option is enabled in :menuselection:`Inventory --> Configuration " +"--> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step " +"Routes` will also activate *Storage Locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +msgid "" +"Activate multi-step routes and storage locations in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:30 +msgid "" +"Next, the warehouse needs to be configured for three step deliveries. To do " +"this, go to :menuselection:`Inventory --> Configuration --> Warehouses`, and" +" click :guilabel:`Edit` to edit the :guilabel:`Warehouse`. Then, select " +":guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for " +":guilabel:`Outgoing Shipments`. Then :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +msgid "Set outgoing shipment option to deliver in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:39 +msgid "" +"Activating three-step receipts and deliveries will create two new internal " +"locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To " +"rename these locations, go to :menuselection:`Configuration --> Locations`, " +"select the :guilabel:`Location` to change, click :guilabel:`Edit`, update " +"the name, and finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:45 +msgid "Process a delivery order in three steps (pick + pack + ship)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:35 +msgid "Create a sales order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:50 +msgid "" +"In the :menuselection:`Sales` application, create a new quote by clicking " +":guilabel:`Create`. Select a :guilabel:`Customer`, add a storable " +":guilabel:`Product`, and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:53 +msgid "" +"A :guilabel:`Delivery` smart button will appear in the top right. Clicking " +"on it will show the picking order, packing order, and the delivery order, " +"which are all associated with the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +msgid "" +"After confirming the sales order, the Delivery smart button appears showing three items\n" +"associated with it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:62 +msgid "Process a picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:64 +msgid "" +"The picking, packing, and delivery orders will be created once the sales " +"order is confirmed. To view these transfers, go to " +":menuselection:`Inventory --> Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +msgid "" +"Ready status for the pick operation while the packing and delivery operations are waiting\n" +"another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:72 +msgid "" +"The status of the picking will be :guilabel:`Ready`, since the product must " +"be picked from stock before it can be packed. The status of the packing " +"order and delivery order will both be :guilabel:`Waiting Another Operation`," +" since the packing and delivery cannot happen until the picking is " +"completed. The status of the delivery order will only change to " +":guilabel:`Ready` when the packing has been marked :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:78 +msgid "" +"The receipt can also be found in the *Inventory* application. In the " +":guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart " +"button in the :guilabel:`Pick` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +msgid "The pick order can be seen in the Inventory Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:85 +msgid "" +"Click on the picking to process. If the product is in stock, Odoo will " +"automatically reserve the product. Click :guilabel:`Validate` to mark the " +"picking as done, and complete the transfer to the :guilabel:`Packing Zone`. " +"Then the packing order will be ready. Since the documents are linked, the " +"products which have been previously picked are automatically reserved on the" +" packing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +msgid "Validate the picking by clicking Validate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:95 +msgid "Process a packing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:97 +msgid "" +"The packing order will be ready to be processed once the picking is " +"completed, and can be found in the :menuselection:`Inventory` application " +":guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart " +"button in the :guilabel:`Pack` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +msgid "The packing order can be seen in the Inventory kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:105 +msgid "" +"Click on the packing order associated with the sales order, then click on " +":guilabel:`Validate` to complete the packing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +msgid "" +"Click Validate on the packing order to transfer the product from the packing zone to the\n" +"output location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:113 +msgid "" +"Once the packing order is validated, the product leaves the " +":guilabel:`WH/Packing Zone` location and moves to the :guilabel:`WH/Output` " +"location. Then, the status of the document will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:118 +msgid "Process a delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:120 +msgid "" +"The delivery order will be ready to be processed once the packing is " +"completed, and can be found in the :menuselection:`Inventory` application " +":guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart " +"button in the :guilabel:`Delivery Orders` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +msgid "The delivery order can be seen in the Delivery Orders Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:128 +msgid "" +"Click on the delivery order associated with the sales order, then click on " +":guilabel:`Validate` to complete the move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +msgid "" +"Click Validate on the delivery order to transfer the product from the output location to\n" +"the customer location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:136 +msgid "" +"Once the delivery order is validated, the product leaves the " +":guilabel:`WH/Output` location and moves to the " +":guilabel:`Partners/Customers` location. Then, the status of the document " +"will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:3 +msgid "Process receipts and deliveries in one step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:7 +msgid "" +"By default, incoming shipments are configured to be received directly into " +"stock, and outgoing shipments are configured to be delivered directly from " +"stock to the customer; the default setting for warehouses in Odoo is one " +"step receipts and deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:12 +msgid "" +"Incoming and outgoing shipments do not need to be configured with the same " +"steps. For example, products can be received in one step, but shipped in " +"three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:15 +msgid "" +"In the following example, one step will be used for both receipts and " +"deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:18 +msgid "Configure the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:20 +msgid "" +"If another receiving or shipping configuration is set on the warehouse, they" +" can easily be set back to the one step setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:23 +msgid "" +"Begin by navigating to :menuselection:`Inventory --> Configuration --> " +"Warehouses`, click on the desired warehouse, and click :guilabel:`Edit`. " +"Next, on the :guilabel:`Warehouse Configuration` tab, under the " +":guilabel:`Shipments` section, select :guilabel:`Receive goods directly (1 " +"step)` for :guilabel:`Incoming Shipments` and/or :guilabel:`Deliver goods " +"directly (1 step)` for :guilabel:`Outgoing Shipments`, and :guilabel:`Save` " +"the changes to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst-1 +msgid "" +"Set incoming and outgoing shipment options to receive and deliver in one " +"step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:35 +msgid "Receive goods directly (1 step)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:46 +msgid "Create a purchase order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:72 +msgid "" +"On the main :menuselection:`Purchase` application dashboard, start by making" +" a new quote by clicking :guilabel:`Create`. Then, select (or create) a " +":guilabel:`Vendor` from the drop-down field, add a storable " +":guilabel:`Product` to the order lines, and click :guilabel:`Confirm Order` " +"to finalize the quote as a new purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:97 +msgid "" +"A :guilabel:`Receipt` smart button will appear in the top-right corner of " +"the :abbr:`PO (purchase order)` form — click it to reveal the associated " +"receipt for the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst-1 +msgid "Receipt smart button appears on the confirmed purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:93 +msgid "" +"Purchase order receipts can also be found in the :menuselection:`Inventory` " +"application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " +"to Process` smart button in the :guilabel:`Receipts` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:0 +msgid "Receipt kanban card's 1 to Process smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:97 +msgid "Process the receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:64 +msgid "" +"When viewing the receipt (associated with the purchase order above), click " +":guilabel:`Validate` to then complete the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst-1 +msgid "Validate the purchase order via the Validate smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:72 +msgid "" +"If :guilabel:`Storage Locations` are activated, clicking the :guilabel:`≣ " +"(bullet list)` details icon next to the :guilabel:`🗑️ (trash)` delete icon " +"enables the :guilabel:`Detailed Operations` screen to pop-up. This allows " +"the location(s) to be specified for the received product(s)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:0 +msgid "" +"Select the Storage Location for the products being received in the Detailed Operations\n" +"pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:81 +msgid "" +"Once the receipt is validated, the product leaves the :guilabel:`Supplier " +"Location` and enters the :guilabel:`WH/Stock Location`. Once it arrives " +"here, it will be available for manufacturing, sales, etc. Then, the status " +"of the document will change to :guilabel:`Done`, thus completing the " +"reception process in one step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:87 +msgid "Deliver goods directly (1 step)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:92 +msgid "" +"Start my navigating to the main :menuselection:`Sales` app dashboard, and " +"make a new quote by clicking :guilabel:`Create`. Then select (or create) a " +":guilabel:`Customer` from the drop-down field, add a storable " +":guilabel:`Product` that is in stock to the order lines, and click " +":guilabel:`Confirm` to finalize the quotation as a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:100 +msgid "" +"A :guilabel:`Delivery` smart button will appear in the top-right corner of " +"the :abbr:`SO (Sales Order)` form — click it to reveal the associated " +"delivery order for the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst-1 +msgid "The Delivery smart button appears after the sales order is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:108 +msgid "" +"Delivery orders can also be found in the :menuselection:`Inventory` " +"application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " +"to Process` smart button in the :guilabel:`Delivery Orders` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:0 +msgid "Delivery Orders kanban card's 1 to Process smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:196 +msgid "Process the delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:119 +msgid "" +"When viewing the delivery order (associated with the sales order above), " +"click :guilabel:`Validate` to then complete the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst-1 +msgid "Validate the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_one_step.rst:126 +msgid "" +"Once the picking order is validated, the product leaves the " +":guilabel:`WH/Stock location` and moves to the :guilabel:`Partners/Customers" +" location`. Then, the status of the document will change to " +":guilabel:`Done`, thus completing delivery in one step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:3 +msgid "Process receipts and deliveries in two steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:7 +msgid "" +"Depending on a company's business processes, multiple steps may be needed " +"before receiving or shipping products. In the two-step receipt process, " +"products are received in an input area, then transferred to stock. Two-step " +"receipts work best when various storage locations are being used, such as " +"locked or secured areas, freezers and refrigerators, or various shelves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:12 +msgid "" +"Products can be sorted according to where they are going to be stored, and " +"employees can stock all the products going to a specific location. The " +"products are not available for further processing until they are transferred" +" into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:16 +msgid "" +"In the two-step delivery process, products that are part of a delivery order" +" are picked from the warehouse according to their removal strategy, and " +"brought to an output location before being shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:20 +msgid "" +"One situation where this would be useful is when using either a :abbr:`FIFO " +"(First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO " +"(First Expired, First Out)` removal strategy, where the products that are " +"being picked need to be selected based on their receipt date or expiration " +"date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:25 +msgid "" +"Odoo is configured by default to :ref:`receive and deliver goods in one step" +" `, so the settings need to be changed" +" in order to utilize two-step receipts and deliveries. Incoming and outgoing" +" shipments do not need to be set to have the same steps. For example, " +"products can be received in two steps, but shipped in one step. In the " +"following example, two steps will be used for both receipts and deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:32 +msgid "Configure multi-step routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:34 +msgid "" +"First, make sure the :guilabel:`Multi-Step Routes` option is enabled in " +":menuselection:`Inventory --> Configuration --> Settings`, under the " +":guilabel:`Warehouse` heading. After enabling the setting, :guilabel:`Save` " +"the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:39 +msgid "" +"Activating the :guilabel:`Multi-Step Routes` setting will also activate the " +":guilabel:`Storage Locations` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:46 +msgid "" +"Next, the warehouse needs to be configured for two-step receipts and " +"deliveries. Go to :menuselection:`Inventory --> Configuration --> " +"Warehouses`, and click :guilabel:`Edit` to change the warehouse settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:50 +msgid "" +"Then, select :guilabel:`Receive goods in input and then stock (2 steps)` for" +" :guilabel:`Incoming Shipments`, and :guilabel:`Send goods in output and " +"then deliver (2 steps)` for :guilabel:`Outgoing Shipments`. :guilabel:`Save`" +" the changes to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +msgid "" +"Set incoming and outgoing shipment options to receive and deliver in two " +"steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:59 +msgid "" +"Activating two-step receipts and deliveries will create new *input* and " +"*output* locations, which by default, are labeled :guilabel:`WH/Input` and " +":guilabel:`WH/Output`, respectively, on the :guilabel:`Locations` dashboard." +" To rename these locations, go to :menuselection:`Configuration --> " +"Locations`, select the :guilabel:`Location` to change, and then click " +":guilabel:`Edit`. On the location form, update the :guilabel:`Location " +"Name`, make any other changes (if necessary) and :guilabel:`Save` the " +"changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:67 +msgid "Process a receipt in two steps (input + stock)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:78 +msgid "" +"For businesses with multiple warehouses that have different step " +"configurations, the :guilabel:`Deliver To` field on the :abbr:`PO (Purchase " +"Order)` form may need to be specified as the correct *input location* " +"connected to the two-step warehouse, which can be done by selecting the " +"warehouse from the drop-down selection that includes the `Receipts` label at" +" the end of the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:84 +msgid "" +"After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` " +"smart button will appear in the top-right corner of the :abbr:`PO (Purchase " +"Order)` form — click it to reveal the associated receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst-1 +msgid "After confirming a purchase order, a Receipt smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:0 +msgid "One receipt ready to process in the Inventory Overview kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:104 +msgid "" +"The receipt and internal transfer will be created once the purchase order is" +" confirmed. The status of the receipt will be :guilabel:`Ready`, since the " +"receipt must be processed first. The status of the internal transfer will be" +" :guilabel:`Waiting Another Operation`, since the transfer cannot happen " +"until the receipt is completed. The status of the internal transfer will " +"only change to :guilabel:`Ready` once the receipt has been marked as " +":guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:110 +msgid "" +"Click on the :guilabel:`Receipt` associated with the purchase order, then " +"click :guilabel:`Validate` to complete the receipt and move the product to " +"the :guilabel:`Input Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +msgid "" +"Validate the receipt by clicking Validate, then the product will be transferred to the\n" +"WH/Input location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:119 +msgid "Process the internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:121 +msgid "" +"Once the product is in the :guilabel:`Input Location`, the internal transfer" +" is ready to move the product into stock. Navigate to the " +":menuselection:`Inventory` app, and on the :guilabel:`Inventory Overview` " +"dashboard, click the :guilabel:`# To Process` smart button in the " +":guilabel:`Internal Transfers` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst-1 +msgid "" +"One Internal Transfer ready to process in the Inventory Overview kanban " +"view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:130 +msgid "" +"Click on the :guilabel:`Transfer` associated with the purchase order, then " +"click :guilabel:`Validate` to complete the receipt and move the product to " +"stock. Once the transfer is validated, the product enters the stock and is " +"available for customer deliveries or manufacturing orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +msgid "Validate the internal transfer to move the item to stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:140 +msgid "Process a delivery order in two steps (pick + ship)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:145 +msgid "" +"In the :menuselection:`Sales` application, create a new quote by clicking " +":guilabel:`Create`. Select or create a :guilabel:`Customer`, add a storable " +":guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:149 +msgid "" +"After confirming the :abbr:`SO (Sales Order)`, a :guilabel:`Delivery` smart " +"button will appear in the top-right corner of the :abbr:`SO (Sales Order)` " +"form. Click it to reveal the associated delivery forms." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +msgid "" +"After confirming the sales order, the Delivery smart button appears showing two items\n" +"associated with it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:159 +msgid "" +"Sales order receipts can also be found in the :menuselection:`Inventory` " +"application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " +"To Process` smart button in the :guilabel:`Pick` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:0 +msgid "The pick order can be seen in the Inventory kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:168 +msgid "Process the picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:170 +msgid "" +"The picking and delivery order will be created once the sales order is " +"confirmed. When the :guilabel:`Delivery` smart button appears, click it to " +"reveal the :guilabel:`Transfers` dashboard, which lists both the picking and" +" the delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:174 +msgid "" +"The status of the picking will be :guilabel:`Ready`, since the product must " +"be picked from stock before it can be shipped. The status of the delivery " +"order will be :guilabel:`Waiting Another Operation`, since the delivery " +"cannot happen until the picking is completed. The status of the delivery " +"order will only change to :guilabel:`Ready` once the picking has been marked" +" as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +msgid "" +"Ready status for the pick operation while the delivery operation is Waiting Another\n" +"Operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:185 +msgid "" +"Click on the picking delivery order to begin processing it. If the product " +"is in stock, Odoo will automatically reserve the product. Click " +":guilabel:`Validate` to mark the picking as :guilabel:`Done`, then the " +"delivery order will be ready for processing. Since the documents are linked," +" the products which have been previously picked are automatically reserved " +"on the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:198 +msgid "" +"The delivery order will be ready to be processed once the picking is " +"completed, and can be found in the :menuselection:`Inventory` application, " +"on the :guilabel:`Inventory Overview` dashboard. Click the :guilabel:`# To " +"Process` smart button in the :guilabel:`Delivery Orders` kanban card to " +"begin." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:203 +msgid "" +"The delivery order associated with the :abbr:`SO (Sales Order)` can also be " +"quickly accessed by clicking on the :guilabel:`Delivery` smart button again," +" and choosing the delivery order on the :guilabel:`Transfers` page (which " +"should now be marked as :guilabel:`Ready`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst-1 +msgid "The delivery order can be seen in the Inventory Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:211 +msgid "" +"Click on the delivery order associated with the :abbr:`SO (Sales Order)`, " +"then click on :guilabel:`Validate` to complete the move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst:219 +msgid "" +"Once the delivery order is validated, the product leaves the " +":guilabel:`WH/Output` location on the :guilabel:`Transfers` dashboard and " +"moves to the :guilabel:`Partners/Customers` location. Then, the status of " +"the document will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:3 +msgid "Process receipts in three steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:7 +msgid "" +"Some companies require a quality control process before receiving goods from" +" suppliers. To accomplish this, Odoo has a three-step process for receiving " +"goods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:10 +msgid "" +"In the three-step receipt process, products are received in an input area, " +"then transferred to a quality area for inspection. Products that pass the " +"quality inspection are then transferred into stock. The products are not " +"available for further processing until they are transferred out of the " +"quality area and into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:18 +msgid "" +"Odoo is configured by default to :ref:`receive and deliver goods in one step" +" `, so the settings need to be changed" +" in order to utilize three-step receipts. First, make sure the *Multi-Step " +"Routes* option is enabled in :menuselection:`Inventory --> Configuration -->" +" Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes`" +" will also activate *Storage Locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst-1 +msgid "" +"Activate multi-step routes and storage locations in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:28 +msgid "" +"Next, the warehouse needs to be configured for three-step receipts. Go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, and click " +":guilabel:`Edit` to edit the warehouse. Then, select :guilabel:`Receive " +"goods in input, then quality and then stock (3 steps)` for " +":guilabel:`Incoming Shipments`. Then, :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst-1 +msgid "Set incoming shipment option to receive in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:37 +msgid "" +"Activating three-step receipts and deliveries will create two new internal " +"locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). " +"To rename these locations, go to :menuselection:`Configuration --> " +"Locations`, select the :guilabel:`Location` to change, click " +":guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:43 +msgid "Process a receipt in three steps (input + quality + stock)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:48 +msgid "" +"In the :menuselection:`Purchase` application, create a new quote by clicking" +" :guilabel:`Create`. Select a :guilabel:`Vendor`, add a storable " +":guilabel:`Product`, and click :guilabel:`Confirm Order`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:52 +msgid "" +"A :guilabel:`Receipt` smart button will appear in the top right, and the " +"receipt will be associated with the purchase order. Clicking on the " +":guilabel:`Receipt` smart button will show the receipt order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:61 +msgid "Process a receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:63 +msgid "" +"One receipt and two internal transfers (one transfer to quality, and a " +"subsequent transfer to stock) will be created once the purchase order is " +"confirmed. To view these transfers, go to :menuselection:`Inventory --> " +"Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst-1 +msgid "" +"The status of the three receipt transfers will show which operation is ready and which ones\n" +"are waiting another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:72 +msgid "" +"The status of the receipt transferring the product to the input location " +"will be :guilabel:`Ready`, since the receipt must be processed before any " +"other operation can occur. The status of the two internal transfers will be " +":guilabel:`Waiting Another Operation`, since the transfers cannot be " +"processed until the linked step before each transfer is completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:77 +msgid "" +"The status of the first internal transfer to *quality* will only change to " +":guilabel:`Ready` when the receipt has been marked :guilabel:`Done`. The " +"status for the second internal transfer to *stock* will be marked " +":guilabel:`Ready` only after the transfer to quality has been marked " +":guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:82 +msgid "" +"The receipt can also be found in the :menuselection:`Inventory` application." +" In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` " +"smart button in the :guilabel:`Receipts` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst-1 +msgid "One Receipt ready to process in the Inventory Overview kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:90 +msgid "" +"Click on the receipt associated with the purchase order, then click " +":guilabel:`Validate` to complete the receipt and move the product to the " +":guilabel:`Input Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst-1 +msgid "" +"Validate the receipt by clicking Validate, and the product will be transferred to the\n" +"WH/Quality location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:99 +msgid "Process a transfer to Quality Control" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:101 +msgid "" +"Once the product is in the :guilabel:`Input Location`, the internal transfer" +" is ready to move the product to :guilabel:`Quality Control`. In the " +":menuselection:`Inventory` :guilabel:`Overview` dashboard, click the " +":guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` " +"kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:110 +msgid "" +"Click on the :guilabel:`Transfer` associated with the purchase order, then " +"click :guilabel:`Validate` to complete the transfer and move the product to " +"the :guilabel:`Quality Control` location. Once the transfer is validated, " +"the product is ready for the quality inspection, but is not available for " +"manufacturing or delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst-1 +msgid "" +"Validate the internal transfer to move the item to the Quality Control " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:120 +msgid "Process a transfer to stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:122 +msgid "" +"Once the product is in the :guilabel:`Quality Control` location, the final " +"internal transfer is ready to move the product to :guilabel:`Stock`. In the " +":guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process`" +" smart button in the :guilabel:`Internal Transfers` Kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:126 +msgid "" +"Click on the final :guilabel:`Transfer` associated with the purchase order, " +"then click :guilabel:`Validate` to complete the transfer and move the " +"product to stock. Once the transfer is validated, the product enters the " +"stock and is available for customer deliveries or manufacturing orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses.rst:5 +msgid "Warehouses" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:3 +msgid "Create a second warehouse" +msgstr "Utwórz drugi magazyn" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:5 +msgid "" +"A *warehouse* is a physical building or space where items are stored. In " +"Odoo, it is possible to set up multiple warehouses and transfer stored items" +" between them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:8 +msgid "" +"By default, the Odoo platform has one warehouse that is already configured, " +"with the address set as the company's address. To create a second warehouse," +" select :menuselection:`Configuration --> Warehouses`, then click " +":guilabel:`Create` and configure the form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:12 +msgid ":guilabel:`Warehouse`: the full name of the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:13 +msgid "" +":guilabel:`Short Name`: the abbreviated code by which the warehouse is " +"referred to; the short name for the default warehouse in Odoo is **WH**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:15 +msgid "" +":guilabel:`Company`: the company that owns the warehouse; this can be set as" +" the company that owns the Odoo database or the company of a customer or " +"vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:17 +msgid ":guilabel:`Address`: the address where the warehouse is located" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:20 +msgid "" +"The options below will only appear if the :guilabel:`Multi-Step Routes` " +"checkbox is enabled in :menuselection:`Configuration --> Settings` under the" +" :guilabel:`Warehouse` heading. For more information about routes and how " +"they work in Odoo, see :ref:`Using Routes and Pull/Push Rules `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:25 +msgid "" +":guilabel:`Incoming/Outgoing Shipments`: select the routes that incoming and" +" outgoing shipments should follow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:27 +msgid "" +":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied " +"from this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:28 +msgid "" +":guilabel:`Manufacture to Resupply`: allow for items to be manufactured in " +"this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:29 +msgid "" +":guilabel:`Manufacture`: select the route that should be followed when " +"manufacturing goods inside the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:31 +msgid "" +":guilabel:`Buy to Resupply`: check the box to allow for purchased products " +"to be delivered to the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:33 +msgid "" +":guilabel:`Resupply From`: select warehouses that can be used to resupply " +"the warehouse being created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst-1 +msgid "A filled out form for creating a new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:41 +msgid "" +"Creating a second warehouse will automatically enable the *Storage " +"Locations* setting, which allows location tracking of products within a " +"warehouse. To toggle this setting, navigate to :menuselection:`Configuration" +" --> Settings` and click the checkbox under the :guilabel:`Warehouse` " +"heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:46 +msgid "" +"After filling out the form, click :guilabel:`Save` and the new warehouse " +"will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:49 +msgid "Add inventory to a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:51 +msgid "" +"If a new warehouse is created that has existing inventory in it, the " +"inventory counts should be added to Odoo so that the stock listed in the " +"Odoo database reflects what is in the physical warehouse. To add inventory " +"to a new warehouse, navigate to :menuselection:`Inventory --> Operations -->" +" Inventory Adjustments`, and then click :guilabel:`Create`. The inventory " +"adjustment form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:57 +msgid "" +":guilabel:`Inventory Reference`: the name or code that the inventory " +"adjustment can be referred to by" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:59 +msgid "" +":guilabel:`Locations`: the location(s) where the inventory is stored; " +"include the new warehouse and any locations within it that inventory will be" +" added to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:61 +msgid "" +":guilabel:`Products`: include all products that will be added to inventory " +"or leave blank to select any product during the next step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:63 +msgid "" +":guilabel:`Include Exhausted Products`: include products with a quantity of " +"zero; does not affect inventory adjustments for new warehouses since they " +"have no existing inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:65 +msgid "" +":guilabel:`Accounting Date`: the date used by accounting teams for " +"bookkeeping related to the inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:67 +msgid "" +":guilabel:`Company`: the company that owns the inventory; can be set as the " +"user's company or as a customer or vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:69 +msgid "" +":guilabel:`Counted Quantities`: choose whether the counted quantities for " +"products being added should default to stock on hand or zero; does not " +"affect inventory adjustments for new warehouses since they have no existing " +"inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst-1 +msgid "A filled out form for an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:77 +msgid "" +"Once the form is properly configured, click on :guilabel:`Start Inventory` " +"to be taken to the next page where products can be added to the inventory " +"adjustment. Add a new product by clicking on :guilabel:`Create` and then " +"fill out the product line as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:81 +msgid ":guilabel:`Product`: the product being added to inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:82 +msgid "" +":guilabel:`Location`: the location where the product is currently stored in " +"the new warehouse; this can be set as the overall warehouse or a location " +"within the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:84 +msgid "" +":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the " +"serial number used to identify it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:86 +msgid "" +":guilabel:`On Hand`: the total quantity of the product stored in the " +"location for which inventory is being adjusted; this should be zero for a " +"new location or warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:88 +msgid "" +":guilabel:`Counted`: the amount of the product that is being added to " +"inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:89 +msgid "" +":guilabel:`Difference`: the difference between the *On Hand* and *Counted* " +"values; this will automatically update to reflect the value entered in the " +":guilabel:`Counted` column" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:91 +msgid ":guilabel:`UoM`: the unit of measure used for counting the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst-1 +msgid "Include a line for each product being added to inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/create_a_second_warehouse.rst:97 +msgid "" +"After adding all the products already stored in the new warehouse, click " +":guilabel:`Validate Inventory` to complete the inventory adjustment. The " +"values in the :guilabel:`On Hand` column will update to reflect those in the" +" :guilabel:`Counted` column and the products added will appear in the " +"inventory of the new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:3 +msgid "Resupply from another warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:5 +msgid "" +"A common use case for multiple warehouses is to have one central warehouse " +"that resupplies multiple shops, and in this case, each shop is considered a " +"local warehouse. When a shop wants to replenish a product, the product is " +"ordered to the central warehouse. Odoo allows the user to easily set which " +"warehouse(s) can resupply another warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:13 +msgid "" +"To resupply from another warehouse, first go to :menuselection:`Inventory " +"--> Configuration --> Settings --> Warehouse` and activate :guilabel:`Multi-" +"Step Routes`. Then, click :guilabel:`Save` to apply the setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst-1 +msgid "Enable Multi-Step Routes in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:21 +msgid "" +"View all the configured warehouses by going to :menuselection:`Inventory -->" +" Configuration --> Warehouses`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:24 +msgid "" +"Create a new warehouse by clicking :guilabel:`Create`. Then, give the " +"warehouse a name and a :guilabel:`Short Name`. Finally, click " +":guilabel:`Save` to finish creating the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:27 +msgid "" +"After that, go back to the :guilabel:`Warehouses` page and open the " +"warehouse that will be resupplied by the second warehouse. Then, click " +":guilabel:`Edit`. In the :guilabel:`Warehouse Configuration` tab, locate the" +" :guilabel:`Resupply From` field, and check the box next to the second " +"warehouse's name. If the warehouse can be resupplied by more than one " +"warehouse, make sure to check those warehouses' boxes too. Finally, click " +":guilabel:`Save` to apply the setting. Now, Odoo knows which warehouses can " +"resupply this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst-1 +msgid "Supply one warehouse with another in the Warehouse Configuration tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:39 +msgid "Set route on a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:41 +msgid "" +"After configuring which warehouse(s) to resupply from, a new route is now " +"available on all product forms. The new route appears as :guilabel:`Supply " +"Product from [Warehouse Name]` under the :guilabel:`Inventory` tab on a " +"product form. Use the :guilabel:`Supply Product from [Warehouse Name]` route" +" with a reordering rule or the make to order (MTO) route to replenish stock " +"by moving the product from one warehouse to another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst-1 +msgid "" +"Route setting which enables a product to resupplied from a second warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:51 +msgid "" +"When a product's reordering rule is triggered and the product has the " +":guilabel:`Supply Product from [Warehouse Name]` route set, Odoo " +"automatically creates two pickings. One picking is a *delivery order* from " +"the second warehouse, which contains all the necessary products, and the " +"second picking is a *receipt* with the same products for the main warehouse." +" The product move from the second warehouse to the main warehouse is fully " +"tracked in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:57 +msgid "" +"On the picking/transfer records created by Odoo, the :guilabel:`Source " +"Document` is the product's reordering rule. The location between the " +"delivery order and the receipt is a transit location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst-1 +msgid "" +"A reordering rule automatically creates two receipts for stock between " +"warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst-1 +msgid "A warehouse order for resupplying one warehouse's stock with another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst-1 +msgid "A receipt for stock received to one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:3 +msgid "Transfer products between warehouses using replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:5 +msgid "" +"For companies that use multiple warehouses, it is often necessary to " +"transfer items between them. This is referred to as an *inter-warehouse " +"transfer*. Odoo *Inventory* handles the administrative process of inter-" +"warehouse transfers to ensure that inventory counts remain accurate during " +"and after the transfer. This document will detail the method for conducting " +"an inter-warehouse transfer using replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:12 +msgid "Configure warehouses for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:14 +msgid "" +"First, ensure the :guilabel:`Multi-Step Routes` setting is enabled by " +"navigating to :menuselection:`Inventory --> Configuration --> Settings`, and" +" then check the box under the :guilabel:`Warehouse` tab. This will provide " +"additional configuration options when creating a second warehouse that are " +"needed for inter-warehouse replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:19 +msgid "" +"By default, Odoo comes with a main warehouse already configured. If an " +"additional warehouse has not already been created, do so now from the " +":guilabel:`Inventory` module by selecting :menuselection:`Configuration --> " +"Warehouses --> Create`. Otherwise, select the warehouse that products will " +"be transferred to from the :guilabel:`Warehouses` page and then click " +":guilabel:`Edit` to change its settings. Configure the warehouse as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:25 +msgid "" +":guilabel:`Warehouse`: choose a name that is not already being used for " +"another warehouse (e.g. `Alternative Warehouse`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:27 +msgid "" +":guilabel:`Short Name`: choose a short name by which the warehouse will be " +"identified (e.g. `ALT_WH`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:30 +msgid "" +"Click :guilabel:`Save` and the new warehouse will be created. In addition, a" +" new :guilabel:`Resupply From` field will appear on the warehouse's form. " +"Click :guilabel:`Edit` and then check the box next to the warehouse that " +"will be used to resupply the warehouse that is currently being configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst-1 +msgid "" +"A warehouse settings form configured to allow resupplying between " +"warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:39 +msgid "" +"For the purposes of this demonstration, the warehouse that products are " +"transferred from (outgoing) will be titled \"San Francisco\", and the " +"warehouse that products are transferred to (incoming) will be titled \"San " +"Francisco 2\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:44 +msgid "Configure products for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:46 +msgid "" +"Products must also be configured properly in order for them to be " +"transferred between warehouses. Navigate to :menuselection:`Inventory --> " +"Products --> Products` and select an existing product or :guilabel:`Create` " +"a new one, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:50 +msgid "" +"Then, on the product form, go to the :guilabel:`Inventory` tab and enable " +"the checkbox for :guilabel:`X: Supply Product from Y`, with *X* being the " +"warehouse receiving the transferred products and *Y* being the warehouse " +"that products are transferred from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst-1 +msgid "Enable the checkbox to resupply one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:59 +msgid "Replenish one warehouse from another" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:61 +msgid "" +"Starting in the :menuselection:`Inventory` module, select " +":menuselection:`Products --> Products` and then choose the product that will" +" be replenished. Click the :guilabel:`Replenish` button on the top left of " +"the product page and fill out the pop-up form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:65 +msgid "" +":guilabel:`Quantity`: the number of units that will be sent to the warehouse" +" being replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:66 +msgid "" +":guilabel:`Scheduled Date`: the date that the replenishment is scheduled to " +"take place" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:67 +msgid ":guilabel:`Warehouse`: the warehouse that will be replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:68 +msgid "" +":guilabel:`Preferred Routes`: select `X: Supply Product from Y`, with *X* " +"being the warehouse to be replenished and *Y* being the warehouse that the " +"product will be transferred from" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst-1 +msgid "The form for replenishing a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:75 +msgid "" +"Click :guilabel:`Confirm` and a delivery order will be created for the " +"outgoing warehouse along with a receipt for the warehouse that will receive " +"the product. Depending on the configuration settings for the outgoing and " +"incoming warehouses, processing delivery orders and receipts will require " +"between one and three steps. This document will detail how to process one-" +"step deliveries and receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:82 +msgid "Process the delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:84 +msgid "" +"The first stage of a replenishment order is processing the delivery from the" +" warehouse that the product is being transferred from. On the " +":menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` " +"button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, " +"then the delivery order created for the replenishment. On the delivery order" +" page, click the :guilabel:`Check Availability` button in the top left to " +"reserve the quantity of the product to be transferred. Once the delivery has" +" been dispatched, click the :guilabel:`Validate` button to register the " +"quantities shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst-1 +msgid "The delivery orders card for the outgoing warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:99 +msgid "" +"Once the goods arrive at the incoming warehouse, the receipt created for " +"that warehouse must be processed as well. Return to the " +":menuselection:`Inventory` dashboard and select the :guilabel:`X to Process`" +" button on the :guilabel:`Receipts` card for the incoming warehouse, then " +"the receipt created for the replenishment. On the receipt page, click the " +":guilabel:`Validate` button in the top left of the page to register the " +"quantities received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:109 +msgid "" +"After processing the receipt, the products transferred will now appear in " +"the inventory of the incoming warehouse. The stock numbers for both " +"warehouses can be viewed by returning to the product page and selecting the " +":guilabel:`X Units On Hand` button at the top of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:114 +msgid "Automate inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:116 +msgid "" +"Using reordering rules, it is possible to automate the process of " +"replenishing one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:119 +msgid "" +"To get started, navigate to :menuselection:`Inventory --> Products --> " +"Products`, and then choose the product that will be replenished. From the " +"product page, select the :guilabel:`Reordering Rules` smart button at the " +"top of the form, and then on the next page, click :guilabel:`Create` to " +"configure the form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:124 +msgid "" +":guilabel:`Location`: the location that the reordering rule will replenish " +"when triggered, in this case, the incoming warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:126 +msgid "" +":guilabel:`Min Quantity`: when the quantity on hand at the incoming " +"warehouse falls below this number, the reordering rule will be triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:128 +msgid "" +":guilabel:`Max Quantity`: when the reordering rule is triggered, the product" +" will be replenished at the incoming warehouse up to this quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:130 +msgid "" +":guilabel:`Multiple Quantity`: specify if the product should be replenished " +"in batches of a certain quantity; for example, a product could be " +"replenished in batches of 20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:132 +msgid "" +":guilabel:`UoM`: the unit of measure used for reordering the product; this " +"value can simply be `Units`, or a specific unit of measurement for weight, " +"length, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst-1 +msgid "A fully configured reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:139 +msgid "" +"Finish by clicking :guilabel:`Save` and the reordering rule will be created." +" Now, when the scheduler runs automatically each day, a transfer will be " +"created for each reordering rule that has been triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:144 +msgid "" +"To manually trigger reordering rules, start from the " +":menuselection:`Inventory` module and select :menuselection:`Operation --> " +"Run Scheduler`, then click the green :guilabel:`Run Scheduler` button in the" +" pop-up that appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:148 +msgid "" +"After the scheduler runs, a delivery order and receipt will be created for " +"the outgoing and incoming warehouses, respectively. Both the delivery order " +"and receipt should be processed using the same method as detailed above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:3 +msgid "Manage Warehouses and Locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:9 +msgid "Warehouse" +msgstr "Magazyn" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:11 +msgid "" +"In Odoo, a **Warehouse** is the actual building/place in which a company's " +"items are stocked. Multiple warehouses can be set up in Odoo and the user " +"can create moves between warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:15 +msgid "Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:17 +msgid "" +"A **Location** is a specific space within the warehouse. It can be a " +"sublocation of the warehouse (a shelf, a floor, an aisle, and so on). " +"Therefore, a location is part of one warehouse only and it is not possible " +"to link one location to multiple warehouses. In Odoo, as many locations can " +"be configured as needed under one warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:22 +msgid "There are three types of locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:24 +msgid "" +"The **Physical Locations** are internal locations that are part of the " +"warehouses that the company owns. They can be the loading and unloading " +"areas of the warehouse, a shelf, a department, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:28 +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 they are not owned by the user's company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:32 +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 recording lost products (**Inventory " +"Loss**), or accounting for products that are on their way to the warehouse " +"(**Procurements**)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:37 +msgid "" +"In Odoo, locations are structured hierarchically. Locations can be " +"structured as a tree, dependent on a parent-child relationship. This gives " +"more detailed levels of analysis of the stock operations and the " +"organization of the warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:44 +msgid "" +"To activate locations, go to :menuselection:`Configuration --> Settings` and" +" enable :guilabel:`Storage Locations`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst-1 +msgid "Enable the storage location feature in Odoo Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:52 +msgid "" +"To manage several routes within the warehouses, also enable " +":guilabel:`Multi-Step Routes` and check " +":doc:`../../routes/concepts/use_routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:41 +msgid "Create a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:58 +msgid "" +"To create a warehouse, go to :menuselection:`Configuration --> Warehouse " +"Management --> Warehouses` and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:61 +msgid "" +"Then, fill out a :guilabel:`Warehouse Name` and a :guilabel:`Short Name`. " +"The short name is five characters maximum." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst-1 +msgid "Short name field of a warehouse on Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:69 +msgid "" +"The :guilabel:`Short Name` appears on transfer orders and other warehouse " +"documents. Odoo recommends using an understandable one like \"WH/[first " +"letters of location]\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:72 +msgid "" +"Now, go back to the :guilabel:`Inventory` dashboard. There, new operations " +"related to the newly created warehouse have been automatically generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst-1 +msgid "" +"Inventory app dashboard displaying new transfer types for the recently " +"created warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:80 +msgid "" +"Adding a second warehouse will automatically activate the " +":guilabel:`Locations` setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:83 +msgid "Create a new location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:85 +msgid "" +"To create a location, go to :menuselection:`Configuration --> Warehouse " +"Management --> Locations` and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:88 +msgid "" +"Then, fill out a :guilabel:`Location Name` and a :guilabel:`Parent Location`" +" and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst-1 +msgid "Create a new warehouse location in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes.rst:5 +msgid "Advanced Routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts.rst:5 +msgid "Concepts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:3 +msgid "Organize a cross-dock in a warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:5 +msgid "" +"Cross-docking is the process of sending products that are received directly " +"to the customers, without making them enter the stock. The trucks are simply" +" unloaded in a *Cross-Dock* area in order to reorganize products and load " +"another truck." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:13 +msgid "" +"For more information on how to organize your warehouse, read our blog: `What" +" is cross-docking and is it for me? `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:20 +msgid "" +"In the *Inventory* app, open :menuselection:`Configuration --> Settings` and" +" activate the *Multi-Step Routes*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:27 +msgid "Doing so will also enable the *Storage Locations* feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:29 +msgid "" +"Now, both *Incoming* and *Outgoing* shipments should be configured to work " +"with 2 steps. To adapt the configuration, go to :menuselection:`Inventory " +"--> Configuration --> Warehouses` and edit your warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:36 +msgid "" +"This modification will lead to the creation of a *Cross-Docking* route that " +"can be found in :menuselection:`Inventory --> Configuration --> Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:43 +msgid "Configure products with Cross-Dock Route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:45 +msgid "" +"Create the product that uses the *Cross-Dock Route* and then, in the " +"inventory tab, select the routes *Buy* and *Cross-Dock*. Now, in the " +"purchase tab, specify the vendor to who you buy the product and set a price " +"for it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:55 +msgid "" +"Once done, create a sale order for the product and confirm it. Odoo will " +"automatically create two transfers which will be linked to the sale order. " +"The first one is the transfer from the *Input Location* to the *Output " +"Location*, corresponding to the move of the product in the *Cross-Dock* " +"area. The second one is the delivery order from the *Output Location* to " +"your *Customer Location. Both are in state *Waiting Another Operation* " +"because we still need to order the product to our supplier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:68 +msgid "" +"Now, go to the *Purchase* app. There, you will find the purchase order that " +"has been automatically triggered by the system. Validate it and receive the " +"products in the *Input Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:77 +msgid "" +"When the products have been received from the supplier, you can go back to " +"your initial sale order and validate the internal transfer from *Input* to " +"*Output*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:86 +msgid "" +"The delivery order is now ready to be processed and can be validated too." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:3 +msgid "Sell stock from multiple warehouses using virtual locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:5 +msgid "" +"While keeping stock and selling inventory from one warehouse might work for " +"smaller companies, bigger companies might need to keep stock in, or sell " +"from, multiple warehouses in multiple locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:9 +msgid "" +"In Odoo, sometimes products included in a single sales order might take " +"stock from two (or more) warehouses. In Odoo, pulling products from multiple" +" warehouses to satisfy sales demands can be done by using *virtual " +"locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:14 +msgid "" +"In order to create virtual locations in warehouses and proceed to the " +"following steps, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step" +" Routes` features will need to be enabled in the :menuselection:`Settings` " +"app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:18 +msgid "" +"To do so, go to :menuselection:`Inventory --> Configuration --> Settings`, " +"scroll down to the :guilabel:`Warehouse` section, and click the checkboxes " +"next to :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`. " +"Then, :guilabel:`Save` the changes to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:23 +msgid "Create and configure a virtual parent location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:25 +msgid "" +"Before creating any virtual stock locations, a new warehouse will need to be" +" created. This new warehouse will act as a *virtual* warehouse, and will be " +"the *parent* location of other physical warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:31 +msgid "" +"Virtual warehouses are great for companies with multiple physical " +"warehouses. This is because a situation might arise when one warehouse runs " +"out of stock of a particular product, but another warehouse still has stock " +"on-hand. In this case, stock from these two (or more) warehouses could be " +"used to fulfill a single sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:36 +msgid "" +"The \"virtual\" warehouse acts as a single aggregator of all the inventory " +"stored in a company's physical warehouses, and is used (for traceability " +"purposes) to create a hierarchy of locations in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:43 +msgid "" +"To create a new warehouse, go to :menuselection:`Inventory --> Configuration" +" --> Warehouses`, and click :guilabel:`Create`. From here, the warehouse " +":guilabel:`Name` and :guilabel:`Short Name` can be changed, and other " +"warehouse details can be changed under the :guilabel:`Warehouse " +"Configuration` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:48 +msgid "" +"Under the :guilabel:`Shipments` heading, set the number of steps used to " +"process :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` by" +" selecting between the :guilabel:`1 step`, :guilabel:`2 steps`, and " +":guilabel:`3 steps` radio buttons. The desired option for " +":guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` will " +"depend on the warehouse's procurement process, and might differ for " +"individual products or product categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:55 +msgid "" +":doc:`How to choose the right flow to handle receipts and deliveries? " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:58 +msgid "" +"Under the :guilabel:`Resupply` heading, configure the method(s) for how the " +"warehouse resupplies its inventory:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:61 +msgid "" +":guilabel:`Resupply Subcontractors`: resupply subcontractors with components" +" from this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:62 +msgid "" +":guilabel:`Manufacture to Resupply`: when products are manufactured, they " +"can be manufactured in this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:64 +msgid "" +":guilabel:`Manufacture`: to produce right away, move the components to the " +"production location directly and start the manufacturing process; to pick " +"first and then produce, unload the components from the stock to input " +"location first, and then transfer it to the production location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:68 +msgid "" +":guilabel:`Buy to Resupply`: when products are bought, they can be delivered" +" to this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:69 +msgid "" +":guilabel:`Resupply From`: automatically create routes to resupply this " +"warehouse from another chosen warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:73 +msgid "" +"*Routes* can be set and configured directly from the :guilabel:`Warehouse` " +"form, by clicking on the :guilabel:`Routes` smart button. Once the warehouse" +" is configured, virtual *Locations* can be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst-1 +msgid "The edit screen for creating a new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:81 +msgid "" +"In order to apply this virtual warehouse as the *parent* location of two " +"*child* location warehouses, there need to be two warehouses configured with" +" physical stock locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid "**Parent Warehouse**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouse`: `Virtual Warehouse`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid ":guilabel:`Location`: `VWH`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid "**Child Warehouses**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouses`: `Warehouse A` and `Warehouse B`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:0 +msgid ":guilabel:`Locations`: `WHA/Stock` and `WHB/Stock`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:95 +msgid "Create a virtual parent location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:98 +msgid "" +"In order to take stock from multiple warehouses to fulfill a sales order, " +"there need to be at least **two** warehouses acting as *child locations* of " +"the *virtual parent location* warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:101 +msgid "" +"To create and edit *Locations*, go to :menuselection:`Inventory --> " +"Configuration --> Locations`. All :guilabel:`Locations` are listed here, " +"including the *Stock* :guilabel:`Location` of the virtual warehouse that was" +" created. Click into the *Stock* :guilabel:`Location` for the virtual " +"warehouse that was previously created (:dfn:`Warehouse Name/Stock`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:106 +msgid "" +"Then, under the :guilabel:`Additional Information` section, change the " +":guilabel:`Location Type` from :guilabel:`Internal Location` to " +":guilabel:`View`. :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:109 +msgid "" +"This identifies this :guilabel:`Location` as a *virtual location*, which is " +"used to create a hierarchical structure for a warehouse and aggregate its " +"*child locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:113 +msgid "" +"Products can *not* be stored in a :guilabel:`View` :guilabel:`Location " +"Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst-1 +msgid "Warehouse location types in location creation screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:120 +msgid "Configure physical warehouse locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:122 +msgid "" +"Navigate back to the :guilabel:`Locations` overview (via the breadcrumbs), " +"and remove any filters in the :guilabel:`Search Bar`. Then, click into the " +"first physical warehouse :guilabel:`Location` that was previously created to" +" be a *child location*, and click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:126 +msgid "" +"Under :guilabel:`Parent Location`, select the virtual warehouse from the " +"drop-down menu, and :guilabel:`Save` changes. Then, navigate back to the " +":guilabel:`Locations` overview, and repeat this step for the second physical" +" warehouse stock location. Be sure to :guilabel:`Save` changes again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:130 +msgid "" +"Both locations are now *child locations* of the virtual warehouse *parent " +"location*. This allows stock to be taken from multiple locations to fulfill " +"a single sales order, if there is not enough stock in any one location " +"(provided they are both tied to the same virtual warehouse *parent " +"location*)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:136 +msgid "Example flow: Sell a product from a virtual warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:139 +msgid "" +"To sell products from multiple warehouses using a virtual *parent* location " +"in this flow, there must be at least **two** products and at least **two** " +"warehouses configured - with at least **one** product with quantity on-hand " +"in each warehouse, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:143 +msgid "" +"To create a new request for quotation, or RFQ, navigate to the " +":menuselection:`Sales` app, and click :guilabel:`Create` from the " +":guilabel:`Quotations` overview. Fill out the information on the new " +"quotation by adding a :guilabel:`Customer`, and click :guilabel:`Add a " +"product` to add the two products stored in the two warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:148 +msgid "" +"Then, click the :guilabel:`Other Info` tab on the sales order form. Under " +"the :guilabel:`Delivery` section, change the :guilabel:`Warehouse` field " +"value listed to the virtual warehouse that was previously created. Once the " +"warehouse has been changed, click :guilabel:`Confirm` to convert the " +"quotation into a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:153 +msgid "" +"Now that the quotation has been confirmed as a sales order, click the " +":guilabel:`Delivery` smart button. From the warehouse delivery form, confirm" +" that the :guilabel:`Source Location` value matches the " +":guilabel:`Warehouse` field value from the sales order. Both should list the" +" virtual warehouse location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:159 +msgid "" +"The :guilabel:`Source Location` on the warehouse delivery form and the " +":guilabel:`Warehouse` under the :guilabel:`Other Info` tab on the sales " +"order form *must* match in order for the products included in the sales " +"order to be pulled from different warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:163 +msgid "" +"If the virtual warehouse is not the value in the :guilabel:`Source Location`" +" field on the warehouse delivery form, then click :guilabel:`Edit`, make the" +" change, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:166 +msgid "" +"If the virtual warehouse is not the value in the :guilabel:`Warehouse` field" +" on the sales order, then a new quotation may need to be generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:168 +msgid "" +"If whe :guilabel:`Warehouse` field is missing on the sales order form, then " +"the virtual warehouse (and its children warehouses) may not have been set up" +" correctly, in which case, review the documentation above again to make sure" +" all settings/configuration were done properly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst-1 +msgid "Delivery order with matching source and child locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:176 +msgid "" +"Finally, on the warehouse delivery form, under the :guilabel:`Detailed " +"Operations` tab, confirm that the *Locations* values under the " +":guilabel:`From` column for each product matches to the *child locations* " +"that are tied to the virtual *parent location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:181 +msgid "" +"To view which *Locations* the products are coming from on the drop-down " +"menus, click the :guilabel:`internal link (arrow)` icon to expand the " +"*Location* information. If needed, it can be changed from here (granted " +"there is quantity on hand for the product in that location)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:185 +msgid "" +"Once everything has been properly set, click :guilabel:`Validate` and then " +":guilabel:`Apply` to validate the delivery. Then, navigate back to the sales" +" order form (via the breadcrumbs), and click :guilabel:`Create Invoice` to " +"invoice for the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:190 +msgid "" +"To use a virtual *parent* location as the default warehouse for sales " +"orders, each salesperson can have the virtual warehouse assigned to them " +"from the drop-down menu next to :guilabel:`Default Warehouse` on their " +"employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst-1 +msgid "Default warehouse location on employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:5 +msgid "Routes and Pull/Push Rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:7 +msgid "" +"In inventory management, the supply chain strategy determines when products " +"should be purchased/manufactured, delivered to distribution centers, and " +"made available to the retail channel." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:11 +msgid "" +"In Odoo, a product's supply chain strategy can be configured using *Routes*," +" which feature *Pull and Push Rules*. Once everything is properly " +"configured, the Inventory app can automatically generate transfers following" +" the configured push/pull rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:16 +msgid "Inside the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:18 +msgid "" +"In a generic warehouse, there are receiving docks, a quality control area, " +"storage locations, picking and packing areas, and shipping docks. All " +"products go through all these locations. As the products move through the " +"locations, each location triggers the products' specified route and rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of a generic warehouse with stock and quality control area." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:27 +msgid "" +"In this example, vendor trucks unload pallets of ordered products at the " +"receiving docks. Operators then scan the products in the receiving area. " +"Depending on the product's route and rules, some of these products are sent " +"to a quality control area (for example, products that are components used in" +" the manufacturing process), while others are directly stored in their " +"respective locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of a generic push to rule when receiving products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:36 +msgid "" +"Here is an example of a fulfillment route. In the morning, items are picked " +"for all the orders that need to be prepared during the day. These items are " +"picked from storage locations and moved to the picking area, close to where " +"the orders are packed. Then, the orders are packed in their respective boxes" +" and conveyors bring them close to the shipping docks, ready to be delivered" +" to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of a generic pull from rule when preparing deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:47 +msgid "Pull rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:49 +msgid "" +"With *Pull Rules*, a demand for some products triggers procurements, while " +"*Push Rules* are triggered by products arriving in a specific location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:52 +msgid "" +"Pull Rules are used to fulfill a sales order. Odoo generates a need at the " +"*Customer Location* for each product in the order. Because pull rules are " +"triggered by a need, Odoo looks for a pull rule defined on the *Customer " +"Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:56 +msgid "" +"In this case, a \"delivery order\" pull rule that transfers products from " +"the *Shipping Area* to the *Customer Location* is found, and a transfer " +"between the two locations is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:59 +msgid "" +"Then, Odoo finds another pull rule that tries to fulfill the need for the " +"*Shipping Area*: the \"packing\" rule that transfers products from the " +"*Packing Area* to the *Shipping Area*. Finally, other pull rules are " +"triggered until a transfer between the *Stock* and the *Picking Area* is " +"created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:65 +msgid "" +"All these product transfers are automatically generated by Odoo based on the" +" pull rules, starting from the end (the customer location) and going " +"backward (the stock warehouse). While working, the operator processes these " +"transfers in the opposite order: first the picking, then the packing, and " +"finally the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:71 +msgid "Push rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:73 +msgid "" +"On the other hand, *Push Rules* are much easier to understand. Instead of " +"generating documents based on needs, they are triggered in real time when " +"products arrive in a specific location. Push rules basically say: \"when a " +"product arrives at a specific location, move it to another location.\"" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:77 +msgid "" +"An example of a push rule would be: when a product arrives in the *Receipt " +"Area*, move it to the *Storage Location*. As different push rules can be " +"applied to different products, the user can assign different storage " +"locations for different products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:81 +msgid "" +"Another push rule could be: when products arrive at a location, move them to" +" the *Quality Control Area*. Then, once the quality check is done, move them" +" to their *Storage Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:85 +msgid "" +"Push rules can only be triggered if there are no pull rules that have " +"already generated the product transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:89 +msgid "" +"Sets of push/pull rules like those are called *Routes*. The grouping on the " +"rule decides if products are grouped in the same transfer or not. For " +"example, during the picking operation, all orders and their products are " +"grouped in one transfer, whereas the packing operation respects the grouping" +" per customer order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:97 +msgid "Use routes and rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:99 +msgid "" +"Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you " +"manage advanced route configurations such as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:102 +msgid "Manage product manufacturing chains." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:103 +msgid "Manage default locations per product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:104 +msgid "" +"Define routes within the stock warehouse according to business needs, such " +"as quality control, after-sales services, or supplier returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:106 +msgid "" +"Help rental management by generating automated return moves for rented " +"products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:108 +msgid "" +"To configure a route for a product, first, open the :guilabel:`Inventory` " +"application and go to :menuselection:`Configuration --> Settings`. Then, in " +"the :guilabel:`Warehouse` section, enable the :guilabel:`Multi-Step Routes` " +"feature and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "Activate the Multi-Step Routes feature in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:117 +msgid "" +"The :guilabel:`Storage Locations` feature is automatically activated with " +"the :guilabel:`Multi-Step Routes` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:120 +msgid "" +"Once this first step is completed, the user can use pre-configured routes " +"that come with Odoo, or they can create custom routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:124 +msgid "Pre-configured routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:126 +msgid "" +"To access Odoo's pre-configured routes, go to :menuselection:`Inventory --> " +"Configuration --> Warehouses`. Then, open a warehouse form. In the " +":guilabel:`Warehouse Configuration` tab, the user can view the warehouse's " +"pre-configured routes for :guilabel:`Incoming Shipments` and " +":guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "A preconfigured warehouse in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:135 +msgid "" +"Some more advanced routes, such as pick-pack-ship, are also available. The " +"user can select the route that best fits their business needs. Once the " +":guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` routes are" +" set, head to :menuselection:`Inventory --> Configuration --> Routes` to see" +" the specific routes that Odoo generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of all the preconfigured routes Odoo offers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:144 +msgid "" +"On the :guilabel:`Routes` page, click on a route to open the route form. In " +"the route form, the user can view which places the route is " +":guilabel:`Applicable On`. The user can also set the route to only apply on " +"a specific :guilabel:`Company`. This is useful for multi-company " +"environments; for example, a user can have a company and warehouse in " +"Country A and a second company and warehouse in Country B." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "" +"View of a route example applicable on product categories and warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:154 +msgid "" +"At the bottom of the route form, the user can view the specific " +":guilabel:`Rules` for the route. Each :guilabel:`Rule` has an " +":guilabel:`Action`, a :guilabel:`Source Location`, and a " +":guilabel:`Destination Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "An example of rules with push & pull actions in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:163 +msgid "Custom Routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:165 +msgid "" +"To create a custom route, go to :menuselection:`Inventory --> Configuration " +"--> Routes`, and click on :guilabel:`Create`. Next, choose the places where " +"this route can be selected. A route can be applicable on a combination of " +"places." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of a pick-pack-ship route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:173 +msgid "" +"Each place has a different behavior, so it is important to tick only the " +"useful ones and adapt each route accordingly. Then, configure the " +":guilabel:`Rules` of the route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:176 +msgid "" +"If the route is applicable on a product category, the route still needs to " +"be manually set on the product category form by going to " +":menuselection:`Inventory --> Configuration --> Product Categories`. Then, " +"select the product category and open the form. Next, click :guilabel:`Edit` " +"and under the :guilabel:`Logistics` section, set the :guilabel:`Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:181 +msgid "" +"When applying the route on a product category, all the rules configured in " +"the route are applied to **every** product in the category. This can be " +"helpful if the business uses the dropshipping process for all the products " +"from the same category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of a route applied to the \"all\" product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:189 +msgid "" +"The same behavior applies to the warehouses. If the route can apply to " +":guilabel:`Warehouses`, all the transfers occurring inside the chosen " +"warehouse that meet the conditions of the route's rules will then follow " +"that route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "" +"View of the warehouse drop-down menu when selecting applicable on warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:197 +msgid "" +"If the route is applicable on :guilabel:`Sales Order Lines`, it is more or " +"less the opposite. The route must be manually chosen when creating a " +"quotation. This is useful if some products go through different routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:201 +msgid "" +"Remember to toggle the visibility of the :guilabel:`Route` column on the " +"quotation/sales order. Then, the route can be chosen on each line of the " +"quotation/sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of the menu allowing to add new lines to sales orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:208 +msgid "" +"Finally, there are routes that can be applied to products. Those work more " +"or less like the product categories: once selected, the route must be " +"manually set on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:211 +msgid "" +"To set a route on a product, go to :menuselection:`Inventory --> Products " +"--> Products` and select the desired product. Then, go to the " +":guilabel:`Inventory` tab and under the :guilabel:`Operations` section, " +"select the :guilabel:`Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of a product form, where the route must be selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:220 +msgid "Rules must be set on the route in order for the route to work." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:223 +msgid "Rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:225 +msgid "" +"The rules are defined on the route form. First, go to " +":menuselection:`Inventory --> Configuration --> Routes` and open the desired" +" route form. Next, click :guilabel:`Edit` and in the :guilabel:`Rules` " +"section, click on :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of the rules menu, where it is possible to add new rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:233 +msgid "" +"The available rules trigger various actions. If Odoo offers *Push* and " +"*Pull* rules, others are also available. Each rule has an " +":guilabel:`Action`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:236 +msgid "" +":guilabel:`Pull From`: this rule is triggered by a need for the product in a" +" specific location. The need can come from a sales order being validated or " +"from a manufacturing order requiring a specific component. When the need " +"appears in the destination location, Odoo generates a picking to fulfill " +"this need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:240 +msgid "" +":guilabel:`Push To`: this rule is triggered by the arrival of some products " +"in the defined source location. In the case of the user moving products to " +"the source location, Odoo generates a picking to move those products to the " +"destination location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:243 +msgid "" +":guilabel:`Pull & Push`: this rule allows the generation of pickings in the " +"two situations explained above. This means that when products are required " +"at a specific location, a transfer is created from the previous location to " +"fulfill that need. This creates a need in the previous location and a rule " +"is triggered to fulfill it. Once the second need is fulfilled, the products " +"are pushed to the destination location and all the needs are fulfilled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:248 +msgid "" +":guilabel:`Buy`: when products are needed at the destination location, a " +"request for quotation is created to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:250 +msgid "" +":guilabel:`Manufacture`: when products are needed in the source location, a " +"manufacturing order is created to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "" +"Overview of a \"Pull From\" rule that creates a transfer between the stock and the packing\n" +"zone." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:258 +msgid "" +"The :guilabel:`Operation Type` must also be defined on the rule. This " +"defines which kind of picking is created from the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:261 +msgid "" +"If the rule's :guilabel:`Action` is set to :guilabel:`Pull From` or " +":guilabel:`Pull & Push`, a :guilabel:`Supply Method` must be set. The " +":guilabel:`Supply Method` defines what happens at the source location:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:265 +msgid "" +":guilabel:`Take From Stock`: the products are taken from the available stock" +" of the source location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:267 +msgid "" +":guilabel:`Trigger Another Rule`: the system tries to find a stock rule to " +"bring the products to the source location. The available stock is ignored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:269 +msgid "" +":guilabel:`Take From Stock, if Unavailable, Trigger Another Rule`: the " +"products are taken from the available stock of the source location. If there" +" is no stock available, the system tries to find a rule to bring the " +"products to the source location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:273 +msgid "" +"In the *Scheduling* section, you can determine how Odoo behaves when one of " +"the chain's pickings is rescheduled. In case you decide to **Propagate " +"Rescheduling**, the next move is also to be rescheduled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:277 +msgid "" +"If you prefer having the choice to reschedule the next move, you can decide " +"to receive an alert in the form of a *next activity*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:281 +msgid "Sample full route flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:283 +msgid "" +"In this example, let's use a custom *Pick - Pack - Ship* route to try a full" +" flow with an advanced custom route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:286 +msgid "" +"First, a quick look at the route's rules and their supply methods. There are" +" three rules, all :guilabel:`Pull From` rules. The :guilabel:`Supply " +"Methods` for each rule are the following:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:289 +msgid "" +":guilabel:`Take From Stock`: When products are needed in the " +":guilabel:`WH/Packing Zone`, *picks* (internal transfers from " +":guilabel:`WH/Stock` to :guilabel:`WH/Packing Zone`) are created from " +":guilabel:`WH/Stock` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:292 +msgid "" +":guilabel:`Trigger Another Rule`: When products are needed in " +":guilabel:`WH/Output`, *packs* (internal transfers from " +":guilabel:`WH/Packing Zone` to :guilabel:`WH/Output`) are created from " +":guilabel:`WH/Packing Zone` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:295 +msgid "" +":guilabel:`Trigger Another Rule`: When products are needed in " +":guilabel:`Partner Locations/Customers`, *delivery orders* are created from " +":guilabel:`WH/Output` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "Overview of all the transfers created by the pick - pack - ship route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:303 +msgid "" +"This means that, when a customer orders products that have a *pick - pack - " +"ship* route set on it, a delivery order is created to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of the operations created by a pull from transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:311 +msgid "" +"If the source document for multiple tranfers is the same sales order, the " +"status is not the same. The status will be :guilabel:`Waiting Another " +"Operation` if the previous transfer in the list is not done yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "" +"View of the transfers' various statuses at the beginning of the process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:319 +msgid "" +"To prepare the delivery order, packed products are needed at the output " +"area, so an internal transfer is requested from the packing zone." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "" +"View of the detailed operations for a transfer between the packing and " +"output zones." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:326 +msgid "" +"Obviously, the packing zone needs products ready to be packed. So, an " +"internal transfer is requested to the stock and employees can gather the " +"required products from the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "" +"View of the detailed operations for a transfer between the stock and packing" +" zones." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:333 +msgid "" +"As explained in the introduction of the documentation, the last step in the " +"process (for this route, the delivery order) is the first to be triggered, " +"which then triggers other rules until we reach the first step in the process" +" (here, the internal transfer from the stock to the packing area). Now, " +"everything is ready to be processed so the customer can get the ordered " +"items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst:338 +msgid "" +"In this example, the product is delivered to the customer when all the rules" +" have been triggered and the transfers are done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use_routes.rst-1 +msgid "View of the transfers' statuses when the route is completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies.rst:5 +msgid "Putaway & Removal Strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:3 +msgid "Putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:6 +msgid "What is a Putaway Rule?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:8 +msgid "" +"A good warehouse implementation makes sure that products automatically move " +"to their appropriate destination location. To make that process easier, Odoo" +" uses *Putaway Rules*. Putaway is the process of taking products from the " +"received shipments and putting them into the appropriate location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:13 +msgid "" +"If, for example, a warehouse contains volatile substances, it is important " +"to make sure that certain products are not stored close to each other " +"because of a potential chemical reaction. That's where putaway rules " +"intervene, to avoid storing products wrongly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:20 +msgid "" +"In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> " +"Settings` and activate the :guilabel:`Multi-Step Routes` feature. By doing " +"so, the :guilabel:`Storage Locations` feature is also automatically " +"activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst-1 +msgid "Activate Multi-Step Routes in Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:29 +msgid "Setting up a putaway rule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:31 +msgid "" +"In some cases, like for a retail shop storing fruits and vegetables, " +"products should be stored in different locations depending on several " +"factors like frequency, size, product category, specific environment needs, " +"and so on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:35 +msgid "" +"In this example, suppose there is one warehouse location, **WH/Stock**, with" +" the following sub-locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:38 +msgid "WH/Stock/Pallets" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:40 +msgid "WH/Stock/Pallets/PAL1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:41 +msgid "WH/Stock/Pallets/PAL2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:42 +msgid "WH/Stock/Pallets/PAL3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:44 +msgid "WH/Stock/Shelf 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:46 +msgid "WH/Stock/Shelf 2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:48 +msgid "WH/Stock/Shelf 2/Small Refrigerator" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:50 +msgid "WH/Stock/Shelf 3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:52 +msgid "" +"Manage those locations with putaway rules. To create a putaway rule, open " +"the :guilabel:`Inventory` app and go to :menuselection:`Configuration --> " +"Putaway Rules`. Then, click on :guilabel:`Create` and configure a putaway " +"rule that indicated the main location the product will enter before being " +"redirected to the right storage location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:58 +msgid "" +"The putaway rules can be defined either per product/product category and/or " +"package type (the :guilabel:`Packages` setting must be enabled for that). " +"Putaway rules are read sequentially until a match is found." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:62 +msgid "Take the following example:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:64 +msgid "" +"If water (category All/drinks) is received, whatever the package, it will be" +" redirected to WH/Stock/Shelf 2/Small Refrigerator." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:66 +msgid "" +"If orange juice cans, packaged in boxes, are received, they will be " +"redirected to WH/Stock/Shelf 2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:68 +msgid "" +"If water or apple juice bottles, packaged in boxes, are received, they will " +"be redirected to WH/Stock/Shelf 3." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:70 +msgid "" +"If a pallet of lemonade cans are receieved, it will be redirected to " +"WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst-1 +msgid "Some examples of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:77 +msgid "Using Storage Categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:79 +msgid "" +"A *Storage Category* is an extra location attribute. Storage categories " +"allow the user to define the quantity of products that can be stored in the " +"location and how the location will be selected with putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:86 +msgid "" +"In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> " +"Settings` and activate the :guilabel:`Storage Categories` feature. By doing " +"so, the :guilabel:`Storage Locations` feature is also automatically " +"activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:91 +msgid "Create a Storage Category" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:93 +msgid "" +"To create a storage category, go to :menuselection:`Inventory --> " +"Configuration --> Storage Categories` and click :guilabel:`Create`. Then, " +"click :guilabel:`Save` and click :guilabel:`Storage Categories` or go to " +":menuselection:`Configuration --> Storage Categories` to create a new " +"storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst-1 +msgid "" +"Create Storage Categories inside Odoo Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:102 +msgid "" +"First, click :guilabel:`Create` and type a name for the storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:104 +msgid "" +"Then, there are options to limit the capacity by weight, by product, or by " +"package type. The :guilabel:`Allow New Product` field defines when the " +"location is considered available to store a product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:108 +msgid "" +":guilabel:`If location is empty`: a product can be added there only if the " +"location is empty." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:109 +msgid "" +":guilabel:`If products are the same`: a product can be added there only if " +"the same product is already there." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:111 +msgid "" +":guilabel:`Allow mixed products`: several different products can be stored " +"in this location at the same time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:114 +msgid "" +"Once the storage category settings are saved, the storage category can be " +"linked to a location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst-1 +msgid "" +"When a Storage Category is created, it can be linked to a warehouse " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:121 +msgid "Storage categories in putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:123 +msgid "" +"To continue the example from above, apply the \"High Frequency Pallets\" on " +"the PAL1 and PAL2 locations and rework the putaway rules as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:126 +msgid "Assume one pallet of lemonade cans is received:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:128 +msgid "" +"If PAL1 and PAL2 are empty, the pallet will be redirected to " +"WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:129 +msgid "" +"If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:130 +msgid "" +"If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst-1 +msgid "Storage Categories used in a variety of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:3 +msgid "What is a Removal Strategy (FIFO, LIFO, FEFO, Closest location)?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:5 +msgid "" +"Usually, *Removal Strategies* are defined in picking operations to select " +"the best products, optimize the distance for the worker, for quality control" +" purposes, or to first move products with the closest expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:9 +msgid "" +"When a product movement needs to be done, Odoo finds available products that" +" can be assigned to the transfer. The way Odoo assigns these products " +"depends on the *Removal Strategy* defined in the *Product Category* or on " +"the *Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:14 +msgid "What happens inside the warehouse?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:16 +msgid "" +"Imagine a generic warehouse plan, with receiving docks and areas, storage " +"locations, picking and packing areas, and shipping docks. All products go " +"through all these locations, but some rules, such as removal strategies, can" +" have an effect on which products are taken for the pickings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "Empty stock waiting for deliveries at the docks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:24 +msgid "" +"Here, vendor trucks unload pallets of goods at the docks. Then, operators " +"scan the products in the receiving area with the reception date and, if the " +"product has an expiration date, the expiration date. After that, products " +"are stored in their respective locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "Products entering stock via the receiving area." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:32 +msgid "" +"Next, several orders for the same product are made, but in this example, the" +" goods weren't received on the same day and they don't have the same " +"expiration date. In that situation, logically, sending those with the " +"closest date first is preferred. Depending on the chosen removal strategy, " +"Odoo generates a transfer with the products that fit the settings the best." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "" +":alt: Products being packed at the packing area for delivery, taking expiration dates into\n" +"account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:43 +msgid "" +"To pick for delivery, the product's lot/serial number can be found on the " +"transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:46 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:49 +msgid "First In, First Out (FIFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:51 +msgid "" +"When using a *First In, First Out* (FIFO) strategy, a demand for some " +"products triggers a removal rule, which requests a transfer for the " +"lot/serial number that has entered the stock first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:54 +msgid "" +"For example, imagine there are three lots of nails in the warehouse. Those " +"three have the following lot numbers: :guilabel:`00001`, :guilabel:`00002`, " +":guilabel:`00003`, each with five boxes of nails in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:58 +msgid "" +":guilabel:`00001` entered the stock on the 23rd of May, :guilabel:`00002` on" +" the 25th of May, and :guilabel:`00003` on the 1st of June. A customer " +"orders six boxes on the 11th of June. With the :abbr:`FIFO (First In, First " +"Out)` removal strategy selected, a transfer is requested for the five boxes " +"of :guilabel:`00001` and one of the boxes in :guilabel:`00002`, because " +":guilabel:`00001` entered the stock before the others. The box from " +":guilabel:`00002` is taken next because it has the oldest reception date " +"after :guilabel:`00001`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:65 +msgid "" +"So, for every order of a product with the :abbr:`FIFO (First In, First Out)`" +" strategy selected, Odoo requests a transfer for the products that have been" +" in the stock for the longest period." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:69 +msgid "Last In, First Out (LIFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:71 +msgid "" +"Similar to :abbr:`FIFO (First In, First Out)`, the *Last In, First Out* " +"(LIFO) strategy moves products based on the date they entered the stock. " +"Here, a demand for some products triggers a removal rule that requests a " +"transfer for the lot/serial number that has entered the stock most recently." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:76 +msgid "" +"For example, imagine there are three lots of screws in the warehouse. Those " +"three have the following numbers: :guilabel:`10001`, :guilabel:`10002`, and " +":guilabel:`10003`, each with 10 boxes of screws in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:80 +msgid "" +":guilabel:`10001` entered the stock on the 1st of June, :guilabel:`10002` on" +" the 3rd of June, and :guilabel:`10003` on the 6th of June. A customer " +"orders seven boxes on the 8th of June. With the :abbr:`LIFO (Last In, First " +"Out)` removal strategy selected, a transfer is requested for seven boxes of " +":guilabel:`10003` because that lot is the last one to have entered the " +"stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:85 +msgid "" +"Basically, for every order of a product with the :abbr:`LIFO (Last In, First" +" Out)` strategy used, a transfer for the last lot to have entered the stock " +"is requested." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:89 +msgid "" +"The :abbr:`LIFO (Last In, First Out)` strategy is banned in many countries " +"and can lead to only having old or obsolete products in the stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:93 +msgid "First Expire, First Out (FEFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:95 +msgid "" +"The *First Expired, First Out* (FEFO) strategy is a bit different from the " +"other two removal strategies. For :abbr:`FEFO (First Expired, First Out)`, " +"the expiration date is important, not the date the product entered the " +"stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:99 +msgid "" +"For example, imagine there are three lots of six-egg boxes (in this specific" +" case, don't forget to use :doc:`units of measure " +"<../../management/products/uom>`). Those three lots have the following " +"numbers: :guilabel:`20001`, :guilabel:`20002`, and :guilabel:`20003`, each " +"with five boxes in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:103 +msgid "" +":guilabel:`20001` entered the stock on the 1st of July and expires on the " +"15th of July, :guilabel:`20002` entered on the 2nd and expires on the 14th " +"of July, and :guilabel:`20003` entered on the 4th and expires on the 21st of" +" July. A customer orders six boxes on the 5th of July. With the :abbr:`FEFO " +"(First Expired, First Out)` strategy selected, a transfer is requested for " +"the five boxes of :guilabel:`20002` and one from :guilabel:`20001`. The " +"transfer for all the boxes in lot :guilabel:`20002` is because they have the" +" closest expiration date. The transfer also requests one box from " +":guilabel:`20001` because has the next closest expiration date after lot " +":guilabel:`20002`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:112 +msgid "" +"Basically, for every sales order of a product with the :abbr:`FEFO (First " +"Expired, First Out)` strategy, a transfer is requested for the product that " +"has the nearest expiration date from the order date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:117 +msgid "Closest Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:119 +msgid "" +"The *Closest Location* strategy is completely different from the other " +"removal strategies. It is not related to the date of entry in the warehouse," +" but rather the location of the product. It is commonly used for products " +"that do not deteriorate with time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:123 +msgid "" +"The aim is to avoid making the warehouse worker take a long journey to the " +"bottom of the stock when the product is also located at a near location. " +"This method is only available if the :guilabel:`Storage Locations` setting " +"is on. The closest location is actually the one that comes first in the " +"alphabetic order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:129 +msgid "Use removal strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:131 +msgid "" +"To differentiate some units from others, the units need to be tracked, " +"either by *lot* or by *serial number*. To do so, go to " +":menuselection:`Inventory --> Configuration --> Settings`. Then, activate " +"the :guilabel:`Storage Location`, :guilabel:`Multi-Step Routes`, and " +":guilabel:`Lots & Serial Numbers` settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "Features to enable in order to properly use removal strategies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:141 +msgid "" +"To work with the :abbr:`FEFO (First Expired, First Out)` strategy, also " +"activate the :guilabel:`Expiration Dates` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:144 +msgid "" +"Next, go to :menuselection:`Inventory --> Configuration --> Product " +"Categories` to define the removal strategy on a product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "Force removal strategy set up as first in first out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:152 +msgid "FIFO (First In, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:154 +msgid "" +"As explained, a :abbr:`FIFO (First In, First Out)` removal strategy implies " +"that products stocked first move out first. Companies should use this method" +" if they are selling products with short demand cycles, such as clothes, and" +" to ensure they are not stuck with outdated styles in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:158 +msgid "" +"In this example, there are three lots of white shirts. The shirts are from " +"the :guilabel:`All/Clothes` category, where *FIFO* is set as the removal " +"strategy. In the stock location (:guilabel:`WH/Stock`), the user can find " +"the three lots available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "View of the white shirt lots inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:166 +msgid "" +"Lot :guilabel:`000001` contains five shirts, :guilabel:`000002` contains " +"three shirts, and :guilabel:`000003` contains two shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:169 +msgid "" +"As seen above, :guilabel:`000001` entered the stock first. Now, create a " +"sales order of six white shirts to check that those products from lot " +":guilabel:`000001` are the first ones to move out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:172 +msgid "" +"On the delivery order linked to the picking, the oldest lot numbers should " +"have been reserved thanks to the :abbr:`FIFO (First In, First Out)` " +"strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "Two lots being reserved for a sales order with the FIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:180 +msgid "LIFO (Last In, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:182 +msgid "" +"With a *LIFO* strategy, that's quite the opposite. In fact, the products " +"that are received last move out first. :abbr:`LIFO (Last In, First Out)` is " +"mostly used for products without a shelf life." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:185 +msgid "" +"In this example, let's use the white shirts again to test the :abbr:`LIFO " +"(Last In, First Out)` strategy. First, open the product category via " +":menuselection:`Inventory --> Configuration --> Product Categories` and " +"change the removal strategy to :abbr:`LIFO (Last In, First Out)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "Last in first out strategy set up as forced removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:193 +msgid "" +"Then, create a sales order for four white shirts and check that the reserved" +" products are from lots :guilabel:`000003` and :guilabel:`000002`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "Two lots being reserved for sale with the LIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:201 +msgid "" +"Don't forget that the :abbr:`LIFO (Last In, First Out)` strategy is banned " +"in many countries!" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:204 +msgid "FEFO (First Expired, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:206 +msgid "" +"With the :abbr:`FEFO (First Expired, First Out)` removal strategy, the way " +"products are picked is not based on the reception date. In this particular " +"case, they are dispatched according to their expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211 +msgid "" +"For have more information about expiration dates, please have a look at " +":doc:`the related doc " +"<../../management/lots_serial_numbers/expiration_dates>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:214 +msgid "" +"By activating the :guilabel:`Expiration Dates` feature, it becomes possible " +"to define different expiration dates on the serial/lot numbers that will be " +"used in :abbr:`FEFO (First Expired, First Out)`. These expiration dates can " +"be set by going to :menuselection:`Inventory --> Products --> Lots/Serial " +"Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "View of the removal date for 0000001." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:223 +msgid "" +"Lots are picked based on their removal date, from earliest to latest. Lots " +"without a removal date defined are picked after lots with removal dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:227 +msgid "" +"Other dates are for informational and reporting purposes only. If not " +"removed from the stock, lots that are past the expiration dates may still be" +" picked for delivery orders!" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:230 +msgid "" +"To use the :abbr:`FEFO (First Expired, First Out)` strategy, go to " +":menuselection:`Inventory --> Configuration --> Product Categories` and set " +":abbr:`FEFO (First Expired, First Out)` in the :guilabel:`Force Removal " +"Strategy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "View of the FEFO strategy being set up as forced removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:238 +msgid "" +"For this particular case, the stock has hand cream. There are three lots of " +"them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 +msgid "**Lot / Serial No**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 +msgid "**Product**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 +msgid "**Expiration Date**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 +msgid "0000001" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 +msgid "Hand Cream" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 +msgid "09/30/2019" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 +msgid "0000002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 +msgid "11/30/2019" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 +msgid "0000003" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 +msgid "10/31/2019" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:250 +msgid "" +"When a sales order for 25 units of Hand Cream is created, Odoo automatically" +" reserves the lots with the closest expiration date, :guilabel:`0000001` and" +" :guilabel:`0000003`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst-1 +msgid "Two hand cream lots reserved for sell with the FEFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping.rst:5 +msgid "Shipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation.rst:5 +msgid "Shipping Operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:3 +msgid "How to cancel a shipping request to a shipper?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo will be linked with the transportation company tracking system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:12 +msgid "" +"It will allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:15 +msgid "You can easily cancel the request made to the carrier system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:18 +msgid "How to cancel a shipping request?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:20 +msgid "" +"If the delivery order is not **Validated**, then the request hasn't been " +"made. You can choose to cancel the delivery or to change the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:24 +msgid "" +"If you have clicked on **Validate**, the request has been made and you " +"should have received the tracking number and the label. You can still cancel" +" the request. Simply click on the **Cancel** button next to the **Carrier " +"Tracking Ref**:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:32 +msgid "You will now see that the shipment has been cancelled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:37 +msgid "You can now change the carrier if you wish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:40 +msgid "How to send a shipping request after cancelling one?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:42 +msgid "" +"After cancelling the shipping request, you can change the carrier you want " +"to use. Confirm it by clicking on the **Send to shipper** button. You will " +"get a new tracking number and a new label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:83 +msgid ":doc:`invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/cancel.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:116 +msgid ":doc:`multipack`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:3 +msgid "Use dropshipping to ship directly from suppliers to customers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:5 +msgid "" +"Dropshipping is an order fulfillment strategy that allows sellers to have " +"items shipped directly from suppliers to customers. Normally, a seller " +"purchases a product from a supplier, stores it in their inventory, and ships" +" it to the end customer once an order is placed. With dropshipping, the " +"supplier is responsible for storing and shipping the item. This benefits the" +" seller by reducing inventory costs, including the price of operating " +"warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:12 +msgid "Configure products to be dropshipped" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:14 +msgid "" +"To use dropshipping as a fulfillment strategy, navigate to the " +":menuselection:`Purchase` app and select :menuselection:`Configuration --> " +"Settings`. Under the :guilabel:`Logistics` heading, click the " +":guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:18 +msgid "" +"Next, go to the :menuselection:`Sales` app, click :menuselection:`Products " +"--> Products` and choose an existing product or select :guilabel:`Create` to" +" configure a new one. On the :guilabel:`Product` page, make sure that the " +":guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are " +"enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst-1 +msgid "" +"Enable the \"Can be Sold\" and \"Can be Purchased\" checkboxes on the " +"product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:27 +msgid "" +"Click on the :guilabel:`Purchase` tab and specify a vendor and the price " +"that they sell the product for. Multiple vendors can be added, but the " +"vendor at the top of the list will be the one automatically selected for " +"purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst-1 +msgid "The product form with a vendor specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:35 +msgid "" +"Finally, select the :guilabel:`Inventory` tab and enable the " +":guilabel:`Dropship` checkbox in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst-1 +msgid "Enable the Dropship option in the product inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:43 +msgid "Fulfill orders using dropshipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:45 +msgid "" +"When a customer completes an online purchase for a dropshipped product, a " +"sales order will be automatically created with an associated request for " +"quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. Sales " +"orders can be viewed in the :menuselection:`Sales` app by selecting " +":menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart " +"button at the top right of a sales order to view the associated :abbr:`RFQ " +"(Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:52 +msgid "" +"Dropship sales orders can also be created manually through the " +":menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders " +"--> Create` and adding a product configured for dropshipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst-1 +msgid "" +"A dropship sales order with the Purchase smart button in the top right " +"corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:60 +msgid "" +"Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a " +"purchase order and a dropship receipt is created and linked to it. The " +"receipt can be viewed by clicking the :guilabel:`Receipt` smart button in " +"the top right corner of the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst-1 +msgid "" +"A dropship purchase order with the Receipt smart button in the top right " +"corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:68 +msgid "" +"The dropship receipt will list the supplier in the :guilabel:`Receive From` " +"section and the customer in the :guilabel:`Destination Location` section. " +"Upon delivery of the product to the customer, click on the " +":guilabel:`Validate` button at the top left of the dropship receipt to " +"confirm the delivered quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst-1 +msgid "Validate the dropship receipt after delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst:77 +msgid "" +"To view all dropship orders, simply navigate to the " +":menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal" +" :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/dropshipping.rst-1 +msgid "" +"Click the green button on the Dropship card to view all dropship orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:3 +msgid "How to invoice the shipping cost to the customer?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:8 +msgid "There are two ways to invoice the shipping costs:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:10 +msgid "Agree with the customer over a cost and seal it down in the sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:13 +msgid "Invoice the real cost of the shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:18 +msgid "" +"To configure the price of your delivery methods, go to the **Inventory** " +"app, click on :menuselection:`Configuration --> Delivery --> Delivery " +"Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:21 +msgid "" +"You can manually set a price for the shipping: It can be fixed or based on " +"rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:24 +msgid "" +"Or you can use the transportation company computation system. Read the " +"document :doc:`../setup/third_party_shipper`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:28 +msgid "How to invoice the shipping costs to the customer?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:31 +msgid "Invoice the price set on the sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:55 +msgid "" +"On your sale order, choose the carrier that will be used. Click on " +"**Delivery Method** to choose the right one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:36 +msgid "" +"The price is computed when you **save** the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:42 +msgid "" +"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. It may vary from the real price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:46 +msgid "" +"When you create the invoice, it will take the price set on the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:53 +msgid "Invoice the real shipping costs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:61 +msgid "" +"The price is computed when you **save** the sale order. Confirm the sale " +"order and proceed to deliver the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:64 +msgid "" +"The real shipping cost is computed when the delivery order is validated, you" +" can see the real cost in the chatter of the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:70 +msgid "" +"Go back to the sale order, the real cost is now added to the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:76 +msgid "" +"When you create the invoice, it will take the price computed by the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:83 +msgid "" +"If you split the delivery and make several ones, each delivery order will " +"add a line to the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:87 +msgid ":doc:`../setup/third_party_shipper`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:84 +msgid ":doc:`labels`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:3 +msgid "Change shipping label size" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:8 +msgid "" +"In Odoo, there are a variety of different types of shipping labels that can " +"be selected for delivery orders. Depending on the types of shipping packages" +" used, different label sizes may be more appropriate, and can be configured " +"to fit the package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:15 +msgid "" +"In the :menuselection:`Inventory` module, go to " +":menuselection:`Configuration --> Delivery --> Shipping Methods.` Choose a " +"delivery method and click :guilabel:`Edit`. For the following example, " +"*FedEx International* will be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst-1 +msgid "Different shipping methods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:23 +msgid "" +"In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose " +"one of the label types available. The availability will vary depending on " +"the carrier. :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst-1 +msgid "Select a label type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:30 +msgid "" +"When a sales order with the corresponding shipping company is confirmed and " +"a delivery order is validated, the shipping label will be automatically " +"created as a PDF and appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:37 +msgid "" +"In the :menuselection:`Sales` application, click :guilabel:`Create` and " +"select an international customer. Click :guilabel:`Add A Product` and select" +" an item. Click :guilabel:`Add Shipping`, select a shipping method, then " +"click :guilabel:`Get Rate`, and finally, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst-1 +msgid "Add a shipping method and rate to a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:45 +msgid "" +"Once the quotation is confirmed by clicking :guilabel:`Confirm`, a " +":guilabel:`Delivery` smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst-1 +msgid "Delivery order smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:52 +msgid "" +"Once the delivery order is validated by clicking :guilabel:`Validate` in the" +" delivery order, the shipping documents appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst-1 +msgid "Shipping PDF documents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:60 +msgid "Example labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:62 +msgid "" +"The default :guilabel:`Label Type` is :guilabel:`Paper Letter`. An example " +"of a FedEx letter sized label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst-1 +msgid "Full page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:69 +msgid "For comparison, an example of a FedEx bottom-half label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst-1 +msgid "Half page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:85 +msgid "How to print shipping labels?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers " +"linked with the transportation company tracking system. It allows you to " +"manage the transport company, the real prices and the destination. And " +"finally, you will be able to print the shipping labels directly from Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:17 +msgid "Install the shipper company connector module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:20 +msgid "" +"In the **Inventory** module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:26 +msgid "Then click on **Apply**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:33 +msgid "Configure the delivery method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:35 +msgid "" +"To configure your delivery methods, go to the **Inventory** module, click on" +" :menuselection:`Configuration --> Delivery Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:35 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:41 +msgid "" +"In the **Pricing** tab, the name of the provider means that the delivery " +"will be handled and computed by the shipper system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:44 +msgid "The configuration of the shipper is split into two columns :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:46 +msgid "" +"The first one is linked to **your account** (develop key, password,...). For" +" more information, please refer to the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:62 +msgid "" +"The second column varies according to the **provider**. You can choose the " +"packaging type, the service type, the weight unit..." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:65 +msgid "Uncheck **Test Mode** when you are done with the testings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:77 +msgid "Company configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:79 +msgid "" +"In order to compute the right price, the provider needs your company " +"information. Be sure your address and phone number are correctly encoded." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:86 +msgid "" +"To check your information, go to the **Settings** application and click on " +"**General Settings**. Click on the first link **Configure your company " +"data**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:90 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:92 +msgid "" +"The shipper companies need the weight of your product, otherwise the price " +"computation cannot be done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:73 +msgid "" +"Go the **Sales** module, click on :menuselection:`Sales --> Products`. Open " +"the products you want to ship and set a weight on it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:80 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to do" +" the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:87 +msgid "" +"The delivery order created from the sale order will take the shipping " +"information from it, but you can change the carrier if you want to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:135 +msgid "" +"If you create a delivery transfer from the inventory module, you can add the" +" third party shipper in the additional info tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:96 +msgid "" +"Click on **Validate** to receive the tracking number and **the label(s)**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:151 +msgid "" +"The label to stick on your package is available in the history underneath :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:104 +msgid "Click on it to open the document and print it :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:110 +msgid "" +"If you are doing multi-packages shippings, most of the time, there will be " +"one label per package. Each label will appear in the delivery history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:3 +msgid "How to manage multiple packs for the same delivery order?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:8 +msgid "" +"By default, Odoo considers that your delivery is composed of one package. " +"But you can easily ship your deliveries with more than one package. It is " +"fully integrated with the third-party shippers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:15 +msgid "" +"To configure the use of packages, go to the menu :menuselection:`Inventory " +"--> Configuration --> Settings`. Locate the **Packages** section and tick " +"**Record packages used on packing: pallets, boxes,...**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:23 +msgid "Click on **Apply** when you are done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:26 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:107 +msgid "Sale process" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:29 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:110 +msgid "Sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:34 +msgid "Click on a **Delivery Method** to choose the right one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:40 +msgid "Multi-packages Delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:42 +msgid "" +"The delivery created from the sale order will take the shipping information " +"from it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:48 +msgid "From here, you can split your delivery into multiple packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:50 +msgid "" +"Choose the quantity you want to put in the first pack in the **Done** " +"column, then click on the link **Put in Pack**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:56 +msgid "It will automatically create a pack with the requested quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:58 +msgid "Do the same steps for the other pieces you want to pack in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:63 +msgid "Click on **Validate** when you are done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:66 +msgid "Multi-packages with a 3rd party-shipper" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:68 +msgid "" +"Once the delivery order is validated, you will receive the tracking number. " +"The **carrier Tracking ref** field will automatically be filled. Click on " +"the **Tracking** button to check your delivery on the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:76 +msgid "" +"The **labels** to stick on your packages are available in the history " +"underneath:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup.rst:5 +msgid "Shipping Setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:3 +msgid "How to setup a delivery method?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/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 "" + +#: ../../content/applications/inventory_and_mrp/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:20 +msgid "Install the inventory module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:29 +msgid "" +"If you want to integrate delivery methods in your e-commerce, you'll have to" +" install the **eCommerce Delivery** module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:39 +msgid "First set a name and a transporter company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/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 "" + +#: ../../content/applications/inventory_and_mrp/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 "" + +#: ../../content/applications/inventory_and_mrp/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 "" + +#: ../../content/applications/inventory_and_mrp/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 "" + +#: ../../content/applications/inventory_and_mrp/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:74 +msgid "Delivery process" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:130 +msgid "Delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:90 +msgid "You can add or change the delivery method on the delivery itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:95 +msgid "" +"On the delivery, check the **Carrier Information**. The carrier is the " +"chosen delivery method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:99 +msgid ":doc:`third_party_shipper`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:158 +msgid ":doc:`../operation/invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:3 +msgid "How to get DHL credentials for integration with Odoo?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:5 +msgid "In order to use the Odoo DHL API, you will need:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:7 +msgid "A DHL.com SiteID" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:9 +msgid "A DHL Password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:11 +msgid "A DHL Account Number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:15 +msgid "" +"Getting SiteID and password for countries other than United States (UK and " +"Rest of the world)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:17 +msgid "" +"You should contact DHL account manager and request integration for XML " +"Express API. The presales should provide you live credentials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:20 +msgid "Getting SiteID and Password for United States" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials.rst:22 +msgid "" +"You need to write to xmlrequests@dhl.com along with your full Account " +"details like account number, region, address, etc. to get API Access." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:3 +msgid "How to integrate a third party shipper?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo can be linked with the transportation company tracking system. It will " +"allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:19 +msgid "" +"In the inventory module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:38 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created. Most of the time, there will be **2** delivery methods for the same" +" provider: one for **international** shipping and the other for **domestic**" +" shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:43 +msgid "" +"You can create other methods with the same provider with other " +"configuration, for example the **Packaging Type**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:46 +msgid "" +"You can change the **Name** of the delivery method. This is the name that " +"will appear on your ecommerce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:49 +msgid "Flag **Shipping enabled** when you are ready to use it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:54 +msgid "" +"In the pricing tab, the name of the provider chosen under the **Price " +"computation** means that the pricing will be computed by the shipper system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:57 +msgid "The configuration of the shipper is split into two columns:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:59 +msgid "" +"The first one is linked to **your account** (developer key, password,...). " +"For more information, please refer to the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:67 +msgid "" +"Finally you can limit the delivery method to a few destinations. You can " +"limit it to some countries, states or even zip codes. This feature limits " +"the list of countries on your e-commerce. It is useful for the domestic " +"providers. For example, USPS US only delivers from the United States to the " +"United States." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:95 +msgid "" +"Go the menu :menuselection:`Sales --> Sales --> Products`. Open the products" +" you want to ship and set a weight on it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:102 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to " +"make the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:115 +msgid "" +"You can now choose the carrier on your sale order. Click on **Delivery " +"method** to choose the right one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:118 +msgid "" +"The price is computed when you save the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:121 +msgid "" +"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. It may vary from the real price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:125 +msgid "" +"Otherwise, the real price (computed when the delivery is validated) will " +"automatically be added to the invoice. For more information, please read the" +" document :doc:`../operation/invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:132 +msgid "" +"The delivery created from the sale order will take the shipping information " +"from it. You can change the carrier if you want to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:141 +msgid "" +"The weight is computed based on the products weights. The shipping cost will" +" be computed once the transfer is validated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:144 +msgid "" +"Click on **Validate** to receive the tracking number. The **Carrier Tracking" +" ref** field will automatically be filled. Click on the **Tracking** button " +"to check your delivery on the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:159 +msgid ":doc:`../operation/labels`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:3 +msgid "How to get UPS credentials for integration with Odoo?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:5 +msgid "In order to use the Odoo UPS API, you will need:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:7 +msgid "A UPS.com user ID and password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:9 +msgid "A UPS account number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:11 +msgid "An Access Key" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:13 +msgid "" +"An Access Key is a 16 character alphanumeric code that allows access to the " +"UPS Developer Kit API Development and Production servers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:17 +msgid "Create a UPS Account" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:19 +msgid "" +"Note that only customers located in the US can open a UPS account online. If" +" you are located outside the US, you will need to contact UPS Customer " +"Service in order to to open an account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:23 +msgid "" +"You can read additional information about opening a UPS account on the their" +" website, on the page, `How to Open a UPS Account Online " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:27 +msgid "" +"If you don't already have a UPS account, you can create one along with your " +"online profile by following these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:30 +msgid "" +"1. Access the UPS.com web site at `www.ups.com `__, and" +" click the **New User** link at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:34 +msgid "" +"2. Click the **Register for MyUPS** button, and follow the prompts to " +"complete the registration process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:37 +msgid "" +"If you already have a UPS account, you can add it to your online profile as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:39 +msgid "" +"Log in to the `UPS.com website `_) using your UPS.com " +"User ID and Password." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:41 +msgid "Click the **My UPS** tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:43 +msgid "Click the **Account Summary** link." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:45 +msgid "" +"4. Click the **Add an Existing UPS Account** link in the **UPS Account " +"Details** section of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:48 +msgid "" +"5. In the **Add New Account** screen, enter the **UPS Account Number**, " +"**Account Name**, and **Postal Code** fields. The country defaults to United" +" States.q" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:52 +msgid "Click the **Next** button to continue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:55 +msgid "Get an Access Key" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:57 +msgid "" +"After you have added your UPS account number to your user profile you can " +"request an Access Key from UPS using the steps below:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:60 +msgid "" +"Go to the `UPS Developer Kit web page " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:61 +msgid "Log into UPS.com with your user ID and password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:62 +msgid "Click on the link **Request an access key**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:63 +msgid "Verify your contact information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:64 +msgid "Click the **Request Access Key** button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials.rst:66 +msgid "" +"The **Access Key** will be provided to you on the web page, and an email " +"with the Access Key will be sent to the email address of the primary " +"contact." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:8 +msgid "Manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:10 +msgid "" +"**Odoo Manufacturing** helps manufacturers schedule, plan and process " +"manufacturing orders. With the work center control panel, put tablets on the" +" shop floor to control work orders in real-time and allow workers to trigger" +" maintenance operations, feedback loops, quality issues, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:15 +msgid "`Odoo Tutorials: MRP `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:17 +msgid ":doc:`IoT Boxes (MES) `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance.rst:5 +msgid "Maintenance" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:3 +msgid "Add new equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:5 +msgid "" +"In Odoo, **equipment** refers to any item that is used in everyday " +"operations, including the manufacturing of products. This can mean a piece " +"of machinery on a production line, a tool that is used in different " +"locations, or a computer in an office space. Equipment registered in Odoo " +"can be owned by the company that uses the Odoo database, or by a third " +"party, such as a vendor in the case of equipment rentals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:11 +msgid "" +"Using Odoo **Maintenance**, it is possible to track individual pieces of " +"equipment, along with information about their maintenance requirements. To " +"add a new piece of equipment, navigate to the :guilabel:`Maintenance` " +"module, select :menuselection:`Equipments --> Machines & Tools --> Create`, " +"and configure the equipment as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:16 +msgid ":guilabel:`Equipment Name`: the product name of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:17 +msgid "" +":guilabel:`Equipment Category`: the category that the equipment belongs to; " +"for example, computers, machinery, tools, etc.; new categories can be " +"created by navigating to :menuselection:`Configuration --> Equipment " +"Categories` and clicking :guilabel:`Create`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:20 +msgid "" +":guilabel:`Company`: the company that owns the equipment; again, this can be" +" the company that uses the Odoo database, or a third-party company" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:22 +msgid "" +":guilabel:`Used By`: specify if the equipment is used by a specific " +"employee, department, or both; select :guilabel:`Other` to specify both an " +"employee and a department" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:24 +msgid "" +":guilabel:`Maintenance Team`: the team responsible for servicing the " +"equipment; new teams can be created by navigating to " +":menuselection:`Configuration --> Maintenance Teams` and selecting " +":guilabel:`Create`; the members of each team can also be assigned from this " +"page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:27 +msgid "" +":guilabel:`Technician`: the person responsible for servicing the equipment; " +"this can be used to assign a specific individual in the event that no " +"maintenance team is assigned or when a specific member of the assigned team " +"should always be responsible for the equipment; any person added to Odoo as " +"a user can be assigned as a technician" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:31 +msgid "" +":guilabel:`Used in location`: the location where the equipment is used; this" +" is a simple text field that can be used to specify locations that are not " +"work centers, like an office, for example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:34 +msgid "" +":guilabel:`Work Center`: if the equipment is used at a work center, specify " +"it here; equipment can also be assigned to a work center by navigating to " +":menuselection:`Maintenance --> Equipments --> Work Centers`, selecting a " +"work center or creating a new one using the :guilabel:`Create` button, and " +"clicking the :guilabel:`Equipment` tab on the work center form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst-1 +msgid "An example of a fully configured new equipment form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:44 +msgid "Include additional product information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:46 +msgid "" +"The :guilabel:`Product Information` tab at the bottom of the form can be " +"used to provide further details about the piece of equipment:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:49 +msgid ":guilabel:`Vendor`: the vendor that the equipment was purchased from" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:50 +msgid "" +":guilabel:`Vendor Reference`: the reference code assigned to the vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:51 +msgid ":guilabel:`Model`: the specific model of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:52 +msgid ":guilabel:`Serial Number`: the unique serial number of the equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:53 +msgid "" +":guilabel:`Effective Date`: the date that the equipment became available for" +" use; this is used to calculate the :abbr:`MTBF (Mean Time Between " +"Failures)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:55 +msgid ":guilabel:`Cost`: the amount the equipment was purchased for" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:56 +msgid "" +":guilabel:`Warranty Expiration Date`: the date on which the equipment's " +"warranty will expire" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst-1 +msgid "The product information tab for the new piece of equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:63 +msgid "Add maintenance details" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:65 +msgid "" +"The :guilabel:`Maintenance` tab includes information that can be useful to " +"maintenance teams:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:67 +msgid "" +":guilabel:`Preventive Maintenance Frequency`: specifies how often " +"maintenance should be performed to prevent equipment failure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:69 +msgid "" +":guilabel:`Maintenance Duration`: the amount of time required to fix the " +"equipment when it fails" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:70 +msgid "" +":guilabel:`Expected Mean Time Between Failure`: the average amount of time " +"that the equipment is expected to operate before failing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst-1 +msgid "The maintenance tab for the new piece of equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:78 +msgid "" +"The :guilabel:`Maintenance` tab also includes sections for :guilabel:`Mean " +"Time Between Failure`, :guilabel:`Estimated Next Failure`, :guilabel:`Latest" +" Failure`, and :guilabel:`Mean Time To Repair`. These values are calculated " +"automatically based on maintenance requests if any exist." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/maintenance/add_new_equipment.rst:84 +msgid "" +"To see the maintenance requests for a piece of equipment, go to the page for" +" the equipment and select :guilabel:`Maintenance` in the top right corner of" +" the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management.rst:5 +msgid "Manufacturing management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:3 +msgid "Create a bill of materials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:5 +msgid "" +"A *Bill of Materials* (or *BoM* for short) is a document that defines the " +"quantity of each component required to make or deliver a finished product. " +"It can also include various operations and the individual step guidelines " +"needed to complete a production process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:9 +msgid "" +"In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be " +"linked to each product, so that even product variants can have their own " +"tailored :abbr:`BoMs (Bills of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:12 +msgid "" +"Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the " +"manufacturing process and save time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:16 +msgid "Set up a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18 +msgid "" +"The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations" +" or instructions, only components. In this case, the production is solely " +"managed using *Manufacturing Orders*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:21 +msgid "" +"To create a :abbr:`BoM (Bill of Materials)` from the " +":guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills " +"of Materials`. Then, click :guilabel:`Create`. Next, specify the " +":guilabel:`Product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:26 +msgid "" +"A :abbr:`BoM (Bill of Materials)` can also be created directly from the " +"product form, in which case the :guilabel:`Product` field is pre-filled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:29 +msgid "" +"For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type`" +" to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line`" +" to specify the various components that make up the production of the final " +"product and their respective quantities. New components can be created " +"quickly through the :abbr:`BoM (Bill of Materials)`, or can be created " +"beforehand in :menuselection:`Manufacturing --> Products --> Products --> " +"Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 +msgid "Set up a Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:41 +msgid "Specify a bill of materials (BoM) for a product variant" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43 +msgid "" +":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *Product " +"Variants*, with two setup options available to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:47 +msgid "" +"In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, " +"the product's variant attributes must already be configured on the product " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:50 +msgid "" +"The first method is to create one :abbr:`BoM (Bill of Materials)` per " +"variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the" +" :guilabel:`Product Variant`. The second method is to create one master " +":abbr:`BoM (Bill of Materials)` that contains all of the components, and " +"specify which variant each component applies to using the :guilabel:`Apply " +"on Variants` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 +msgid "Product Variants in the Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:60 +msgid "Set up operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:62 +msgid "" +"Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify" +" instructions for production and register time spent on an operation. To use" +" this feature, first enable the :guilabel:`Work Orders` feature in " +":menuselection:`Manufacturing --> Configuration --> Settings --> " +"Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:67 +msgid "" +"Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the " +":guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new " +"operation. In the :guilabel:`Create Operations` box, give the operation a " +"name, specify the :guilabel:`Work Center` and duration settings. Like " +"components, Odoo gives the option to specify a product variant in the " +":guilabel:`Apply on Variants` field so the operation only applies to that " +"variant. Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:74 +msgid "" +"Each operation is unique, as it is always exclusively linked to one " +":abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a" +" new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing " +"Operations` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 +msgid "Copy Existing Operations feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:83 +msgid "Add by-products to a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85 +msgid "" +"A *By-Product* is a residual product that is created during production in " +"addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike " +"the primary product, there can be more than one by-product on a :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:89 +msgid "" +"To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the " +":guilabel:`By-Products` feature in :menuselection:`Manufacturing --> " +"Configuration --> Settings --> Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:92 +msgid "" +"Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill " +"of Materials)` by clicking on the :guilabel:`Operations` tab and clicking " +":guilabel:`Add a line`. Then, name the by-product and indicate the " +":guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM " +"(Bill of Materials)` has configured operations, specify exactly which " +"operation the by-product is produced from in the :guilabel:`Produced in " +"Operation` field. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:3 +msgid "Use kits" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:5 +msgid "" +"A *kit* is a set of unassembled components. Kits may be sold as products, " +"but are also useful tools for managing more complex bills of materials " +"(BoMs). To use kits, the :guilabel:`Manufacturing` and :guilabel:`Inventory`" +" applications need to be installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:10 +msgid "Create the kit as a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:12 +msgid "" +"To use a kit as a sellable product or simply as a component organization " +"tool, the kit should first be created as a product. To create a kit product," +" go to :menuselection:`Manufacturing or Inventory --> Products --> " +"Products`, and then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:16 +msgid "" +"Next, set the :guilabel:`Product Type` to :guilabel:`Storable Product`: this" +" allows for management of kit inventory. The :guilabel:`Route` designation " +"under the :guilabel:`Inventory` tab does not matter, since Odoo uses the " +"routes of the kit's components for replenishment purposes. All other " +"parameters for the kit product may be modified according to preference. " +"Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:22 +msgid "" +"The kit's components must also be configured as products via " +":menuselection:`Manufacturing or Inventory --> Products --> Products`. These" +" components require no specific configuration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:26 +msgid "Set up the kit BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:28 +msgid "" +"After fully configuring the kit product and its components, create a " +":abbr:`BoM (Bill of Materials)` for the kit product. Go to " +":menuselection:`Manufacturing --> Products --> Bills of Materials`, and then" +" click :guilabel:`Create`. Next, set the :guilabel:`Product` field to the " +"previously configured kit product. Then, set the :guilabel:`BoM Type` to " +":guilabel:`Kit`. Finally, add each component and specify its quantity. Make " +"sure to :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 +msgid "Kit selection on the bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:38 +msgid "" +"If the kit is solely being used as a sellable product, then only components " +"need to be added under the :guilabel:`Components` tab, and configuring " +"manufacturing operations is not necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:42 +msgid "" +"When a kit is sold as a product, it appears as a single line item on the " +"quotation and sales order. However, on delivery orders, each component of " +"the kit is listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:46 +msgid "Use kits to manage complex BoMs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:48 +msgid "" +"Kits are also used to manage *multilevel* :abbr:`BoMs (Bills of Materials)`." +" These are products that contain other products as components and therefore " +"require nested :abbr:`BoMs (Bills of Materials)`. Incorporating pre-" +"configured kits into multilevel :abbr:`BoMs (Bills of Materials)` allows for" +" cleaner organization of bundled products. Under :guilabel:`Components`, " +"list a kit as a component in a higher-level product's :abbr:`BoM (Bills of " +"Material)` to eliminate the need to add the kit's parts individually. Any " +":guilabel:`BoM Type` can be used for the higher-level product's :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 +msgid "Kit as a component in a multilevel bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:60 +msgid "" +"To access a comprehensive overview of the multilevel :abbr:`BoM's (Bill of " +"Material's)` components, click on the :guilabel:`Structure & Cost` smart " +"button. Sublevel :abbr:`BoMs (Bills of Materials)` can be expanded and " +"viewed from this report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 +msgid "Expanded kit in the Structure and Cost report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:68 +msgid "" +"When creating a manufacturing order for a product with a multilevel " +":abbr:`BoM (Bill of Materials)`, the kit product automatically expands to " +"show all components. Any operations in the kit's :abbr:`BoM (Bill of " +"Materials)` are also added to the list of work orders on the manufacturing " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:74 +msgid "" +"Kits are primarily used to bundle components together for organization or " +"sale. To manage multilevel products that require manufactured subcomponents," +" refer to :doc:`this documentation ` on sub-assemblies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3 +msgid "Managing BoMs for product variants" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:5 +msgid "" +"Odoo allows one bill of materials (BoM) to be used for multiple variants of " +"the same product. Having a consolidated BoM for a product with variants " +"saves time by preventing the need to manage multiple BoMs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:10 +msgid "Activate product variants" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:12 +msgid "" +"To activate variants, simply navigate to :menuselection:`Inventory --> " +"Configuration --> Settings --> Products`, and then enable the " +":guilabel:`Variants` option. After that, click :guilabel:`Save` to apply the" +" setting. For more information on configuring product variants, refer to " +":doc:`this page <../../../sales/sales/products_prices/products/variants>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Selecting \"Variants\" from Inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:22 +msgid "Apply BoM components to product variants" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:24 +msgid "" +"Next, create a new BoM or edit an existing one by going to " +":menuselection:`Manufacturing --> Products --> Bills of Materials`. Then, " +"click :guilabel:`Edit`. The :guilabel:`Apply on Variants` option to assign " +"components to specific product variants on the BoM is available once the " +":guilabel:`Variants` setting is activated from the :guilabel:`Inventory` " +"application. If the :guilabel:`Apply on Variants` field is not immediately " +"visible, activate it from the additional options menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "\"Apply on Variants\" option on the additional options menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:35 +msgid "" +"Each component can be assigned to multiple variants. Components with no " +"variants specified are used in every variant of the product. The same " +"principle applies when configuring operations and by-products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:39 +msgid "" +"When defining variant BoMs by component assignment, the :guilabel:`Product " +"Variant` field in the main section of the BoM should be left blank, as shown" +" below. This field is used only when creating a BoM specifically for one " +"product variant." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Applying components to multiple variants." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:3 +msgid "Quality Control" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:5 +msgid "" +"Whether you want to control the quality of your production, or the " +"production of your subcontractor, before registering the products into your " +"stock, you can rely on Odoo's Quality module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:10 +msgid "" +"To control the quality of your production, you need to set a *Quality " +"Control Point* on the Manufacturing Operation Type, as shown below. To " +"create it, Go to :menuselection:`Quality --> Quality Control --> Control " +"Points`, and click **Create**. If the check only applies to specific " +"products, or product categories, you can specify these during the setup as " +"well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:19 +msgid "" +"Regarding the reception of subcontracted products, instead of the " +"Manufacturing Operation Type, you need to select the 'Receipts' Operation " +"type. For the rest, the same principles apply." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:25 +msgid "" +"By doing so, a quality check is automatically created each time a finished " +"product is made and/or received. Note that several Quality Check *Types* can" +" be chosen from the dropdown. Note also that several Quality Check Points " +"can be set up for the same Operation Type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:3 +msgid "Manage semi-finished products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:5 +msgid "" +"A *semi-finished product*, also known as a *subassembly*, is a manufactured " +"product that is used as a component in another product's bill of materials " +"(BoM). Semi-finished products are used to simplify complex :abbr:`BoMs " +"(Bills of Materials)` or to more accurately represent a manufacturing flow. " +"A :abbr:`BoM (Bill of Materials)` that contains semi-finished products is " +"referred to as a *multilevel BoM*, where the main *top-level product* and " +"its subassemblies are distinguished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:12 +msgid "Configure semi-finished products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:14 +msgid "" +"To set up a multilevel :abbr:`BoM (Bill of Materials)`, the top-level " +"product and semi-finished products must be configured. Therefore, the first " +"step is to create the semi-finished products and their :abbr:`BoMs (Bills of" +" Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:19 +msgid ":doc:`bill_configuration`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 +msgid "A bill of materials for a semi-finished product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:26 +msgid "Create the top-level bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:28 +msgid "" +"After the semi-finished products are fully configured, navigate to " +":menuselection:`Manufacturing --> Products --> Products`. Then, " +":guilabel:`Create` the top-level product. Configure the product's " +"specifications as desired, and be sure to :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:32 +msgid "" +"Once the top-level product is configured, click the :guilabel:`Bill of " +"Materials` smart button on the product form, then click :guilabel:`Create` " +"to make a :abbr:`BoM (Bill of Materials)` for the top-level product. Then, " +"simply add the semi-finished products to this :abbr:`BoM (Bill of " +"Materials)`, along with any other necessary components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 +msgid "" +"A bill of materials for a top-level product, containing a subassembly " +"component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:42 +msgid "Manage production planning" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:44 +msgid "" +"There are several methods to manage manufacturing order automation for " +"products with multilevel :abbr:`BoMs (Bills of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:48 +msgid "" +"Semi-finished products are specifically used to manage manufacturable " +"products with multilevel BoMs. If a BoM is being created simply to organize " +"components or bundle sellable products, using :doc:`Kits ` is " +"the more appropriate option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:52 +msgid "" +"To automatically trigger manufacturing orders for semi-finished products " +"after confirming a manufacturing order for the main product, there are two " +"options:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:55 +msgid "" +"**Option 1 (recommended):** Create *Reordering Rules* for the semi-finished " +"products and set both the minimum and maximum desired stock quantities to " +"`0`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:59 +msgid ":doc:`../../purchase/products/reordering`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:61 +msgid "" +"**Option 2:** Activate the :guilabel:`Replenish on Order (MTO)` and " +":guilabel:`Manufacture` routes under the :guilabel:`Inventory` tab of the " +"semi-finished product's product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:64 +msgid "" +"Option 1 is more flexible than Option 2 and is therefore recommended. " +"Reordering rules do not directly link demand to replenishment, and therefore" +" allow stocks to be unreserved and redirected to other orders, if necessary." +" The Replenish on Order (MTO) route creates a unique link between the semi-" +"finished and top-level products, exclusively reserving quantities for the " +"confirmed top-level manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:70 +msgid "" +"Regardless of the method chosen, semi-finished products must be fully " +"manufactured before manufacturing can begin on the top-level product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 +msgid "A manufacturing order for a top-level product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:3 +msgid "Subcontract your Manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:5 +msgid "" +"Outsourcing a portion or all of your company’s manufacturing needs is not " +"easy. To make it work correctly, you have to:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:8 +msgid "Manage the inventory of raw materials at your subcontractor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:9 +msgid "Ship raw material to your subcontractors, at the right time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:10 +msgid "Control incoming goods quality" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:11 +msgid "Control subcontractors bills" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:13 +msgid "" +"Here is an example of subcontracting the manufacturing of “C”, which is " +"produced out of raw materials “A” and “B”." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:20 +msgid "" +"With its MRP subcontracting feature, Odoo helps you handle this flow easily." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:25 +msgid "" +"To use the subcontracting feature, go to :menuselection:`Manufacturing --> " +"Configuration --> Settings` and tick the box *Subcontracting*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:32 +msgid "" +"To define if a product must be subcontracted, use a *Bill of Materials " +"(BoM)* of type *Subcontracting*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:35 +msgid "" +"To create a new *BoM*, go to :menuselection:`Manufacturing --> Products --> " +"Bill of Materials` and hit create. Then, list the components your " +"subcontractor needs to manufacture the product. For costing purposes, you " +"might want to register all the components, even the ones that are sourced " +"directly from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:41 +msgid "" +"Once you have set the *BoM Type* to *Subcontracting*, specify one or several" +" subcontractors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:49 +msgid "Basic Subcontracting Flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:51 +msgid "" +"To let your subcontractor know how many products you need, create and send " +"them purchase orders (PO). To do so, go to the *Purchase* app and create a " +"new purchase order. Be sure to send the PO to a vendor that is defined as a " +"subcontractor on the *BoM* of these products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:60 +msgid "" +"Once the *PO* is validated (1), a pending receipt is created. When the " +"products are received, validate the receipt (2), with the actual quantity " +"received. As a result, Odoo does the following things for you:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:64 +msgid "" +"Consumes the respective components at the subcontractor’s location, based on" +" the *BoM* and your input (3);" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:66 +msgid "Produces the finished goods at the subcontractor’s location (4);" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:68 +msgid "" +"Moves products from that subcontractor’s location to YourCompany via the " +"validated receipt (5)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:73 +msgid "" +"The *PO* is optional. If you create a receipt manually, with the right " +"subcontractor, Odoo still performs all the moves. This can be useful if the " +"subcontractor does not bill a fixed price per item, but rather the time and " +"materials used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:79 +msgid "Inventory Valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:81 +msgid "The cost of the manufactured product “C” is defined as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:83 +msgid "**C = A + B + s**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:85 +msgid "With:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:87 +msgid "**A**: Cost of raw materials coming from YourCompany;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 +msgid "**B**: Cost of raw materials sourced directly from the" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 +msgid "subcontractor;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:92 +msgid "**s**: Cost of the subcontracted service." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:94 +msgid "" +"Sending raw materials to your subcontractors (**A**) does not impact the " +"inventory valuation, as the components are still valued as part of your " +"stock. This is managed by making the *Subcontracting Location* an *Internal " +"Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:99 +msgid "" +"Then, the vendor price set on the product C form has to be what has to be " +"paid to the subcontractor for his parts and service time: **B + s**. The " +"product cost has to be: **A + B + s**, how much the product is valued in the" +" accounting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:104 +msgid "" +"Finally, the subcontractor bill then matches the purchase order, with the " +"proposed price coming from the finished products C." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:108 +msgid "" +"If managing the replenishment of raw materials **B** at your subcontractor’s" +" location is not needed, simply include the cost of **B** in the " +"subcontractor’s price **s** and remove the products *B* from the *BoM*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:114 +msgid "Traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:116 +msgid "" +"In case the received products from the subcontractor contain tracked " +"components, their serial or lot numbers need to be specified during the " +"receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:120 +msgid "" +"In that case, on the receipt of the subcontracted product, a *Record " +"Components* button appears. Click on it to open a dialog box and record the " +"serial/lot numbers of the components. If the finished product is also " +"tracked, its serial/lot number can be registered here too." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:129 +msgid "" +"For audit purposes, it is possible to check the lot numbers recorded on a " +"receipt by using the icon on the right of the finished products:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:136 +msgid "" +"Also note that in case flexible consumption has been selected on the " +"subcontracted BOM for a non-tracked product, the record components option " +"will also appear optionally on each move line, if you want to register more " +"or less component consumption at your subcontracting location, when " +"receiving your final product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:145 +msgid "" +"As you can see, the reception of both of these non-tracked products can " +"either be executed by selecting the 'Set Quantities' Option or via the move " +"line hamburger menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:149 +msgid "Automate Replenishment of Subcontractors" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:151 +msgid "" +"There are two ways to automate the supply of raw materials to your " +"subcontractors when purchasing the final product. The chosen method depends " +"on whether or not you want the materials to transit through your warehouse. " +"Both of these methods are described as pull style mechanisms as their " +"trigger is the inital PO to the subcontractor, which creates a need at the " +"subcontracting location, for raw material." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:158 +msgid "" +"If you are supplying your subcontractor with raw material from your own " +"warehouse, you must activate the 'Resupply Subcontractor on Order' route as " +"shown below. If this is a component that you buy from a vendor, the buy " +"route should also be activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:169 +msgid "" +"Now, if you want your vendor to resupply your subcontractor directly, you " +"must choose the 'Dropship Subcontractor on Order' option instead. In order " +"for this option to be active on the product form, you must first activate " +"the dropship option from :menuselection:`Purchase --> Configuration --> " +"Settings --> Dropshipping`. Once the PO to the subcontractor is validated, " +"this route will create a dropship RFQ from your vendor to that " +"subcontractor. You then just need to review and validate it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:182 +msgid "" +"Note that the buy route is not selected in this case, as the dropship route " +"is a buy route already." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:185 +msgid "" +"Finally, if you want to track the stock of these raw materials at your " +"subcontracting location(s), then you must activate *Multi-locations* in " +":menuselection:`Inventory --> Configuration --> Settings --> Storage " +"locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:189 +msgid "From the location form, you are then able to access the Current Stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:198 +msgid "Manual Replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:200 +msgid "You can also choose to replenish your subcontractors manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:202 +msgid "" +"If you want to send components to your subcontractor at your own " +"convenience, select the 'Resupply Subcontractor' Operation Type from the " +"*Inventory* Module, and create a picking, specifying to which subcontractor " +"you are delivering to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:210 +msgid "" +"Alternatively, you can also manually ask your vendor to resupply your " +"subcontractor by creating a dropship type PO, with your subcontractor set as" +" the delivery address." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:3 +msgid "Use the Master Production Schedule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:5 +msgid "" +"The Master Production Schedule (MPS) is a valuable tool to plan your " +"production based on your demand forecast." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 +msgid "" +"Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` " +"and activate the Master Production Schedule feature before hitting save." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:15 +msgid "" +"In the MPS settings, you can define the time range of your MPS " +"(month/week/day) and the number of periods you want to display at all times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:18 +msgid "" +"Now, go to :menuselection:`Planning --> Master Production Schedule` and " +"click on *add a product*. You can now define your safety stock target (= the" +" stock you want to have on hand at the end of the period) and the minimum " +"and maximum quantities that must or can be replenished in each period." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:26 +msgid "" +"In the MPS view, you can decide which information you would like to display " +"by clicking on *rows*. For instance, the *Actual demand* will show you which" +" quantity of products has already been ordered for the period, or *Available" +" to Promise*, what can still be sold during that same period (what you plan " +"to replenish - what is already sold during the period). You can also decide " +"to hide rows if you like." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:36 +msgid "Estimate your demand and launch replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:38 +msgid "" +"The next step is to estimate the demand for the chosen period. This is done " +"in the *Forecasted Demand* Row. You can easily, at any time, compare the " +"demand forecast with the actual demand (= confirmed sales). The demand " +"forecast for a finished product will impact the indirect demand for its " +"components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:46 +msgid "" +"Once the forecasted demand has been set, the quantity to replenish for the " +"different periods will automatically be computed. The replenishments you are" +" supposed to launch based on your lead times (vendor lead time or " +"manufacturing lead time) are then displayed in green. You can now launch the" +" replenishment by clicking on the replenish button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:52 +msgid "" +"Depending on the configuration of the product (buy vs. manufacture), " +"requests for quotations or manufacturing orders will be created. You can " +"easily access those by clicking on the *Actual Replenishment* cell." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:59 +msgid "" +"In case you manually edit the *Suggested Replenishment* quantity, a small " +"cross will appear on the left hand side of the cell. In case you want to go " +"back to the automatically computed value given by Odoo, simply click the " +"cross." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:65 +msgid "Cells color signification" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:67 +msgid "" +"The cells, which are part of the *Suggested Replenishment* line, can take " +"different colors depending on the situation:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:70 +msgid "" +"**Green**: quantity of products which should be replenished to reach the " +"expected safety stock considering the demand forecast and the indirect " +"demand forecast." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:72 +msgid "" +"**Grey**: replenishment order has already been generated, and its quantity " +"still matches current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:74 +msgid "" +"**Red**: replenishment order has already been generated, and its quantity " +"was too high considering current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:76 +msgid "" +"**Orange**: replenishment order has already been generated, and its quantity" +" was too low considering current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:78 +msgid "" +"The *Forecasted stock* line can also contain red cells, which means the " +"stock will be negative during the period in question." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:82 +msgid "What if I have underestimated the demand?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:84 +msgid "" +"You can still increase the demand forecast. It will impact the quantity to " +"replenish. The cell will become orange, and you’ll be able to launch a new " +"replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:89 +msgid "What if I have overestimated the demand?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:91 +msgid "" +"You can decrease the demand forecast. The cell will become red to inform you" +" that you’ve ordered more than planned. If you’re still able to do it, you " +"can cancel some RFQ or MO manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:96 +msgid "What if I wrongly added a product to the MPS?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:98 +msgid "" +"You can easily remove a product from the MPS by clicking the small bin on " +"the right of its name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:3 +msgid "Manage work orders using work centers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:5 +msgid "" +"Odoo *Manufacturing* allows for work orders to be carried out at specific " +"work centers. When a manufacturing order is created for a product, any work " +"orders listed in the :guilabel:`Operations` tab of the product *Bill of " +"Materials* (*BoM*) will be automatically created as well and assigned to the" +" specified work center. Work orders can be managed in the " +":menuselection:`Manufacturing` module by selecting " +":menuselection:`Operations --> Work Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:11 +msgid "" +"In order to use work centers, the :guilabel:`Work Orders` feature must first" +" be enabled. To do so, go to the :menuselection:`Manufacturing` module, " +"select :menuselection:`Configuration --> Settings`, and activate the " +"checkbox next to :guilabel:`Work Orders`. Work centers can then be created " +"and managed by selecting :menuselection:`Configuration --> Work Centers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:17 +msgid "Create a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:19 +msgid "" +"Within the :menuselection:`Manufacturing` module, select " +":menuselection:`Configuration --> Work Centers --> Create`. The work center " +"form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:22 +msgid "" +":guilabel:`Work Center Name`: give the work center a concise name that " +"describes the type of operations it will be used for" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:24 +msgid ":guilabel:`Tag`: assign the work center one or more user-created tags" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:25 +msgid "" +":guilabel:`Alternative Workcenters`: specify an alternative work center for " +"operations to be carried out at if the main work center is not available" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:27 +msgid ":guilabel:`Code`: assign the work center a reference code" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:28 +msgid "" +":guilabel:`Working Hours`: define the number of hours that the work center " +"can be in use each week" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:29 +msgid "" +":guilabel:`Company`: select the company that the work center belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "An example of a fully configured work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:36 +msgid "Set standards for work center productivity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:38 +msgid "" +"The :guilabel:`General Information` tab on the work center form allows for " +"productivity goals to be assigned to a work center:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:41 +msgid "" +":guilabel:`Time Efficiency`: used to calculate the expected duration of a " +"work order at the work center; for example, if a work order normally takes " +"one hour and the efficiency is set to 200%, the work order will take 30 " +"minutes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:44 +msgid "" +":guilabel:`Capacity`: the number of operations that can be performed at the " +"work center simultaneously" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:46 +msgid ":guilabel:`OEE Target`: the target for efficiency at the work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:47 +msgid "" +":guilabel:`Setup Time`: time required to set up the work center before work " +"can commence" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 +msgid "" +":guilabel:`Cleanup Time`: time required to clean the work center after work " +"is finished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 +msgid "" +":guilabel:`Cost per hour`: the cost of operating the work center for one " +"hour" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:50 +msgid "" +":guilabel:`Analytic Account`: the account where the cost of the work center " +"should be recorded" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The general information tab of the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:57 +msgid "Assign equipment to a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:59 +msgid "" +"Using the :guilabel:`Equipment` tab, it is possible for specific pieces of " +"equipment to be assigned to a work center. The following information will be" +" displayed for each piece of equipment added:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:62 +msgid ":guilabel:`Equipment Name`: the name of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:63 +msgid "" +":guilabel:`Technician`: the technician responsible for servicing the " +"equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:64 +msgid ":guilabel:`Equipment Category`: the category the equipment belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:65 +msgid "" +":guilabel:`MTBF`: mean time between failures; the average time that the " +"piece of equipment will operate before failing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:67 +msgid "" +":guilabel:`MTTR`: mean time to recovery; the average time it takes for the " +"equipment to become fully operational again" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:69 +msgid "" +":guilabel:`Est. Next Failure`: an estimate of when the next equipment " +"failure will occur" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The equipment tab of the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:76 +msgid "" +":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are " +"all calculated automatically based on past failure data, if any exists." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:82 +msgid "Integrate IoT devices" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:84 +msgid "" +"The :guilabel:`IoT Triggers` tab enables the integration of :abbr:`IoT " +"(Internet of Things)` devices with a work center:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:87 +msgid ":guilabel:`Device`: specifies the IoT device to be triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 +msgid ":guilabel:`Key`: the security key for the device" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:89 +msgid ":guilabel:`Action`: the IoT device action triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The IoT Triggers tab of the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:96 +msgid "Use case: configure an alternative work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:98 +msgid "" +"When a work center is at capacity, it cannot accept any new work orders. " +"Instead of waiting for the work center to become available, it is possible " +"to specify an alternative work center where surplus work orders should be " +"carried out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:102 +msgid "" +"Begin by creating a new work center. Configure the :guilabel:`Equipment` tab" +" so that it has all of the same equipment as the main work center. This will" +" ensure that the same tasks can be carried out at both work centers. " +"Navigate to the main work center and include the new work center in the " +":guilabel:`Alternative Workcenters` selection field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:107 +msgid "" +"Now, create a new manufacturing order that uses the main work center for one" +" of its operations. The main work center will automatically be selected for " +"the operation in the :guilabel:`Work Orders` tab. After confirming the " +"manufacturing order, click the :guilabel:`Plan` button that appears at the " +"top left of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "" +"Click the plan button to automatically select an available work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:116 +msgid "" +"If the main work center is at capacity, the work center selected for the " +"operation will be automatically changed to the alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The alternative work center is automatically selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:124 +msgid "Monitor work center performance" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:126 +msgid "" +"Performance for an individual work center can be viewed by selecting " +":menuselection:`Configuration --> Work Centers`, and clicking on a work " +"center. A variety of metrics showing work center performance can be viewed " +"at the top right of the form:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:130 +msgid "" +":guilabel:`OEE`: overall effective efficiency, the percentage of time that " +"the work center has been fully productive" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:132 +msgid ":guilabel:`Lost`: the amount of time lost due to work stoppages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 +msgid "" +":guilabel:`Load`: the amount of time it will take to complete the current " +"workload" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:134 +msgid "" +":guilabel:`Performance`: the real duration of work time, shown as a " +"percentage of the expected duration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:3 +msgid "Make work centers unavailable using Time Off" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:5 +msgid "" +"In Odoo, *work centers* are used to carry out manufacturing operations at " +"specific locations. However, if a work center cannot be used for some " +"reason, work orders begin to pile up at the work center until it is " +"operational again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:9 +msgid "" +"As a result, it is necessary to make the work center unavailable in Odoo so " +"that the platform routes new work orders to alternative work centers that " +"are operational. Using Odoo *Time Off*, it is possible to designate a work " +"center as being unavailable for a set period of time. Doing so ensures that " +"manufacturing operations can continue until the impacted work center is " +"available again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:17 +msgid "" +"Before a work center can be designated as unavailable, the Odoo platform " +"must be properly configured. First, it is necessary to enable " +":ref:`developer mode `. This allows the :guilabel:`Time Off`" +" smart button to appear on each work center's :guilabel:`Working Hours` pop-" +"up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:22 +msgid "" +"Enable developer mode by going to :menuselection:`Settings`, scrolling to " +"the bottom of the page, and clicking :guilabel:`Activate the developer mode`" +" under the :guilabel:`Developer Tools` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The \"Activate the developer mode\" button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:29 +msgid "" +"Next, install the *Time Off* app. This is the app used for assigning time " +"off to all resources within Odoo, including employees and work centers. " +"Navigate to :menuselection:`Apps`, then type `Time Off` in the " +":guilabel:`Search...` bar. The card for the :guilabel:`Time Off` module " +"should be the only one that appears on the page. Click the green " +":guilabel:`Install` button on the card to install the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Time Off module installation card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:39 +msgid "" +"The last step is to properly configure work centers. For this workflow, it " +"is necessary to have at least two work centers: one that is made unavailable" +" and a second that receives the work orders that the other cannot accept. If" +" no second work center is configured, Odoo cannot route work orders away " +"from the unavailable work center and they will pile up in its queue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:44 +msgid "" +"To create a work center, navigate to :menuselection:`Manufacturing --> " +"Configuration --> Work Centers --> Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:47 +msgid "" +"Make sure that both work centers have the same equipment listed under the " +":guilabel:`Equipment` tab. This ensures that operations carried out at one " +"work center can also be performed at the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The equipment tab on a work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:54 +msgid "" +"For the work center that will be made unavailable, select the second work " +"center on the :guilabel:`Alternative Workcenters` drop-down menu. Now, Odoo " +"knows to send work orders to the second work center when the first is " +"unavailable for any reason." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "A work center form configured with an alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:63 +msgid "Add time off for a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:65 +msgid "" +"With configuration completed, time off can now be assigned to the work " +"center that will be made unavailable. Begin by navigating to " +":menuselection:`Manufacturing --> Configuration --> Work Centers` and " +"selecting the affected work center. Click :guilabel:`Edit`, and then the " +":guilabel:`↗ (external link)` button next to the :guilabel:`Working Hours` " +"drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Working Hours \"External link\" button on the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:74 +msgid "" +"A pop-up appears, titled :guilabel:`Open: Working Hours`. The standard " +"working hours for the work center are listed here, along with various other " +"details about it. Since developer mode was enabled, there is a " +":guilabel:`Time Off` button in the top right of the pop-up. Click it to be " +"taken to the :guilabel:`Resource Time Off` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Time Off button on the Working Hours pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:83 +msgid "" +"On this page, click :guilabel:`Create` to configure a new time-off entry. On" +" the time-off form, note the :guilabel:`Reason` for the work center closure " +"(broken, maintenance, etc.), select the affected work center as the " +":guilabel:`Resource`, and choose a :guilabel:`Start Date` and :guilabel:`End" +" Date` to specify the period during which the work center will be " +"unavailable. Click :guilabel:`Save` and the time off for the work center is " +"logged in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The \"Resource Time Off\" form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:94 +msgid "Route orders to an alternative work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:96 +msgid "" +"Once a work center is within its specified time-off period, work orders sent" +" to it can be automatically routed to an alternative work center using the " +":guilabel:`Plan` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:99 +msgid "" +"Begin by creating a new manufacturing order by selecting " +":menuselection:`Operations --> Manufacturing Orders --> Create`. On the " +"manufacturing order form, specify a :guilabel:`Product` that uses the " +"unavailable work center for one of its operations. Click :guilabel:`Confirm`" +" to confirm the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:104 +msgid "" +"On the confirmed work order, select the :guilabel:`Work Orders` tab. By " +"default, the unavailable work center is specified in the :guilabel:`Work " +"Center` column. There is also a green :guilabel:`Plan` button on the top " +"left of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Plan button on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:112 +msgid "" +"Click :guilabel:`Plan` and the work center listed under the :guilabel:`Work " +"Orders` tab is automatically changed to the alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "" +"The selected work center updates automatically after clicking the Plan " +"button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:119 +msgid "" +"Once the time-off period for the unavailable work center ends, Odoo " +"recognizes that the work center is available again. At this point, clicking " +"the :guilabel:`Plan` button does not route work orders to an alternative " +"work center unless the first one is at capacity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control.rst:5 +msgid "Quality control" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:3 +msgid "Create quality alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:5 +msgid "" +"Configuring quality control points is a great way to ensure that quality " +"checks are performed at routine stages during specific operations. However, " +"quality issues can often appear outside of these scheduled checks. Using " +"Odoo *Quality*, users can create quality alerts for issues that are not " +"detected by automated processes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:11 +msgid ":doc:`Add quality control points `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:14 +msgid "Find and fill out the quality alerts form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:16 +msgid "" +"In some situations, it is necessary to manually create quality alerts within" +" the *Quality* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:19 +msgid "" +"A helpdesk user who is notified of a product defect by a customer ticket can" +" create an alert that brings the issue to the attention of the relevant " +"quality team." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:22 +msgid "" +"To create a new quality alert, start from the :menuselection:`Quality` " +"module and select :menuselection:`Quality Control --> Quality Alerts --> " +"Create`. The quality alert form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:26 +msgid "" +":guilabel:`Title`: choose a concise, yet descriptive title for the quality " +"alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:27 +msgid "" +":guilabel:`Product`: the product about which the quality alert is being " +"created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:28 +msgid "" +":guilabel:`Product Variant`: the specific variant of the product that has " +"the quality issue, if applicable" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:30 +msgid ":guilabel:`Lot`: the lot number assigned to the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:31 +msgid "" +":guilabel:`Work Center`: the work center where the quality issue originated" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:32 +msgid "" +":guilabel:`Picking`: the picking operation during which the quality issue " +"originated" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:33 +msgid "" +":guilabel:`Team`: the quality team that will be notified by the quality " +"alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:34 +msgid "" +":guilabel:`Responsible`: the individual responsible for managing the quality" +" alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:35 +msgid "" +":guilabel:`Tags`: classify the quality alert based on user-created tags" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:36 +msgid ":guilabel:`Root Cause`: the cause of the quality issue, if known" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:37 +msgid "" +":guilabel:`Priority`: assign a priority between one and three stars to " +"ensure more urgent issues are prioritized" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:40 +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:40 +msgid "" +"The tabs at the bottom of the form can be used to provide additional " +"information to quality teams:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:42 +msgid "" +":guilabel:`Description`: provide additional details about the quality issue" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:43 +msgid "" +":guilabel:`Corrective Actions`: the method for fixing affected products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:44 +msgid "" +":guilabel:`Preventive Actions`: procedures for preventing the issue from " +"occurring in the future" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:46 +msgid "" +":guilabel:`Miscellaneous`: the product vendor (if applicable), the company " +"that produces the product, and the date assigned" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst-1 +msgid "An example of a completed quality alert form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:54 +msgid "Add quality alerts during the manufacturing process" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:56 +msgid "" +"Odoo enables manufacturing employees to create quality alerts within a work " +"order without accessing the *Quality* module. From the work order tablet " +"view, click the :guilabel:` ☰ ` hamburger menu icon in the top left corner " +"and select :guilabel:`Quality Alert`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst-1 +msgid "Access the work order menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:64 +msgid "" +"The quality alert form can then be filled out as detailed in the previous " +"section. After saving the form, a new alert will appear on the " +":guilabel:`Quality Alerts` dashboard that can be found through the " +":menuselection:`Quality --> Quality Control` menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:69 +msgid "Manage existing quality alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:71 +msgid "" +"By default, quality alerts are organized in a kanban board view. The stages " +"of the kanban board are fully configurable and alerts can be moved from one " +"stage to the next by dragging and dropping or from within each alert. " +"Additional options are available for viewing alerts, including graph, " +"calendar, and pivot table views." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_alerts.rst:77 +msgid "" +"Filter alerts based on diverse criteria like date assigned or date closed. " +"Alerts can also be grouped by quality team, root cause, or other parameters " +"found under the :guilabel:`Filters` button menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:3 +msgid "Add quality controls" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:5 +msgid "" +"Use **Odoo Quality** to control the quality of products before they are " +"registered into stock, during picking operations, and when leaving the " +"warehouse for a delivery order. By creating *quality control points*, " +"manufacturers can set up quality checks that automatically trigger at " +"specific points during production." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:11 +msgid "Configure quality control points" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:13 +msgid "" +"To create a new quality control point, go to :menuselection:`Quality Control" +" --> Control Points --> Create`. Then, fill in the following form fields, " +"accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:16 +msgid "" +":guilabel:`Title`: give the quality control point a simple, but informative " +"title so production floor and quality check teams can understand it easily" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:18 +msgid "" +":guilabel:`Products`: indicate which product(s) should pass through the " +"specific quality control point" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:20 +msgid "" +":guilabel:`Operations`: determine which operations team(s) should perform " +"the quality control check (e.g., `Manufacturing`, `Receipts`, `Delivery " +"Orders`, etc.)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:22 +msgid "" +":guilabel:`Work Order Operation`: for manufacturing operations, use the " +"drop-down menu to indicate which type of work order the quality control " +"point applies to: :guilabel:`Manual Assembly`, :guilabel:`Packing`, " +":guilabel:`Assembly`, :guilabel:`Testing` or :guilabel:`Long time assembly`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:26 +msgid "" +":guilabel:`Company`: add the company that will implement the quality control" +" point. Usually this will be the company that owns the Odoo database. " +"However, a multi-company or vendor profile can be selected, as well, for " +"cases where there are multiple manufacturing or engineering locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:29 +msgid "" +":guilabel:`Control Type`: using the drop-down menu, choose from " +":guilabel:`All Operations`, :guilabel:`Randomly` or :guilabel:`Periodically`" +" to determine how often the control point should executed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:32 +msgid "" +":guilabel:`Type`: using the drop-down menu, choose the control point type: " +":guilabel:`Instructions`, :guilabel:`Take a Picture`, :guilabel:`Pass - " +"Fail`, or :guilabel:`Measure`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:35 +msgid "" +":guilabel:`Team`: decide which quality team should receive the results of " +"the quality control point check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:37 +msgid "" +":guilabel:`Responsible`: add a point person to manage the status and " +"evolution of the quality control point over time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:42 +msgid ":guilabel:`Instructions`: describe the quality check to be performed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:43 +msgid "" +":guilabel:`Message If Failure`: detail what should be done if the check " +"fails" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:44 +msgid ":guilabel:`Notes`: use to include any additional information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst-1 +msgid "" +"An example of a completed quality control point form for a Pass-Fail test." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:50 +msgid "" +"Once a control point has been configured, a quality check will be " +"automatically created and assigned when the specified operation or work " +"order has been reached. Quality checks can be managed by selecting " +":menuselection:`Quality Control --> Quality Checks`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:55 +msgid "" +"To see all of the quality checks created by a control point, go to " +":menuselection:`Quality Control --> Control Points`, select a control point," +" and click :guilabel:`Quality Checks` in the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:60 +msgid "Use case: configure a measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:62 +msgid "" +"To ensure that a product meets specific measurement requirements, select " +":guilabel:`Measure` from the :guilabel:`Type` drop-down menu. Selecting the " +":guilabel:`Measure` quality check type reveals three new fields: " +":guilabel:`Device`, :guilabel:`Norm`, and :guilabel:`Tolerance`. These " +"fields can be configured so that only products within a certain tolerance " +"will pass the check:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:67 +msgid "" +":guilabel:`Device`: select the measuring device that should be used to take " +"the measurement (e.g., measuring tape)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:69 +msgid "" +":guilabel:`Norm`: specify the desired measurement that the product should " +"conform to and the unit of measurement that should be used" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:71 +msgid "" +":guilabel:`Tolerance`: select the range that a measurement can be within " +"while still passing the check (e.g., :guilabel:`from` 59.5 mm :guilabel:`to`" +" 60.5 mm)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst-1 +msgid "" +"An example of a quality control point form configured for a measure quality " +"check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:78 +msgid "" +"When the quality control points form is complete, click :guilabel:`Save`. " +"Now, this measurement-based test will trigger for products that were " +"specified on the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/quality_control/quality_control_points.rst:81 +msgid "" +"When production of the specified product reaches the operation that requires" +" a measure quality check, the manufacturing employee responsible will be " +"prompted to record and validate the measured value in the tablet view. For " +"products that measure within the values indicated in the " +":guilabel:`Tolerance` fields, the test will pass. However, for products that" +" measure outside of those values, the test will fail. In that case, the " +"worker who performed the check would create a quality alert from the tablet " +"view. That quality alert can then be addressed by the quality management " +"team." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase.rst:8 +msgid "Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase.rst:10 +msgid "" +"**Odoo Purchase** helps you keep track of purchase agreements, quotations, " +"and purchase orders. Learn how to keep track of purchase tender, automate " +"replenishments and follow up on your orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase.rst:14 +msgid "`Odoo Tutorials: Purchase `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:3 +msgid "Analyze the performance of your purchases" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:5 +msgid "" +"If your company regularly purchases products, you have several reasons to " +"track and analyze your performance. The insights gathered can help you to " +"better forecast and plan your future orders. For example, you can assess if " +"your business is dependent on particular vendors, and the data can help you " +"negotiate discounts on prices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:11 +msgid "Generate customized reports" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:13 +msgid "" +"Go to *Reporting* to access the purchase analysis. Simply by accessing the " +"reporting dashboard, you can get a quick overview of your actual " +"performance. By default, the reporting dashboard displays a line chart " +"presenting the untaxed amount of your purchase orders per day, and below it," +" key metrics and a pivot table." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Reporting dashboard in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:22 +msgid "" +"While the data initially presented is useful, there are several tools and " +"features you can use to get even more insights on your purchases." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:26 +msgid "Use filters to select the data you need" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:28 +msgid "" +"Odoo offers several default filters you can use and combine by clicking on " +"*Filters*. When you select one or several filters, Odoo looks for all the " +"orders that match at least one of the filters you have chosen and populates " +"the chart, key metrics, and pivot table with the data. The pre-configured " +"filters are:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:33 +msgid "All *Requests for Quotation*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:35 +msgid "All *Purchase Orders*, except canceled ones" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:37 +msgid "" +"*Confirmation Date Last Year* includes all orders that were confirmed the " +"previous year, canceled purchase orders included" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:40 +msgid "" +"*Order Date* includes all orders - request for quotations and purchases " +"orders (canceled ones included) - depending on their date of creation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:43 +msgid "" +"*Confirmation Date* includes all confirmed orders, canceled ones included, " +"depending on their date of confirmation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:47 +msgid "" +"When you have to select a period, you can use multiple years, and, with at " +"least one year selected, multiple quarters and the three most recent months." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:51 +msgid "" +"If you use the *Order Date* or *Confirmation Date* filters, the *Comparison*" +" feature appears next to *Filters*. It enables you to compare the period you" +" filtered with the previous one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Reporting filters in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:59 +msgid "Add custom filters" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:61 +msgid "" +"Thanks to the 31 filtering options to choose from, the possibilities of your" +" customizing your dataset are almost limitless. Go to " +":menuselection:`Filters --> Add Custom Filter`, specify the condition the " +"filtering option should meet (e.g. *is equal to*, *contains*, etc.), and " +"click on *Apply*. If you want to select orders matching several conditions " +"simultaneously (*and* operator), repeat the process to add another custom " +"filter. If you want to use the *or* operator, don't click on *Apply*, and " +"click on *Add a condition* instead. Once you have added all the desired " +"filtering options, click on *Apply*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Custom reporting filter in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:74 +msgid "" +"To avoid having to recreate custom filters every time, save them by clicking" +" on :menuselection:`Favorites --> Save current search --> Save`. The " +"customized search filter can then be accessed by clicking on *Favorites* or " +"can even be set as the default filter when you open the reporting dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:80 +msgid "Measure exactly what you need" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:82 +msgid "" +"Before selecting what you want to measure, you need to decide whether you " +"prefer using the graph view or the pivot view. By default, the dashboard " +"presents both views. However, the measures you select won't be applied to " +"both views. You can access each view separately by clicking on the icons at " +"the top right of the dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Switch reporting view in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:92 +msgid "Visualize your data" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:94 +msgid "" +"You can transform the main graph in just a click by selecting one of the " +"three charts: bar, line or pie. Fourteen different measures are available, " +"but you can only use one at a time. However, you can group the measure using" +" one or several of the 19 *Groups*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Reporting graph view in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:102 +msgid "" +"For bar and line charts, the selected measure is your y-axis, and the first " +"group you select is used to create the x-axis. Adding more group adds " +"additional lines (line chart) or transforms your bar chart into a stacked " +"bar chart. For pie charts, the more groups you select, the more slices are " +"displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:108 +msgid "Explore your data" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:110 +msgid "" +"The pivot table view enables you to explore your data in great detail. " +"Unlike the graph view, the pivot table enables you to add several measures " +"at the same time. By clicking on *Measures* or on the **+** sign in the " +"*Total* column, you can add as many as you want, each assigned to a new " +"column. By clicking on the **+** sign in the *Total* row, you can add " +"*Groups*. If you click on a group's **+** sign, you can add a sub-group, and" +" so on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Pivot table view in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:121 +msgid "" +"You can insert your pivot table's data directly in the Spreadsheet app or " +"export it as an Excel file." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals.rst:5 +msgid "Manage deals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:3 +msgid "Purchase agreements: blanket orders and calls for tenders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:5 +msgid "" +"There are two main types of purchase agreements preconfigured in Odoo: " +"blanket orders and call for tenders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:8 +msgid "" +"Blanket orders are long-term agreements between a company and a vendor to " +"deliver products on a recurring basis with predetermined pricing. Your " +"company should consider using them when you frequently purchase the same " +"products from the same vendor in varying quantities and/or at different " +"times. Among their many benefits, you can save time as the ordering process " +"is simplified, and money thanks to more advantageous bulk pricing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:14 +msgid "" +"Calls for tenders use a special procedure to request offers from multiple " +"vendors at the same time. While public sector organizations are often " +"legally bound to release calls for tenders when they want to purchase goods " +"or services, private organizations can also use them to get the best deal " +"among several vendors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:20 +msgid "Enable purchase agreements" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:22 +msgid "" +"From the Purchase app, go to :menuselection:`Configuration --> Settings` and" +" activate *Purchase Agreements*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst-1 +msgid "Enable purchase agreements in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:30 +msgid "Configure or create new types of purchase agreements" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:32 +msgid "" +"Before you start using purchase agreements, make sure they are configured " +"the way you want by going to :menuselection:`Configuration --> Purchase " +"Agreement Types`. From there, you can edit the way blanket orders and calls " +"for tenders or *Create* a new type of purchase agreement. You can configure " +"the:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:37 +msgid "Agreement Type: the name you want to give to the agreement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:39 +msgid "" +"Agreement Selection Type: you can either select multiple offers using " +"*Select multiple RFQ (non-exclusive)*, which is the default setting for both" +" blanket orders and calls for tenders, or a single offer using *Select only " +"one RFQ (exclusive)*, which is sometimes needed for calls for tenders where " +"you only want to select a single vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:44 +msgid "" +"Lines: generally, you would always want to select *Use lines of agreement*, " +"which are the different product lines you can configure when you set up your" +" purchase agreement. However, you can select *Do not create RfQ lines " +"automatically* if you don't want your requests for quotations to be pre-" +"filled in with that information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:49 +msgid "" +"Quantities: if you use lines of agreements, you can also specify " +"independently if the products' quantities should be used to pre-fill new " +"requests for quotations. The default option for blanket orders is *Set " +"quantities manually*, while for calls for tenders are set to *Use quantities" +" of agreement*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst-1 +msgid "Configure purchase agreements types in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:59 +msgid "Set up a blanket order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:61 +msgid "" +"Go to :menuselection:`Orders --> Purchase Agreements` and click on *Create*." +" Select *Blanket Order* as your *Agreement Type*. Next, select the vendor. " +"The other fields aren't mandatory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:64 +msgid "" +"Next, add the products you want to order and their price. Note that you can " +"also add a *Quantity* for each product, for example, if you have agreed with" +" your vendor to order a specific minimum quantity each time or in total. If " +"you have configured your blanket order to *Set quantities manually*, this is" +" only used for informational purposes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst-1 +msgid "Set up a blanket order in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:73 +msgid "" +"You can also write any *Terms and Conditions* at the bottom of the " +"agreement. Once you are satisfied with your blanket order, click on " +"*Confirm*. Its status then changes from *Draft* to *Ongoing* and it's ready " +"to be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:78 +msgid "Create requests for quotation from the blanket order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:80 +msgid "" +"You can now create new quotations from the blanket order whenever you need " +"it by clicking on *New Quotation*. Odoo automatically fills in requests for " +"quotation with the information initially defined when you set up the blanket" +" order. Depending on the way you configured the *Purchase Agreement Type*, " +"product lines can also be pre-filled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:85 +msgid "" +"From here, you can quickly view all the requests for quotations made under " +"that blanket order by clicking on *RFQs/Orders*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst-1 +msgid "Create new quotations for an ongoing blanket order in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:93 +msgid "" +"You can also create a *Request for Quotation* the usual way and then link it" +" to an existing *Blanket Order*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:97 +msgid "Blanket orders and replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:99 +msgid "" +"Blanket orders can be used for :doc:`automated replenishment " +"<../../purchase/products/reordering>`, as once a blanket order is confirmed," +" a new vendor line is added to your product. Make sure the related vendor is" +" in the first position if you have several vendors linked to your product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst-1 +msgid "Blanket order added to product configuration in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:108 +msgid "Set up a call for tenders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:110 +msgid "" +"Go to :menuselection:`Orders --> Purchase Agreements` and click on *Create*." +" Select *Call for Tenders* as your *Agreement Type*. The other fields aren't" +" mandatory, but you can add the date you want to be delivered and set an " +"agreement deadline. You usually don't want to select a vendor for calls for " +"tenders as you are looking to get quotations from multiple vendors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:115 +msgid "" +"Next, add the products you want to order and in what quantity. For calls for" +" tenders, you typically don't add a price, as the vendors should give you " +"their best quote." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:118 +msgid "" +"You can also write any *Terms and Conditions* at the bottom of the " +"agreement. Once you are ready, click on *Confirm*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst-1 +msgid "Set up a call for tenders in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:126 +msgid "Requests quotations from the call for tenders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:128 +msgid "" +"You can now request new quotations from the call for tenders. Click on *New " +"Quotation* and select one of your vendors you want to invite to the call for" +" tenders. Product lines should also be pre-filled in, depending on how you " +"configured the *Purchase Agreement Type*. Click on *Send by email* to send " +"it to the vendor. Go back to the call for tenders and repeat this process " +"for each vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst-1 +msgid "Request a quotation from a call for tenders in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:138 +msgid "" +"Once you have sent a request for quotation to every vendor and receiving " +"their quotes, click on *Validate* to proceed to the bid selection. Next, " +"click on the RFQs/Orders smart button to view all your vendors' quotations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst-1 +msgid "Validate a call for tenders and view all quotations in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst:146 +msgid "" +"Click on each request for quotation to add the price communicated by your " +"vendors manually. When that's done, select the most advantageous offer and " +"click on *Confirm Order*. This automatically closes the call for tenders. " +"You can now proceed with the purchase order as you would for a regular one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/agreements.rst-1 +msgid "Confirm an order in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:3 +msgid "Control and know when vendor bills should be paid" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:5 +msgid "" +"With Odoo, you can define how your vendor bills are controlled. For each " +"purchase order, you can decide when the related vendor bill should be paid: " +"either before or after you have received your products. You can also check " +"at a glance what is the billing status of each purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:9 +msgid "" +"With the 3-way matching feature, Odoo compares the information appearing on " +"the *Purchase Order*, the *Vendor Bill* and the *Receipt*, and lets you know" +" if you should pay the bill. This way you can avoid paying incorrect or " +"fraudulent vendor bills." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:14 +msgid "Vendor bills default control policy" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:16 +msgid "" +"As a first step, open your Purchase app and go to " +":menuselection:`Configuration --> Settings` to set the default bill control " +"policy for all the products created onwards." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Vendor bills default control setting for new products in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:23 +msgid "" +"By selecting *On ordered quantities*, you can create a vendor bill as soon " +"as you confirm an order. The quantities mentioned in the purchase order are " +"used to generate the draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:26 +msgid "" +"If you choose *On received quantities* instead, you can only create one once" +" you have at least received some of the products you have ordered. The " +"quantities you have received are used to generate the draft bill. If you try" +" to create one without having received any product, you get an error " +"message." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "No invoiceable line error message in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:36 +msgid "Change a specific product's control policy" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:38 +msgid "" +"If you want to modify a specific product's control policy, go to " +":menuselection:`Products --> Products`, open it, click on *Edit* and go to " +"the *Purchase tab*. There you can change a product's default bill control " +"policy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:47 +msgid "View a purchase order's billing status" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:49 +msgid "" +"Once you confirm an order, you can view its *Billing Status* by going to the" +" *Other Information* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Purchase order billing status in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:56 +msgid "" +"Below you can find a list of the different *Billing Status*, and when they " +"are displayed, depending on the products' bill control policy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:60 +msgid "**Billing status**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:60 +msgid "**Conditions**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:62 +msgid "*On received quantities*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:62 +msgid "*On ordered quantities*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:64 +msgid "*Nothing to Bill*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:64 +msgid "PO confirmed; no products received" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:64 +msgid "*(Not applicable)*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:66 +msgid "*Waiting Bills*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:66 +msgid "All/some products received; bill not created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:66 +msgid "PO confirmed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:68 +msgid "*Fully Billed*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:68 +msgid "All/some products received; draft bill created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:68 +msgid "Draft bill created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:72 +msgid "Determine when to pay with 3-way matching" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:74 +msgid "" +"First, go to :menuselection:`Configuration --> Settings` and activate *3-way" +" matching*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "3-way-matching setting in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:81 +msgid "" +"3-way matching is intended to work with the bill control policy set to *On " +"received quantities*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:84 +msgid "Should I pay the vendor bill?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:86 +msgid "" +"With the feature activated, your vendor bills now display the *Should Be " +"Paid* field under the *Other info* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Should Be Paid field under a vendor bill in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:93 +msgid "" +"As you can't create a bill until you have received your products - and if " +"you haven't received all of them, Odoo only includes the products you have " +"received in the draft bill - the *Should Be Paid* status is set to *Yes* " +"when you create one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:97 +msgid "" +"If you edit a draft bill to increase the billed quantity, change the price, " +"or add other products, the *Should Be Paid* status is set to *Exception*. It" +" means Odoo notices the discrepancy, but that you might have a valid reason " +"to have done so." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:101 +msgid "" +"Once the payment has been registered and mentions *Paid*, the *Should Be " +"Paid* status is set to *No*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Paid bill in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:109 +msgid "" +"The *Should Be Paid* status is set automatically by Odoo. However, you can " +"change the status manually when you are viewing a bill in edit mode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:3 +msgid "Manage vendor bills" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:7 +msgid "" +"A *vendor bill* is an invoice received for products and/or services that a " +"company purchases from a vendor. Vendor bills record payables as they arrive" +" from vendors, and can include amounts owed for the goods and/or services " +"purchased, sales taxes, freight and delivery charges, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:11 +msgid "" +"In Odoo, a vendor bill can be created at different points in the purchasing " +"process, depending on the *bill control* policy chosen in the *Purchase* app" +" settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:15 +msgid "Bill control policies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:17 +msgid "" +"To view and edit the default bill control policy and make changes to it, go " +"to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll " +"down to the :guilabel:`Invoicing` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:21 +msgid "" +"Here, there are two :guilabel:`Bill Control` policy options: " +":guilabel:`Ordered quantities` and :guilabel:`Received quantities`. After a " +"policy is selected, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Bill control policies in purchase app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:28 +msgid "" +"The policy selected will be the default for any new product created. The " +"definition of each policy is as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31 +msgid "" +":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase " +"order is confirmed. The products and quantities in the purchase order are " +"used to generate a draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:33 +msgid "" +":guilabel:`Received quantities`: a bill is only created **after** part of " +"the total order has been received. The products and quantities **received** " +"are used to generate a draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:37 +msgid "" +"If a product needs a different control policy, the default bill control " +"policy can be overridden by going to the :guilabel:`Purchase` tab in a " +"product's template, and modifying its :guilabel:`Control Policy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Control policy field on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:46 +msgid "3-way matching" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:48 +msgid "" +"*3-way matching* ensures vendor bills are only paid once some (or all) of " +"the products included in the purchase order have actually been received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:51 +msgid "" +"To activate it, go to :menuselection:`Purchase app --> Configuration --> " +"Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, check" +" the box next to :guilabel:`3-way matching: purchases, receptions, and " +"bills`, and click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:56 +msgid "" +":guilabel:`3-way matching` is **only** intended to work with the " +":guilabel:`Bill Control` policy set to :guilabel:`Received quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 +msgid "Activated three-way matching feature in purchase settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:64 +msgid "Create and manage vendor bills on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:66 +msgid "" +"When products are received into a company's warehouse, receipts are created." +" Once the company processes the received quantities, they can choose to " +"create a vendor bill directly from the warehouse receipt form. Depending on " +"the bill control policy chosen in the settings, vendor bill creation is " +"completed at different steps of the procurement process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:72 +msgid "With the bill control policy set to ordered quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:74 +msgid "" +"To create and manage vendor bills on receipts using the *ordered quantities*" +" bill control policy, first go to :menuselection:`Purchase app --> " +"Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` " +"section, and select :guilabel:`Ordered quantities` under :guilabel:`Bill " +"Control`. Then, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:79 +msgid "" +"Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` " +"to create a new request for quotation (RFQ). Doing so reveals a blank " +":abbr:`RFQ (request for quotation)` detail form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:82 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:144 +msgid "" +"On the blank detail form, add a vendor to the :abbr:`RFQ (request for " +"quotation)` in the :guilabel:`Vendor` field, and add products to the " +":guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:86 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148 +msgid "" +"Then, confirm the :abbr:`RFQ (request for quotation)` by clicking the " +":guilabel:`Confirm Order` button above the detail form. Doing so turns the " +":abbr:`RFQ (request for quotation)` into a purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:90 +msgid "" +"Then, click the :guilabel:`Create Bill` button to create a vendor bill for " +"the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:92 +msgid "" +"Clicking the :guilabel:`Create Bill` button reveals the :guilabel:`Draft " +"Bill` page for the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:95 +msgid "" +"On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button to modify " +"the bill, and add a bill date in the :guilabel:`Bill Date` field. If needed," +" add additional products to the :guilabel:`Product` lines by clicking " +":guilabel:`Add a line` in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:99 +msgid "" +"Next, confirm the bill by clicking the :guilabel:`Confirm` button on the " +":guilabel:`Draft Bill` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:103 +msgid "" +"Since the bill control policy is set to *ordered quantities*, the draft bill" +" can be confirmed as soon as it is created, before any products have been " +"received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:106 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:179 +msgid "" +"On the new :guilabel:`Vendor Bill`, add a :guilabel:`Bill Reference` number," +" which can be used to match the bill with additional documents (such as the " +":abbr:`PO (purchase order)`). Then, click :menuselection:`Confirm --> " +"Register Payment`. Doing so causes a pop-up to appear, wherein a payment " +":guilabel:`Journal` can be chosen; a :guilabel:`Payment Method` selected; " +"and a :guilabel:`Recipient Bank Account` can be selected from a drop-down " +"menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:112 +msgid "" +"Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and " +":guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. " +"Once ready, click :guilabel:`Create Payment` to finish creating the " +":guilabel:`Vendor Bill`. Doing so causes a green :guilabel:`In Payment` " +"banner to display on the :abbr:`RFQ (request for quotation)` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Vendor bill form for ordered quantities control policy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:122 +msgid "" +"Each vendor bill provides the option to either :guilabel:`Add Credit Note` " +"or :guilabel:`Add Debit Note`. A *credit note* is typically issued when a " +"vendor or supplier of goods get some quantity of products back from the " +"customer to whom they were sold, while *debit notes* are reserved for goods " +"returned from the customer/buyer to the vendor or supplier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:128 +msgid "With the bill control policy set to received quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:131 +msgid "" +"If the creation of a vendor bill is attempted without receiving any " +"quantities of a product (while using the *received quantities* bill control " +"policy), an error message appears, and settings must be changed before " +"proceeding." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:135 +msgid "" +"To create and manage vendor bills on receipts using the *received " +"quantities* bill control policy, first go to :menuselection:`Purchase app " +"--> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` " +"section, and select :guilabel:`Received quantities` under :guilabel:`Bill " +"Control`. Then, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:140 +msgid "" +"Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` " +"to create a new :abbr:`RFQ (request for quotation)`. Doing so reveals a " +"blank :abbr:`RFQ (request for quotation)` detail form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:152 +msgid "" +"Finally, click the :guilabel:`Create Bill` button to create a bill for the " +"purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:155 +msgid "" +"Clicking :guilabel:`Create Bill` before any products have been received will" +" cause a :guilabel:`User Error` pop-up to appear. The :guilabel:`Purchase " +"Order` requires the receipt of at least partial quantity of the items " +"included on the order to create a vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "User error pop-up for received quantities control policy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:163 +msgid "" +"Next, click the :guilabel:`Receipt` smart button to view the warehouse " +"receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:165 +msgid "" +"On the warehouse receipt form, click :menuselection:`Validate --> Apply` to " +"mark the :guilabel:`Done` quantities. Then, navigate back to the " +":menuselection:`Purchase Order` (via the breadcrumbs), and click the " +":guilabel:`Create Bill` button on the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:169 +msgid "" +"Doing so reveals the :guilabel:`Draft Bill` for the purchase order. On the " +":guilabel:`Draft Bill`, click the :guilabel:`Edit` button, and add a " +":guilabel:`Bill Date`. If needed, add additional products to the " +":guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:173 +msgid "" +"Next, click the :guilabel:`Confirm` button to confirm the :guilabel:`Draft " +"Bill`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:176 +msgid "" +"Since the bill control policy is set to *received quantities*, the draft " +"bill can **only** be confirmed when at least some of the quantities are " +"received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:185 +msgid "" +"Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and " +":guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. " +"Once ready, click :guilabel:`Create Payment` to finish creating the vendor " +"bill. Doing so causes a green **In Payment** banner to display on the " +":abbr:`RFQ (request for quotation)` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:191 +msgid "Create and manage vendor bills in Accounting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:193 +msgid "" +"Vendor bills can also be created directly from the *Accounting* app, " +"**without** having to create a purchase order first. To do this, go to " +":menuselection:`Accounting app --> Vendors --> Bills`, and click " +":guilabel:`Create`. Doing so reveals a blank vendor bill detail form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:197 +msgid "" +"On this blank vendor bill detail form, add a vendor in the " +":guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines " +"(under the :guilabel:`Invoice Lines` tab), by clicking :guilabel:`Add a " +"line`. Then, add a bill date in the :guilabel:`Bill Date` field, and any " +"other necessary information. Finally, click :guilabel:`Confirm` to confirm " +"the bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:202 +msgid "" +"From here, click the :guilabel:`Journal Items` tab to view (or change) the " +":guilabel:`Account` journals that were populated based on the configuration " +"on the corresponding :guilabel:`Vendor` and :guilabel:`Product` forms." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:206 +msgid "" +"Then, click :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note` to add" +" credit or debit notes to the bill. Or, add a :guilabel:`Bill Reference` " +"number (while in :guilabel:`Edit` mode)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:209 +msgid "" +"Then, when ready, click :menuselection:`Register Payment --> Create Payment`" +" to complete the :guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:213 +msgid "" +"To tie the draft bill to an existing purchase order, click the drop-down " +"menu next to :guilabel:`Auto-Complete`, and select a :abbr:`PO (purchase " +"order)` from the menu. The bill will auto-populate with the information from" +" the :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 +msgid "Auto-complete drop-down list on draft vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:222 +msgid "Batch billing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:224 +msgid "" +"Vendor bills can be processed and managed in batches in the *Accounting* " +"app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:226 +msgid "" +"To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`. " +"Then, click the :guilabel:`checkbox` at the top left of the page, beside the" +" :guilabel:`Number` column, under the :guilabel:`Create` button. This " +"selects all existing vendor bills with a :guilabel:`Posted` or " +":guilabel:`Draft` :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:231 +msgid "" +"From here, click the :guilabel:`Action` gear icon to export, delete, or send" +" & print the bills; click the :guilabel:`Print` icon to print the invoices " +"or bills; or click :guilabel:`Register Payment` to create and process " +"payments for multiple vendor bills at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:235 +msgid "" +"When :guilabel:`Register Payment` is selected, a pop-up appears. In this " +"pop-up window, select the appropriate journal in the :guilabel:`Journal` " +"field, choose a payment date in the :guilabel:`Payment Date` field, and " +"choose a :guilabel:`Payment Method`. There is also the option to " +":guilabel:`Group Payments` on this pop-up, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:240 +msgid "" +"When ready, click the :guilabel:`Create Payment` button, which creates a " +"list of journal entries on a separate page. This list of journal entries are" +" all tied to their appropriate vendor bills." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Batch billing register payment pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:248 +msgid "" +"The :guilabel:`Register Payment` option for vendor bills in batches will " +"only work for journal entries whose :guilabel:`Status` is set to " +":guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:252 +msgid "" +":doc:`/applications/inventory_and_mrp/purchase/manage_deals/control_bills`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:3 +msgid "Configure reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:5 +msgid "" +"For certain products, it is necessary to ensure that there is always a " +"minimum amount available on hand at any given time. By adding a reordering " +"rule to a product, it is possible to automate the reordering process so that" +" a purchase order is automatically created whenever the amount on hand falls" +" below a set threshold." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:11 +msgid "The *Inventory* module must be installed to use reordering rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:14 +msgid "Configure products for reordering" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:16 +msgid "" +"Products must be configured in a specific way before a reordering rule can " +"be added to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:18 +msgid "" +"Starting from the :menuselection:`Inventory`, " +":menuselection:`Manufacturing`, :menuselection:`Purchase`, or " +":menuselection:`Sales` module, navigate to :menuselection:`Products --> " +"Products` and then click :guilabel:`Create` to make a new product. " +"Alternatively, find a product that already exists in the database and click " +"into it's product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:23 +msgid "" +"Next, on the product form, enable reordering by checking the :guilabel:`Can " +"be Purchased` option underneathe the :guilabel:`Product Name` field. " +"Finally, set the :guilabel:`Product Type` to `Storable Product` under the " +":guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst-1 +msgid "Configure a product for reordering in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:32 +msgid "Add a reordering rule to a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:34 +msgid "" +"After properly configuring a product, a reordering rule can be added to it " +"by selecting the now visible :guilabel:`Reordering Rules` tab at the top of " +"that product's form, and then clicking :guilabel:`Create` on the " +":guilabel:`Reordering Rules` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst-1 +msgid "Access reordering rules for a product from the product page in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:42 +msgid "" +"Once created, the reordering rule can be configured to generate purchase " +"orders automatically by defining the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:45 +msgid "" +":guilabel:`Location` specifies where the ordered quantities should be stored" +" once they are received and entered into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:47 +msgid "" +":guilabel:`Min Quantity` sets the lower threshold for the reordering rule " +"while :guilabel:`Max Quantity` sets the upper threshold. If the stock on " +"hand falls below the minimum quantity, a new purchase order will be created " +"to replenish it up to the maximum quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:52 +msgid "" +"If :guilabel:`Min Quantity` is set to `5` and :guilabel:`Max Quantity` is " +"set to `25` and the stock on hand falls to four, a purchase order will be " +"created for 21 units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:55 +msgid "" +":guilabel:`Multiple Quantity` can be configured so that products are only " +"ordered in batches of a certain quantity. Depending on the number entered, " +"this can result in the creation of a purchase order that would put the " +"resulting stock on hand above what is specified in the :guilabel:`Max " +"Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:61 +msgid "" +"If :guilabel:`Max Quantity` is set to `100` but :guilabel:`Multiple " +"Quantity` is set to order the product in batches of `200`, a purchase order " +"will be created for 200 units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:65 +msgid "" +":guilabel:`UoM` specifies the unit of measurement by which the quantity will" +" be ordered. For discrete products, this should be set to `Units`. However, " +"it can also be set to units of measurement like `Volume` or `Weight` for " +"non-discrete products like water or bricks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst-1 +msgid "Configure the reordering rule in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:74 +msgid "Manually trigger reordering rules using the scheduler" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:76 +msgid "" +"Reordering rules will be automatically triggered by the scheduler, which " +"runs once a day by default. To trigger reordering rules manually, navigate " +"to :menuselection:`Inventory --> Operations --> Run Scheduler`. On the pop-" +"up window, confirm the manual action by clicking :guilabel:`Run Scheduler`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:82 +msgid "" +"Manually triggering reordering rules will also trigger any other scheduled " +"actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:85 +msgid "Manage reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:87 +msgid "" +"To manage the reordering rules for a single product, navigate to that " +"product page's form and select the :guilabel:`Reordering Rules` tab at the " +"top of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:90 +msgid "" +"To manage all reordering rules for every product, go to " +":menuselection:`Inventory --> Configuration --> Reordering Rules`. From this" +" dashboard, typical bulk actions in Odoo can be performed such as exporting " +"data or archiving rules that are no longer needed. As well, the " +":guilabel:`Filters`, :guilabel:`Group By` or triple-dotted menu on the form " +"are available to search for and/or organize the reordering rules as desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:3 +msgid "Purchase in different units of measure than sales" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:5 +msgid "" +"When you purchase a product, it may happen that your vendor uses a different" +" unit of measure than you do when you sell it. This can cause confusion " +"between sales and purchase representatives. It is also time-consuming to " +"convert measures manually every time. With Odoo, you can configure your " +"product once and let Odoo handle the conversion." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:10 +msgid "Consider the following examples:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:12 +msgid "" +"You purchase orange juice from an American vendor, and they use **gallons**." +" However, your customers are European and use **liters**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:15 +msgid "" +"You buy curtains from a vendor in the form of **rolls** and you sell pieces " +"of the rolls to your customers using **square meters**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:19 +msgid "Enable units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:21 +msgid "" +"Open your Sales app and go to :menuselection:`Configuration --> Settings`. " +"Under Product Catalog, enable *Units of Measure*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Enable the units of measure option in Odoo Sales" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:29 +msgid "Specify sales and purchase units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:32 +msgid "Standard units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:34 +msgid "" +"A variety of units of measure are available by default in your database. " +"Each belongs to one of the five pre-configured units of measure categories: " +"*Length / Distance*, *Unit*, *Volume*, *Weight* and *Working Time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:39 +msgid "" +"You can create your new units of measure and units of measure categories " +"(see next section)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:41 +msgid "" +"To specify different units of measures for sales and purchases, open the " +"Purchase app and go to :menuselection:`Products --> Products`. Create a " +"product or select an existing one. Under the product's *General Information*" +" tab, first select the *Unit of Measure* to be used for sales (as well as " +"for other apps such as inventory). Then, select the *Purchase Unit of " +"Measure* to be used for purchases." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:47 +msgid "" +"Back to the first example, if you purchase orange juice from your vendor in " +"**gallons** and sell it to your customers in **liters**, first select *L* " +"(liters) as the *Unit of Measure*, and *gal (US)* (gallons) as the *Purchase" +" Unit of Measure*, then click on *Save*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Configure a product's units of measure in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:56 +msgid "Create new units of measure and units of measure categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:58 +msgid "" +"Sometimes you need to create your own units and categories, either because " +"the measure is not pre-configured in Odoo or because the units do not relate" +" with each other (e.g. kilos and centimeters)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:62 +msgid "" +"If you take the second example where you buy curtains from a vendor in the " +"form of **rolls** and you sell pieces of the rolls using **square meters**, " +"you need to create a new *Units of Measure Category* in order to relate both" +" units of measure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:66 +msgid "" +"To do so, go to :menuselection:`Configuration --> Units of Measure " +"Categories`. Click on *Create* and name the category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Create a new units of measure category in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:73 +msgid "" +"The next step is to create the two units of measures. To do so, go to " +":menuselection:`Configuration --> Units of Measure`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:76 +msgid "" +"First, create the unit of measure used as the reference point for converting" +" to other units of measure inside the category by clicking on *Create*. Name" +" the unit and select the units of measure category you just created. For the" +" *Type*, select *Reference Unit of Measure for this category type*. Enter " +"the *Rounding Precision* you would like to use. The quantity computed by " +"Odoo is always a multiple of this value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:82 +msgid "" +"In the example, as you cannot purchase less than 1 roll and won't use " +"fractions of a roll as a unit of measure, you can enter 1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Create a new reference unit of measure in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:89 +msgid "" +"If you use a *Rounding Precision* inferior to 0.01, a warning message might " +"appear stating that it is higher than the *Decimal Accuracy* and that it " +"might cause inconsistencies. If you wish to use a *Rounding Precision* lower" +" than 0.01, first activate the :ref:`developer mode `, then " +"go to :menuselection:`Settings --> Technical --> Database Structure --> " +"Decimal Accuracy`, select *Product Unit of Measure* and edit *Digits* " +"accordingly. For example, if you want to use a rounding precision of " +"0.00001, set *Digits* to 5." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:96 +msgid "" +"Next, create a second unit of measure, name it, and select the same units of" +" measure category as your reference unit. As *Type*, select *Smaller* or " +"*Bigger than the reference Unit of Measure*, depending on your situation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:100 +msgid "" +"As the curtain roll equals to 100 square meters, you should select " +"*Smaller*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:102 +msgid "" +"Next, you need to enter the *Ratio* between your reference unit and the " +"second one. If the second unit is smaller, the *Ratio* should be greater " +"than 1. If the second unit is larger, the ratio should be smaller than 1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:106 +msgid "For your curtain roll, the ratio should be set to 100." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Create a second unit of measure in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:112 +msgid "" +"You can now configure your product just as you would using Odoo's standard " +"units of measure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Set a product's units of measure using your own units in Odoo Purchase" +msgstr "" diff --git a/locale/pl/LC_MESSAGES/marketing.po b/locale/pl/LC_MESSAGES/marketing.po new file mode 100644 index 000000000..e054596d7 --- /dev/null +++ b/locale/pl/LC_MESSAGES/marketing.po @@ -0,0 +1,4284 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"PO-Revision-Date: 2021-11-02 08:49+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications/marketing.rst:5 +msgid "Marketing" +msgstr "" + +#: ../../content/applications/marketing/events.rst:5 +msgid "Events" +msgstr "" + +#: ../../content/applications/marketing/events.rst:8 +msgid "`Odoo Tutorials: Events `_" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:3 +msgid "Event essentials" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:5 +msgid "" +"Odoo Events provides event coordinators with an arsenal of planning, " +"communications, and reporting tools to create immersive and engaging " +"experiences for customers. Namely, staff can create and publish events on " +"their website, sell tickets online, scan tickets with Odoo barcode, send out" +" automated emails, and generate rich reporting data once the event accepts " +"registrations." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:11 +msgid "Kanban concepts and organization" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:13 +msgid "" +"To get started, click on the :guilabel:`Events` application on the home " +"dashboard, which then leads to the kanban view populated with a variety of " +"pipeline stages. Key information is listed on each event card, such as the " +"date/time of the event, along with the number of expected (and confirmed) " +"attendees." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:18 +msgid "" +"To create a new stage, click :guilabel:`Add a Column` and provide a " +"befitting title to reflect the purpose of that stage." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:21 +msgid "" +"To reorganize the stages, just drag-and-drop them until they are in the " +"correct order. Stages can also be “folded” in the kanban for a cleaner " +"presentation, via the :guilabel:`Settings` menu to the right of each stage's" +" title, which is represented by a gear icon." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:26 +msgid "" +"The gear icon, by default, is hidden and will appear next to the " +":guilabel:`+` icon when moused over." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:29 +msgid "When clicked, a drop-down menu of settings will appear." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "Overview of events setting with the kanban view in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:36 +msgid "Create a new event" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:38 +msgid "" +"To create an event, click :guilabel:`Create` from the Events dashboard. Odoo" +" will then direct the page to a blank event template form." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:41 +msgid "" +"From the event form, fill out the necessary fields, either by choosing from " +"existing data in the Odoo database or by creating and editing new field " +"data. Key information to enter for the event includes:" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:45 +msgid ":guilabel:`Event Name`: give the event a title." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:46 +msgid "" +":guilabel:`Date`: includes the start and end dates/times for the event." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:47 +msgid "" +":guilabel:`Timezone`: covers the timezone for when the event is taking " +"place." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:48 +msgid "" +":guilabel:`Template`: choose from a pre-built event template or build a " +"custom one and connect it here." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:50 +msgid "" +":guilabel:`Tags`: add tags to indicate briefly what the event is for (e.g. " +"`tradeshow`). Tags help better organize event cards in the kanban and are " +"useful when using search filters during reporting periods." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:53 +msgid "" +":guilabel:`Organizer`: detail the organizer(s) for the event. This field is " +"usually the company that owns the Odoo database, or a vendor." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:55 +msgid "" +":guilabel:`Responsible`: name the point person who is responsible for " +"organizing the event." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:56 +msgid "" +":guilabel:`Website`: indicate which Odoo website(s) the event event should " +"be published to." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:57 +msgid "" +":guilabel:`Venue`: list the venue details here if it's a new record, or " +"choose from an existing location." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:59 +msgid "" +":guilabel:`Limit Registrations`: when enabled, this setting caps the " +"attendee registrations to a specified amount" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:61 +msgid "" +":guilabel:`Autoconfirmation`: when enabled, this setting skips the " +"confirmation request that gets sent by email to event registrants, and " +"automatically confirms their registration." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:64 +msgid "" +"Once the fields in the event form are set, move on to the " +":guilabel:`Tickets` and :guilabel:`Communication` tabs, and optionally the " +":guilabel:`Questions` tab if registrations should require additional " +"information." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:69 +msgid "Add and sell event tickets" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:71 +msgid "" +"Under the :guilabel:`Tickets` tab, add line items for each type of ticket " +"the event plans to offer. Here, determine the ticket price, start/end dates " +"for registrations, as well as the maximum number of tickets that can be " +"sold." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:75 +msgid "" +"If selling tickets isn't necessary for the event, a simple " +":guilabel:`Registration` button will be displayed on the event's page by " +"default." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of the ticket tab in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:83 +msgid "Send automated emails, text, and social posts to event attendees" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:85 +msgid "" +"Under the :guilabel:`Communication` tab, configure personalized email, SMS, " +"or social post messages to keep in touch with event attendees. For each " +"communication, click :guilabel:`Add a line` in the :guilabel:`Communication`" +" tab form, and then choose (or create) a communications template using the " +"drop-down menu under the :guilabel:`Template` column." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:90 +msgid "" +"Next, define the :guilabel:`Interval` and :guilabel:`Unit` of time for how " +"often the communication should be sent; use these time fields to specify the" +" frequency of :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or " +":guilabel:`Months` communications should be sent. There is also the option " +"to send communications `Immediately` after a specified :guilabel:`Trigger` " +"is activated." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:96 +msgid "" +"In the last column, determine the :guilabel:`Trigger` which controls how and" +" when the communication is sent. For this action, choose between: " +":guilabel:`Before the event`, :guilabel:`After each registration`, or " +":guilabel:`After the event`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of the communication tab in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:105 +msgid "Attach a questionnaire to event registrations" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:107 +msgid "" +"Implementing a questionnaire during event sign up is an effective way to " +"gauge the wants, needs, and interests of the event's attendees ahead of " +"time. Questionnaires also act as informative analytics tools for reporting " +"periods before (or after) events take place." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:111 +msgid "" +"To create a questionnaire, from the :guilabel:`Events` application, navigate" +" to :menuselection:`Configuration --> Settings` and then enable the " +":guilabel:`Questions` setting." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:114 +msgid "" +"With the setting enabled, questions and answers can now be added (and " +"recorded) under the the :guilabel:`Questions` tab back on the event form. " +"For each question, specify if it should only be asked once with the " +":guilabel:`Ask once per order` checkbox, or if the question requires a " +":guilabel:`Mandatory Answer`, which will make the question required for " +"registration." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:120 +msgid "" +"If the :guilabel:`Once per order` checkbox is enabled, then a single " +"registration for 3 event attendees will show the questionnaire only once." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:123 +msgid "" +"There are two :guilabel:`Question Types` to choose from: " +":guilabel:`Selection` and :guilabel:`Text Input`. The :guilabel:`Selection` " +"type, allows attendees to select an answer from pre-configured options, " +"which are entered in the :guilabel:`Answers` tab below. The :guilabel:`Text " +"Input` type allows attendees to write in their own answer to the question in" +" a text box." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of an event form, open the questions tab, and add a question." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:133 +msgid "Log internal notes or add ticket instructions" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:135 +msgid "" +"In the :guilabel:`Notes` tab, there is the option to add a :guilabel:`Note` " +"and/or :guilabel:`Ticket instructions`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:138 +msgid "" +"Under :guilabel:`Note`, internal notes can be left (such as: to-do lists, " +"contact information, etc.) for event staff to reference. In the " +":guilabel:`Ticket instructions` field, helpful information for staff and " +"attendees can be shared (like, directions to the venue, opening/closing " +"times, etc.)" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:144 +msgid "" +"Type `/` in either text field (:guilabel:`Note` or :guilabel:`Ticket " +"instructions`) to reveal a sub-menu of :guilabel:`Structure` options. These " +"options provide various formatting options to ensure vital internal " +"information is organzied for event staff to review." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of the Notes tab in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:153 +msgid "Invite attendees to the event" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:155 +msgid "" +"To invite people to an event, click the :guilabel:`Invite` button located in" +" the top left corner of the event form." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:158 +msgid "" +"Inside the invite template form, are options to sent email or SMS invites. " +"Each message can be fully customized, and recipients can be added." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:161 +msgid "" +"Adding a :guilabel:`Subject` line for the invite message is required, but " +"the :guilabel:`Preview Text` field is optional. The :guilabel:`Preview Text`" +" is a catchy preview sentence meant to encourage recipients to open the " +"email." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:166 +msgid "" +"In most cases, the :guilabel:`Preview Text` is displayed next to the " +"subject. Keep this field empty to ensure the first characters of the email " +"content appear, instead." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:170 +msgid "Select invitees and configure recipient filters" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:172 +msgid "" +"In the middle of the invitation form, find and click the " +":guilabel:`Recipients` field, to reveal a drop-down menu of recipient " +"options. These choices represent where Odoo will find the desired " +"recipients' information." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:176 +msgid "" +"Once an option from this menu is selected (e.g. :guilabel:`Applicant`, " +":guilabel:`Contact`, :guilabel:`Event Registration`, " +":guilabel:`Lead/Opportunity`, etc.), Odoo will send the invitation to all " +"recipients who match that initial rule. Additional rules can be added to " +"narrow down the target recipients, by clicking :guilabel:`Add Filter`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "" +"View of the add filter button beneath the recipients field in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:185 +msgid "" +"Clicking :guilabel:`Add Filter` reveals three fields, formatted like an " +"equation. To reveal the sub-menu options, click each field, and make the " +"desired selections, until the preferred configuration has been acheived. The" +" number of :guilabel:`Records` that match the rule(s) are indicated to the " +"right of the :guilabel:`Recipients` field, in green." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:191 +msgid "" +"Some sub-menu options in the first rule field allow for a second choice to " +"provide even more specificity." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:194 +msgid "" +"To the right of each rule, are :guilabel:`x`, :guilabel:`+`, and " +":guilabel:`...` icons. The :guilabel:`x` icon deletes a specific node (line)" +" of the rule. The :guilabel:`+` icon adds a node (line) to the rule. And, " +"the :guilabel:`...` icon adds a branch to the node. A branch means two " +"additional, indented sub-nodes are added to the rule, providing even more " +"specificity to the line above it." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:201 +msgid "Build a custom event invite" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:203 +msgid "" +"In the :guilabel:`Mail Body` tab, there are a number of pre-configured " +"message templates to choose from. Select the desired template, and modify " +"every element of its design details with Odoo's drag-and-drop web builder, " +"located on the right sidebar." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "" +"View of the drag and drop building blocks used to customize event invite " +"emails." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:212 +msgid "" +"To build an email event invite from scratch, select the :guilabel:`Plain " +"Text` template, and Odoo will provide a blank email canvas, which can be " +"customized either by using the front-end rich text editor that accepts slash" +" (`/`) commands, or the XML code editor when :ref:`developer mode " +"` is engaged and the :guilabel:`` icon is pressed." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:218 +msgid "" +"The :guilabel:`Mail Body` tab (and template options), are only available if " +"the event invite :guilabel:`Mailing Type` is designated as an " +":guilabel:`Email`. If :guilabel:`SMS` is the :guilabel:`Mailing Type`, a " +":guilabel:`SMS Content` tab (consisting of a blank text space), is " +"available, instead." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:224 +msgid "Modify event invite settings" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:226 +msgid "" +"The options under the :guilabel:`Settings` tab are different, depending on " +"the specified :guilabel:`Mailing Type`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:229 +msgid "" +"If the :guilabel:`Email` option is selected as the :guilabel:`Mailing Type`," +" an employee can be designated as the :guilabel:`Responsible`, meaning that " +"person is the one responsible for this particular invite message. " +":guilabel:`Send From` and :guilabel:`Reply To` email aliases can be " +"designated here, as well." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:234 +msgid "" +"Also, if any specific documents are required (or helpful) for this event " +"invite, they can be sent along with this email, by clicking " +":guilabel:`ATTACH A FILE`, and adding the appropriate document(s)." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:238 +msgid "" +"If the :guilabel:`SMS` option is selected as the :guilabel:`Mailing Type`, a" +" :guilabel:`Responsible` can be designated, and the option to " +":guilabel:`Include an opt-out link` is available." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:242 +msgid "Send event invitations to recipients" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:244 +msgid "" +"If the selected :guilabel:`Mailing Type` is :guilabel:`Email`, there are " +"three options to send the invite: :guilabel:`Send`, :guilabel:`Schedule`, " +"and :guilabel:`Test`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:247 +msgid "" +"The :guilabel:`Send` option sends the invite right away. The " +":guilabel:`Schedule` option reveals a pop-up, in which a scheduled date/time" +" can be selected for the email to be sent. The :guilabel:`Test` option " +"reveals a :guilabel:`Test Mailing` pop-up, where specific recipient email " +"addresses can be entered for Odoo to send them the current version of the " +"mailing for review before officially sending it out to prospective event " +"attendees." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:253 +msgid "" +"If the selected :guilabel:`Mailing Type` is :guilabel:`SMS`, there are four " +"options to send the invite: :guilabel:`Put in Queue`, :guilabel:`Send Now`, " +":guilabel:`Schedule`, and :guilabel:`Test`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:256 +msgid "" +"The :guilabel:`Put in Queue` option schedules an SMS message to all " +"recipients (that match the designated rules, if any) in the near future. " +"Clicking :guilabel:`Put in Queue` reveals a pop-up, requiring confirmation. " +"When confirmed, a blue banner appears on the event invite template form, " +"indicating that the SMS will be sent later that day." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:262 +msgid "" +"The :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test` options" +" all function the same way for both :guilabel:`Mailing Type` options." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:266 +msgid "Publish events" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:268 +msgid "" +"Until an event is published, it will remain hidden from public view on the " +"website and registering for it will not be possible. To publish an event, " +"navigate to it either from the back end of Odoo through the " +":guilabel:`Events` application, or access the hidden event page through the " +"front end as either a priveliged user or administrator." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:273 +msgid "" +"If navigating from the back end, go to the event form, and click the " +":guilabel:`Go to Website` smart button to reach the event page on the " +"website (on the front end). If starting from the front end, simply navigate " +"to the event page that needs to be published." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:277 +msgid "" +"No matter the route, an event page can only be published from the front end." +" In the upper right corner of the event page on the website, toggle the " +"switch from the red :guilabel:`Unpublished` status to the green " +":guilabel:`Published` status. Doing so instantly makes the event page " +"accessible to the public on the website." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "" +"View of a website page and the option to publish the event in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:3 +msgid "Sell tickets" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:5 +msgid "" +"Create custom ticket tiers (with various price points) for potential " +"attendees to choose from, directly on the event template form, under the " +":guilabel:`Tickets` tab. Odoo simplifies the ticket-purchasing process by " +"providing plenty of payment method options." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:10 +#: ../../content/applications/marketing/events/track_manage_talks.rst:9 +msgid "Configuration" +msgstr "Konfiguracja" + +#: ../../content/applications/marketing/events/sell_tickets.rst:12 +msgid "" +"First, in order to enable the creation (and selling of) event tickets, go to" +" :menuselection:`Configuration --> Settings`, then enable the " +":guilabel:`Tickets` and :guilabel:`Online Ticketing` features." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:16 +msgid "" +"The :guilabel:`Tickets` feature allows tickets to be sold for an event." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:18 +msgid "" +"The :guilabel:`Online Tickets` feature allows for the sale of tickets to " +"occur through the website." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:21 +msgid "" +"If these options are *not* enabled, a default :guilabel:`Register` button " +"will be available for free registrations." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "View of the settings page for Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:29 +msgid "Sell tickets through sales orders" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:31 +msgid "" +"In the :guilabel:`Sales` application, choose a previously-created Event " +"Registration (as if it were a product), and add it as a product line. Upon " +"adding the registration, a pop-up appears, which allows for the selection of" +" a specific event (and ticket tier). That specific event ticket is then " +"attached to the sales order." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "" +"View of a sales order and option to choose the specific event in Odoo " +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:40 +msgid "" +"Events with tickets sold online or through sales orders have a " +":guilabel:`Sales Smart Button` shortcut, located at the top of the event " +"template form (in the :guilabel:`Events` application)." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:43 +msgid "" +"Clicking the :guilabel:`Sales Smart Button` reveals a page with all the " +"sales orders related to that event." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "View of an event's form and the sales smart button in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "" +"View of an event form highlighting the column product under the tickets tab in Odoo\n" +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:56 +msgid "Sell tickets through the website" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:58 +msgid "" +"With tickets purchased through the website, the process is similar to " +"creating a :guilabel:`Sales Order` with a specific :guilabel:`Registration` " +"product. Here, tickets are added to a virtual cart, and the transaction can " +"be completed as usual - utilizing any of the pre-configured payment methods " +"options that have been set up on the website." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:63 +msgid "" +"The completed purchase is automatically produced in a :guilabel:`Sales " +"Order`, which can be easily accessed in the back end of the database." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "View of website transaction for Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:3 +msgid "Track and manage talks" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:5 +msgid "" +"With Odoo Events, it's possible to provide attendees with the power to " +"propose presenters to speak at events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:11 +msgid "" +"First, go to :menuselection:`Events --> Configuration --> Settings` and " +"enable :guilabel:`Schedule & Tracks`." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:14 +msgid "" +"When that feature is enabled, two more options become available: *Live " +"Broadcast* and *Event Gamification*." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:17 +msgid "" +":guilabel:`Live Broadcast` allows for the airing of tracks online through a " +"YouTube integration." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:19 +msgid "" +":guilabel:`Event Gamification` allows for the sharing of a quiz with your " +"attendees, once a track (talk) is over." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:23 +msgid "" +":guilabel:`Event Gamification` isn't necessary for tracks to appear on the " +"event page on the website, but it can enhance the engagement and overall " +"enjoyablity of the event for attendees." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:27 +msgid "Talks, talk proposals, and agenda" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:29 +msgid "" +"Once those two features are enabled, the following links are automatically " +"added to the sub-header menu, located on the event page on the website: " +":guilabel:`Talks`, :guilabel:`Talk Proposals`, and :guilabel:`Agenda`. Any " +"attendee can freely access these menu items and their corresponding content." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:33 +msgid "" +"The :guilabel:`Talks` link takes the attendee to a page full of all the " +"talks for that event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:35 +msgid "" +"The :guilabel:`Talks Proposals` link takes the attendee to a form page, " +"where they can propose talks for the event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:38 +msgid "" +"The :guilabel:`Agenda` link takes the attendee to a page with all the talks " +"for the event, but in a calendar/time-slot format." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "" +"View of the published website and the talks, talk proposals, and agenda in " +"Odoo Events" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:46 +msgid "Manage talk proposals" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:48 +msgid "" +"When attendees fill out and submit a talk proposal form on the website, a " +"new :guilabel:`Proposal` is instantly created in the back end for the event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:52 +msgid "" +"All talks (Proposals, Confirmed, Announced, etc.) are accessible via the " +":guilabel:`Tracks` smart button on the event form." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "" +"View of the talks' proposals page emphasizing the column proposal in Odoo " +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:59 +msgid "" +"If a proposal is accepted, move the :guilabel:`Event Track` to the " +"appropriate stage in the Kanban view (e.g. `Confirmed`, etc.). Then, go to " +"that particular event's template form, and click the :guilabel:`Go to " +"Website` smart button to reach that specific talk's page on the website." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:63 +msgid "" +"In the upper right corner, toggle the switch from :guilabel:`Unpublished` to" +" :guilabel:`Published`, and the talk is instantly accessible on the website." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:67 +msgid "Without publishing a talk, attendees will never be able to access it." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "View of the website page to publish a proposed talk for Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:74 +msgid "Attendees list and attendance" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:76 +msgid "" +"Once attendees have registered for a specific event, they are added to the " +":guilabel:`Attendee List` for that event, which is accessible via the " +":guilabel:`Attendees` smart button on the event template form, or " +":menuselection:`Reporting --> Attendees` and sorted by event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:81 +msgid "" +"When an attendee arrives at the event, they will be marked as attending " +"(:guilabel:`Confirmed Attendance`), and the status of that attendee will " +"change to :guilabel:`Attended.`" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "Overview of events with the kanban view in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:88 +msgid "" +"When analyzing an :guilabel:`Attendees list`, Odoo provides different ways " +"to view the information. Each view option presents the same information, but" +" in a slightly different layout. To change the view, click on the icons in " +"the upper right hand of the screen." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "Various view options on the attendees list page." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:96 +msgid "" +"In the :guilabel:`Kanban` view, it can be confirmed whether the attendees " +"have already paid or remain unpaid." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:99 +msgid "" +"The :guilabel:`List` view provides information in a more traditional list " +"formation." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:101 +msgid "" +"The :guilabel:`Calendar` view provides a clear schedule visualization of " +"which attendees are arriving on specific dates of the event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:104 +msgid "" +"The :guilabel:`Graph` view provides graphical representations of that " +"event's attendees, along with numerous filters and customizable measures for" +" deeper analysis." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:107 +msgid "" +"The :guilabel:`Cohort` view lays out attendee data to better analyze the " +"number of registration dates." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:111 +msgid "" +"Tickets sold through sales orders validate attendees as soon as the " +"quotation is confirmed." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:114 +msgid "Manage registrations" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:116 +msgid "" +"Upon selecting an attendee, Odoo reveals that specific attendee's detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:118 +msgid "" +"From here, event badges can be sent manually, by selecting :guilabel:`Send " +"By Email`. The :guilabel:`Attendee` can also be marked as " +":guilabel:`Attended`, or the registration can be canceled altogether via the" +" :guilabel:`Cancel Registration` button." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "" +"View of an attendee form emphasizing the send by email and cancel registration in Odoo\n" +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:128 +msgid "Lead Generation Rules" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:130 +msgid "With Odoo, leads can be generated from events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:132 +msgid "" +"To create and configure a :guilabel:`Lead Generation Rule` related to " +"events, navigate to :menuselection:`Events app --> Configuration --> Lead " +"Generation`." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:135 +msgid "" +"On the :guilabel:`Lead Generation Rule` page, every configured " +":guilabel:`Lead Generation Rule` can be found, along with pertinent data " +"related to those rules." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "How the Lead Generation Rule page looks in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:142 +msgid "" +"To create a new :guilabel:`Lead Generation Rule`, click :guilabel:`Create`, " +"and fill out the :guilabel:`Lead Generation Rule` form." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "How the Lead Generation Rule template looks in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:149 +msgid "" +"After naming the rule, configure *how* the lead should be created (either " +":guilabel:`Per Attendee` or :guilabel:`Per Order`), and *when* they should " +"be created, (when :guilabel:`Attendees are created`, when " +":guilabel:`Attendees are confirmed`, or when :guilabel:`Attendees attended` " +"the event)." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:154 +msgid "" +"In the :guilabel:`For any of these Events` section, there are fields to " +"attach this rule to any specific event categories, company, and/or event. To" +" add even more specificity to the rule, a domain filter rule can be " +"configured to ensure the rule only applies to a specific target audience of " +"attendees (found in the :guilabel:`If the Attendees meet these Conditions` " +"section)." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:159 +msgid "" +"Lastly, in the :guilabel:`Lead Default Values` section, designate a " +":guilabel:`Lead Type`, then assign it to a specific :guilabel:`Sales Team` " +"(and/or :guilabel:`Salesperson`), and attach tags to the rule, if necessary." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation.rst:8 +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:3 +msgid "Marketing Automation" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation.rst:11 +#: ../../content/applications/marketing/sms_marketing.rst:11 +#: ../../content/applications/marketing/social_marketing.rst:11 +msgid "" +"`Odoo Tutorials: Marketing `_" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:3 +msgid "Understanding metrics" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:5 +msgid "" +"Metrics are detailed statistics that measure the progress (and success) of " +"marketing campaigns. When creating marketing activities in a workflow, Odoo " +"will visually display various metrics related to the campaign with graphs " +"and data." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:9 +msgid "Consider the following example:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "An example of a marketing automation campaign in Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:15 +msgid "" +"In this case, the :guilabel:`Target` of this campaign is set to " +":guilabel:`Lead/Opportunity` and was narrowed down to only focus on the " +"Leads (or Opportunities) whose :guilabel:`Tag Name` contain a value of " +"`product` and they *also* have an email address set up in the database." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:19 +msgid "" +"Beneath the filter nodes, Odoo will display how many records in the database" +" fall into the previously-specified criteria filter. In this example, there " +"are 18 records in the database that match the criteria." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "" +"Lead generation filters used to refine records on marketing automation " +"campaigns in Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:27 +msgid "" +"At the top of the marketing automation form, there are a series of smart " +"buttons. The :guilabel:`Participations` smart button in this example " +"indicates that, out of those 18 records, 25 have become participants. In " +"other words, they have matched the criteria, and have already interacted " +"with the campaign in one way or another." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:33 +msgid "" +":guilabel:`Records` represent a real-time number. Therefore, while the " +"workflow is running, changes in opportunity records (deletions, additions, " +"adjustments) may occur. This means there will be real-time updates to the " +"number of :guilabel:`Records`, but such updates do *not* change the number " +"of :guilabel:`Participants`, as the metric *will not* exclude opportunities " +"that have already been set as :guilabel:`Participants` before - Odoo will " +"just add new ones. That's why the number of :guilabel:`Records` can be " +"different from the number of :guilabel:`Participants` from time to time." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "" +"Difference between real-time record count and total participants on a " +"markeing campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:45 +msgid "" +"Whenever the system runs, updating numbers and triggering actions, it will " +"look at the :guilabel:`Target` model, and check if new :guilabel:`Records` " +"have been added (or modified), which always keeps the flow up-to-date." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:50 +msgid "" +"The filter here is applied to *all* activities. Leads that lose that " +"specific :guilabel:`Tag` in the meantime will be excluded from later " +"activities." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:54 +msgid "" +"Filters can also be applied to individual activities, in the " +":guilabel:`Domain` section of the activity pop-up form. Use this feature to " +"specify an individual filter that will only be performed if the records " +"satisfy *both* filter criteria - the activity filter and its specific domain" +" filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:59 +msgid "" +"(*Example*: when configuring an SMS activity, make sure a certain phone " +"number is set, in order to avoid triggering a SMS that would never be sent.)" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 +msgid "" +"A relevant targeting filter that applies to a type of individual activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:66 +msgid "" +":guilabel:`Success` represents the number of times the searching for " +"participants - who match the criteria filter(s) of that activity - was " +"performed successfully, in relation to the total number of participants. If " +"a participant does *not* match the conditions, it will be added to " +":guilabel:`Rejected`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "" +"Overview showing participants who do or do not match filtering criteria on " +"an activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:75 +msgid "" +"Hovering over the graph, Odoo displays the number of successful and rejected" +" participants, per day, over the last 15 days." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:79 +msgid "" +"Whenever a new record is added to the :guilabel:`Target` model, it will " +"automatically be added to the workflow, and it will start the workflow from " +"the beginning (:guilabel:`Parent Action`)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started.rst:5 +msgid "Getting Started" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:5 +msgid "" +"The Odoo Marketing Automation app automates a variety of marketing tasks by " +"combining specific rules and filters to generate timed actions. Instead of " +"manually having to build each stage of a campaign (such as a series of timed" +" massmails), the Marketing Automation app allows marketers to build the " +"entire campaign, and all of its stages, in one place on one dashboard." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:11 +msgid "Create a campaign" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:13 +msgid "" +"To create a new automated marketing campaign, open the :guilabel:`Marketing " +"Automation` app and click :guilabel:`Create`. On the :guilabel:`Campaign` " +"page, there are the following smart buttons and fields:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "" +"A dashboard showing the creation of a new marketing automation campaign in " +"Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:21 +msgid "" +":guilabel:`Templates`: represents the number of pre-configured mail " +"templates being used in this particular campaign. (Templates can always be " +"created on-the-fly as well)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:23 +msgid "" +":guilabel:`SMS`: represents the number of personalized SMS messages " +"connected to this campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:24 +msgid "" +":guilabel:`Clicks`: represents the number of times attached links have been " +"clicked by recipients of this campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:26 +msgid "" +":guilabel:`Participants`: represents the number of contacts that have " +"directly participated in this campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:28 +msgid "" +":guilabel:`Target`: this field is a drop-down menu to choose which model is " +"targeted by this campaign (i.e., by Contacts, Sales Order, Lead/Opportunity," +" etc.)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:32 +msgid "Campaign filters" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:34 +msgid "" +"To add a filter to the target audience, click :guilabel:`Add Filter`, and a " +"node field will appear. In the node field, a custom equation can be " +"configured for Odoo to use when filtering who to include (and exclude) in " +"this specific marketing campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "A filter node in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:42 +msgid "" +"When the first field of the node is clicked, a nested drop-down menu of " +"options appears on the screen where specific criteria is chosen based on " +"needs of the campaign. The remaining fields on the node further define the " +"criteria which determines which records to include (or exclude) in the " +"execution of the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:47 +msgid "" +"To add another node, simply click the :guilabel:`+ (plus sign)` icon to the " +"right of the filtering rule. To add a branch of multiple nodes at the same " +"time, click the :guilabel:`... (ellipses)` icon." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:51 +msgid "" +"For further information on filters, refer to :doc:`this documentation page " +"`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:54 +msgid "" +":guilabel:`Records` represent the number of contacts in the system that fit " +"the specified criteria for a campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:58 +msgid ":doc:`testing_running`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:59 +msgid ":doc:`workflow_activities`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:3 +msgid "Target an audience" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:5 +msgid "" +"Delivering marketing campaigns to the right audience is paramount when " +"trying to grow a business. The Odoo *Marketing Automation* application helps" +" marketers to do just that by providing detailed filtering tools, which can " +"be as simple (or as complex) as necessary, to reach the right customers at " +"the right time." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:11 +msgid "Configure target filters" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:13 +msgid "" +"When configuring the target filters on a marketing campaign, there are some " +"options that have an :guilabel:`> (arrow)` icon beside them. The " +":guilabel:`> (arrow)` icon signifies that the particular filter has more " +"refined parameters within it that can be customized." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst-1 +msgid "The drop-down filter menu in the Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:21 +msgid "" +"Filters can be extended by adding *branches* and *nodes*. A *node* adds " +"another filtering parameter to a group of targeting conditions (e.g. a new " +"line), and a *branch* creates a narrowly refined cluster of parameters, " +"allowing filters to be grouped with :guilabel:`ANY` or :guilabel:`ALL` " +"statements." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:26 +msgid "Every time a new branch is created, there are two options:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:28 +msgid "" +"Either the records can match :guilabel:`ALL` criteria for the upcoming rules" +" (creating an AND statement where *all* criteria must match)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:30 +msgid "" +"Or, the records can match :guilabel:`ANY` criteria for the upcoming rules " +"(creating an OR statement where *only one* of the criteria must match)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:33 +msgid "" +"To change between these two options, simply click the drop-down arrow icon " +"in the green box and select :guilabel:`ANY` or :guilabel:`ALL`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:36 +msgid "" +"To add a node, click on the :guilabel:`➕ (plus sign)` icon, and to add " +"another branch click on the :guilabel:`⋯ (ellipses)` icon. To exclude a node" +" or a branch, click on :guilabel:`✖ (delete)` icon to delete it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:45 +msgid "Use cases" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:47 +msgid "" +"The following scenarios outline different combinations of filters a " +"marketing campaign might commonly use." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:51 +msgid "Scenario #1: Narrow target down to new opportunities in the pipeline" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:53 +msgid "" +"While in *Edit mode* on a campaign template form (by clicking the " +":guilabel:`Edit` button), select the :guilabel:`Target` field, and click " +":guilabel:`Search More` from the drop-down menu. Then, search for " +":guilabel:`Lead/Opportunity`, and select it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:57 +msgid "" +"Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Then, " +"click on the default :guilabel:`ID` filter option in the first portion of " +"the filter equation. Doing so reveals a drop-down menu full of filter " +"options. From this drop-down, scroll down (or search for) :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:62 +msgid "" +"Keep the second portion of the filter equation on the default :guilabel:`🟰 " +"(equal sign)` icon." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:64 +msgid "" +"Next, change the third (and final) portion of the filter equation from " +":guilabel:`Lead` to :guilabel:`Opportunity`. The number of " +":guilabel:`Records` that fit this specific filter equation changes as the " +"equation is customized." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:68 +msgid "" +"Add another node to this filter by clicking the :guilabel:`➕ (plus sign)` " +"icon to the right of the equation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:71 +msgid "" +"With \"new\" opportunities being the target of this filter, the second node " +"will focus on *only* locating opportunities that are in the :guilabel:`New` " +"stage of the pipeline. To do that, select the default :guilabel:`ID` from " +"the first portion of the second filter equation, and scroll down (or search " +"for) :guilabel:`Stage` from the field drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:76 +msgid "" +"Once again, leave the second portion of the filter equation on :guilabel:`🟰 " +"(equal sign)` icon." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:78 +msgid "" +"Lastly, highlight the default value in the third (and final) portion of the " +"second filter equation, and type in `New`. With that in place, Odoo only " +"targets opportunities that are in the \"New\" stage of the pipeline." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst-1 +msgid "" +"A standard scenario using filters in the Odoo Marketing Automation app." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:87 +msgid "" +"Scenario #2: Narrow down target to event attendees who purchased a specific " +"ticket" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:89 +msgid "" +"While in *Edit mode* on a campaign template form (by clicking the " +":guilabel:`Edit` button), select the :guilabel:`Target` field, and click " +":guilabel:`Search More` from the drop-down menu. Then, scroll down (or " +"search for) :guilabel:`Event`, and select it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:93 +msgid "" +"Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on" +" the default :guilabel:`ID` filter option in the first portion of the filter" +" equation. Doing so reveals a drop-down menu full of filter options. From " +"this drop-down, scroll down (or search for) :guilabel:`Event`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:98 +msgid "" +"Click the default :guilabel:`🟰 (equal sign)` icon in the second portion of " +"the filter equation. This reveals a drop-down menu. From this drop-down " +"menu, select :guilabel:`contains`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:101 +msgid "" +"In the third (and final) empty portion of the filter equation, type in the " +"name of the event(s) that Odoo should consider for this campaign filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:104 +msgid "" +"Then, add another node to this filter by clicking the :guilabel:`➕ (plus " +"sign)` icon to the right of the equation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:107 +msgid "" +"The second node will focus on targeting this campaign to attendees who " +"purchase a specific type of ticket to the aforementioned event(s) mentioned " +"in the first filter equation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:110 +msgid "" +"To do that, select the default :guilabel:`ID` from the first portion of the " +"second filter equation, and scroll down (or search for) :guilabel:`Event " +"Ticket` from the field drop-down menu. Then, in that same drop-down menu, " +"select :guilabel:`Name`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:114 +msgid "" +"Once again, click the default :guilabel:`🟰 (equal sign)` icon in the second " +"portion of the filter equation, and select :guilabel:`contains`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:117 +msgid "" +"Lastly, in the third (and final) portion of the second filter equation, " +"which is blank, type in the name of the ticket type that should be used for " +"the filter. In this case, :guilabel:`Standard` is the name of the event " +"ticket type for this sample filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst-1 +msgid "An event ticket filter in the Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:3 +msgid "Testing/running campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5 +msgid "" +"Odoo gives users the ability to test marketing campaigns (and mailings) " +"before officially running them." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:8 +msgid "" +"First, open the :menuselection:`Marketing Automation` application, and " +"select the desired campaign, which reveals that campaign's detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:11 +msgid "" +"On the campaign detail form, make sure the campaign already has activities " +"configured (or build a campaign by following the directions here on " +":doc:`this documentation " +"`)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:15 +msgid "" +"To start a test, click the :guilabel:`Launch a Test` button at the top of " +"the campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "Launch a test button in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:21 +msgid "" +"When clicked, a :guilabel:`Launch a test` pop-up window appears. In the " +"drop-down field, choose an existing record (or create a new one) to run the " +"test on. To create a brand new record, click the :guilabel:`Search More...` " +"link at the bottom of the drop-down menu, and then click the " +":guilabel:`Create` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:26 +msgid "" +"Doing so reveals a blank contact form, in which the :guilabel:`Name` and " +":guilabel:`Email` **must** be entered. When all the necessary information " +"has been entered, click :guilabel:`Save`, and Odoo returns to the " +":guilabel:`Launch a test` pop-up, with that new record in the " +":guilabel:`Choose an existing record or create a new one to test` field." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:31 +msgid "" +"Once a record is selected, click :guilabel:`Continue`, and Odoo reveals the " +"campaign test page." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "Test screen in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:37 +msgid "" +"On the campaign test page, the name of the :guilabel:`Record` being tested " +"is visible, along with the precise time this test workflow was started in " +"the :guilabel:`Workflow Started On` field. Beneath that, in the " +":guilabel:`Workflow` section is the first activity (or activities) in the " +"workflow that's being tested." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:42 +msgid "" +"To start a test, click the :guilabel:`Run` button, represented by a " +":guilabel:`▶️ (play button)` icon beside the first activity in the workflow." +" When clicked, the page reloads, and Odoo shows the various results (and " +"analytics) connected to that specific activity as they occur, in real-time." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "Workflow test progress in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:50 +msgid "" +"Once all the workflow activities are completed, the test will end, and move " +"to the :guilabel:`Completed` stage. To stop a test before all the workflow " +"activities are completed, click the :guilabel:`Stop` button in the upper-" +"left corner of the campaign test page." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3 +msgid "Marketing activities" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:5 +msgid "" +"When creating a campaign in the *Marketing Automation* app, users can plan " +"marketing activities, such as email or SMS campaigns." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:8 +msgid "" +"To get started, navigate to the bottom of a marketing automation campaign " +"detail form, and click :guilabel:`Add New Activity`. Doing so reveals a " +":guilabel:`Create Activities` pop-up window. This pop-up window is a blank " +"activity template, where specific parameters can be set for that particular " +"activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:13 +msgid "" +"The following fields are available in the :guilabel:`Create Activities` pop-" +"up window (when :guilabel:`Add New Activity` is clicked):" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "An activity template in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20 +msgid ":guilabel:`Activity Name`: the title of the activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21 +msgid "" +":guilabel:`Activity Type`: choose between `Email`, `Server Action` (internal" +" Odoo operation), or `SMS`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:23 +msgid "" +":guilabel:`Mail Template`: choose from pre-configured templates (or create a" +" new one on-the-fly)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:24 +msgid ":guilabel:`Trigger`: choose when this activity should be triggered." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25 +msgid "" +":guilabel:`Expiry Duration`: configure to stop the actions after a specific " +"amount of time (after the scheduled date). When selected, a " +":guilabel:`Cancel after` field appears, in which the user can choose how " +"many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to " +"cease after the initial date." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:29 +msgid "" +":guilabel:`Activity Filter`: domain related to this activity (and all " +"subsequent child activities)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:31 +msgid "" +":guilabel:`Applied Filter`: activity will *only* be performed if it " +"satisfies the specified domain (filter)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:34 +msgid "" +"After the activity's settings are fully configured, click :guilabel:`Save & " +"Close` to save the activity and return to the marketing automation campaign " +"form, :guilabel:`Save & New` to save the activity and immediately create " +"another one in a fresh :guilabel:`Create Activities` pop-up window, or " +":guilabel:`Discard` to delete the activity and return to the marketing " +"automation campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:40 +msgid "Workflow activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:42 +msgid "" +"Once an activity is saved, the :guilabel:`Workflow Activity` section appears" +" at the bottom of the marketing automation campaign form. Each activity is " +"displayed as a line graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:45 +msgid "" +"The configured :guilabel:`Trigger` time for that activity can be found to " +"the left of the :guilabel:`Workflow Activity` card in the " +":guilabel:`Workflow` section." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:48 +msgid "" +"Once the activity has been triggered, a figure representing the number of " +":guilabel:`Success` or :guilabel:`Rejected` activities will be displayed to " +"the right of the graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "Typical workflow activity in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:56 +msgid "" +"If the :guilabel:`Activity Type` of the activity is set to " +":guilabel:`Email`, there are more in-depth analytics beneath the activity " +"graph data, detailing how many emails have been :guilabel:`Sent`, and what " +"percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, " +"or :guilabel:`Bounced`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:62 +msgid "Child activities" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:64 +msgid "" +"There is also the option to add a *child activity* by clicking " +":guilabel:`Add child activity`, located at the bottom of each activity block" +" in the :guilabel:`Workflow` section of a marketing automation form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:68 +msgid "" +"Child activities are sub-activities that are connected to (and triggered by)" +" the activity above it, which is also known as its *parent activity*." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:71 +msgid "" +"Odoo provides a number of triggering options to launch a child activity - " +"all of which depend on the trigger configurations related to the parent " +"activity. Under the desired parent activity, hover over :guilabel:`Add child" +" activity`, and select any of the following triggers:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75 +msgid ":guilabel:`Add Another Activity`: instantly add another activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:76 +msgid "" +":guilabel:`Opened`: the next activity will be triggered if the (email) " +"recipient opens the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:78 +msgid "" +":guilabel:`Not Opened`: the next activity will be triggered if the recipient" +" does not open the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:80 +msgid "" +":guilabel:`Replied`: the next activity will be triggered if the recipient " +"replies to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:81 +msgid "" +":guilabel:`Not Replied`: the next activity will be triggered if the " +"recipient does not reply to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:83 +msgid "" +":guilabel:`Clicked`: the next activity will be triggered if the recipient " +"clicks on a link included in the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:85 +msgid "" +":guilabel:`Not Clicked`: the next activity will be triggered if the " +"recipient does not click on a link included in the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:87 +msgid "" +":guilabel:`Bounced`: the next activity will be triggered if the mailing is " +"bounced (not sent)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:89 +msgid "" +"Once a trigger is selected, the user can configure the child activity (it " +"has the same configuration options as a regular activity), and click " +":guilabel:`Save & Close` to finish creating the child activity, which will " +"then be displayed in the :guilabel:`Workflow` section, in a slightly " +"indented position beneath its parent activity." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:8 +msgid "SMS Marketing" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials.rst:5 +#: ../../content/applications/marketing/social_marketing/essentials.rst:5 +msgid "Essentials" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:3 +msgid "Mailing lists and blacklists" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:5 +msgid "" +"Creating or importing mailing lists in Odoo is very useful when curating " +"content to specific groups of people that already share similar demographics" +" or interests. Mailing lists are also a great way to get started if a " +"company is migrating from another system, and already has a established " +"audience." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:10 +msgid "" +"Moreover, providing an audience with the option to 'unsubscribe' from " +"mailings, helps businesses maintain good customer relations, by giving " +"recipients the power to control what they are (and aren't) sent." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:15 +msgid "Mailing lists" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:17 +msgid "" +"In the :guilabel:`SMS Marketing` app, there's an option on the header menu " +"called :guilabel:`Mailing Lists`. When clicked, a sub-menu is revealed with " +"options for :guilabel:`Mailing Lists` and :guilabel:`Mailing List Contacts`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:21 +msgid "" +"Click :menuselection:`Mailing Lists --> Mailing Lists` to see an overview of" +" all mailing lists in the database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "" +"View of the main SMS mailing list page on the Odoo SMS Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:28 +msgid "" +"To edit any existing list, select the desired list from the " +":guilabel:`Mailing Lists` page, and proceed to modify it in a number of " +"ways." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:31 +msgid "" +"To create a new mailing list, click :guilabel:`Create` in the upper left " +"corner of the :guilabel:`Mailing Lists` page. Doing so, will reveal a blank " +"mailing list template form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of the mailing list pop-up window in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:38 +msgid "" +"First, choose a name for the :guilabel:`Mailing List`, and activate the " +"option :guilabel:`Is Public`, to make the mailing list accessible to " +"recipients on the :guilabel:`Subscription Management page`. Doing so allows " +"users to update their subscription preferences at any time." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:43 +msgid "" +"Checking the :guilabel:`Is Public` box is not required, but is recommended " +"to maintain good customer relations." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:46 +msgid "" +"When those fields are filled in, click :guilabel:`Create` to finalize the " +"form. Then on the main :guilabel:`Mailing Lists` dashboard, the new mailing " +"list that was just created will be accessible." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:49 +msgid "" +"To edit or customize the mailing list further, select the mailing list from " +"the main :guilabel:`Mailing Lists` page to reveal the mailing list detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:52 +msgid "" +"Along the top of the mailing list detail form, there are various analytical " +"smart buttons displaying statistics for different metrics related to the " +"mailing list (e.g. :guilabel:`Recipients`, :guilabel:`Mailings`, etc.)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:56 +msgid "" +"To review or edit any of those elements, click the desired smart button to " +"reveal a separate page with in-depth data associated with the mailing list." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:59 +msgid "" +"To make changes to the mailing list itself, click the :guilabel:`Edit` " +"button in the upper-left corner of the mailing list detail form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of the mailing list template form in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:67 +msgid "" +"Don't forget to hit the :guilabel:`Save` button once changes have been made." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:70 +msgid "Mailing lists contacts" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:72 +msgid "" +"Access contacts information from one or more mailing lists navigate to " +":menuselection:`Mailing Lists --> Mailing List Contacts` to reveal a " +"dashboard with with all the contacts associated with one or more of the " +"configured mailing lists in the database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "" +"View of the mailing lists contact page in the Odoo SMS Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:81 +msgid "" +"By default, Odoo reveals the :guilabel:`Mailing List Contacts` page with the" +" :guilabel:`Exclude Blacklisted Phone` filter in the search bar. Therefore " +"only showing contact information for recipients who still want to receive " +"communications and mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:86 +msgid "Communication history in the Chatter" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:88 +msgid "" +"An accessible record of every sent mailing(s) is kept on each recipient's " +"*chatter* section, located beneath a recipient's contact form (in the " +"*Contacts* application)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:91 +msgid "" +"Database users can reference the chatter to easily keep track of " +"communications, and see a history of interactions with contacts and " +"prospects." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:94 +msgid "" +"For example, sales representatives can use the chatter to quickly find out " +"which :abbr:`SMS (Short Message Service)` mailing promotions a certain " +"customer has received (or not received)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of what the chatter looks like in the Odoo Contacts app." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:102 +msgid "Blacklist" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:104 +msgid "" +"Odoo *SMS Marketing* has a :guilabel:`Blacklist` feature that provides " +"recipients with the power to add their phone number to a list of people who " +"no longer want to receieve communications or mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:108 +msgid "" +"This is also known as the unsubscribe process: customers will automatically " +"be added onto a *blacklist*, if they click :guilabel:`Unsubscribe`, via " +"their :guilabel:`Subscription Management` page. Customers can also be added " +"manually to the blacklist, if necessary." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:112 +msgid "" +"To see a complete collection of blacklisted numbers, navigate to the " +":menuselection:`SMS Marketing app --> Configuration --> Blacklisted Phone " +"Numbers` to reveal a dashboard containing every blacklisted phone number in " +"the database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "SMS Blacklist menu in the application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:120 +msgid "" +"To manually add a number to a blacklist, click the :guilabel:`Create` button" +" in the upper-left corner of the dashboard and enter the phone number on the" +" next page's form. There's also a checkbox to indicate whether that " +"particular phone numnber is :guilabel:`Active` (or not)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:128 +msgid "" +"Once the form is completed, click :guilabel:`Save` to add it to the " +":guilabel:`Blacklisted Phone Numbers` list. To remove any number from the " +"blacklist, select the desired number on the dashboard, and then, on the " +"phone number's form, click :guilabel:`Unblacklist`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:133 +msgid "Importing blacklists" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:135 +msgid "" +"During a software/platform migration, it is possible to import an already " +"existing blacklist of contacts. This would include customers, who have " +"already asked to be blacklisted` on :abbr:`SMS (Short Message Service)` " +"mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:139 +msgid "" +"To do that, navigate to :menuselection:`SMS Marketing app --> Configuration " +"--> Blacklisted Phone Numbers`, and then select the :guilabel:`Favorites` " +"drop-down menu (beneath the search bar), and click :guilabel:`Import " +"records`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of how to import a blacklist in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:3 +msgid "SMS campaign settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:5 +msgid "" +"Utilizing :abbr:`SMS (Short Message Service)` campaigns with Odoo *SMS " +"Marketing* isn't just an effective advertisement strategy, it's also a great" +" way to remind people about upcoming events, issued invoices, and so much " +"more." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:9 +msgid "" +"But, before :abbr:`SMS (Short Message Service)` campaigns can be created " +"(and sent), a few specific settings and features must be enabled first." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:13 +msgid "SMS campaign setting" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:15 +msgid "" +"To enable :abbr:`SMS (Short Message Service)` campaigns in Odoo, make sure " +"the *Mailing Campaigns* feature is activated by going to " +":menuselection:`Email Marketing --> Configuration --> Settings`, and then " +"enable :guilabel:`Mailing Campaigns` and :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "View of the mailing campaigns setting in Odoo." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:24 +msgid "" +"Activating the *Mailing Campaigns* feature in the *General Settings* also " +"enables the *A/B Test* feature." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:27 +msgid "" +"Once the setting is enabled, navigate back to the :menuselection:`SMS " +"Marketing` app, and notice the :guilabel:`Campaigns` header menu is now " +"available for use. Similarly, the :guilabel:`A/B Test` tab is now also " +"available on every :abbr:`SMS (Short Message Service)` template form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:32 +msgid "A/B tests" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:34 +msgid "" +":guilabel:`A/B Tests` allows any :abbr:`SMS (Short Message Service)` " +"mailings to be tested against other versions within the same campaign, in " +"order to compare which version is the most successful in producing " +"engagement and/or conversion outcomes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:38 +msgid "" +"On an :abbr:`SMS (Short Message Service)` template form, under the " +":guilabel:`A/B Tests` tab, initially, there's only a single checkbox " +"labeled: :guilabel:`Allow A/B Testing.`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:41 +msgid "When clicked, a series of other options appear." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"The A/B Test tab is located on an Odoo SMS Marketing app campaign form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:47 +msgid "" +"In the first field, enter a desired percentage of recipients to conduct the " +"A/B Test on." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:49 +msgid "" +"Beneath the percentage field is the :guilabel:`Winner Selection` field. This" +" is what Odoo will use to determine the successful result of an A/B Test. In" +" other words, this tells Odoo how to pick a winning A/B test." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:53 +msgid "" +"The following sections are available: :guilabel:`Manual`, :guilabel:`Highest" +" Click Rate`, :guilabel:`Leads`, :guilabel:`Quotations`, or " +":guilabel:`Revenues`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:56 +msgid "" +"Finally, the :guilabel:`Send Final On` field is listed. This represents the " +"date-time that Odoo uses as a deadline to determine the winning mailing " +"variation. Then, Odoo sends that winning mailing variation to the remaining " +"recipients, who weren't involved in the test, at that prior date and time." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:62 +msgid "" +"Quickly create different versions of the mailing to add to the A/B Test by " +"clicking the :guilabel:`Create an Alternate Version` button." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:66 +msgid "" +"Remember, the winning mailing variation is based on the criteria selected in" +" the :guilabel:`Winner Selection` field." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:70 +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:15 +msgid "Campaigns page" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:72 +msgid "" +"To create, edit, or analyze any campaign, click :menuselection:`Campaigns` " +"in the header menu of the :guilabel:`SMS Marketing` app. On the " +":guilabel:`Campaigns` page, each campaign displays various information " +"related to the mailings associated with that campaign (e.g. number of " +"emails, social posts, SMSs, and push notifications)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"Dasbhoard view of different Campaigns in the Odoo SMS Marketing app, " +"separated by stage." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:82 +msgid "Campaign templates" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:84 +msgid "" +"Click :guilabel:`Create` to create a new campaign, and Odoo reveals a blank " +"campaign template form to fill out. Alternatively, select any previously-" +"made campaign in order to duplicate, review, or edit its campaign template " +"form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "View of an SMS campaign template in Odoo SMS marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:92 +msgid "" +"With each campaign, the options to :guilabel:`Send New Mailing`, " +":guilabel:`Send SMS`, :guilabel:`Send Social Post`, and :guilabel:`Push " +"Notifications` are available above the template form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:96 +msgid "" +"Whenever one of those communication options is added to the campaign, Odoo " +"will create a new corresponding tab on the template form, where those types " +"of messages can be reviewed or edited, along with various data sets related " +"to each specific mailing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:100 +msgid "" +"At the top of the template, there are various analytical smart buttons. When" +" clicked, Odoo reveals in-depth metrics related to that specific topic (e.g." +" :guilabel:`Engagement`, :guilabel:`Opportunities`, etc.) on a separate " +"page." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:104 +msgid "" +"Beneath the smart buttons, are fields for :guilabel:`Campaign Name` and " +":guilabel:`Responsible`. Odoo also allows for various :guilabel:`Tags` to be" +" added, as well (if necessary)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:108 +msgid "Sending SMSs through the Contacts app" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:110 +msgid "" +"Sending :abbr:`SMS (Short Message Service)` mailings directly through a " +"contact's form is available by default." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:113 +msgid "" +"In order to send an :abbr:`SMS (Short Message Service)` in this fashion, " +"navigate to the :menuselection:`Contacts` app, select the desired contact in" +" the database, and click on the :guilabel:`SMS` icon on the contact form " +"(next to the :guilabel:`Phone Number` field)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"The SMS icon is located on an individual's contact form in Odoo Contacts." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:121 +msgid "" +"To send a message to multiple contacts at once, navigate to the main " +":menuselection:`Contacts` app main dashboard, choose the :guilabel:`List " +"View`, and select all the desired contacts to whom the message should be " +"sent. Then, under :guilabel:`Action`, select :guilabel:`Send SMS`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"Select a number of contacts, click action, and select send multiple SMSs." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:130 +msgid "Set up SMS templates for future use" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:132 +msgid "" +"In order to set up :guilabel:`SMS Templates` for future use, activate " +":ref:`developer mode `, by navigating to the main Odoo " +"dashboard that is full of apps, and select the :menuselection:`Settings " +"app`. Then, scroll down to the :guilabel:`Developer Tools` section, and " +"click :guilabel:`Activate the Developer Mode`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:137 +msgid "" +"Once *developer mode* is activated, the main Odoo dashboard appears once " +"more, with a now-visible bug icon, which is located at the top-right corner " +"of the dashboard; this bug icon indicates that developer mode is currently " +"active." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:141 +msgid "" +"Next return to the :menuselection:`Settings app` and, in the now-visible " +"header menus at the top, choose :menuselection:`Technical --> SMS Templates`" +" to begin setting up :abbr:`SMS (Short Message Service)` templates for " +"future marketing campaigns." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"Select the SMS Template option in the Technical dropdown on the Settings " +"app." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:149 +msgid "" +"Inside of the :guilabel:`SMS Templates` dashboard, Odoo reveals an entire " +"page of :abbr:`SMS (Short Message Service)` templates. The default " +":guilabel:`List` view showcases each template's name, and to which " +"recipients it applies." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:153 +msgid "" +"On this page, :abbr:`SMS (Short Message Service)` templates can be edited or" +" created from scratch." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"The SMS Templates page in Odoo is available after enabling developer mode in the General\n" +"Settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:3 +msgid "SMS essentials" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:5 +msgid "" +"Utilizing :abbr:`SMS (Short Message Service)` outreach in communication " +"strategies can help companies expand their market reach, especially in some " +"countries, where emails might not be very common, or even used at all." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:9 +msgid "" +"Odoo's *SMS Marketing* application can also help boost conversion rates " +"around valuable actions, such as event registrations, free trials, " +"purchases, etc., since text and mobile-based marketing channels typically " +"yield higher :abbr:`CTOR (click-to-open rate)` and :abbr:`CTR (click-through" +" rate)` outcomes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:15 +msgid "SMS marketing dashboard" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:17 +msgid "" +"When the application is opened, Odoo displays the main :guilabel:`SMS " +"Marketing` dashboard, which showcases the various SMS mailings that have " +"been created, along with pertinent information and data related to that " +"specific message." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:21 +msgid "" +"The :guilabel:`Kanban` view is the default Odoo uses when the application is" +" opened, which provides an organized display of the SMS mailings that have " +"been created, and what their current status is at the moment." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:26 +msgid "" +"An :abbr:`SMS (Short Message Service)` mailing can have one of the following" +" statuses: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, or " +":guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:29 +msgid "" +"In the upper right corner of the main :guilabel:`SMS Marketing` dashboard, " +"there are a few different view options to choose from. Each one provides a " +"unique take on the same SMS information." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:32 +msgid "" +"The :guilabel:`List` view provides the same useful data related to SMS " +"mailings, but in a more traditional list layout." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:35 +msgid "" +"The :guilabel:`Calendar` view provides a simple calendar, making it easy to " +"see when SMS mailings are going to be sent (or have been sent). If a future " +"date is clicked, Odoo reveals a blank SMS template that, when completed, " +"will be scheduled to be sent on that specific future date." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:39 +msgid "" +"Lastly, the :guilabel:`Graph` view visualizes that same SMS-related data in " +"series of graphs and charts. Odoo also provides various ways to sort and " +"group the data for more detailed analysis." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:43 +msgid "Create SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:45 +msgid "" +"To start, click :guilabel:`Create` on the main :guilabel:`SMS Marketing` " +"dashboard, and Odoo reveals a blank SMS template form, which can be " +"configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "Creating an SMS marketing template." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:52 +msgid "" +"First, give the mailing a :guilabel:`Subject`, which describes what the " +"mailing is about." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:54 +msgid "" +"Next, in the :guilabel:`Recipients` field, choose to whom this :abbr:`SMS " +"(Short Message Service)` will be sent. By default, Odoo has " +":guilabel:`Mailing List` selected. If this is the desired " +":guilabel:`Recipients` field option, specify which mailing list Odoo should " +"send this :abbr:`SMS (Short Message Service)` to in the :guilabel:`Select " +"Mailing List` field." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:60 +msgid "" +"To create (or edit) a mailing list, go to :menuselection:`Mailing Lists --> " +"Mailing List`. There, Odoo displays all previously created mailing lists, " +"along with various types of data related to that specific list (e.g. number " +"of contacts, mailings, recipients, etc.)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:64 +msgid "" +"To learn more about mailing lists and contacts, check out " +":doc:`mailing_lists_blacklists`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "View of the mailing list page in the SMS marketing application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:71 +msgid "" +"To reveal all the possible options in the :guilabel:`Recipients` field, " +"click the field to see all the choices Odoo makes avaialble." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:74 +msgid "" +"When another field (other than :guilabel:`Mailing List`) is selected, the " +"option to specify that chosen field even further becomes available — either " +"with a default recipient filter equation that appears automatically (which " +"can be customized to fit any business need), or, if no default recipient " +"filter equation is present, an :guilabel:`Add Filter` button will appear." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:79 +msgid "" +"Clicking the :guilabel:`Add Filter` button, reveals fully customizable " +"domain rule fields, which can be configured similar to an equation. You can " +"create multiple recipient rules, if necessary." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:82 +msgid "" +"Then, Odoo will only send the :abbr:`SMS (Short Message Service)` to " +"recipients who fit into whatever criteria is configured in those fields. " +"Multiple rules can be added." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:86 +msgid "" +"If :guilabel:`Contact` is chosen, all of the *Contacts* records in the Odoo " +"database (vendors, customers, etc.) will receive the :abbr:`SMS (Short " +"Message Service)`, by default — unless more specific recipient rules are " +"entered." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:90 +msgid "" +"For instance, the message below will only be sent to contacts in the " +"database that are located in the United States (e.g. `Country` > `Country " +"Name` equals `United States`), and they haven't blacklisted themselves from " +"any mailings (e.g. `Blacklist` > `is` > `not set`)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:0 +msgid "Contact recipients on SMS marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:99 +msgid "Writing SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:101 +msgid "" +"Enter the content of the :abbr:`SMS (Short Message Service)` in the text " +"field, found in the :guilabel:`SMS Content` tab. Links and emojis can also " +"be included. Beneath the text field, Odoo displays how many characters are " +"used in the message, along with how many :abbr:`SMS (Short Message Service)`" +" mailings it will take to deliver the complete message." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:107 +msgid "" +"To check the price of sending an :abbr:`SMS (Short Message Service)` for a " +"country, click on the :guilabel:`Information` icon." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "SMS price check icon." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:115 +msgid "" +"Credits must be purchased from Odoo in order to take advantage of the *SMS " +"Marketing* app; :abbr:`SMS (Short Message Service)` messages will not be " +"sent without credits." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:119 +msgid "`Odoo SMS - FAQ `_" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:122 +msgid "Track links used in SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:124 +msgid "" +"When links are used in :abbr:`SMS (Short Message Service)` messages, Odoo " +"automatically generates link trackers to gather analytical data and metrics " +"related to those specific links, which can be found by going to " +":menuselection:`Configuration --> Link Tracker`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "SMS Link Tracker page." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:133 +msgid "Adjust SMS settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:135 +msgid "" +"Under the :guilabel:`Settings` tab of the SMS template, there is an option " +"to :guilabel:`Include opt-out link`. If activated, the recipient is able to " +"unsubscribe from the mailing list, thus avoiding all future mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:139 +msgid "" +"An employee can be designated as the :guilabel:`Responsible` in the " +":guilabel:`Tracking` section of the :guilabel:`Settings` tab, as well." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "SMS Settings tab." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:147 +msgid "Send SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:149 +msgid "" +"Once a mailing is created, choose when Odoo should deliver the message from " +"the following options:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:151 +msgid "" +":guilabel:`Send`: sends the message immediately. Consider using this option " +"if the recipient list is highly refined, or in cases that involve fast " +"approaching deadlines, such as a \"flash sale.\"" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:153 +msgid "" +":guilabel:`Schedule`: choose a day (and time) for Odoo to send the mailing. " +"This is typically the best option for mailings related to a specific event. " +"Such a method can also be used to promote a limited-time offer, or to help " +"plan a company's content strategy in advance." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:156 +msgid "" +":guilabel:`Test`: allows for an :abbr:`SMS (Short Message Service)` to be " +"sent to one or multiple numbers for test purposes. Remember to use a comma " +"between phone numbers if multiple numbers are used as recipients." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:161 +msgid "Visualize reports" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:163 +msgid "" +"On the :guilabel:`Reporting` page (accessible via the " +":menuselection:`Reporting` option in the header menu), there are options to " +"apply different combinations of :guilabel:`Filters` and :guilabel:`Measures`" +" to view metrics in a number of different layouts (e.g. :guilabel:`Graph`, " +":guilabel:`List`, and :guilabel:`Cohort` views.)" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:168 +msgid "" +"Each :guilabel:`Reporting` metric view option allows for more extensive " +"performance analysis of :abbr:`SMS (Short Message Service)` mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:171 +msgid "" +"For example, while in the default :guilabel:`Graph` view, :abbr:`SMS (Short " +"Message Service)` data is visualized as different graphs and charts, which " +"can be sorted and grouped in various ways (e.g. :guilabel:`Measures` drop " +"down menu)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "Reporting page in SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:180 +msgid ":doc:`sms_campaign_settings`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:181 +msgid ":doc:`mailing_lists_blacklists`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing.rst:5 +msgid "Pricing and FAQ" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:5 +msgid "SMS Pricing and FAQ" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:8 +msgid "What do I need to send SMSs?" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:10 +msgid "" +"SMS Text Messaging is an In-App Purchase (IAP) service that *requires " +"prepaid credits* to work." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:13 +msgid "How many types of SMSs are there?" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:15 +msgid "There are 2 types: GSM7 and UNICODE." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:17 +msgid "" +"**GSM7** is the standard format, with a limit of 160 characters per message," +" that includes the following characters:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "GSM7 characters available in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:24 +msgid "" +"**UNICODE** is the format applied if a special character, that *is not* in " +"the GSM7 list, is used. Limit per SMS: 70 characters." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:28 +msgid "" +"For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above" +" these limits, the content is divided into a multi-part message* and the " +"limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. Then, " +"in real-time, the system displays the number of SMS mailings the message " +"represents." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34 +msgid "How much does it cost to send an SMS?" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:36 +msgid "" +"The price of an SMS depends on the destination and the length (number of " +"characters) of the message. To see the **price per country, please " +"consult**: `Odoo SMS - FAQ `_." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:40 +msgid "" +"The number of SMSs a message represents will always be available in the " +"database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "" +"Number of GSM7 characters that fit in an SMS message in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:47 +msgid "How to buy credits" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49 +msgid "Go to :menuselection:`Settings --> Buy Credits`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "Buying credits for SMS Marketing in Odoo settings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:55 +msgid "Or go to :menuselection:`Settings --> View my Services`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "Using Odoo IAP to recharge credits for SMS Marketing in Odoo settings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:62 +msgid "" +"If Odoo Online (Saas) is being used, along with the Enterprise version, free" +" trial credits are available to test the feature." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:66 +msgid "More common questions" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Is there an expiration time for my credits?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "No, credits do not expire." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**Can I send an SMS to a phone number (which is not a mobile phone) because " +"I see the icon in front of the field “phone”?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Only if that phone number supports SMS (e.g. SIP phones)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Do I receive an invoice to buy my credits?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Yes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Can the recipient answer me?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "No, it is not possible to reply to the SMS." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**What happens if I send multiple SMSs at once, but I don't have enough " +"credits to send them all?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"Multiple SMS communications at once at are counted as a single transaction, " +"so no SMSs will be sent until there are enough credits to send them all." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Do I have a history of the sent SMSs?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"A history of sent SMSs, along with all pertinent information related to its " +"sent contacts (and the message itself), can be found in the :guilabel:`Sent`" +" column of the main :guilabel:`SMS Marketing` dashboard (while in " +":guilabel:`Kanban` view)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:91 +msgid "" +"For more detailed information, select a desired SMS from the main dashboard " +"(in :guilabel:`Kanban` view), and click on either link in the blue banner " +"above the SMS detail form to learn more." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Can I send as many SMSs I want at once?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Yes, if you have enough credits." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**If an SMS is sent to a number that doesn't exist in the list of " +"recipients, will credits be lost?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"No, not if the phone number is incorrectly formatted (e.g. too many digits)." +" However, if the SMS is sent to the wrong person (or to a fake number), the " +"credit for that SMS will be lost." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**What happens if I send my SMS to a paying number (e.g.: a contest to win a" +" ticket for a festival)?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"The SMS will not be delivered to that kind of number, so no charges will be " +"made." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**Can I identify the numbers that do not exist when I send several SMSs?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Only the ones that have an invalid format." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**How does the GDPR regulation affect this service?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"Please find our `Privacy Policy here `__." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Can I use my own SMS provider?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"Yes, but it is not possible out-of-the-box. Odoo experts can help customize " +"a database to allow for the use of a personal SMS provider. Please check our" +" success packs `here `_." +msgstr "" + +#: ../../content/applications/marketing/social_marketing.rst:8 +msgid "Social Marketing" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:3 +msgid "Social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:5 +msgid "" +"Social marketing campaigns help companies connect directly with the " +"marketplace. These campaigns are helpful when introducing a new product to " +"customers, explaining the value of a product or service, or when advertising" +" an upcoming event or product release." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:9 +msgid "" +"The most effective social marketing campaigns typically involve multiple " +"channels to maximize content distribution, and Odoo's *Social Marketing* " +"application acts as a singular control center to monitor, plan, post, track," +" and analyze all of the various content and content channels within a single" +" dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:17 +msgid "" +"To access a complete overview of all social marketing campaigns, open the " +":menuselection:`Social Marketing` application, and click " +":menuselection:`Campaigns` from the header menu. Doing so reveals a separate" +" page with every campaign in a default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 +msgid "View of the campaigns page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:25 +msgid "" +"Each *stage* in the kanban view can be edited, by clicking the " +":guilabel:`gear icon` to the left of the :guilabel:`+ (plus sign)` - located" +" to the right of the stage title." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:29 +msgid "" +"The **gear icon** *only* appears when the cursor hovers to the left of the " +"**+ (plus sign)**. When the gear icon is clicked, a drop-down menu reveals " +"the options: :guilabel:`Fold`, :guilabel:`Edit Stage`, and " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:37 +msgid "" +"Clicking :guilabel:`Fold` minimizes that specific stage's column. The stage " +"column can be restored by clicking the folded version of it on the main " +":guilabel:`Campaigns` dashboard in the default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:41 +msgid "" +"Selecting :guilabel:`Edit Stage` reveals a pop-up window, in which the name " +"and the sequence of the stage can be modified. If changes are made, be sure " +"to click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:44 +msgid "Clicking :guilabel:`Delete` removes the stage entirely." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:47 +msgid "" +"To add a new stage to the pipeline, side-scroll to the right on the " +":guilabel:`Campaigns` dashboard, click :guilabel:`Add a Column`, enter in " +"the desired information, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:52 +msgid "" +"The same social marketing campaign information on the :guilabel:`Campaigns` " +"dashboard can also be viewed as a list, by selecting the :guilabel:`List` " +"option, located under the search bar, in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:57 +msgid "Create social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:59 +msgid "" +"First, open the :menuselection:`Social Marketing` application, and select " +":guilabel:`Campaigns` from the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:62 +msgid "" +"On the :guilabel:`Campaigns` dashboard, a new campaign can be created by " +"clicking the quick add :guilabel:`+ (plus sign)` located in the top-right " +"corner of each stage in the pipeline, visible in the kanban view. Campaigns " +"can also be created by clicking :guilabel:`Create` in the upper-left corner " +"of the :guilabel:`Campaigns` dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:67 +msgid "" +"Both options reveal a new campaign detail window directly on the " +":guilabel:`Campaigns` dashboard when clicked." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 +msgid "View of the quick add option for campaigns in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:74 +msgid "" +"Here, the :guilabel:`Campaign Name`, :guilabel:`Responsible`, and " +":guilabel:`Tags` can be entered. When all modifications are complete, click " +":guilabel:`Add` to add the campaign to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:78 +msgid "Edit social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:80 +msgid "" +"In order to edit a campaign in greater detail, and create/send various forms" +" of communications related to it, the template page for that campaign must " +"be accessed and modified, accordingly. There are multiple ways to access a " +"template page for a campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:84 +msgid "" +"After entering the pertinent information in the :guilabel:`Quick Add` " +"campaign drop-down, click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:86 +msgid "" +"Simply select the desired campaign from the :guilabel:`Campaigns` dashboard " +"in list or kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:88 +msgid "" +"On the :guilabel:`Campaigns` dashboard in the kanban view, select the " +":guilabel:`⋮ (three dots)` drop-down menu on the desired campaign, and " +"select :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:91 +msgid "" +"Any of the above routes will reveal the *Campaign Template* page for that " +"specific campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:94 +msgid "Social marketing campaign templates" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:96 +msgid "" +"On a *Campaign Template* page, numerous elements can be customized/modified," +" and various forms of communications can be created, modified, and sent or " +"scheduled. Below is a sample of a completed campaign template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 +msgid "View of a sample campaign template page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:105 +msgid "" +"In order for the :guilabel:`Send New Mailing` option to appear on campaign " +"templates, make sure the *Mailing Campaigns* feature is enabled in the " +"*Email Marketing* app. To do that, navigate to :menuselection:`Email " +"Marketing --> Configuration --> Settings`, activate :guilabel:`Mailing " +"Campaigns`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:111 +msgid "" +"In order for the :guilabel:`Send SMS` option to appear, the Odoo *SMS " +"Marketing* application must be installed on the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:115 +msgid "Add content and communications to campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:117 +msgid "" +"If the proper settings and applications are installed (as instructed above)," +" there are four forms of communication/content options that can be added to " +"campaigns. Each of these options are displayed as buttons in the upper-left " +"corner of the campaign template page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:121 +msgid "" +":guilabel:`Send New Mailing`: reveals a blank email template on a separate " +"page, in which the message can be fully customized in a variety of ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:123 +msgid "" +":guilabel:`Send SMS`: reveals a blank SMS template on a separate page, in " +"which a SMS communication can be created and configured." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:125 +msgid "" +":guilabel:`Send Social Post`: reveals a blank social post template on a " +"separate page, in which a post can be created, and applied to social media " +"accounts that are already connected to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:128 +msgid "" +":guilabel:`Push Notification`: reveals a similar blank social post template " +"on a separate page, however, the :guilabel:`Push Notification` options are " +"already pre-selected in the :guilabel:`Post on` field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:132 +msgid "" +"Whichever form of communication is created, once it's completed, Odoo " +"returns to the :guilabel:`Campaign Template` page, showcasing that new " +"content in its corresponding tab (e.g. :guilabel:`Mailings`, " +":guilabel:`SMS`, :guilabel:`Social Media`, and/or :guilabel:`Push " +"Notifications`)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:137 +msgid "" +"As content and communications are added to a campaign, tabs for those " +"specific mediums appear, along with a variety of analytical smart buttons " +"(e.g. :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Leads`, " +"etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:141 +msgid "" +"These smart buttons, located at the top of the template, display different " +"metrics related to the campaign, and its various communications and content." +" Clicking any smart button reveals a separate page dedicated to that " +"particular element of the campaign, allowing for quicker, more organized " +"analysis." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:147 +msgid "" +"The Odoo *Social Marketing* app is integrated with other Odoo applications, " +"such as *Sales*, *Invoicing*, *CRM*, and *Website*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:151 +msgid "" +":doc:`/applications/marketing/social_marketing/essentials/social_essentials`" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:3 +msgid "Social marketing essentials" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:5 +msgid "" +"Odoo's *Social Marketing* helps content marketers create and schedule posts," +" manage various social media accounts, analyze content effectiveness, and " +"engage directly with social media followers in one, centralized location." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:10 +msgid "Add social media accounts" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:12 +msgid "" +"In order to create posts, each social media account must be added as a " +"stream in the Odoo *Social Marketing* application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:16 +msgid "Add a social media stream" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:18 +msgid "" +"Add a social media account as a stream by navigating to " +":menuselection:`Social Marketing` and then select the :guilabel:`Add A " +"Stream` button located in the upper left corner" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:21 +msgid "" +"When :guilabel:`Add A Stream` is clicked, the following pop-up appears, " +"displaying the different social media outlets to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"View of the pop-up that appears when 'Add a Stream' is selected in Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:29 +msgid "" +"Additional social media outlet options are available depending on your " +"version of Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:31 +msgid "" +"From this pop-up, select a social media option: :guilabel:`Facebook`, " +":guilabel:`LinkedIn`, or :guilabel:`Twitter`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:34 +msgid "" +"Then, Odoo navigates directly to that specific social media outlet's " +"authorization page, where permission must be granted, in order for Odoo to " +"add that particular social media account to the *Social Marketing* " +"application as a stream on the main dashboard of the app." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:39 +msgid "" +"A Facebook page can be added as long as the Facebook account that grants " +"permission is the administrator for the page. Also, different pages can be " +"added for different streams." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:42 +msgid "" +"Once permission is granted, Odoo navigates back to the :guilabel:`Feed` on " +"the main :guilabel:`Social Marketing` dashboard, and a new column with that " +"account's posts are automatically added." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:46 +msgid "" +"From here, new accounts and/or streams can be added and managed at any time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Example of how a populated stream-filled dashboard looks in Odoo Social " +"Marketing" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:53 +msgid "" +"Adding social media accounts to the feed also links that specific social " +"media platform's KPIs (if the platform has them). To get redirected to the " +"statistics and metrics related to any social account, click on " +":guilabel:`Insights`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "" +"The insights link that can be accessed for each social media stream added in" +" Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:62 +msgid "Create and publish social media posts in Odoo" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:64 +msgid "" +"To create content for social media accounts in the :menuselection:`Social " +"Marketing` application, click the :guilabel:`New Post` button located in the" +" upper-left corner of the main dashboard, or navigate to " +":menuselection:`Posts --> Create` from the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:68 +msgid "" +"Either route reveals a blank post template page that can be customized and " +"configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "How to create a social media post directly through Odoo" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:76 +msgid "Post template" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:78 +msgid "The post template page has many different options avaiable." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:81 +msgid "'Your Post' section" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:83 +msgid "" +"The first option is the :guilabel:`Post on` field. This is where it's " +"determined on what social media account(s), or on which website(s) via push " +"notification, this post will be published." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:87 +msgid "" +"In order for the :guilabel:`Push Notification` option to appear, make sure " +"the *Enable Web Push Notifications* feature is enabled in the *Website* app." +" To do that, navigate to :menuselection:`Website --> Configuration --> " +"Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the " +"corresponding fields, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:92 +msgid "" +"Odoo automatically provides every available social media account that's been" +" linked to the database as an option in this section, as well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:96 +msgid "" +"If a social media account hasn't been added as a stream to the *Social " +"Marketing* application, it will not appear as an option on the post " +"template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:99 +msgid "" +"Next, there's the :guilabel:`Message` field. This is where the main content " +"of the post is created." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:101 +msgid "" +"Type the desired message for the post in this field. To the right, as the " +":guilabel:`Message` field is populated, Odoo displays visual samples of how " +"the post will look on all the previously selected social media accounts from" +" the :guilabel:`Post on` field above." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:106 +msgid "" +"Emojis can also be added directly to the text in the :guilabel:`Message` " +"field. Just click the :guilabel:`emoji (smiley face) icon`, located on the " +"line of the :guilabel:`Message` field to the far right. Clicking this icon " +"reveals a drop-down containing numerous emojis to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:110 +msgid "" +"If images are to be used in the post, click the :guilabel:`ATTACH IMAGES` " +"link beneath the :guilabel:`Message` field, and Odoo reveals a pop-up " +"window. In this pop-up, the desired image must be chosen, and then uploaded." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:114 +msgid "" +"A preview of the entire post, text and image (if applicable), is instantly " +"displayed in the visual preview of the post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:117 +msgid "" +"Next, there's the option to attach this post to a specific marketing " +"campaign in the database in the :guilabel:`Campaign` field. Click the blank " +"line next to :guilabel:`Campaign` to reveal the previously configured " +"campaigns to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:122 +msgid "" +"A new campaign can be created, as well, by typing the name of the new " +"campaign on the blank :guilabel:`Campaign` field, and selecting " +":guilabel:`Create` from the drop-down field menu. Or, select " +":guilabel:`Create and edit` from the menu to further customize that newly-" +"created campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:128 +msgid "A social post does *not* need to be attached to a campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:130 +msgid "" +"Then, in the :guilabel:`When` field, choose either :guilabel:`Send Now` to " +"have Odoo publish the post immediately, or :guilabel:`Schedule later` to " +"have Odoo publish the post at a later date and time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:134 +msgid "" +"If :guilabel:`Schedule later` is selected, Odoo reveals a new field beneath " +"it (the :guilabel:`Scheduled post date` field). Clicking that empty field " +"reveals a pop-up calendar, in which a future date and time is designated. At" +" which time, Odoo will promptly publish the post on the pre-determined " +"social media accounts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:139 +msgid "" +"Click on the desired date to schedule the post for that day. Then, either " +"select and customize the default time in the :guilabel:`Scheduled post date`" +" field manually. Or, adjust the desired post time, by clicking the " +":guilabel:`scheduling (clock) icon` located on the calendar pop-up, and " +"choose the desired time for Odoo to publish this post on that future date." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:144 +msgid "" +"If scheduling a post, remember to hit :guilabel:`Schedule` in the upper left" +" of the post template. Doing so, locks in that specific date/time for Odoo " +"to send the post, and it changes the status of the post to " +":guilabel:`Scheduled`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:149 +msgid "" +"Also, when :guilabel:`Schedule` is clicked, a number of analytical smart " +"buttons appear on the post page. Each one offers up a detailed anaylsis of " +"the corresponding metric (e.g. :guilabel:`Leads`, :guilabel:`Revenues`, " +"etc.). These same smart buttons appear when a post is officially published, " +"as well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:155 +msgid "'Web Notification Options' section" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:157 +msgid "" +"If any :guilabel:`Push Notifications` are selected in the :guilabel:`Post " +"on` field, Odoo provides another section of settings/options at the bottom " +"of the post template. It should be noted that *none* of these fields are " +"required." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:161 +msgid "" +"The first field is for a :guilabel:`Push Notification Title`. This is text " +"that is displayed as the title of the push notification whenever it's sent. " +"Odoo displays a visual preview of this title, if one is created." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:165 +msgid "" +"To designate a specific page on the website that should trigger this push " +"notification, enter that page's URL in the :guilabel:`Push Target URL` " +"field. Then, once a visitor reaches that specific page, Odoo will display " +"the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:169 +msgid "" +"Below that field is the option to add a custom :guilabel:`Push Icon Image`. " +"This is an icon that appears beside the push notification. By default, Odoo " +"uses a \"smiley face\" as the icon." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:172 +msgid "" +"To upload a new image, click the :guilabel:`Edit (pencil) icon` when the " +":guilabel:`Push Icon Image` field is hovered over with the cursor. Then, " +"proceed to locate and upload the desired image, and Odoo automatically " +"displays a preview of how the icon will appear on the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:176 +msgid "" +"Next, there is the option to :guilabel:`Send at Visitors' Timezone`. If " +"enabled, Odoo will send it at the appropriate, pre-determined time, taking " +"the visitor's location into consideration." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:180 +msgid "Save, post, and test notification options" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:182 +msgid "" +"When all the modifications have been made, and the post is completed, either" +" click :guilabel:`Save` to save the post as a *Draft*. Or, if the post is " +"ready to be published immediately, click :guilabel:`Post`, and Odoo " +"automatically publishes the post on the pre-determined social media " +"accounts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:187 +msgid "" +"There is also the option to :guilabel:`Test Notification`, if a " +":guilabel:`Push Notification` was selected in the :guilabel:`Post on` field." +" Clicking that, provides a quick example of how the notification will appear" +" for visitors." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:192 +msgid "Social post status bar" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:194 +msgid "" +"In the top-right of the :guilabel:`Post Template` page is the " +":guilabel:`Status Bar`. This displays the current status of the post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:197 +msgid "When :guilabel:`Save` is clicked, the post is in the *Draft* status." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:199 +msgid "" +"If the post is scheduled to be sent at a future date/time, and the " +":guilabel:`Schedule` button has been clicked, the status of the post is " +"*Scheduled*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:202 +msgid "" +"If the post is in the process of currently being published or sent, the " +"status of the post is *Posting*. And, lastly, if the post has already been " +"published or sent, the status is *Posted*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:206 +msgid "Posts page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:208 +msgid "" +"To see a complete overview of posts, go to Odoo :menuselection:`Social " +"Marketing`, and click :menuselection:`Posts` in the header menu. Here, every" +" post that has been created and posted with Odoo is available." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:212 +msgid "" +"There are four different view options for :guilabel:`Posts` page data: " +"*kanban*, *calendar*, *list*, and *pivot*. The view options are located in " +"the upper right corner of the :guilabel:`Posts` page, beneath the search " +"bar." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:218 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:220 +msgid "" +"By default, Odoo displays the posts in a kanban view. The information on " +"this page can be sorted even further, via the :guilabel:`Filters` and " +":guilabel:`Group by` drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "" +"Kanban view of the posts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:227 +msgid "Calendar view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:229 +msgid "" +"The calendar view option displays a visual representation in a calendar " +"format of when posts were published, or are scheduled to be published. This " +"option provides a clear overview of any planned day, week, or month, and " +"Odoo displays all drafted, scheduled, and published posts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "Example of the calendar view in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:237 +msgid "List view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:239 +msgid "" +"The list view option is similar to the kanban option, but instead of " +"individual blocks, all the post information is displayed in a clear, list " +"layout. Each line of the list displays the :guilabel:`Social Accounts`, " +":guilabel:`Message`, and :guilabel:`Status` of every post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "View of the list option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:247 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:249 +msgid "" +"The pivot view option provides a fully customizable grid table, where " +"different measures of data can be added and analyzed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "View of the pivot option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:256 +msgid "" +"The pivot view option provides numerous analytical options, allowing for in-" +"depth, detailed analysis of various posts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:259 +msgid "" +"Click on any :guilabel:`+ (plus sign) icon` next to a line in the pivot " +"table to reveal more metric options to add to the grid." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:262 +msgid "" +"While in the pivot view, the option to :guilabel:`Insert in Spreadsheet` is " +"available, located to the right of the :guilabel:`Measures` drop-down." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:265 +msgid "" +"When clicked, a pop-up appears, where the option to add this information to " +"a current spreadsheet is available. The option to create a new spreadsheet " +"for this information on-the-fly is also available in this pop-up, as well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:269 +msgid "" +"Next to the :guilabel:`Insert in Spreadsheet` are three view options, " +"specific to the pivot view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:272 +msgid "From left to right, the options are:" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:274 +msgid "" +":guilabel:`Flip Axis`, which switches the *X* and *Y* axis in the grid " +"table." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:275 +msgid "" +":guilabel:`Expand All`, which expands each line in the grid, revealing more " +"detailed information related to it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:277 +msgid "" +":guilabel:`Download`, which, when clicked, instantly downloads the pivot " +"table as a spreadsheet." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:281 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:283 +msgid "" +"To see a complete overview of all the people who have visited the website(s)" +" connected to the database, navigate to :menuselection:`Social Marketing -->" +" Visitors` in the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "View of the Visitors page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:290 +msgid "" +"Here, Odoo provides a detailed layout of all the visitors' pertinent " +"information in a default kanban view. This same information can be sorted " +"via the :guilabel:`Filters` and :guilabel:`Group By` options." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:294 +msgid "" +"The visitor data can also be viewed as a list or a graph. Those view options" +" are located in the upper-right corner of the :guilabel:`Visitors` page " +"beneath the search bar." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:298 +msgid "Social media page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:300 +msgid "" +"Go to :menuselection:`Configuration --> Social Media` to see a collection of" +" all social media options: :guilabel:`Facebook`, :guilabel:`LinkedIn`, " +":guilabel:`Twitter`, and :guilabel:`Push Notifications`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"View of the social media page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:308 +msgid "" +"If no account has been linked to any particular social media, click " +":guilabel:`Link Account` to proceed through the linking process." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:312 +msgid "Social accounts page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:314 +msgid "" +"To see a list of all social accounts linked to the database, go to " +":menuselection:`Configuration --> Social Accounts`. This page will display " +"the :guilabel:`Medium Name` and the :guilabel:`Social Media` platform it is " +"associated with." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"View of the social accounts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:322 +msgid "" +"To edit/modify any social accounts, simply select the desired account from " +"the list on this page, and proceed to make any adjustments necessary. Don't " +"forget to hit :guilabel:`Save` to secure any changes." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:327 +msgid "Social streams page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:329 +msgid "" +"Navigate to :menuselection:`Configuration --> Social Streams` to reveal a " +"separate page containing all of the social media streams that have been " +"added to the main dashboard of the *Social Marketing* app, accessible via " +"the :guilabel:`Feed` option in the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:337 +msgid "" +"Here, the social stream information is organized in a list with the " +":guilabel:`Social Media`, the :guilabel:`Title` of the stream, and the " +":guilabel:`Type` of the stream (e.g. :guilabel:`Posts`, :guilabel:`Keyword`," +" etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:341 +msgid "" +"To modify any stream's information, simply click the desired stream from the" +" list, and proceed to make any necessary adjustments. Don't forget to hit " +":guilabel:`Save` to secure any changes." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:345 +msgid "" +":doc:`/applications/marketing/social_marketing/essentials/social_campaigns`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:5 +msgid "Surveys" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:8 +msgid "`Odoo Tutorials: Surveys `_" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:3 +msgid "Survey essentials" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:5 +msgid "" +"Companies often use surveys to collect valuable information from their " +"customers and employees, which in turn, allows them to make more informed " +"business decisions." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:8 +msgid "" +"In Odoo, surveys are used to collect customer feedback, evaluate the success" +" of a recent event, measure the satisfaction of customers (or employees), " +"and gain more insight into shifting market sentiments." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:13 +msgid "Getting started" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:15 +msgid "" +"To begin, open the :guilabel:`Surveys` application and click " +":guilabel:`Create`. Odoo then redirects the page to a blank survey template " +"form." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:18 +msgid "" +"On the survey form, add a :guilabel:`Survey Title` and then add a cover " +"image to the survey by hovering over the photo icon and clicking on the " +":guilabel:`Edit (pencil)` icon. When the file explorer window opens, choose " +"an image from the local files." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:22 +msgid "" +"Below the :guilabel:`Survey Title` are various tabs in which the survey " +"questions and format can be created and customized. These tabs are labeled " +"as follows:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:25 +msgid ":guilabel:`Questions`: the list of questions to be asked in the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:26 +msgid "" +":guilabel:`Description`: contextual information to aid in understanding the " +"survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:27 +msgid "" +":guilabel:`Options`: choices for survey respondents to answer the questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst-1 +msgid "Various tabs that can be found on the survey template page." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:34 +msgid "Questions tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:36 +msgid "" +"Add questions and sections to the survey in the :guilabel:`Questions` tab. A" +" section divides the survey into parts in order to visually group similar " +"questions together. To make a section, click :guilabel:`Add a section` and " +"type in a section name. Then, add questions or drag and drop questions into " +"the divided sections." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:41 +msgid "" +"Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and" +" Questions` pop-up to create and customize the survey question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst-1 +msgid "The survey question pop-up window." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:49 +msgid "Create questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:51 +msgid "" +"In the :guilabel:`Create Sections and Questions` pop-up, type the question " +"in the :guilabel:`Question` field. Then, choose the :guilabel:`Question " +"Type`. A preview of how the question type looks is shown in the preview " +"window." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:55 +msgid "Choose from the following :guilabel:`Question Types`:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:57 +msgid ":guilabel:`Multiple Lines Text Box`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:58 +msgid ":guilabel:`Single Line Text Box`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:59 +msgid ":guilabel:`Numerical Value`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:60 +msgid ":guilabel:`Date`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:61 +msgid ":guilabel:`Datetime`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:62 +msgid ":guilabel:`Multiple choice: only one answer`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:63 +msgid ":guilabel:`Multiple choice: multiple answers allowed`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:64 +msgid ":guilabel:`Matrix`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:67 +msgid "" +"Different features appear in the :guilabel:`Answers` and :guilabel:`Options`" +" tabs, depending on the :guilabel:`Question Type` chosen. However, the " +":guilabel:`Description` tab always remains the same, regardless of what " +"question is chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:72 +msgid "Create sections and questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:74 +msgid "" +"Once a :guilabel:`Question Type` has been selected, there are three possible" +" tabs where information can be customized for the question. These include " +"the :guilabel:`Answers` (if applicable), :guilabel:`Description`, and " +":guilabel:`Options` tabs." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:78 +msgid "" +"Each tab offers a variety of different features depending on what " +":guilabel:`Question Type` was chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:81 +msgid "" +"For example, in the :guilabel:`Options` tab, the following options may " +"appear:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:83 +msgid ":guilabel:`Mandatory Answer`: the question must be answered." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:84 +msgid "" +":guilabel:`Matrix Type`: for matrix-type questions, select if one choice or " +"multiple choices can be selected per row." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:86 +msgid ":guilabel:`Number of columns`: select how many columns are displayed." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:87 +msgid ":guilabel:`Images on answers`: allow images on the answer options." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:88 +msgid "" +":guilabel:`Conditional Display`: determine if the question is displayed " +"based on the participant's answer to a previous question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:90 +msgid "" +":guilabel:`Show Comments Field`: allow the participant to type a comment in " +"a text box." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:91 +msgid "" +":guilabel:`Question Time Limit`: for live session surveys, set a time limit " +"for the question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:94 +msgid "Conditional Display" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:96 +msgid "" +":guilabel:`Conditional Display` means the question is only displayed if the " +"specified conditional answer has been selected in a previous question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:99 +msgid "" +"When the box next to :guilabel:`Conditional Display` is selected, the " +":guilabel:`Triggering Question` field appears. Select a question from the " +"survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:102 +msgid "" +"Then, a :guilabel:`Triggering Answer` field appears. Here, select which " +"answer will trigger this :guilabel:`Conditional Display` question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:106 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:108 +msgid "" +"Back on the main survey template form, under the :guilabel:`Options` tab, " +"there are different sections of settings that can be modified." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:111 +msgid "The sections include:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:113 +msgid "" +":guilabel:`Questions`: focuses on the overall presentation of the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:114 +msgid ":guilabel:`Scoring`: decides how the survey is scored" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:115 +msgid ":guilabel:`Candidates`: manages access to the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:116 +msgid "" +":guilabel:`Live Session`: enables the survey into a real-time group " +"activity." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:119 +msgid "Questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:121 +msgid "" +"First, select the :guilabel:`Layout` of the survey. The following options " +"can be chosen:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:123 +msgid ":guilabel:`One page with all the questions`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:124 +msgid ":guilabel:`One page per section`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:125 +msgid ":guilabel:`One page per question`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:127 +msgid "" +"If either the :guilabel:`One page per section` or :guilabel:`One page per " +"question` options are chosen, then the :guilabel:`Back Button` option " +"appears. If selected, the :guilabel:`Back Button` option allows the " +"participant to go back to a question during the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:131 +msgid "" +"Under the :guilabel:`Layout` options is the :guilabel:`Progression Mode` " +"setting, which indicates how the participant's progress during the survey is" +" displayed. It is shown as either a :guilabel:`Percentage` or a " +":guilabel:`Number`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:135 +msgid "" +"Next, there is an option available to add a :guilabel:`Survey Time Limit`. " +"To implement this option, simply check the box, and enter the amount of time" +" (in minutes) participants have to complete the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:139 +msgid "" +"After the :guilabel:`Survey Time Limit` option is a section labeled " +":guilabel:`Selection`. Here, questions can be :guilabel:`Randomized per " +"section`, in other words, the number of random questions can be configured " +"by section. This mode is ignored in a live session." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:144 +#: ../../content/applications/marketing/surveys/scoring.rst:56 +msgid ":doc:`time_random`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:147 +msgid "Scoring" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:149 +msgid "" +"The following options are available when deciding how a :guilabel:`Scoring` " +"method:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:151 +msgid ":guilabel:`No scoring`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:152 +msgid ":guilabel:`Scoring with answers at the end`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:153 +msgid ":guilabel:`Scoring without answers at the end`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:155 +msgid "" +"If either the :guilabel:`Scoring with answers at the end` or " +":guilabel:`Scoring without answers at the end` options are selected, a " +":guilabel:`Success %` field appears. Set the percentage of correct answers " +"needed to pass the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:159 +msgid "" +"Next, there is the option to make the survey a certification. To do so, " +"check the box next to the option labeled :guilabel:`Is a Certification`, and" +" two additional fields appear. Select a color theme in the " +":guilabel:`Certification Template` field and then choose an :guilabel:`Email" +" Template`. When a participant passes the certification with the required " +"score, an email from Odoo will automatically be sent to that person using " +"the selected email template." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:165 +msgid "" +"If the :guilabel:`Give Badge` feature is enabled and the " +":guilabel:`Certification Badge` is set, the survey participant also receives" +" a badge upon passing the certification." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:169 +#: ../../content/applications/marketing/surveys/time_random.rst:48 +msgid ":doc:`scoring`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:172 +msgid "Candidates" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:174 +msgid "" +"To determine access to the survey, the :guilabel:`Access Mode` has two " +"options to choose between: :guilabel:`Anyone with the link` and " +":guilabel:`Invited people only`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:177 +msgid "" +"Below the :guilabel:`Appraisal Managers Only` checkbox is the " +":guilabel:`Login Required` option to require a login to participate in the " +"survey. If this option is activated, an :guilabel:`Attempts Limit` field " +"also populates, in which the number of survey attempts is defined for the " +"participant." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:182 +msgid "Live Session" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:184 +msgid "" +"The :guilabel:`Live Session` section is dedicated to users who are " +"conducting surveys in real-time, wherein they directly engage with and " +"collect answers from a live audience." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:187 +msgid "" +"Customize the :guilabel:`Session Code` here; this code is needed for " +"participants to access the live session survey. Reward participants for " +"quick answers by selecting the checkbox labeled :guilabel:`Reward quick " +"answers`. By checking it, attendees will get more points if they answer " +"quickly." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:193 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:195 +msgid "" +"Back on the main survey template page is the :guilabel:`Description` tab, " +"where a custom description of the survey can be added. This is displayed " +"beneath the title on the survey's homepage, which is on the front end of the" +" website made through the Odoo :guilabel:`Website` app." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:200 +msgid "Test and share the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:202 +msgid "" +"Once the survey is created and saved, run a test to check for possible " +"errors before finally sending it out to the participants by clicking " +":guilabel:`Test` in the upper left corner of the survey template page." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:206 +msgid "" +"When activated, Odoo redirects the page to a test version of the survey on " +"the front end of the website. This page displays how the survey will look to" +" participants. Proceed to run through the survey, like a normal participant," +" to check for errors." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:210 +msgid "" +"To return to the survey template form in the backend, simply click the " +":guilabel:`This is a test survey. Edit Survey` link in the blue banner along" +" the top of the page. Once Odoo redirects the page to the survey template in" +" the backend, make any further changes, as needed, before officially sending" +" the survey out to participants." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:215 +msgid "" +"When the survey is ready to be shared with the audience, click the " +":guilabel:`Start Survey` button in the upper-left corner of the survey " +"template form. Then, click :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:218 +msgid "" +"In the pop-up window, add the survey recipients in the " +":guilabel:`Recipients` field (for existing contacts in the Odoo database) or" +" the :guilabel:`Additional emails` field (for contacts that do not want to " +"be listed in the Odoo database). Finally, click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:222 +msgid "" +"As answers are received, check them by clicking the :guilabel:`Answers` " +"smart button on the survey template form, or the :guilabel:`See Results` " +"button in the upper left corner. To end the survey, click the " +":guilabel:`Close` button on the survey template form." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:3 +msgid "Scoring surveys" +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:5 +msgid "" +"To measure a survey participant's performance, knowledge, or overall " +"satisfaction, Odoo ascribes points to survey answers. At the end of the " +"survey, these points are summed up, resulting in the participant's final " +"score." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:9 +msgid "" +"To add points to questions, open the :guilabel:`Surveys` application, choose" +" the desired survey form, and then click on the :guilabel:`Options` tab. " +"Under the :guilabel;`Scoring` section, choose between :guilabel:`Scoring " +"with answers at the end` or :guilabel:`Scoring without answers at the end`." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:14 +msgid "" +":guilabel:`Scoring with answers at the end` shows the survey participant " +"their answers after completing the survey, and displays which questions they" +" got right or wrong. On questions where there was an incorrect answer, the " +"correct answer will be highlighted." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:18 +msgid "" +":guilabel:`Scoring without answers at the end` does not show the survey " +"participant their answer choices after completing the survey, only their " +"final score." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:21 +msgid "" +"To indicate correct answers, click on the :guilabel:`Questions tab` and " +"choose a question. In the question form, check the :guilabel:`Is a correct " +"answer` box for the choice that is the correct answer and attach a score " +"value." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:25 +msgid "" +"Back on the :guilabel:`Options` tab of the survey, set the " +":guilabel:`Success %`. The percentage entered determines what percentage of " +"correct answers is needed to pass the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:28 +msgid "" +"Further on the :guilabel:`Options` tab of the survey, survey administrators " +"can also choose to make the survey a certification. A certification " +"indicates that the survey asks questions to test the participants' knowledge" +" level on a subject." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:32 +msgid "" +"When enabling the :guilabel:`Is a certification` option, choose a " +":guilabel:`Certification email template`. The certification will " +"automatically be emailed using this email template to users who pass the " +"survey with a final score that is greater than or equal to the set " +":guilabel:`Success %`." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:36 +msgid "" +"In the :guilabel:`Candidates` section, participants can be required to log " +"in to take the survey. If the :guilabel:`Login Required` setting is enabled," +" two new options appear: the :guilabel:`Attempts Limit` checkbox, which " +"limits the number of times a participant can attempt the survey, and the " +"option to :guilabel:`Give Badge`, located beneath the " +":guilabel:`Certification` options in the :guilabel:`Scoring` section." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst-1 +msgid "" +"Setting the Required Score (percentage), login required, and certification " +"template." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:46 +msgid "" +"Badges are displayed on the eLearning portion of a given user's portal, and " +"are a way to set milestones and reward participants for passing surveys or " +"gaining points. Besides the awardee, website visitors who access the " +":guilabel:`Courses` page will also be able to see the granted badges." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst-1 +msgid "Example of how a badge looks on the eLearning portion of the website." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:3 +msgid "Timed and randomized questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:5 +msgid "" +"When creating a survey in Odoo, there are options to set a time limit on the" +" survey and randomize the questions." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:9 +msgid "Time limit" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:11 +msgid "" +"During a timed survey, participants must finish the survey within a " +"specified period of time. A common use case for implementing a time limit is" +" that it greatly reduces the chance of participants looking up responses via" +" external resources (e.g. web search), and reduces the survey to a \"closed " +"book\" testing environment." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:16 +msgid "" +"Find the :guilabel:`Survey Time Limit` setting in the :guilabel:`Options` " +"tab of the survey form, under the :guilabel:`Questions` section." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst-1 +msgid "Time limit field in the options tab of a survey template form." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:23 +msgid "" +"When the :guilabel:`Survey Time Limit` option is checked, a timer will be " +"displayed on every page of the survey, letting participants keep track of " +"the time remaining while the survey is active." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:27 +msgid "" +"Participants that do not submit their survey by the preconfigured time limit" +" will *not* have their answers saved." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:31 +msgid "Randomized selection" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:33 +msgid "" +"When a survey is randomized, Odoo shuffles the questions and reveals them in" +" a random order every time a participant begins the questionnaire. Using " +"randomization as a survey method discourages participants from looking at " +"each other's responses, and helps control for individual testing." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:37 +msgid "" +"To randomize a survey, click the :guilabel:`Options` tab on the survey form." +" In the :guilabel:`Questions` section, select :guilabel:`Randomized per " +"section` for the :guilabel:`Selection` field. After enabling, navigate to " +"the :guilabel:`Questions` tab and look in the :guilabel:`Random questions " +"count` column. From there, determine how many questions (per section) Odoo " +"should select and display during the shuffling of questions." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst-1 +msgid "Randomized question count in the questions tab of a survey." +msgstr "" diff --git a/locale/pl/LC_MESSAGES/productivity.po b/locale/pl/LC_MESSAGES/productivity.po new file mode 100644 index 000000000..f1acceeaa --- /dev/null +++ b/locale/pl/LC_MESSAGES/productivity.po @@ -0,0 +1,6275 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"PO-Revision-Date: 2021-11-02 08:49+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications/productivity.rst:5 +msgid "Productivity" +msgstr "" + +#: ../../content/applications/productivity/calendar.rst:5 +#: ../../content/applications/productivity/studio/views.rst:201 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:3 +msgid "Synchronize Google calendar with Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:5 +msgid "" +"Synchronize Google Calendar with Odoo to see and manage meetings from both " +"platforms (updates go in both directions). This integration helps organize " +"schedules, so a meeting is never missed." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:9 +msgid ":doc:`/applications/general/auth/google`" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:10 +msgid ":doc:`/administration/maintain/google_oauth`" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:13 +msgid "Setup in Google" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:16 +msgid "Select (or create) a project" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:18 +msgid "" +"Create a new Google API project and enable the Google Calendar API. First, " +"go to the `Google API Console `_ and " +"log into the Google account." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:22 +msgid "" +"If this is the first time visiting this page, Google will prompt the user to" +" enter a country and agree to the Terms of Service. Select a country from " +"the drop-down list and agree to the :abbr:`ToS (Terms of Service)`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:26 +msgid "" +"Next, click :guilabel:`Select a project` and select (or create) an API " +"project to configure OAuth in, and store credentials. Click :guilabel:`New " +"Project`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Create a new API project to store credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:34 +msgid "" +"Give the API Project a clear name, like \"Odoo Sync\", so it can be easily " +"identified." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:37 +msgid "Enable Google calendar API" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:39 +msgid "" +"Now, click on :guilabel:`Enabled APIs and Services` in the left menu. Select" +" :guilabel:`Enabled APIs and Services` again if the :guilabel:`Search bar` " +"doesn't appear." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Enable APIs and Services on the API Project." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:46 +msgid "" +"After that, search for `Google Calendar API` using the search bar and select" +" :guilabel:`Google Calendar API` from the search results. Click " +":guilabel:`Enable`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Enable the Google Calendar API." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:54 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:56 +msgid "" +"Now that the API project has been created, OAuth should be configured. To do" +" that, click on :guilabel:`OAuth consent` in the left menu and then select " +"the :guilabel:`User Type`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:60 +msgid "" +"*Personal* Gmail Accounts are only allowed to be **External** User Type, " +"which means Google may require an approval, or for *Scopes* to be added on. " +"However, using a *Google WorkSpace* account allows for **Internal** User " +"Type to be used." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:64 +msgid "" +"Note, as well, that while the API connection is in the *External* testing " +"mode, then no approval is necessary from Google. User limits in this testing" +" mode is set to 100 users." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:67 +msgid "" +"In the second step, :guilabel:`OAuth Consent Screen`, type `Odoo` in the " +":guilabel:`App name` field, select the email address for the :guilabel:`User" +" support email` field, and type the email address for the " +":guilabel:`Developer contact information` section. Then, click " +":guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:72 +msgid "" +"Skip the third step, :menuselection:`Scopes`, by clicking :guilabel:`Save " +"and Continue`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:74 +msgid "" +"Next, if continuing in testing mode (External), add the email addresses " +"being configured under the :guilabel:`Test users` step, by clicking on " +":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " +"summary of the app registration appears." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:78 +msgid "" +"Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:80 +msgid "" +"Now, the OAuth consent has been configured, and it's time to create " +"credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:83 +msgid "Create credentials" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:85 +msgid "" +"The *Client ID* and the *Client Secret* are both needed to connect Google " +"Calendar to Odoo. This is the last step in the Google console. Begin by " +"clicking :guilabel:`Credentials` in the left menu. Then, click " +":guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`, " +"Google will open a guide to create credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:90 +msgid "" +"Under :menuselection:`Create OAuth Client ID`, select :guilabel:`Website " +"application` for the :guilabel:`Application Type` field, and type `My Odoo " +"Database` for the :guilabel:`Name`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:93 +msgid "" +"Under the :guilabel:`Authorized JavaScript Origins` section, click " +":guilabel:`+ Add URI` and type the company's Odoo full :abbr:`URL (Uniform " +"Resource Locator)` address." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:95 +msgid "" +"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ " +"Add URI` and type the company's Odoo :abbr:`URL (Uniform Resource Locator)` " +"address followed by `/google_account/authentication`. Finally, click " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "" +"Add the authorized JavaScript origins and the authorized redirect URIs." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:103 +msgid "" +"A :guilabel:`Client ID` and :guilabel:`Client Secret` will appear, copy " +"these to a notepad." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:106 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:108 +msgid "" +"Once the *Client ID* and the *Client Secret* are located, open the Odoo " +"database and go to :menuselection:`Settings --> General Settings --> " +"Integrations --> Google Calendar`. Check the box next to :guilabel:`Google " +"Calendar`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "The Google Calendar checkbox in General Settings." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:116 +msgid "" +"Next, copy and paste the *Client ID* and the *Client Secret* from the Google" +" Calendar API credentials page into their respective fields below the " +":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:121 +msgid "Sync calendar in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:123 +msgid "" +"Finally, open the :menuselection:`Calendar` app in Odoo and click on the " +":guilabel:`Google` sync button to sync Google Calendar with Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "" +"Click the Google sync button in Odoo Calendar to sync Google Calendar with " +"Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:131 +msgid "" +"When syncing Google Calendar with Odoo for the first time, the page will " +"redirect to the Google Account. From there, select the :guilabel:`Email " +"Account` that should have access, then select :guilabel:`Continue` (should " +"the app be unverifed), and finally select :guilabel:`Continue` (to give " +"permission for the transfer of data)`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Give Odoo permission to access Google Calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:140 +msgid "Now, Odoo Calendar is successfully synced with Google Calendar!" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:143 +msgid "" +"Odoo highly recommends testing the Google calendar synchronization on a test" +" database and a test email address (that is not used for any other purpose) " +"before attempting to sync the desired Google Calendar with the user's " +"production database." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:147 +msgid "Once a user synchronizes their Google calendar with the Odoo calendar:" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:149 +msgid "" +"Creating an event in Odoo causes Google to send an invitation to all event " +"attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:150 +msgid "" +"Deleting an event in Odoo causes Google to send a cancellation to all event " +"attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:151 +msgid "" +"Adding a contact to an event causes Google to send an invitation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:152 +msgid "" +"Removing a contact from an event causes Google to send a cancellation to all" +" event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:154 +msgid "" +"Events can be created in Google Calendar without sending a notification by " +"selecting :guilabel:`Don't Send` when prompted to send invitation emails." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:3 +msgid "Outlook Calendar synchronization" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:5 +msgid "" +"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping " +"track of their tasks and appointments across all related applications." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:9 +msgid ":doc:`/applications/general/auth/azure`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:10 +msgid ":doc:`/administration/maintain/azure_oauth`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:13 +msgid "Register the application with Microsoft Azure" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:15 +msgid "" +"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account" +" is needed. Creating an account is free for users who have never tried or " +"paid for Azure. For more information, `click here " +"`_." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:19 +msgid "" +"Refer to `Microsoft's documentation `_ on how to" +" set up an Azure AD Tenant (also called an *environment*), which is a " +"representation of an organization to manage and register apps." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:23 +msgid "" +"Then, `Register an Application `_, choosing the " +"appropriate :guilabel:`Supported account type`. Users who wish to connect " +"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any " +"organizational directory (Any Azure AD directory - Multitenant) and personal" +" Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported " +"account types`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:29 +msgid "" +"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and " +"copy the Odoo database URI (URL) followed by " +"`/microsoft_account/authentication`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:33 +msgid "" +"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` " +"for the :guilabel:`Redirect URI`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "" +"The \"Supported account type\" and \"Redirect URI\" settings in the " +"Microsoft Azure AD portal." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:40 +msgid "" +"For more information on the restrictions and limitations of URIs, `check " +"this page `_." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:43 +msgid "" +"Regarding the application credentials, the user *must* add a client secret, " +"which allows Odoo to authenticate itself, requiring no interaction from the " +"user's side. :guilabel:`Certificates` are optional." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:47 +msgid "" +"To do add a client secret, click :guilabel:`Add a certificate or secret` and" +" then click :guilabel:`New client secret`. Next, type a " +":guilabel:`Description` and select when the client secret " +":guilabel:`Expires`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:51 +msgid "" +"Since resetting the synchronization can be tricky, Odoo recommends setting " +"the maximum allowed expiration date for the client secret (24 months), so " +"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to " +"generate the client secret (:guilabel:`Secret ID`)." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:56 +msgid "Configuration in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:58 +msgid "" +"In the Odoo database, go to :menuselection:`Settings --> General Settings " +"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Outlook Calendar\" setting activated in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:65 +msgid "" +"From the Microsoft Azure portal, under the :guilabel:`Overview` section of " +"the application, copy the :guilabel:`Application (Client) ID`, and paste it " +"into the :guilabel:`Client ID` field in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Client ID\" in the Microsoft Azure portal." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:72 +msgid "" +"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` " +"section, copy the :guilabel:`Client Secret Value` and paste it into the " +":guilabel:`Client Secret` field in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:79 +msgid "" +"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, " +"click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:84 +msgid "Sync with Outlook" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:88 +msgid "" +"Odoo highly recommends testing the Outlook calendar synchronization on a " +"test database and a test email address (that is not used for any other " +"purpose) before attempting to sync the desired Outlook Calendar with the " +"user's production database." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:92 +msgid "" +"If the user has any past, present, or future events on their Odoo calendar " +"before syncing their Outlook calendar, Outlook will treat the events pulled " +"from Odoo's calendar during the sync as new events, causing an email " +"notification to be sent from Outlook to all the event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:96 +msgid "" +"To avoid unwanted emails being sent to all past, present, and future event " +"attendees, the user must add the events from the Odoo calendar to the " +"Outlook calendar before the first ever sync, delete the events from Odoo, " +"and then start the sync." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:100 +msgid "" +"Even after synchronizing the Odoo Calendar with the Outlook calendar, " +"Outlook will still send a notification to all event participants every time " +"an event is edited (created, deleted, unarchived, or event date/time " +"changed), with no exceptions. This is a limitation that cannot be fixed from" +" Odoo's side." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:105 +msgid "" +"After one user syncs their Outlook calendar to the Odoo database, unwanted " +"email notifications are unavoidable because the first synchronized user's " +"events will be in the Odoo Calendar. If the Odoo database is shared amongst " +"multiple users, and another user wants to sync their Outlook calendar with " +"Odoo Calendar, Outlook will again pull the existing Odoo Calendar events " +"during the sync and treat them as new events, causing Outlook to send email " +"invitations to all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:112 +msgid "" +"In summary, once a user synchronizes their Outlook calendar with the Odoo " +"calendar:" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:114 +msgid "" +"Creating an event in Odoo causes Outlook to send an invitation to all event " +"attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:115 +msgid "" +"Deleting an event in Odoo causes Outlook to send a cancellation to all event" +" attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:116 +msgid "" +"Unarchiving an event in Odoo causes Outlook to send an invitation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:117 +msgid "" +"Archiving an event in Odoo causes Outlook to send a cancellation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:118 +msgid "" +"Adding a contact to an event causes Outlook to send an invitation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:119 +msgid "" +"Removing a contact from an event causes Outlook to send a cancellation to " +"all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:122 +msgid "Sync Odoo Calendar and Outlook" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:124 +msgid "" +"In the Odoo database, go to the :guilabel:`Calendar` module and click the " +":guilabel:`Outlook` sync button. The page will redirect to a Microsoft login" +" page, and the user is asked to log in to their account, if they are not " +"already, and grant the required permissions." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Outlook\" sync button in Odoo Calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:132 +msgid "" +"The synchronization is a two-way process, meaning that events are reconciled" +" in both accounts (Outlook and Odoo)." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:136 +msgid "" +"All users that want to use the synchronization simply need to :ref:`sync " +"their calendar with Outlook `. The configuration of " +"Microsoft's Azure account is only done once, as Azure AD tenants' Client IDs" +" and Client Secrets are unique, and represent an organization that helps the" +" user to manage a specific instance of Microsoft cloud services for their " +"internal and external users." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:143 +msgid ":doc:`../mail_plugins/outlook`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:144 +msgid ":doc:`google`" +msgstr "" + +#: ../../content/applications/productivity/discuss.rst:8 +msgid "Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:3 +msgid "Configure ICE servers with Twilio" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:5 +msgid "" +"Odoo Discuss uses WebRTC API and peer-to-peer connections for voice and " +"video calls. If one of the call attendees is behind a symmetric NAT, you " +"need to configure an ICE server to establish a connection to the call " +"attendee. To set up an ICE server, first, create a Twilio account for video " +"calls, and then, connect that Twilio account to Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:11 +msgid "Create a Twilio account" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:13 +msgid "" +"First, go to `Twilio `_ and click :guilabel:`Sign " +"up` to create a new Twilio account. Next, enter your name and email address," +" create a password, and accept Twilio's terms of service. Then, click " +":guilabel:`Start your free trial`. Verify your email address with Twilio, as" +" per their instructions." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:18 +msgid "" +"Next, enter your phone number into Twilio. Then, Twilio will send you an SMS" +" text message containing a verification code. Enter the verification code " +"into Twilio to verify your phone number." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:22 +msgid "" +"After that, Twilio redirects to a welcome page. Use the following list to " +"answer Twilio's questions:" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:25 +msgid "" +"For :guilabel:`Which Twilio product are you here to use?`, select " +":guilabel:`Video`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:26 +msgid "" +"For :guilabel:`What do you plan to build with Twilio?`, select " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:27 +msgid "" +"For :guilabel:`How do you want to build with Twilio?`, select " +":guilabel:`With no code at all`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:28 +msgid "" +"For :guilabel:`What is your goal today?`, select :guilabel:`3rd party " +"integrations`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "The Twilio welcome page." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:34 +msgid "" +"If necessary, change the billing country. Finally, click :guilabel:`Get " +"Started with Twilio`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:37 +msgid "Locate the Twilio Account SID and Auth Token" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:39 +msgid "" +"To locate the Account SID and Auth Token, go to the Twilio account " +"dashboard. Then, click :guilabel:`Develop` on the sidebar. In the " +":guilabel:`Account Info` section, locate the :guilabel:`Account SID` and the" +" :guilabel:`Auth Token`. Both of these are needed to connect Twilio to Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "" +"The Twilio Account SID and Auth Token can be found uner the Account Info " +"section." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:49 +msgid "Connect Twilio to Odoo" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:51 +msgid "" +"Open the Odoo database and go to :menuselection:`Settings --> General " +"Settings --> Discuss`. Check the box next to :guilabel:`Use Twilio ICE " +"servers` and enter the Twilio account's :guilabel:`Account SID` and " +":guilabel:`Auth Token`. Finally, click :guilabel:`Save` to apply these " +"changes." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "Enable the \"Use Twilio ICE servers\" option in Odoo General Settings." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:61 +msgid "Define a list of custom ICE servers" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:63 +msgid "" +"This step is not required for the Twilio configuration. However, if Twilio " +"is not configured or is not working at any given moment, Odoo will fall back" +" on the custom ICE servers list. The user must define the list of custom ICE" +" servers." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:67 +msgid "" +"In :menuselection:`Settings --> General Settings --> Discuss`, click the " +":guilabel:`ICE Servers` button under :guilabel:`Custom ICE server list`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "The \"ICE Servers\" button in Odoo General Settings." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:74 +msgid "" +"Odoo will redirect to the :guilabel:`ICE servers` page. Here you can define " +"your own list of ICE servers." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "The \"ICE servers\" page in Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:3 +msgid "Get Started with Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:5 +msgid "" +"Discuss allows you to bring all of your company’s communication together " +"through messages, notes, and chat. Share information, projects, files, " +"prioritize tasks, and stay connected with colleagues and partners throughout" +" applications. Forge better relationships, increase productivity and " +"transparency by promoting a convenient way of communicating." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:13 +msgid "Choose your notifications preference" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:15 +msgid "" +"Access your *Preferences* and choose how you would like your notifications " +"to be handled." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of the preferences page for Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:23 +msgid "" +"By default, the field is set as *Handle by Emails* making messages, notes, " +"and notifications where you were mentioned or that you follow, to be sent " +"through email. By choosing *Handle in Odoo*, they are shown in the *Inbox*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:24 +msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of an inbox message and its action options in Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:30 +msgid "" +"The messages tagged as *Mark as Todo* are also shown in *Starred*, while the" +" ones *Marked as Read* are moved to *History*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of messages marked as todo in Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:38 +msgid "Start Chatting" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:40 +msgid "" +"The first time you log in to your account, OdooBot sends you a message " +"asking for permission to receive desktop notifications to chats. If " +"accepted, you receive push notifications to the messages sent to you despite" +" of where you are in Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "" +"View of the messages under the messaging menu emphasizing the request for push\n" +"notifications for Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:50 +msgid "" +"To stop receiving desktop notifications, reset the notifications settings of" +" your browser." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:52 +msgid "" +"To start a chat, click on *New Message* on the *Messaging Menu*, or go to " +"*Discuss* and send a *Direct Message*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "" +"View of discuss’s panel emphasizing the titles channels and direct messages " +"in Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:60 +msgid "" +"You can also create :doc:`public and private channels `." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:63 +msgid "Mentions in the chat and on the Chatter" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:66 +msgid "" +"To mention a user within a chat or the chatter type *@user-name*; to refer " +"to a channel, type *#channel-name*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:68 +msgid "" +"A notification is sent to the user mentioned either to his *Inbox* or " +"through email, depending on his settings." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of a couple of chat window messages for Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:75 +msgid "" +"When a user is mentioned, the search list (list of names) suggests values " +"first based on the task’s followers, and secondly on *Employees*. If the " +"record being searched does not match with either a follower or employee, the" +" scope of the search becomes all partners." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:80 +msgid "Chat status" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:82 +msgid "" +"It is helpful to see what colleagues are up to and how quickly they can " +"respond to messages by checking their *Status*. The status is shown on the " +"left side of a contact’s names on Discuss’ sidebar and on the *Messaging " +"menu*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:86 +msgid "Green = online" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:87 +msgid "Orange = away" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:88 +msgid "White = offline" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:89 +msgid "Airplane = out of the office" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of the contacts’ status for Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:97 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:65 +msgid ":doc:`team_communication`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:98 +msgid ":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3 +msgid "Get Organized by Planning Activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:5 +msgid "" +"When you plan activities you minimize the risk of uncertainties, as you " +"provide clear directions for the course of your next action. In addition to " +"that, you do not leave space for wasteful activities and reduce the chance " +"of having overlapping actions between team members." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10 +msgid "Where do I see my schedule activities?" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:12 +msgid "" +"Access and manage your activities wherever you are in Odoo by the " +"*Activities* menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "" +"View of crm leads page emphasizing the activities menu for Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:20 +msgid "Plan activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:22 +msgid "" +"Activities can be planned and managed from the chatter by clicking on " +"*Schedule activity*, or through Kanban views." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "" +"View of crm leads and the option to schedule an activity for Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:31 +msgid "Set your activity types" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:33 +msgid "" +"A number of activities types are available by default in Odoo (call, email, " +"meeting, etc.). However, you can set new ones going to " +":menuselection:`Settings --> Activity types`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "" +"View of the settings page emphasizing the menu activity types for Odoo " +"Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:42 +msgid "" +"If you need to create an activity type with an available calendar, make sure" +" to create it with an *Action to Perform* set as *Meeting*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:46 +msgid "Recommend next activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:48 +msgid "" +"Odoo helps you to plan a flow of activities by allowing you to set " +"*Recommended Next Activities*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "" +"View of an activity type form emphasizing the field recommended next activities for Odoo\n" +"Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:55 +msgid "" +"Once the respective activity is completed, select *Done & Schedule Next* and" +" next steps are suggested to you." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "" +"View of an activity being schedule emphasizing the recommended activities field being\n" +"shown for Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:64 +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:115 +msgid ":doc:`get_started`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:3 +msgid "Efficiently Communicate Using Channels" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:5 +msgid "" +"You can use channels to organize discussions between individual teams, " +"departments, projects, or any other group that requires regular " +"communication. This way, you keep everyone in the loop updated with the " +"latest developments." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:10 +msgid "Public and Private channels" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:12 +msgid "" +"A *Public* channel can be seen by everyone, while a *Private* one is only " +"visible to users invited to it." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of discuss’s sidebar and a channel being created in Odo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:21 +msgid "" +"A public channel is best used when many employees need to access information" +" (such as company announcements), whereas a private channel could be used " +"whenever information should be limited to specific groups (such as a " +"specific department)." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:26 +msgid "Configuration options" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:28 +msgid "" +"You can configure a channel’s name, description, email alias, and privacy by" +" clicking on the *Channel Settings* icon on the sidebar." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of a channel’s settings form in Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:36 +msgid "Privacy and Members" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:40 +msgid "" +"Changing *Who can follow the group’s activities?* allows you to control " +"which groups can have access to the channel. Note that allowing *Everyone* " +"to follow a private channel lets other users view and join it, as they would" +" a public one." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:42 +msgid "" +"If you choose *Invited people only*, go to the *Members* tab to add your " +"members, or, go to Discuss’ main page, select the channel and click on " +"*Invite*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "" +"View of Discuss’ sidebar emphasizing the option to invite members in Odoo " +"Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:49 +msgid "" +"For *Selected group of users*, the option *Auto Subscribe Groups* " +"automatically add its members as followers. In other words, while " +"*Authorized Groups* limits which users can access the channel, *Auto " +"Subscribe Groups* automatically adds the user as a member as long as they " +"are part of the group." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:55 +msgid "Use a channel as a mailing list" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:57 +msgid "" +"Choosing to *Send messages by email* configures the channel to behave as a " +"mailing list." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:59 +msgid "" +"Enabling this option allows you to *Moderate this channel*, meaning that " +"messages will need to be approved before being sent." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of a message with a pending moderation status in Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:66 +msgid "" +"Under the *Moderation* tab choose as many moderators as you need, and if you" +" would like them to receive an *Automatic notification*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:67 +msgid "" +"Mark *Send guidelines to new subscribers* to automatically send instructions" +" to newcomers." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "" +"View of a channel’s settings form emphasizing the tab moderation in Odoo " +"Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:73 +msgid "" +"Moderators can: *Accept*, *Reject*, *Discard*, *Always Allow* or *Ban* " +"messages." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of a message to be moderated in Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:80 +msgid "" +"Members of a mailing channel receive messages through email regardless of " +"their :doc:`notification preference `." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:83 +msgid "" +"Once a channel is moderated, the menu *Ban List* allows you to add email " +"addresses per moderated channel to auto-ban them from sending messages." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "" +"View of a channel’s setting form emphasizing the ban Lists menu in Odoo " +"Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:91 +msgid "Quick search bar" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:93 +msgid "" +"Once at least 20 channels, direct message and live chat conversations (if " +"the module is installed on your database) are pinned in the sidebar, a " +"*Quick search…* bar is displayed. It is a clever way to filter conversations" +" and quickly find the one you need." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "" +"View of the Discuss’ sidebar emphasizing the quick search bar in Odoo " +"Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:103 +msgid "Finding channels" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:106 +msgid "" +"Click on *Channels* (on the sidebar), browse through the list of public " +"channels, and join or leave them from a single screen." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:108 +msgid "" +"Apply filters criteria and save it for later use. The search function " +"accepts wildcards by using the underscore character *(_)* to represent a " +"single character." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of a channel being searched through filters in Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:116 +msgid ":doc:`plan_activities`" +msgstr "" + +#: ../../content/applications/productivity/iot.rst:8 +msgid "Internet of Things (IoT)" +msgstr "" + +#: ../../content/applications/productivity/iot/config.rst:5 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:6 +msgid "Configuration" +msgstr "Konfiguracja" + +#: ../../content/applications/productivity/iot/config/connect.rst:3 +msgid "Connect an IoT box to Odoo" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:5 +msgid "" +"An Internet of Things (IoT) box is a micro-computer device that allows for " +"the connection of input and output devices to an Odoo database. An " +":abbr:`IoT (Internet of Things)` box subscription is required in order to " +"use the :abbr:`IoT (Internet of Things)` box with a secured connection. A " +"computer is also required to set up the :abbr:`IoT (Internet of Things)` " +"box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:11 +msgid "`IoT Box FAQ `_" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:13 +msgid "" +"Begin the :abbr:`IoT (Internet of Things)` configuration process by " +":ref:`installing the IoT app ` on the Odoo database through" +" the :menuselection:`Apps` application." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "The Internet of Things (IoT) app on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:20 +msgid "" +"Next, after the *IoT app* is installed, navigate to :menuselection:`IoT app " +"--> IoT Boxes`, and then click on the :guilabel:`Connect` button located in " +"the upper-left corner of the :menuselection:`IoT Boxes` dashboard." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Connecting an IoT box to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:28 +msgid "" +"There are two recommended ways to connect the :abbr:`IoT (Internet of " +"Things)` box to the database once the *IoT app* is installed. Follow the " +"steps in either of the next two sections to connect the :abbr:`IoT (Internet" +" of Things)` box via :ref:`wired ethernet connection `" +" or via :ref:`WiFi `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Connection steps for a wired connection or WiFi connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:38 +msgid "" +"The disk image that the :abbr:`IoT (Internet of Things)` box SD card is " +"formatted with is unique to the version of the Odoo database that the " +":abbr:`IoT (Internet of Things)` box is running on. Ensure that the " +":abbr:`IoT (Internet of Things)` box is :doc:`flashed ` with " +"the most up-to-date disk image." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:46 +msgid "Ethernet connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:48 +msgid "" +"The following is the process to connect the :abbr:`IoT (Internet of Things)`" +" box via an ethernet cable to the Odoo database (by way of the ethernet " +"port; RJ-45)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:51 +msgid "" +"First, connect all wired devices to the :abbr:`IoT (Internet of Things)` box" +" (ethernet, :abbr:`USB (Universal Serial Bus)` devices, etc.). At minimum, " +"an HDMI screen should be connected. Then, plug the :abbr:`IoT (Internet of " +"Things)` box into a power source." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:55 +msgid "" +"Immediately after the unit powers on and boots up, read the *pairing code* " +"from the screen or from the printout of a receipt printer connected to the " +":abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:59 +msgid "" +"By default, the :abbr:`IoT (Internet of Things)` box will display the " +"*pairing code* for a maximum of 5 minutes after the unit boots up. After 5 " +"minutes, the *pairing code* will disappear for security purposes and the " +":abbr:`IoT (Internet of Things)` box will need to be rebooted manually by " +"unplugging the unit from the power source for ten seconds and re-plugging it" +" back in." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:65 +msgid "" +"If no screen is attached to the :abbr:`IoT (Internet of Things)` box, then " +"the *pairing code* can be accessed from the :abbr:`IoT (Internet of Things)`" +" box homepage by clicking on the :guilabel:`POS Display` button. For " +"instructions on how to access the :abbr:`IoT (Internet of Things)` box " +"homepage visit :ref:`iot_connect/token`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:70 +msgid "" +"On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and " +"then click on the :guilabel:`Connect` button located in the upper-left " +"corner of the the :menuselection:`IoT Boxes` dashboard. Input the *pairing " +"code* in the :guilabel:`Pairing Code` field and click on the " +":guilabel:`Pair` button. The database will now link to the :abbr:`IoT " +"(Internet of Things)` box and it will appear on the :menuselection:`IoT " +"Boxes` page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:79 +msgid "WiFi connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:81 +msgid "" +"The following is the process to connect the :abbr:`IoT (Internet of Things)`" +" box via a WiFi connection to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:84 +msgid "" +"First, ensure there is no ethernet cable plugged into the :abbr:`IoT " +"(Internet of Things)` box. Then, connect all wired devices to the :abbr:`IoT" +" (Internet of Things)` box (:abbr:`USB (Universal Serial Bus)` devices, " +"etc.)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:88 +msgid "" +"After connecting the devices, plug the :abbr:`IoT (Internet of Things)` box " +"into to a power source. On the computer, navigate to :menuselection:`IoT app" +" --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in" +" the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Then" +" copy the :guilabel:`Token` from the :guilabel:`WiFi connection` section as " +"this will later be used to link the Odoo database to the :abbr:`IoT " +"(Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:94 +msgid "" +"Back on the computer, navigate to the available WiFi networks and connect to" +" the :abbr:`IoT (Internet of Things)` box WiFi network. The WiFi network " +"dispersed by the :abbr:`IoT (Internet of Things)` box will start with " +"`IoTBox-xxxxxxxxxx`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "WiFi networks available on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:102 +msgid "" +"Upon connecting to the :abbr:`IoT (Internet of Things)` box WiFi, a browser " +"will automatically redirect to the :menuselection:`Configure Iot Box` " +"wizard. Name the :abbr:`IoT (Internet of Things)` box, then paste the " +"previously copied *token* into the :guilabel:`Server Token` field, and then " +"click on :guilabel:`Next`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Enter the server token into the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:112 +msgid "" +"If the :abbr:`IoT (Internet of Things)` box WiFi connection wizard doesn't " +"start, then see the documentation on :ref:`connecting with a token " +"`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:115 +msgid "" +"Now, choose the WiFi network that the :abbr:`IoT (Internet of Things)` box " +"will connect with (enter the password if there is one) and click on " +":guilabel:`Connect`. Wait a few seconds and the browser will redirect to the" +" :abbr:`IoT (Internet of Things)` box homepage. The computer may need to be " +"manually re-connected back to the original WiFi connection, if this does not" +" happen automatically." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Configuring the WiFi for the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:124 +msgid "" +"After completing each step, the :abbr:`IoT (Internet of Things)` box should " +"appear when navigating to :menuselection:`IoT app --> IoT Boxes` on the Odoo" +" database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "The IoT box has been successfully configured on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:132 +msgid "" +"The :abbr:`IoT (Internet of Things)` box may need to be manually rebooted " +"upon successfully connecting via WiFi for the box to appear in the *IoT app*" +" on the Odoo database. To do so, simply unplug the device and plug it back " +"into the power source after ten seconds." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:139 +msgid "Manually connecting the IoT box using the token" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:141 +msgid "" +"A manual connection of the :abbr:`IoT (Internet of Things)` box to the " +":abbr:`IoT (Internet of Things)` app can be made using the *token*, from a " +"computer. The *token* can be found by navigating to :menuselection:`IoT app " +"--> IoT Boxes` and clicking on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:145 +msgid "" +"Under the :guilabel:`WiFi Connection` section of the :guilabel:`Connect an " +"IoT Box` page that appears, click :guilabel:`Copy` to the right of the " +":guilabel:`Token`. This token will be entered into the :abbr:`IoT (Internet " +"of Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:149 +msgid "" +"Access the :abbr:`IoT (Internet of Things)` box homepage by entering the " +":abbr:`IP (Internet Protocol)` address of the :abbr:`IoT (Internet of " +"Things)` box into a browser window from a computer on the same network as " +"the :abbr:`IoT (Internet of Things)` box (preferably by ethernet " +"connection)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:154 +msgid "" +"The :abbr:`IP (Internet Protocol)` address can be accessed by the router " +"admin console that the :abbr:`IoT (Internet of Things)` box is connected to," +" or by connecting a receipt printer to the :abbr:`IoT (Internet of Things)` " +"box. A receipt will print out with the :abbr:`IoT (Internet of Things)` " +"box's :abbr:`IP (Internet Protocol)` address on it." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:159 +msgid "" +"On the :abbr:`IoT (Internet of Things)` box homepage, enter the *token* " +"under the :guilabel:`Server` section by clicking on :guilabel:`Configure`. " +"Then, paste the *token* into the :guilabel:`Server Token` field and click " +":guilabel:`Connect`. The :abbr:`IoT (Internet of Things)` box will then link" +" to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:167 +msgid "IoT box schema" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:170 +msgid "Raspberry Pi 4" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:174 +msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:177 +msgid "Raspberry Pi 3" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:181 +msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:3 +msgid "Flashing the SD card" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:5 +msgid "" +"In some circumstances, the :abbr:`IoT (Internet of Things)` box's micro SD " +"Card may need to be re-flashed to benefit from Odoo's latest :abbr:`IoT " +"(Internet of Things)` image update. This means that the Odoo :abbr:`IoT " +"(Internet of Things)` box software may need to be updated." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:10 +msgid "Upgrade from the IoT box home page" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:12 +msgid "" +"Go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to " +":menuselection:`IoT app --> IoT Boxes` and clicking on the :guilabel:`IP " +"address` of the :abbr:`IoT (Internet of Things)` box. Then click on " +":guilabel:`Update` (next to the version number)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:16 +msgid "" +"If a new version of the :abbr:`IoT (Internet of Things)` Box image is " +"available, an :guilabel:`Upgrade to _xx.xx_` button will appear at the " +"bottom of the page. Click this button to upgrade the unit and the :abbr:`IoT" +" (Internet of Things)` box will then flash itself to the new version. All of" +" the previous configurations will be saved." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:22 +msgid "" +"This process can take more than 30 minutes. Do not turn off or unplug the " +":abbr:`IoT (Internet of Things)` box as it would leave it in an inconsistent" +" state. This means that the :abbr:`IoT (Internet of Things)` box will need " +"to be re-flashed with a new image. See :ref:`flash_sdcard/etcher`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst-1 +msgid "IoT box software upgrade in the IoT Box Home Page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:34 +msgid "Upgrade with Etcher Software" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:37 +msgid "" +"A computer with a micro SD card reader/adapter is required in order to re-" +"flash the micro SD card." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:40 +msgid "" +"Navigate to Balena's website and download `Etcher " +"`_. It's a free and open-source utility used for " +"burning image files onto drives. Click to `download " +"`_. Install and launch the " +"program on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:44 +msgid "" +"Then download the version-specific :abbr:`IoT (Internet of Things)` image " +"from `nightly `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:47 +msgid "" +"The following are image versions on the `nightly " +"`_ website with their corresponding " +"Odoo database version:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:50 +msgid "Odoo V16 --> iotbox-latest.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:51 +msgid "Odoo V15 --> iotboxv21_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:52 +msgid "Odoo V14 --> iotboxv21_04.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:53 +msgid "Odoo V13 --> iotboxv20_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:55 +msgid "" +"The images should be downloaded and extracted to a convenient file location." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:57 +msgid "" +"After this step is complete, insert the :abbr:`IoT (Internet of Things)` " +"box's micro SD card into the computer or reader. Open *Etcher* and select " +":guilabel:`Flash from file`, then find and select the image just downloaded " +"and extracted. Next, select the drive the image should be burned to. Lastly," +" click on :guilabel:`Flash` and wait for the process to finish." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst-1 +msgid "Balena's Etcher software dashboard." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:67 +msgid "" +"An alternative software for flashing the micro SD card is *Raspberry Pi " +"Imager*. Download the *Raspberry Pi* software `here " +"`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:5 +msgid "HTTPS certificate (IoT)" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:8 +msgid "What is HTTPS?" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:10 +msgid "" +"*Hypertext Transfer Protocol Secure* (HTTPS) is the secure version of " +"*Hypertext Transfer Protocol* (HTTP), which is the primary protocol used to " +"send data back and forth between a web browser and a website. :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` is encrypted in order to increase the " +"security of data transfer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:15 +msgid "" +":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` uses an encryption " +"protocol to encrypt communications. The protocol is called *Transport Layer " +"Security* (TLS), although formerly it was known as *Secure Sockets Layer* " +"(SSL)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:19 +msgid "" +":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` occurs based upon the " +"transmission of :abbr:`TLS (Transport Layer Security)`/:abbr:`SSL (Secure " +"Sockets Layer)` certificates, which verify that a particular provider is who" +" they say they are." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:24 +msgid "" +"In this documentation and throughout Odoo the term \"HTTPS certificate\" " +"will be used to define the fact that the :abbr:`SSL (Secure Sockets Layer)` " +"certificate is valid and allows a :abbr:`HTTPS (Hypertext Transfer Protocol " +"Secure)` connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:29 +msgid "Why is it needed?" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:31 +msgid "" +"In order to communicate with certain network devices (in particular for " +"payment terminals), the usage of :abbr:`HTTPS (Hypertext Transfer Protocol " +"Secure)` is mandatory. If the :abbr:`HTTPS (Hypertext Transfer Protocol " +"Secure)` certificate isn't valid, some devices won't be able to interact " +"with the :abbr:`IoT (Internet of Things)` Box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:37 +msgid "How to obtain a Hypertext Transfer Protocol Secure (HTTPS) certificate" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:39 +msgid "" +"The generation of the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " +"certificate is automatic." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:41 +msgid "" +"The :abbr:`IoT (Internet of Things)` Box will send a specific request to " +"``_ which will send back the :abbr:`HTTPS (Hypertext " +"Transfer Protocol Secure)` certificate if the :abbr:`IoT (Internet of " +"Things)` box and database are eligible." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:48 +msgid "Internet of Things (IoT) eligibility" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:50 +msgid "" +"The database should be a **production** instance. The database instance " +"should not be a copy, a duplicate, a staging, or a development environment." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:52 +msgid "The Odoo subscription must:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:54 +msgid "Have an :guilabel:`IoT Box Subscription` line." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:55 +msgid ":guilabel:`Status` must be :guilabel:`In Progress`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:57 +msgid "" +"If the subscription is linked to a ``_ portal user " +"check the information on the portal subscription page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +msgid "Odoo.com portal subscriptions filtered by \"in progress\"." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:64 +msgid "" +"In this case, both subscriptions are considered \"in progress\" as the " +":guilabel:`Filter By\\: In Progress` was used." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:68 +msgid "" +"If the subscription is in question, contact the database's Account Manager " +"or Partner regarding the matter." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:72 +msgid "" +"Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate " +"errors" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:74 +msgid "" +"If anything goes wrong during the process of the \"HTTPS certificate\" " +"generation or reception, a specific error will code be given on the " +":abbr:`IoT (Internet of Things)` box home page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:78 +msgid "" +"Accessing the :abbr:`IoT (Internet of Things)` box homepage will check for " +"the presence of the \"HTTPS certificate\" and will attempt its generation if" +" it is missing. As such, if there is an error on the :abbr:`IoT (Internet of" +" Things)` box home page, refresh the :abbr:`IoT (Internet of Things)` home " +"page to see if the error disappears." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:84 +msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:88 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:101 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:132 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:150 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:167 +msgid "Reason:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:87 +msgid "" +"The configuration regarding the server is missing. In other words, the Odoo " +"instance is not connected with the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:114 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:138 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:160 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:171 +msgid "Solution:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 +msgid "Ensure that the server is configured." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:94 +msgid ":doc:`/applications/productivity/iot/config/connect`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:97 +msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:100 +msgid "" +"An unhandled error happened when trying to read the existing :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 +msgid "" +"Ensure that the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " +"certificate file is readable." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:107 +msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 +msgid "" +"The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is " +"missing." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:113 +msgid "" +"Ensure that both values are configured as intended. To modify them, go to " +"the :abbr:`IoT (Internet of Things)` box home page, and navigate to " +":guilabel:`Credential`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:117 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:120 +msgid "" +"An unexpected error happened when the :abbr:`IoT (Internet of Things)` box " +"tried to reach ``_. The causes are likely due to the " +"network infrastructure/configuration:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:124 +msgid "" +"The :abbr:`IoT (Internet of Things)` box does not have access to internet." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:125 +msgid "" +"The network does not allow the :abbr:`IoT (Internet of Things)` box to " +"communicate with ``_. This may be due to network " +"devices preventing the communication (firewalls, etc.) or the network " +"configuration (:abbr:`VPN (Virtual Private Network)`, etc.)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:131 +msgid "" +"More information regarding the error that occurred can be found in the full " +"request exception details, which are in the :abbr:`IoT (Internet of Things)`" +" box logs." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:136 +msgid "" +"Consult with your system or network administrator should this issue arise. " +"This error code depends on the network infrastructure and goes beyond " +":doc:`Odoo support's service scope `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:141 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:144 +msgid "" +"The IoT-box was able to reach ``_ but received an " +"unusual `HTTP response (status codes) `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:148 +msgid "" +"This error code will also give the HTTP response status codes. For example, " +"if the error reads `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` it means that the" +" page returned a 404 error, which is the \"Page Not Found\" code." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:153 +msgid "" +"Check if ``_ is down using a web browser, as it's " +"possible that it is down due to maintenance." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:156 +msgid "" +"If ``_ is down due to maintenance, unfortunately there" +" is nothing that can be done but instead wait for it to recover." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:158 +msgid "" +"If ``_ is not down due to maintenance, open a `support" +" ticket `_ on the matter. Ensure that the 3 " +"digits status code next to the code error is included in the support ticket." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:163 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:166 +msgid "" +"The :abbr:`IoT (Internet of Things)` box was able to reach " +"``_ but it refused to deliver the :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:170 +msgid "" +"Ensure that the :abbr:`IoT (Internet of Things)` box and database are " +"eligible for a certificate: :ref:`Internet of Things (IoT) eligibility " +"`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:174 +msgid "How to ensure that the HTTPS certificate is correct" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:176 +msgid "" +"If the certificate has been applied successfully, a new :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` :abbr:`URL (Uniform Resource Locator)`" +" for the :abbr:`IoT (Internet of Things)` box ending with `.odoo-iot.com` " +"will appear on the Odoo database, inside of the :menuselection:`IoT` " +"application on that specific device's form." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst-1 +msgid "Odoo IoT app IoT box with .odoo-iot.com domain." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:185 +msgid "" +"When navigating to the :abbr:`URL (Uniform Resource Locator)` in a browser a" +" secured :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection will " +"be established." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:192 +msgid "Example of valid SSL certificate details on the browser." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:192 +msgid "" +"Padlock in Chrome on Windows 10 attesting the fact that the connection is " +"secured in :abbr:`HTTPS (Hypertext Transfer Protocol Secure)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:195 +msgid "" +"The IoT-box homepage will now display an `OK` status next to `HTTPS " +"certificate`. The drop-down menu icon, when clicked, will reveal information" +" regarding the certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst-1 +msgid "IoT box homepage with HTTPS certificate OK status." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:203 +msgid "Domain Name System (DNS) issue" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:205 +msgid "" +"If the :abbr:`IoT (Internet of Things)` box can be accessed from its " +":abbr:`IP (Intrernet Protocol)` address but not the Odoo assigned domain: " +"`.odoo-iot.com`; then the :abbr:`IoT (Internet of Things)` box is likely " +"running into a :abbr:`DNS (Domain Name System)` issue. On some browsers, it " +"will give an error code mentioning :abbr:`DNS (Domain Name System)` (like " +"`DNS_PROBE_FINISHED_NXDOMAIN`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:210 +msgid "" +"These :abbr:`DNS (Domain Name System)` issues may appear as the following in" +" different browsers:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:214 +msgid "Chrome" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:220 +msgid "DNS issue on Chrome browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:223 +msgid "Firefox" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:229 +msgid "DNS issue on Firefox browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:231 +msgid "Edge" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:237 +msgid "DNS issue on Edge browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:241 +msgid "Domain Name System (DNS) issue solution" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:243 +msgid "" +"Should the router allow the :abbr:`DNS (Domain Name System)` to be manually " +"changed, change the DNS to use `Google DNS " +"`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:245 +msgid "" +"If your router doesn't allow for this, then a change will need to be made on" +" the :abbr:`DNS (Domain Name System)` settings of each of the devices using " +"`Google DNS `_. This will " +"need to occur on **every** device that plans to interact with the :abbr:`IoT" +" (Internet of Things)` box (e.g. computer, tablet or phone). The individual " +"device configuration processes can be found on the website of the device's " +"manufacturer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:253 +msgid "" +"Other :abbr:`IoT (Internet of Things)` devices such as payment terminals " +"likely won't need their :abbr:`DNS (Domain Name System)` settings changed as" +" they are already configured with custom :abbr:`DNS (Domain Name System)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:258 +msgid "" +"Consult with your system or network administrator should this issue arise. " +"This error code depends on the network infrastructure, and it goes beyond " +":doc:`Odoo support's service scope `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:3 +msgid "Use an IoT box with a PoS" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:6 +msgid "Prerequisites" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:8 +msgid "Before starting, make sure the following equipment is available:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:10 +msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:11 +msgid "A computer or tablet with an up-to-date web browser." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:12 +msgid "" +"Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* " +"applications installed." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:13 +msgid "" +"A local network set up with :abbr:`DHCP (Dynamic Host Configuration " +"Protocol)` (this is the default setting)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:15 +msgid "" +"An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already " +"built in)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:16 +msgid "" +"Any of the supported hardware (receipt printer, barcode scanner, cash " +"drawer, payment terminal, scale, customer display, etc.). The list of " +"supported hardware can be found on the `POS Hardware page " +"`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:21 +msgid "Setup" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:25 +msgid "A suggested configuration for a point of sale system." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:27 +msgid "" +"To connect hardware to the :abbr:`PoS (Point of Sale)`, the first step is to" +" connect an :abbr:`IoT (Internet of Things)` box to the database. To do " +"this, follow these instructions: :doc:`Connect an Internet of Things (IoT) " +"box to the Odoo database `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:31 +msgid "" +"Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)`" +" box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:37 +msgid "Device Name" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:38 +msgid "Instructions" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:39 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 +msgid "Printer" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:40 +msgid "" +"Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus)` " +"port or to the network, and power it on. Refer to " +":doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:43 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:149 +msgid "Cash drawer" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:44 +msgid "The cash drawer should be connected to the printer with an RJ25 cable." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:45 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:117 +msgid "Barcode scanner" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:46 +msgid "" +"In order for the barcode scanner to be compatible it must end barcodes with " +"an `ENTER` character (keycode 28). This is most likely the default " +"configuration of the barcode scanner." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:48 +msgid "Scale" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:49 +msgid "" +"Connect the scale and power it on. Refer to " +":doc:`/applications/productivity/iot/devices/scale`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:51 +msgid "Customer display" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:52 +msgid "" +"Connect a screen to the :abbr:`IoT (Internet of Things)` box to display the " +":abbr:`PoS (Point of Sale)` order. Refer to " +":doc:`/applications/productivity/iot/devices/screen`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:54 +msgid "Payment terminal" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:55 +msgid "" +"The connection process depends on the terminal. Refer to the :doc:`payment " +"terminals documentation " +"`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:58 +msgid "" +"Once this is completed, connect the :abbr:`IoT (Internet of Things)` box to " +"the :menuselection:`PoS` application. To do this, go to " +":menuselection:`Point of Sale --> Configuration --> PoS`, tick the " +":guilabel:`IoT Box` option, and select the devices to be used in this " +":abbr:`PoS (Point of Sale)`. :guilabel:`Save` the the changes." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst-1 +msgid "Configuring the connected devices in the POS application." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:67 +msgid "" +"Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be " +"launched." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:3 +msgid "Troubleshooting" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 +msgid "IoT box connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:9 +msgid "Unable to locate the pairing code to connect the IoT box" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:11 +msgid "" +"The pairing code should be printed on receipt printers connected to the " +":abbr:`IoT (Internet of Things)` box and should also be displayed on " +"connected monitors." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:14 +msgid "The pairing code doesn't show under the following circumstances:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:16 +msgid "" +"The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo " +"database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:17 +msgid "" +"The :abbr:`IoT (Internet of Things)` box is not connected to the Internet." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:18 +msgid "" +"The code is only valid for 5 minutes after the :abbr:`IoT (Internet of " +"Things)` box has started. It's automatically removed from connected displays" +" when this time has expired." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:20 +msgid "" +"The version of the :abbr:`IoT (Internet of Things)` box image is too old. If" +" the :abbr:`IoT (Internet of Things)` box image is from an earlier version, " +"then the SD card of the :abbr:`IoT (Internet of Things)` box will need to be" +" re-flashed to update the image (see :doc:`Flashing the SD Card " +"`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:25 +msgid "" +"If none of the cases listed above correct the issue, then make sure that the" +" :abbr:`IoT (Internet of Things)` box has correctly started, by checking " +"that a fixed green LED is showing next to the power port." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:30 +msgid "IoT box is connected but it's not showing in the database" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:32 +msgid "" +"When an :abbr:`IoT (Internet of Things)` box connects to a database, it may " +"restart. If so, it can take up to five minutes before appearing in the " +"database. If the :abbr:`IoT (Internet of Things)` box is still not showing " +"after five minutes, make sure that the :abbr:`IoT (Internet of Things)` box " +"can reach the database and that the server doesn't use a multi-database " +"environment." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:37 +msgid "" +"To access the database from the :abbr:`IoT (Internet of Things)` box, open a" +" browser and type in the database address." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:41 +msgid "The IoT box is connected to the Odoo database, but cannot be reached" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:43 +msgid "" +"Make sure that the :abbr:`IoT (Internet of Things)` box and the computer " +"running the browser are located on the same network, as the :abbr:`IoT " +"(Internet of Things)` box cannot be reached from outside the local network." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:48 +msgid "The HTTPS certificate doesn't generate" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:50 +msgid "" +"In order to generate a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " +"certificate, an IoT box subscription is required for the :abbr:`IoT " +"(Internet of Things)` box. Connecting the :abbr:`IoT (Internet of Things)` " +"box prior to configuring an :abbr:`IoT (Internet of Things)` subscription " +"for the database and :abbr:`IoT (Internet of Things)` box with the Account " +"Manager will result in an unsecured connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:56 +msgid "" +"In addition, a firewall can also prevent the :abbr:`HTTPS (Hypertext " +"Transfer Protocol Secure)` certificate from generating correctly. In this " +"case, deactivate the firewall until the certificate is successfully " +"generated. It should also be noted that certain devices, such as a router " +"that has a built-in firewall, can prevent the :abbr:`HTTPS (Hypertext " +"Transfer Protocol Secure)` certificate from generating." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:63 +msgid ":doc:`HTTPS certificate (IoT) `" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:69 +msgid "The printer is not detected" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:71 +msgid "" +"If a printer doesn't show up in the devices list, go to the :abbr:`IoT " +"(Internet of Things)` box homepage and make sure that it is listed under " +":guilabel:`Printers`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 +msgid "The IoT box Home Page landing page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:78 +msgid "" +"If the printer is not present on the :abbr:`IoT (Internet of Things)` box " +"homepage, click :guilabel:`Printers Server`, go to the " +":guilabel:`Administration` tab and click on :guilabel:`Add Printer`. If the " +"printer is not present in the list, it's likely not connected properly." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:83 +msgid "The printer outputs random text" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:85 +msgid "" +"For most printers, the correct driver should be automatically detected and " +"selected. However, in some cases, the automatic detection mechanism might " +"not be enough, and if no driver is found, the printer might print random " +"characters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:89 +msgid "" +"The solution is to manually select the corresponding driver. On the " +":abbr:`IoT (Internet of Things)` box homepage, click on :guilabel:`Printers " +"Server`, go to the :guilabel:`Printers` tab and select the printer in the " +"list. In the :guilabel:`Administration` dropdown, click on :guilabel:`Modify" +" Printer`. Follow the steps and select the *make* and *model* corresponding " +"to the printer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 +msgid "Edit the printer connected to the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:99 +msgid "" +"Epson and Star receipt printers and Zebra label printers do not need a " +"driver to work. Make sure that no driver is selected for those printers." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:103 +msgid "The Zebra printer doesn't print anything" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:105 +msgid "" +"Zebra printers are quite sensitive to the format of the Zebra Programming " +"Language (ZPL) code that is printed. If nothing comes out of the printer or " +"blank labels are printed, try changing the format of the report that is sent" +" to the printer by accessing :menuselection:`Settings --> Technical --> User" +" Interface --> Views` in :ref:`developer mode ` and look for" +" the corresponding template." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:112 +msgid "" +"Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming " +"Language)` files `here `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:120 +msgid "The characters read by the barcode scanner don't match the barcode" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:122 +msgid "" +"By default, most barcode scanners are configured in the US QWERTY format. If" +" the barcode scanner uses a different layout, go to the form view of the " +"device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select " +"the correct format." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:127 +msgid "Nothing happens when a barcode is scanned" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:129 +msgid "" +"Make sure that the correct device is selected in the :menuselection:`Point " +"of Sale` configuration and that the barcode is configured to send an `ENTER`" +" character (keycode 28) at the end of every barcode. To do so, navigate to " +":menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> " +"Edit`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:135 +msgid "The barcode scanner is detected as a keyboard" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:138 +msgid "" +"Some barcode scanners do not advertise themselves as barcode scanners but as" +" a USB keyboard instead, and will not be recognized by the :abbr:`IoT " +"(Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:141 +msgid "" +"The device type can be manually changed by going to its form view " +"(:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the" +" :guilabel:`Is scanner` option." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 +msgid "Modifying the form view of the barcode scanner." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 +msgid "The cash drawer does not open" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154 +msgid "" +"The cash drawer should be connected to the printer and the :guilabel:`Cash " +"drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` " +"configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu " +"on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer " +"checkbox`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices.rst:5 +msgid "Devices" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:3 +msgid "Connect a camera" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:5 +msgid "" +"A camera can be connected to an :abbr:`IoT (Internet of Things)` box with an" +" Odoo database in just a few steps. Once a camera is connected to an " +":abbr:`IoT (Internet of Things)` box, it can be used in a manufacturing " +"process, or it can be linked to a quality control point/quality check. Doing" +" so allows for the taking of pictures when a chosen quality control " +"point/check has been reached, or when a specific key is pressed during " +"manufacturing." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:12 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:14 +#: ../../content/applications/productivity/iot/devices/printer.rst:11 +#: ../../content/applications/productivity/iot/devices/scale.rst:10 +#: ../../content/applications/productivity/iot/devices/screen.rst:18 +msgid "Connection" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:14 +msgid "" +"To connect a camera to an :abbr:`IoT (Internet of Things)` box, simply " +"connect the two via cable. This is usually done with a :abbr:`USB (Universal" +" Serial Bus)` cable of some sort." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:17 +msgid "" +"If the camera is `supported `_, " +"there is no need to set up anything, as it'll be detected as soon as it's " +"connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst-1 +msgid "Camera recognized on the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:25 +msgid "Link camera to quality control point in manufacturing process" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:27 +msgid "" +"In the :menuselection:`Quality app`, a device can be set up on a " +":guilabel:`Quality Control Point`. To do that, navigate to the " +":menuselection:`Quality app --> Quality Control --> Control Points` and open" +" the desired :guilabel:`Control Point` that'll be linked to the camera." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:31 +msgid "" +"On the control point form, edit the control point by selecting the " +":guilabel:`Type` field, and clicking on :guilabel:`Take a Picture` from the " +"drop-down menu. Doing so reveals a field called :guilabel:`Device`, wherein " +"the attached *device* can be selected. :guilabel:`Save` the changes, if " +"required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst-1 +msgid "Setting up the device on the quality control point." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:40 +msgid "" +"The camera is now useable with the selected quality control point. When the " +"quality control point is reached during the manufacturing process, the " +"database prompts the operator to take a picture." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst-1 +msgid "Graphic user interface of the device on the quality control point." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:48 +msgid "" +"Quality control points can also be accessed by navigating to " +":menuselection:`IoT App --> Devices`. From here, select the device. There is" +" a :guilabel:`Quality Control Points` tab, where they can be added with the " +"device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:53 +msgid "" +"On a quality check form, the :guilabel:`Type` of check can also be specified" +" to :guilabel:`Take a Picture`. Navigate to :menuselection:`Quality app --> " +"Quality Control --> Quality Checks --> New` to create a new quality check " +"from the :guilabel:`Quality Checks` page." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:58 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:66 +#: ../../content/applications/productivity/iot/devices/printer.rst:70 +msgid "" +":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_control_points`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:59 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:67 +#: ../../content/applications/productivity/iot/devices/printer.rst:71 +msgid "" +":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_alerts`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:62 +msgid "Link camera to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:64 +msgid "" +"To link a camera to an action, it first needs to be configured on a work " +"center. Navigate to :menuselection:`Manufacturing app --> Configuration --> " +"Work Centers`. Next, go to the desired :guilabel:`Work Center` in which a " +"camera will be used to reveal that specific work center's detail form. From " +"here, add the device in the :guilabel:`IoT Triggers` tab, in the " +":guilabel:`Device` column, by clicking :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:70 +msgid "" +"Now, the camera device can be linked to the :guilabel:`Action` column drop-" +"down option labeled :guilabel:`Take a Picture`. A key can also be added to " +"trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:74 +msgid "" +"The first trigger listed is chosen first. The order of triggers matters, and" +" they can be dragged into any desired order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:78 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the camera." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:82 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:52 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:90 +#: ../../content/applications/productivity/iot/devices/printer.rst:95 +msgid ":ref:`workcenter_iot`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:3 +msgid "Connect a footswitch" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:5 +msgid "" +"When working in a manufacturing environment, it's always better for an " +"operator to have both hands available at all times. Odoo's :abbr:`IoT " +"(Internet of Things)` box makes this possible when using a footswitch." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:9 +msgid "" +"In fact, with a footswitch, the operator is able to go from one screen to " +"another, and perform actions using their foot. This can be configured in " +"just a few steps on the work center in the *Manufacturing* app." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:16 +msgid "" +"To connect a footswitch to the :abbr:`IoT (Internet of Things)` box, connect" +" the two devices via cable. More often than not, this is done with a " +":abbr:`USB (Universal Serial Bus)` cable." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:19 +msgid "" +"If the footswitch is a `supported device `_, there is no need to take further action, since it'll be " +"automatically detected when connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst-1 +msgid "Footswitch recognized on the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:27 +msgid "Link a footswitch to a work center in the Odoo Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:29 +msgid "" +"To link a footswitch to an action, it first needs to be configured on a work" +" center. Navigate to :menuselection:`Manufacturing app --> Configuration -->" +" Work Centers`. From here, go to the desired :guilabel:`Work Center` in " +"which the footswitch will be used, and add the device in the :guilabel:`IoT " +"Triggers` tab, under the :guilabel:`Device` column, by selecting " +":guilabel:`Add a Line`. Doing so means the footswitch can be linked to an " +"option in the :guilabel:`Action` column drop-down, and optionally, a key can" +" be added to trigger it. An example of an :guilabel:`Action` in the " +"*Manufacturing app* could be the :guilabel:`Validate` or :guilabel:`Mark as " +"Done` buttons on a manufacturing work order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst-1 +msgid "Footswitch trigger setup on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:43 +msgid "" +"It should be noted that the first listed trigger is chosen first. So, the " +"order matters, and these triggers can be dragged into any order. In the " +"picture above, using the footswitch automatically skips the part of the " +"process that's currently being worked on." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:48 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the footswitch." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:3 +msgid "Connect a measurement tool" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:5 +msgid "" +"With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect " +"measurement tools to the Odoo database for use in the *Quality app* on a " +"quality control point/quality check, or for use in a work center during the " +"manufacturing process." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:9 +msgid "" +"Find the list of supported devices here: `Supported devices " +"`_." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:13 +msgid "Connect with universal serial bus (USB)" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 +msgid "" +"To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the " +":abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of " +"Things)` box, and the device appears in the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 +msgid "Measurement tool recognized on the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:24 +msgid "Connect with bluetooth" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 +msgid "" +"Activate the Bluetooth functionality on the device (see the device manual " +"for further explanation), and the :abbr:`IoT (Internet of Things)` box " +"automatically connects to the device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 +msgid "Bluetooth indicator on measurement tool." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:35 +msgid "" +"Link a measurement tool to a quality control point in the manufacturing " +"process" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 +msgid "" +"In the *Quality app*, a device can be set up on a quality control point. To " +"do that, navigate to :menuselection:`Quality app --> Quality Control --> " +"Control Points`, and open the desired control point to which the measurement" +" tool should be linked." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:41 +msgid "" +"From here, edit the control point, by selecting the :guilabel:`Type` field, " +"and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a" +" field called :guilabel:`Device`, where the attached device can be selected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:45 +msgid "" +"Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. " +":guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:48 +msgid "" +"At this point, the measurement tool is linked to the chosen quality control " +"point. The value, which usually needs to be changed manually, is " +"automatically updated while the tool is being used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 +msgid "Measurement tool input in the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:56 +#: ../../content/applications/productivity/iot/devices/printer.rst:60 +msgid "" +"Quality control points can also be accessed by navigating to " +":menuselection:`IoT App --> Devices`, then select the device. There is a " +":guilabel:`Quality Control Points` tab, where they can be added with the " +"device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:61 +msgid "" +"On a quality check detail form, the :guilabel:`Type` of check can also be " +"specified to :guilabel:`Measure`. Access a new quality check detail page, by" +" navigating to :menuselection:`Quality app --> Quality Control --> Quality " +"Checks --> New`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:70 +msgid "Link a measurement tool to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 +msgid "" +"To link a measurement tool to an action, it first needs to be configured on " +"a work center. To do that, navigate to :menuselection:`Manufacturing app -->" +" Configuration --> Work Centers`. Then, select the desired work center in " +"which the measurement tool will be used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:76 +msgid "" +"On the work center page, add the device in the :guilabel:`IoT Triggers` tab," +" under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. " +"Then, the measurement tool can be linked to the :guilabel:`Action` drop-down" +" menu option labeled :guilabel:`Take Measure`. A key can be added to trigger" +" the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:82 +msgid "" +"It should be noted that the first listed trigger is chosen first. The order " +"matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:86 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the measurement tool." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:3 +msgid "Connect a printer" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:5 +msgid "" +"Printer installation can be done in a few easy steps. The printer can be " +"used to print receipts, labels, orders, or even reports from the different " +"Odoo apps. In addition, printer actions can be assigned as an *action on a " +"trigger* during the manufacturing process, or added onto a quality control " +"point or a quality check." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:13 +msgid "" +"The :abbr:`IoT (Internet of Things)` box supports printers connected through" +" :abbr:`USB (Universal Serial Bus)`, network connection, or Bluetooth. " +"`Supported printers `__ are detected" +" automatically, and appear in the :guilabel:`Devices` list of the *IoT app*." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst-1 +msgid "The printer as it would appear in the IoT app devices list." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:23 +msgid "" +"The printer can take up to two minutes to appear in the *IoT app* devices " +"list." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:26 +msgid "Link printer" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:29 +msgid "Link printer to work orders" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:31 +msgid "" +"*Work Orders* can be linked to printers, via a quality control point, to " +"print labels for manufactured products." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:34 +msgid "" +"In the *Quality app*, a device can be set up on a quality control point. To " +"do that, go to the :menuselection:`Quality app --> Quality Control --> " +"Control Points`, and open the desired control point to which the printer " +"will be linked." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:39 +msgid "" +"A *Manufacturing Operation* and *Work Order Operation* need to be attached " +"to a quality control point before the :guilabel:`Type` field allows for the " +":guilabel:`Print Label` option to be selected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:43 +msgid "" +"From here, edit the control point, by selecting the :guilabel:`Type` field, " +"and selecting :guilabel:`Print Label` from the drop-down menu of options. " +"Doing so reveals a field called :guilabel:`Device`, where the attached " +"*device* can be selected. :guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst-1 +msgid "This is the quality control point setup." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:52 +msgid "" +"The printer can now be used with the selected quality control point. When " +"the quality control point is reached during the manufacturing process, the " +"database presents the option to print labels for a specific product." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:65 +msgid "" +"On a quality check detail form, the :guilabel:`Type` of check can also be " +"specified to :guilabel:`Print Label`. To create new quality checks, navigate" +" to :menuselection:`Quality app --> Quality Control --> Quality Checks --> " +"New`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:74 +msgid "Link a printer to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:76 +msgid "" +"To link a printer to an action, it first needs to be configured on a work " +"center. To do that, navigate to :menuselection:`Manufacturing app --> " +"Configuration --> Work Centers`. From here, select the desired work center " +"in which the printer will be used. Next, add the device in the " +":guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by " +"selecting :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:82 +msgid "" +"Then, the printer can be linked to either of the following options in the " +":guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, " +":guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can " +"also be added to trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:87 +msgid "" +"The first listed trigger on the form will be chosen first. So, the order " +"matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:91 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the printer." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:98 +msgid "Link printer to reports" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:100 +msgid "" +"It's also possible to link a type of report to a certain printer. In the " +"*IoT app*, go to the :guilabel:`Devices` menu, and select the desired " +"printer that needs to be configured." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:103 +msgid "" +"From here, click :guilabel:`Edit`, go to the :guilabel:`Printer Reports` " +"tab, and select :guilabel:`Add a line`. In the window that appears, check " +"all the types of :guilabel:`Reports` that should be linked to this printer." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst-1 +msgid "The printer devices listed in the IoT Devices menu." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:111 +msgid "" +"Now, each time :guilabel:`Print` is selected in the control panel, instead " +"of downloading a PDF, Odoo sends the report to the selected printer, and " +"automatically prints it." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:115 +msgid "" +":doc:`POS Order Printing " +"<../../../sales/point_of_sale/restaurant/kitchen_printing>`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:118 +msgid "" +"Reports can also be configured in the :guilabel:`Technical Menu` while in " +":ref:`debug mode `. To do that, navigate to " +":menuselection:`Settings App --> Technical Menu --> Actions --> Reports`. " +"From here, the individual report can be found in this list, where the " +":guilabel:`IoT Device` can be set on the report." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:3 +msgid "Connect a scale" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:5 +msgid "" +"A scale can be connected to the :abbr:`IoT (Internet of Things)` box on an " +"Odoo database in a few easy steps. After setup, the *Point of Sale* app can " +"be used to weigh products, which is helpful if their prices are calculated " +"based on weight." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:12 +msgid "" +"To link the scale to the :abbr:`IoT (Internet of Things)` box, connect it " +"with a :abbr:`USB (Universal Serial Bus)` cable." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:16 +msgid "" +"In some cases, a serial port to :abbr:`USB (Universal Serial Bus)` adapter " +"may be needed." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:18 +msgid "" +"If the scale is `compatible with Odoo IoT Box " +"`_, there is no need to set up " +"anything because it will be automatically detected as soon as it is " +"connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "IOT box auto detection." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:25 +msgid "" +"The :abbr:`IoT (Internet of Things)` box may need to be restarted and the " +"scale's drivers may need to be downloaded to the box in some cases. To " +"update the drivers, go to the :abbr:`IoT (Internet of Things)` box homepage " +"and click on :guilabel:`Drivers List`. Then, click on :guilabel:`Load " +"Drivers`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "View of the IoT box settings and driver list." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:34 +msgid "" +"If loading the drivers still doesn't allow for the scale to function, it may" +" be that the scale is not compatible with the Odoo :abbr:`IoT (Internet of " +"Things)` box. In this case, a different scale will need to be used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:39 +msgid "Use a scale in a point of sale (POS) system" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:41 +msgid "" +"To use the scale in the *Point of Sale app*, go to :menuselection:`PoS app " +"--> 3-Dot Menu on the PoS --> Settings`, then enable the :abbr:`IoT " +"(Internet of Things)` box feature. After this is complete, the scale device " +"can be set." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:45 +msgid "" +"Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then " +"click :guilabel:`Save` to save the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "List of the external tools that can be used with PoS and the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:52 +msgid "" +"The scale is now available in all the :abbr:`PoS (Point of Sale)` sessions. " +"Now, if a product has a price per weight set, clicking on it on the " +":guilabel:`PoS` screen opens the scale screen, where the cashier can weigh " +"the product and add the correct price to the cart." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "Electronic Scale dashboard view when no items are being weighed." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:3 +msgid "Connect a screen" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:5 +msgid "" +"In Odoo, an :abbr:`IoT (Internet of Things)` box can be connected to a " +"screen display. After being configured, the screen can be used to display a " +"Point of Sale (PoS) order to a client." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:10 +msgid "An example of a PoS (point of sale) order on a screen display." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:12 +msgid "" +"Access the customer display by going to the :abbr:`IoT (Internet of Things)`" +" box homepage and clicking on the :guilabel:`PoS Display` button. To get to " +"the :abbr:`IoT (Internet of Things)` box homepage, navigate to " +":menuselection:`IoT app --> IoT Boxes` and click on the :abbr:`IoT (Internet" +" of Things)` box homepage link." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:20 +msgid "" +"The way to connect the screen display to the :abbr:`IoT (Internet of " +"Things)` box differs depending on the model." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:25 +msgid "IoT Box model 4" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:27 +msgid "" +"Connect up to two screens with micro-HDMI cables on the side of the " +":abbr:`IoT (Internet of Things)` box. If two screens are connected, they can" +" display distinct content (see :ref:`Screen Usage `)." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:31 +msgid "IoT Box model 3" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:33 +msgid "" +"Connect the screen with an HDMI cable on the side of the :abbr:`IoT " +"(Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:36 +msgid ":ref:`See the Raspberry Pi Schema `." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:39 +msgid "" +"Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` " +"box is switched on. If it is already on, connect the screen(s), and then " +"restart the :abbr:`IoT (Internet of Things)` box by unplugging it for ten " +"seconds and plugging it back into its power source." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:44 +msgid "" +"The usage of HDMI/micro-HDMI adapters may cause issues which will result in " +"a blank, black screen on the screen display. Using the specific cable for " +"the display connection is recommended." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:47 +msgid "" +"If the connection was successful, the screen should display the " +":guilabel:`POS Client display` screen." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "" +"The default \"POS Client Display\" screen that appears when a screen display is successfully\n" +"connected to an IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:55 +msgid "" +"The screen should also appear in the list of :guilabel:`Displays` on the " +":abbr:`IoT (Internet of Things)` box homepage. Alternatively, the display " +"can be seen by accessing :menuselection:`IoT app --> Devices`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "An example of a screen display name shown on the IoT Box Home Page." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:64 +msgid "" +"If no screen is detected, a default display named :guilabel:`Distant " +"Display` will be displayed instead. This indicates that there is no hardware" +" screen connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:0 +msgid "The \"Distant Display\" screen name will be used if no screen is detected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:74 +msgid "Usage" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:77 +msgid "Show Point of Sale orders to customers" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:79 +msgid "" +"To use the screen in the *Point of Sale app*, go to :menuselection:`Point of" +" Sale --> Configuration --> Point of Sale`, select a :abbr:`PoS (Point of " +"Sale)`, click :guilabel:`Edit` if necessary, and enable the :guilabel:`IoT " +"Box` feature." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:83 +msgid "" +"Next, select the screen from the :guilabel:`Customer Display` drop-down " +"menu. Then click :guilabel:`Save`, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "Connect the screen display to the Point of Sale app." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:90 +msgid "" +"The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A " +"screen icon will appear in the menu at the top of the screen to indicate the" +" screen's connection status." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "" +"The \"screen\" icon on the Point of Sale display shows the connection status with the\n" +"screen." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:98 +msgid "" +"The screen will automatically show the :abbr:`PoS (Point of Sale)` orders " +"and update when changes are made to the order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "An example of a PoS order on a screen display." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:106 +msgid "Display a website on the screen" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:108 +msgid "" +"Open the screen form view by accessing :menuselection:`IoT app --> Devices " +"--> Customer Display`. This allows the user to choose a particular website " +"URL to display on the screen using the :guilabel:`Display URL` field." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:5 +msgid "Mail Plugins" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:13 +msgid "" +"Mail Plugins are connectors that bridge your mailbox with your Odoo " +"database. With them, you can interact with your Odoo database directly from " +"your mailbox by:" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:16 +msgid "Creating leads and centralizing prospects' emails into the CRM app." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:17 +msgid "Generating tasks in any Odoo project." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:18 +msgid "Creating tickets in the Helpdesk app." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:19 +msgid "Searching and storing insights on your contacts." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:21 +msgid "" +"Mail Plugins are available for :doc:`Outlook ` and " +":doc:`Gmail `." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:27 +msgid "Pricing" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:29 +msgid "Mail Plugins are **free** to install and use." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:31 +msgid "" +"However, they can provide **Lead Enrichment**, which is part of a paid " +"service known as **Lead Generation**." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:34 +msgid "" +"Mail plugins allow you to test Lead Enrichment for free, whether you connect" +" the plugins to a database or not. After a while, the plugins ask you to buy" +" :doc:`../general/in_app_purchase` credits if you would like to keep using " +"this service." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:41 +msgid "Lead Generation IAP service" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:43 +msgid "" +"Lead Enrichment uses the *Lead Generation IAP service*. Each request " +"consumes one *Lead Generation credit*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:46 +msgid "" +"To buy credits, go to :menuselection:`Settings --> CRM --> Lead Enrichment " +"--> Buy credits` and select a package." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:50 +msgid "" +"If you are out of credits, the only information populated when clicking on " +"the suggested company is its website link and logo." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:52 +msgid "" +"Check out the `Lead Generation IAP service Privacy Policy " +"`_." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:56 +msgid ":doc:`../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:57 +msgid "`Odoo Tutorials: Lead Enrichment `_" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:3 +msgid "Gmail Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:5 +msgid "" +"The *Gmail Plugin* integrates an Odoo database with a Gmail inbox, so users " +"can keep track of all their work between Gmail and Odoo, without losing any " +"information." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:9 +msgid "Odoo Online users" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:11 +msgid "" +"For databases hosted on Odoo Online (or Odoo.sh), follow the steps below to " +"configure the Gmail Plugin." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:15 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:94 +msgid "Install the Gmail Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:17 +msgid "" +"First, log in to the Gmail account that the user wishes to connect to Odoo." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:19 +msgid "" +"From the Gmail inbox, click the plus sign icon on the right side panel to " +"get add-ons. If the side panel is not visible, click on the arrow icon at " +"the bottom right corner of the inbox to reveal it." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "Plus sign icon on the Gmail inbox side panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:26 +msgid "" +"Then, use the search bar to search for `Odoo` and locate the :guilabel:`Odoo" +" Inbox Addin`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "Odoo Inbox Addin on Google Workspace Marketplace." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:32 +msgid "" +"Or, go directly to the :guilabel:`Odoo Inbox Addin` page on the `Google " +"Workspace Marketplace " +"`_." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:35 +msgid "" +"Once the plugin is located, click :guilabel:`Install`. Then, click " +":guilabel:`Continue` to start the installation." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:38 +msgid "" +"Next, select which Gmail account the user wishes to connect to Odoo. Then " +"click :guilabel:`Allow` to let Odoo access the Google account. Google will " +"then show a pop-up window confirming that the installation was successful." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:43 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:134 +msgid "Configure the Odoo database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:45 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:136 +msgid "" +"The :guilabel:`Mail Plugin` feature must be enabled in the Odoo database in " +"order to use the Gmail Plugin. To enable the feature, go to " +":menuselection:`Settings --> General Settings`. Under the " +":guilabel:`Integrations` section, activate :guilabel:`Mail Plugin`, and then" +" click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "The Mail Plugin feature in the Settings." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:55 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:145 +msgid "Configure the Gmail inbox" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:57 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:147 +msgid "" +"In the Gmail inbox, a purple Odoo icon is now visible on the right side " +"panel. Click on the Odoo icon to open up the Odoo plugin window. Then, click" +" on any email in the inbox. Click :guilabel:`Authorize Access` in the plugin" +" window to grant Odoo access to the Gmail inbox." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "" +"The Authorize Access button in the right sidebar of the Odoo plugin panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:65 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:155 +msgid "" +"Next, click :guilabel:`Login`. Then, enter the URL of the Odoo database that" +" the user wishes to connect to the Gmail inbox, and log in to the database." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:69 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:159 +msgid "" +"Use the general URL for the database, not the URL of a specific page in the " +"database. For example, use `https://mycompany.odoo.com`, not " +"`https://mycompany.odoo.com/web#cids=1&action=menu`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:73 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:163 +msgid "" +"Finally, click :guilabel:`Allow` to let Gmail access the Odoo database. The " +"browser will then show a :guilabel:`Success!` message. After that, close the" +" window. The Gmail inbox and Odoo database are now connected." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:78 +msgid "Odoo On-Premise users" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:80 +msgid "" +"For databases hosted on servers other than Odoo Online (or Odoo.sh), follow " +"the steps below to configure the Gmail Plugin." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:84 +msgid "" +"As part of their security guidelines, Google requires add-on creators to " +"provide a list of URLs that can be used in actions and redirections launched" +" by the add-on. This protects users by ensuring, for example, that no add-on" +" redirects users toward a malicious website. (Read more on `Google Apps " +"Script `_.)" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:89 +msgid "" +"Since Odoo can only list the `odoo.com` domain and not every on-premise " +"customer's unique server domain, on-premise customers cannot install the " +"Gmail Plugin from the Google Workspace Marketplace." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:96 +msgid "" +"First, access the `GitHub repository `_ for the Odoo Mail Plugins. Next, click on the green " +":guilabel:`Code` button. Then, click :guilabel:`Download ZIP` to download " +"the Mail Plugin files onto the user's computer." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "" +"Download the ZIP file from the Odoo GitHub repository for Mail Plugins." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:104 +msgid "" +"Open the ZIP file on the computer. Then, go to :menuselection:`mail-client-" +"extensions-master --> gmail --> src --> views`, and open the " +":file:`login.ts` file using any text editor software, such as Notepad " +"(Windows), TextEdit (Mac), or Visual Studio Code." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:108 +msgid "" +"Delete the following three lines of text from the :file:`login.ts` file:" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:116 +msgid "" +"This removes the `odoo.com` domain constraint from the Gmail Plugin program." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:118 +msgid "" +"Next, in the ZIP file, go to :menuselection:`mail-client-extensions-master " +"--> gmail`, and open the file called :guilabel:`appsscript.json`. In the " +":guilabel:`urlFetchWhitelist` section, replace all the references to " +"`odoo.com` with the Odoo customer's unique server domain." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:122 +msgid "" +"Then, in the same :guilabel:`gmail` folder, open the file called " +":guilabel:`README.md`. Follow the instructions in the :guilabel:`README.md` " +"file to push the Gmail Plugin files as a Google Project." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:126 +msgid "" +"The computer must be able to run Linux commands in order to follow the " +"instructions on the :guilabel:`README.md` file." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:129 +msgid "" +"After that, share the Google Project with the Gmail account that the user " +"wishes to connect to Odoo. Then, click :guilabel:`Publish` and " +":guilabel:`Deploy from manifest`. Lastly, click :guilabel:`Install the add-" +"on` to install the Gmail Plugin." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:3 +msgid "Outlook Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:8 +msgid "" +"The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both" +" on Odoo and Outlook." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:13 +msgid "Enable Mail Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:15 +msgid "" +"First, you need to enable the *Mail Plugin* feature in your database. Go to " +":menuselection:`Settings --> General Settings --> Integrations`, enable " +"*Mail Plugin*, and *Save* the configuration." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:21 +msgid "Install the Outlook Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:23 +msgid "Open your Outlook mailbox and select any email." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:25 +msgid "Click on the *More actions* button and select *Get Add-ins*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "More actions button in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:31 +msgid "Select the *My add-ins* tab." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "My add-ins in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:37 +msgid "" +"Under *Custom add-ins*, click on *+ Add a custom add-in*, and then on *Add " +"from URL...*" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Custom add-ins in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:43 +msgid "" +"Enter the following URL " +"`https://download.odoocdn.com/plugins/v15/outlook/manifest.xml` and press " +"*OK*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Entering the add-in URL in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:50 +msgid "Read the warning and click on *Install*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Custom add-in installation warning in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:59 +msgid "Connect your database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:61 +msgid "" +"Open any email in your Outlook mailbox, click on the *More actions* button, " +"and select *Odoo for Outlook*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Odoo for Outlook add-in button" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:68 +msgid "" +"The right-side panel can now display **Company Insights**. At the bottom, " +"click on *Login*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Logging in your Odoo database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:75 +msgid "" +"Only a limited amount of *Company Insights* (*Lead Enrichment*) requests are" +" available as a trial. This feature requires :ref:`prepaid credits " +"`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:79 +msgid "" +"If, after a short while, the panel is still empty, it is possible that your " +"browser cookie settings prevented it from loading. Note that these settings " +"also change if you are in \"Incognito\" mode on your browser." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:84 +msgid "" +"To fix this issue, configure your browser to always allow cookies on Odoo's " +"plugin page." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:86 +msgid "" +"For Google Chrome, you can do so by following the guide at: " +"`https://support.google.com/chrome/answer/95647 " +"`_" +" and adding `download.odoo.com` to the list of `Sites that can always use " +"cookies`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:90 +msgid "Once done, the Outlook panel needs to be opened again." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:93 +msgid "Enter your Odoo database URL and click on *Login*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Entering your Odoo database URL" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:99 +msgid "Click on *Allow* to open the pop-up window." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "New window pop-up warning" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:105 +msgid "If you aren't logged into your database, enter your credentials." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:107 +msgid "Click on *Allow* to let the Outlook Plugin connect to your database." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Allowing the Outlook Plugin to connect to a database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:116 +msgid "Add a shortcut to the plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:118 +msgid "" +"By default, the Outlook Plugin can be opened from the *More actions* menu. " +"However, to save time, it's possible to add it next to the other default " +"actions." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:121 +msgid "" +"In your Outlook mailbox, click on *Settings*, then on *View all Outlook " +"settings*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Viewing all Outlook settings" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:127 +msgid "" +"Select *Customize actions* under *Mail*, click on *Odoo for Outlook*, and " +"then *Save*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +msgid "Odoo for Outlook customized action" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:133 +msgid "Open any email; the shortcut should be displayed." +msgstr "" + +#: ../../content/applications/productivity/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:17 +msgid "" +"Studio is a toolbox that allows you to customize Odoo without coding " +"knowledge. For example, you can, on any app, add or modify:" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:20 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:21 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:22 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:23 +msgid ":doc:`Automated actions `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:24 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:25 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:26 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:28 +msgid "" +"Or you can :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/productivity/studio.rst:31 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:3 +msgid "Automated actions (automations)" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:5 +msgid "" +"Automated actions are used to trigger automatic changes based on user " +"actions (e.g., apply a modification when a field is set to a specific value)" +" or on time conditions (e.g., archive a record 7 days after its last " +"update)." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:9 +msgid "" +"To create an automated action with Studio, go to :guilabel:`Automations` " +"from anywhere within Studio." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:12 +msgid "" +"For every automated action you create, the following elements should be " +"defined: the :ref:`studio/automated-actions/model`, the " +":ref:`studio/automated-actions/trigger`, the :ref:`studio/automated-" +"actions/apply-on`, and the :ref:`studio/automated-actions/action`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of an automated action on the Subscription model" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:25 +msgid "Model" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:27 +msgid "Select the model where the automated action should be applied." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:30 +msgid "" +"The model you are on when you click on :guilabel:`Automations` is pre-" +"selected by default." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:35 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:37 +msgid "" +"Define when the automated action should be applied. Six triggers are " +"available." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:42 +msgid "On Creation" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:44 +msgid "The action is triggered when a record is created and then saved." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:49 +msgid "On Update" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:51 +msgid "" +"The action is triggered when a previously saved record is edited and then " +"saved." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:53 +msgid "" +"Use :guilabel:`Trigger Fields` to specify which fields - and only those - " +"trigger the action on their update." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:55 +msgid "" +"To detect when a record changes from one state to another, define a " +":guilabel:`Before Update Domain` filter, which checks if the condition is " +"satisfied before the record is updated. Then set an :ref:`studio/automated-" +"actions/apply-on` filter, which checks if the condition is met after the " +"record is updated." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:61 +msgid "" +"If you want the automated action to happen when an email address is set on a" +" contact, define the :guilabel:`Before Update Domain` to `Email is not set`," +" and the :guilabel:`Apply on` domain to `Email is set`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of an On Update trigger" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:72 +msgid "On Creation & Update" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:74 +msgid "" +"The action is triggered when a record is created and saved or edited " +"afterward and saved." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:79 +msgid "On Deletion" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:81 +msgid "The action is triggered when a record is deleted." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:84 +msgid "" +"This trigger is rarely used, as archiving records is usually preferred to " +"deletion." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:89 +msgid "Based on Form Modification" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:91 +msgid "" +"The action is triggered when any change is done to a trigger field's value " +"on the :ref:`Form view `, even before saving the " +"record. This trigger only works on the user interface when a modification is" +" made by a user. If the field is changed through another action and not by " +"the user, the action will not run." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:97 +msgid "" +"This trigger can only be used with the :ref:`Execute Python Code action " +"`, so development is required." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:103 +msgid "Based on Timed Condition" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:105 +msgid "" +"The action is triggered when a trigger field's date or date & time value is " +"reached." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:107 +msgid "" +"To trigger the action after the :guilabel:`Trigger Date`, add a number of " +"minutes, hours, days, or months under :guilabel:`Delay after trigger date`. " +"To trigger the action before, add a negative number instead." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:112 +msgid "" +"If you want to send a reminder email 30 minutes before the start of a " +"calendar event, select the :guilabel:`Start (Calendar Event)` under " +":guilabel:`Trigger Date` and set the :guilabel:`Delay after trigger date` to" +" **-30** :guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Based on Timed Condition trigger" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:121 +msgid "By default, the scheduler checks for trigger dates every 4 hours." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:126 +msgid "Apply on" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:128 +msgid "" +"Define on which records of the model the automated action should be applied." +" It works the same way as when you apply filters on a model." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:134 +msgid "Action" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:136 +msgid "" +"Determine what the automated action should do (server action). There are " +"eight types of action to choose from." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:142 +msgid "Execute Python Code" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:144 +msgid "" +"The action is used to execute Python code. The available variables are " +"described on the :guilabel:`Python Code` tab, which is also used to write " +"your code, or on the :guilabel:`Help` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:147 +msgid "" +"To allow the action to be run through the website, tick :guilabel:`Available" +" on the Website` and add a :guilabel:`Website Path`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:153 +msgid "Create a new Record" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:155 +msgid "The action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:158 +msgid "" +"Selecting a :guilabel:`Target Model` is only required if you want to target " +"another model than the one you are on." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:161 +msgid "" +"To link the record that triggered the creation of the new record, select a " +"field under :guilabel:`Link Field`. For example, you could create a contact " +"automatically when a lead is turned into an opportunity." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:164 +msgid "" +":guilabel:`Data to Write` tab: the tab is used to specify the new record's " +"values. After selecting a :guilabel:`Field`, select its " +":guilabel:`Evaluation Type`:" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:167 +msgid "" +":guilabel:`Value`: used to directly give the field's raw value in the " +":guilabel:`Value` column." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:168 +msgid "" +":guilabel:`Reference`: used to select the record under the " +":guilabel:`Record` column and let Studio add the internal ID in the " +":guilabel:`Value` column." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:172 +msgid "" +"If an automated action creates a new task in a project, you can assign it to" +" a specific user by setting the :guilabel:`Field` to :guilabel:`Responsible " +"User (Project)`, the :guilabel:`Evaluation Type` to :guilabel:`Reference`, " +"and the :guilabel:`Record` to a specific user." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Create a new Record action" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:181 +msgid "" +":guilabel:`Python expression`: used to dynamically define the newly created " +"record’s value for a field using Python code in the :guilabel:`Value` " +"column." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:187 +msgid "Update the Record" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:189 +msgid "" +"The action is used to set value(s) for field(s) of any record on the current" +" model." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:192 +msgid "" +"The process to fill in the :guilabel:`Data to Write` tab is the same as " +"described under :ref:`studio/automated-actions/action/new-record`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:198 +msgid "Execute several actions" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:200 +msgid "" +"The action is used to trigger multiple actions at the same time. To do so, " +"click on :guilabel:`Add a line` under the :guilabel:`Actions` tab. In the " +":guilabel:`Child Actions` pop-up, click on :guilabel:`Create` and configure " +"the action." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:207 +msgid "Send Email" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:209 +msgid "" +"The action is used to send an email to a contact linked to a specific " +"record. To do so, select or create an :guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:215 +msgid "Add Followers" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:217 +msgid "The action is used to subscribe existing contacts to the record." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:222 +msgid "Create Next Activity" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:224 +msgid "" +"The action is used to schedule a new activity linked to the record. Use the " +":guilabel:`Activity` tab to set it up as usual, but instead of the " +":guilabel:`Assigned to` field, select an :guilabel:`Activity User Type`. " +"Select :guilabel:`Specific User` and add the user under " +":guilabel:`Responsible` if the activity should always be assigned to the " +"same user. To dynamically target a user linked to the record, select " +":guilabel:`Generic User From Record` instead and change the :guilabel:`User " +"field name` if necessary." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:232 +msgid "" +"After a lead is turned into an opportunity, you want your automated action " +"to set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity` to :guilabel:`Call` and set the :guilabel:`Activity " +"User Type` to :guilabel:`Generic User From Record`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Create Next Activity action" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:243 +msgid "Send SMS Text Message" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:245 +msgid "" +"The action is used to send an SMS to a contact linked to the record. To do " +"so, select or create an :guilabel:`SMS Template`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:249 +msgid "" +"If you want sent messages to be logged in the Chatter, tick :guilabel:`Log " +"as Note`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:26 +#: ../../content/applications/productivity/studio/fields.rst:325 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:36 +#: ../../content/applications/productivity/studio/fields.rst:220 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:38 +#: ../../content/applications/productivity/studio/fields.rst:71 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:66 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:68 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:82 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:84 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:87 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:89 +#: ../../content/applications/productivity/studio/fields.rst:118 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:91 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:103 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:105 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:109 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:112 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the later " +"as it offers more functionalities." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:115 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:116 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:120 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:131 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:133 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:136 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:149 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:151 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:153 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:164 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:166 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:168 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:180 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:182 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:185 +msgid "" +":guilabel:`Date`: used to record the time without displaying it on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:186 +msgid "" +":guilabel:`Remaining days`: displays the remaining number of days before the" +" selected date (e.g., *In 5 days*), based on the current date and time." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:198 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:200 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:203 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:204 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:215 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:217 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:222 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:224 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:228 +#: ../../content/applications/productivity/studio/fields.rst:352 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:231 +msgid "" +"By default, radio buttons are organized vertically. Tick :guilabel:`display " +"horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:243 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:245 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default " +"and four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:253 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:266 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:268 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:271 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:274 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:276 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:288 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:290 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:297 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:303 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:305 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:311 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:320 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:322 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:330 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:332 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:336 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:345 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:347 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:348 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:350 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:357 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:359 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:363 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:371 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-" +"search of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:378 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:380 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:384 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:397 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:399 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:405 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:413 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:414 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:421 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:423 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:430 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:441 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:443 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:447 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:453 +msgid "Properties" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:455 +msgid "" +":guilabel:`Invisible`: When it is not necessary for users to view a field on" +" the UI, tick :guilabel:`Invisible`. It helps clear the UI by only showing " +"the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:460 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:465 +msgid "" +"The :guilabel:`Invisible` attribute also applies to Studio. To view hidden " +"fields inside Studio, click on a view's :guilabel:`View` tab and tick " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:469 +msgid "" +":guilabel:`Required`: If a field should always be completed by the user " +"before being able to proceed, tick :guilabel:`Required`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:471 +msgid "" +":guilabel:`Read only`: If users should not be able to modify a field, tick " +":guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:474 +msgid "" +"You can choose to apply these three properties only for specific records by " +"clicking on :guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:477 +msgid "" +":guilabel:`Label`: The :guilabel:`Label` is the field's name on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:480 +msgid "" +"This is not the same name as used in the PostgreSQL database. To view and " +"change the latter, activate the :ref:`Developer mode `, and " +"edit the :guilabel:`Technical Name`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:483 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, write a " +"description under :guilabel:`Help Tooltip`. It is displayed inside a tooltip" +" box when hovering with your mouse over the field's label." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:486 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, write it under :guilabel:`Placeholder`. It is displayed in light " +"gray in lieu of the field's value." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:488 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:490 +msgid "" +":guilabel:`Default value`: To add a default value to a field when a record " +"is created, use :guilabel:`Default value`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:492 +msgid "" +":guilabel:`Limit visibility to groups`: To limit which users can see the " +"field, select a user access group." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +":guilabel:`Studio customizations` is added to your database." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:217 +msgid "" +"To export these customizations, go to :menuselection:`Main dashboard --> " +"Studio --> Customizations --> Export` to download a ZIP file containing all " +"customizations." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:220 +msgid "" +"To import and install these customizations in another database, connect to " +"the destination database and go to :menuselection:`Main dashboard --> Studio" +" --> Customizations --> Import`, then upload the exported ZIP file before " +"clicking on the :guilabel:`Import` button." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:225 +msgid "" +"Before importing, make sure the destination database contains the same apps " +"and modules as the source database. Studio does not add the underlying " +"modules as dependencies of the exported module." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can edit existing PDF reports (e.g., orders and quotations)" +" or create new ones." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:8 +msgid "" +"To edit a standard PDF report, it is strongly recommended to **duplicate** " +"it and make changes to the duplicated version, as changes made to standard " +"reports will be overwritten after an Odoo upgrade. To duplicate a report, go" +" to :menuselection:`Studio --> Reports`. Hover the mouse pointer on the top " +"right corner of the report, click the vertical ellipsis icon " +"(:guilabel:`⋮`), and then select :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:20 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:22 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings --> Companies: Document Layout --> Configure " +"Document Layout`. Layout settings apply to all reports but only to the " +"current company." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:27 +msgid "" +"Use :guilabel:`Download PDF Preview` to view how the different settings " +"affect the layout of a sample invoice." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:33 +msgid "Layout" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:35 +msgid "Four layouts are available." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:39 +msgid "Light" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:44 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:49 +msgid "Bold" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:54 +msgid "Striped" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:62 +msgid "Font" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:64 +msgid "" +"Seven fonts are available. Click on the links below to preview them on " +"`Google Fonts `_." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:67 +msgid "`Lato `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:68 +msgid "`Roboto `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:69 +msgid "`Open Sans `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:70 +msgid "" +"`Montserrat `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:71 +msgid "`Oswald `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:72 +msgid "`Raleway `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:73 +msgid "`Tajawal `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:76 +msgid ":guilabel:`Tajawal` supports both Arabic and Latin scripts." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:81 +msgid "Company logo" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:83 +msgid "Upload an image file to add a :guilabel:`Company Logo`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:86 +msgid "" +"This adds the logo to the company’s record on the *Company* model, which you" +" can access by going to :menuselection:`General Settings --> Companies --> " +"Update Info`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:92 +msgid "Colors" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:94 +msgid "" +"Change the primary and secondary colors used throughout reports to highlight" +" important elements. The default colors are automatically generated based on" +" the colors of the logo." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:100 +msgid "Layout background" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:102 +msgid "Change the :guilabel:`Layout Background` of the report:" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:104 +msgid ":guilabel:`Blank`: nothing is displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:105 +msgid "" +":guilabel:`Geometric`: an image featuring geometric shapes is displayed in " +"the background." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:106 +msgid ":guilabel:`Custom`: use a custom background image by uploading one." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:111 +msgid "Company tagline" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:113 +msgid "" +"The :guilabel:`Company Tagline` is displayed on the header of :ref:`External" +" reports `. You can add multiple " +"lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:119 +msgid "Company details" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:121 +msgid "" +"The :guilabel:`Company Details` are displayed on the header of " +":ref:`External reports `. You can" +" add multiple lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:127 +msgid "Footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:129 +msgid "" +"Use the :guilabel:`Footer` field to put any text in the :ref:`External " +"reports' ` footers. You can add " +"multiple lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:135 +msgid "Paper format" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:137 +msgid "" +"Use the :guilabel:`Paper format` field to change the paper size of reports. " +"You can either select :guilabel:`A4` (21 cm x 29.7 cm) or :guilabel:`US " +"Letter` (21.59 cm x 27.54 cm)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:141 +msgid "" +"You can change the :guilabel:`Paper format` on individual reports. Open the " +"app containing the report, then go to :menuselection:`Studio --> Reports -->" +" Select or Create a report --> Report --> Select a Paper format`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "Configuration pop-up window for the default layout of PDF reports" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:151 +msgid "Header and footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:153 +msgid "" +"When creating a new report in Studio, you must choose between one of three " +"styles of reports first. This is solely used to determine what is displayed " +"on the header and footer. To do so, go to the app on which you want to add a" +" new report, then :menuselection:`Studio button --> Reports --> Create` and " +"select :ref:`studio/pdf-reports/header-footer/external`, :ref:`studio/pdf-" +"reports/header-footer/internal`, or :ref:`studio/pdf-reports/header-" +"footer/blank`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:162 +msgid "External" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:164 +msgid "" +"The header displays the company :ref:`studio/pdf-reports/default-" +"layout/logo` and several values set on the *Company* model: the " +":guilabel:`Company Name`, :guilabel:`Phone`, :guilabel:`Email`, and " +":guilabel:`Website`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:169 +msgid "" +"To change a company's information, go to :menuselection:`Settings --> " +"Companies --> Update Info`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "Example of an External header" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:174 +msgid "" +"The footer displays the values set on the :ref:`studio/pdf-reports/default-" +"layout/footer`, :ref:`studio/pdf-reports/default-layout/details`, and " +":ref:`studio/pdf-reports/default-layout/tagline` fields, as well as the page" +" number." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "Example of an External footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:184 +msgid "Internal" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:186 +msgid "" +"The header displays the user's current date and time, :guilabel:`Company " +"Name`, and page number." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:188 +msgid "There is no footer." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:193 +msgid "Blank" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:195 +msgid "There is neither a header nor a footer." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:200 +msgid "Add tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:202 +msgid "" +"After opening an existing report or creating a new one, go to the " +":guilabel:`Add` tab to add or edit elements. The elements are organized into" +" four categories: :ref:`studio/pdf-reports/elements/block`, " +":ref:`studio/pdf-reports/elements/inline`, :ref:`studio/pdf-" +"reports/elements/table`, and :ref:`studio/pdf-reports/elements/column`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:210 +msgid "Block" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:212 +msgid "" +"Block elements start on a new line and occupy the full width of the page." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:215 +msgid "" +"You can set an element's width by selecting it and going to the " +":guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:217 +#: ../../content/applications/productivity/studio/pdf_reports.rst:246 +msgid ":guilabel:`Text`: add any text using small font size by default." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:219 +msgid "" +":guilabel:`Title Block`: add any text using larger font size by default." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:221 +msgid "" +":guilabel:`Image`: add an image. You can either upload one from your device," +" add one from an URL, or select one already existing on your database." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:224 +#: ../../content/applications/productivity/studio/pdf_reports.rst:248 +msgid ":guilabel:`Field`: dynamically add a field's value." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:226 +msgid "" +":guilabel:`Field & Label`: to dynamically add a field's value and label." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:228 +msgid "" +":guilabel:`Address Block`: to dynamically add the values, if any, of a " +"contact's (`res.partner` model): *Name*, *Address*, *Phone*, *Mobile*, and " +"*Email*." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Example of an Address Block" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:237 +msgid "Inline" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:239 +msgid "" +"Inline elements are used around other elements. They do not start on a new " +"line and the width adapts to length of the content." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:243 +msgid "" +"You can set an element's width and margins by selecting it and going to the " +":guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:253 +msgid "Table" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:255 +msgid "Table elements are used together to create a data table." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:257 +msgid "" +":guilabel:`Data table`: create a table and dynamically add a first column " +"displaying the *Name* values of a :ref:`Many2Many ` or :ref:`One2Many ` field on your model." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Example of a Data table" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:264 +msgid "" +":guilabel:`Field Column`: add a new column to the table displaying the " +"values of a :ref:`Related Field ` to the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:268 +msgid ":guilabel:`Text in Cell`: add any text within an existing table cell." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:270 +msgid "" +":guilabel:`Field in Cell`: add, within an existing table cell, the values of" +" a :ref:`Related Field ` to " +"the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:274 +msgid "" +":guilabel:`Subtotal & Total`: add an existing :guilabel:`Total` field's " +"value. If a :guilabel:`Taxes` field exists, the untaxed and taxes amounts " +"are added before the total amount." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:280 +msgid "Column" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:282 +msgid "" +"Columns are used to add multiple :ref:`blocks ` elements on the same line." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:285 +msgid ":guilabel:`Two Columns`: add any text in two different columns." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:287 +msgid ":guilabel:`Three Columns`: add any text in three different columns." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:290 +msgid "Report tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:292 +msgid "" +"Several configuration options are available under the :guilabel:`Report` " +"tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:294 +msgid "" +":guilabel:`Name`: change the report name. The new name is applied everywhere" +" (in Studio, under the :guilabel:`Print` button, and for the PDF file name)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:297 +msgid ":guilabel:`Paper format`: change the paper size of the report." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:299 +msgid "" +":guilabel:`Add in print`: add the report under the :guilabel:`🖶 Print` " +"button available on the record." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:302 +msgid "" +":guilabel:`Limit visibility to groups`: limit the availability of the PDF " +"report to specific :doc:`user groups <../../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:306 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:308 +msgid "" +"Select an element on the report to access the element's options and edit it." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "The Options tab for a text element" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:314 +msgid "" +"You can select and edit multiple elements at the same time by clicking on " +"the different sections or divisions (e.g., `div`, `table`, etc.)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:317 +msgid "Below are presented some of the most common options:" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:319 +msgid "" +":guilabel:`Margins`: add spacing at the :guilabel:`top`, :guilabel:`right`, " +":guilabel:`bottom`, and :guilabel:`left` of the element." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:322 +msgid ":guilabel:`Width`: set the element's maximum width." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:324 +msgid "" +":guilabel:`Visible if`: set under which condition(s) the element should be " +"displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:326 +msgid "" +":guilabel:`Visible for`: set for which :doc:`users groups " +"<../../general/users/access_rights>` the element should be displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:329 +msgid "" +":guilabel:`Remove from View`: remove the element from the report's view." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:331 +msgid ":guilabel:`Text decoration`: bold, italicize, and underline the font." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:333 +msgid "" +":guilabel:`Alignment`: align the element to the left, center, or right of " +"the report." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:335 +msgid ":guilabel:`Font style`: use one of the default font styles." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:337 +msgid ":guilabel:`Colors`: change the font's color and the background color." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:340 +msgid "" +"You may need to select a section or division above the element you want to " +"edit to see some of the options described above." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +"model. One model can have several views, which are simply different ways to " +"show the same data. In Studio, views are organized into four categories: " +":ref:`general `, :ref:`multiple records " +"`, :ref:`timeline `, " +"and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:12 +msgid "" +"To change the default view of a model, go to :menuselection:`Studio --> " +"Views --> Dropdown menu (⋮) --> Set as Default`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:16 +msgid "" +"You can modify views by using the built-in XML editor. To do so, activate " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab and then click on :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:21 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard views and inherited views, as those would be reset and " +"would not be kept in case of an update or module upgrade. Always make sure " +"you select the right Studio inherited views. Indeed, when you modify a view " +"in Studio by drag-and-dropping a new field, a specific Studio inherited view" +" and its XPath, the latter which defines which part of the view is modified," +" are automatically generated." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:31 +msgid "General views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:34 +#: ../../content/applications/productivity/studio/views.rst:97 +#: ../../content/applications/productivity/studio/views.rst:195 +#: ../../content/applications/productivity/studio/views.rst:311 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:40 +msgid "Form" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:42 +msgid "" +"The :guilabel:`Form` view is used when creating and editing records, such as" +" contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:45 +msgid "" +"To structure a form, drag-and-drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:47 +#: ../../content/applications/productivity/studio/views.rst:132 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:59 +msgid "Activity" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:61 +msgid "" +"The :guilabel:`Activity` view is used to schedule and have an overview of " +"activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:65 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:76 +msgid "Search" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:78 +msgid "" +"The :guilabel:`Search` view is added on top of other views to filter, group," +" and search records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:80 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:82 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:94 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:103 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:105 +msgid "" +"The :guilabel:`Kanban` view is often used to support business flows by " +"moving records across stages or as an alternative way to display records " +"inside *cards*." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:109 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:112 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:113 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:115 +msgid "" +"To change the way records are grouped by default, select a new group under " +":guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:127 +msgid "List" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:129 +msgid "" +"The :guilabel:`List` view is used to overview many records at once, look for" +" records, and edit simple records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:134 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`New record on top` or :guilabel:`New record at the bottom` under " +":guilabel:`Editable`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:138 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:141 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:142 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:145 +msgid "" +"To add a drag handle icon to reorder records manually, add an :ref:`Integer " +"field ` with the :guilabel:`Handle` " +"widget." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:161 +msgid "Map" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:163 +msgid "" +"The :guilabel:`Map` view is used to display records on a map. For example, " +"it is used in the Field Service app to plan an itinerary between different " +"tasks." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:167 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:170 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:172 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:174 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:175 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:187 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:190 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:203 +msgid "" +"The :guilabel:`Calendar` view is used to overview and manage records inside " +"a calendar." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:205 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:209 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:213 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:217 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:220 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:223 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:227 +msgid "" +"You can also use :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` " +"field on the model which specifies the duration of the event. However, if " +"you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not " +"be taken into account." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:242 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:244 +msgid "" +"The :guilabel:`Cohort` view is used to examine the life cycle of records " +"over a time period. For example, it is used in the Subscriptions app to view" +" the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:247 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:249 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:251 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:255 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:268 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:270 +msgid "" +"The :guilabel:`Gantt` view is used to forecast and examine the overall " +"progress of records. Records are represented by a bar under a time scale." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:273 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:275 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:279 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:282 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:283 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:284 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:286 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:288 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:292 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:294 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:308 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:317 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:319 +msgid "" +"The :guilabel:`Pivot` view is used to explore and analyze the data contained" +" in records in an interactive manner. It is especially useful to aggregate " +"numeric data, create categories, and drill down the data by expanding and " +"collapsing different levels of data." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:323 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:325 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:327 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:329 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:341 +msgid "Graph" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:343 +msgid "" +"The :guilabel:`Graph` view is used to showcase data from records in a bar, " +"line, or pie chart." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:345 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:347 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:349 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:351 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:354 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:356 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:368 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:370 +msgid "" +"The :guilabel:`Dashboard` view is used to display multiple reporting views " +"and key performance indicators. Which elements are displayed on the view " +"depends on the configuration of the other reporting views." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales Analysis Report model's Dashboard view" +msgstr "" diff --git a/locale/pl/LC_MESSAGES/sales.po b/locale/pl/LC_MESSAGES/sales.po new file mode 100644 index 000000000..472f720d7 --- /dev/null +++ b/locale/pl/LC_MESSAGES/sales.po @@ -0,0 +1,9209 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" +"PO-Revision-Date: 2021-11-02 08:49+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications/sales.rst:5 +#: ../../content/applications/sales/sales.rst:8 +msgid "Sales" +msgstr "" + +#: ../../content/applications/sales/crm.rst:8 +msgid "CRM" +msgstr "" + +#: ../../content/applications/sales/crm.rst:10 +msgid "" +"**Odoo CRM** helps you organize your sales activities: track leads, close " +"opportunities and get accurate forecasts. Keep opportunities organized with " +"the pipeline and manage your day-to-day activities with meetings and next " +"activities." +msgstr "" + +#: ../../content/applications/sales/crm.rst:15 +msgid "`Odoo Tutorials: CRM `_" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads.rst:5 +msgid "Acquire leads" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:3 +msgid "Convert leads into opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:5 +msgid "" +"The system can generate leads instead of opportunities, in order to add a " +"qualification step before converting a *Lead* into an *Opportunity* and " +"assigning to the right sales people." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:9 +msgid "" +"You can activate this mode from the CRM Settings. It applies to all your " +"sales channels by default. But you can make it specific for specific " +"channels from their configuration form." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:14 +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 +#: ../../content/applications/sales/crm/optimize/gamification.rst:11 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:9 +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:10 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12 +#: ../../content/applications/sales/point_of_sale/configuration.rst:6 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:11 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:12 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:16 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:12 +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:9 +#: ../../content/applications/sales/point_of_sale/restaurant.rst:20 +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10 +#: ../../content/applications/sales/rental.rst:20 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:13 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:23 +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:9 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:9 +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:16 +#: ../../content/applications/sales/subscriptions/configuration.rst:5 +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:16 +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:32 +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:31 +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:25 +msgid "Configuration" +msgstr "Konfiguracja" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:16 +msgid "" +"For this feature to work, go to :menuselection:`CRM --> Configuration --> " +"Settings` and activate the *Leads* feature." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:22 +msgid "" +"You will now have a new submenu *Leads* under *Leads* where they will " +"aggregate." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:29 +msgid "Convert a lead into an opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:31 +msgid "" +"When you click on a *Lead* you will have the option to convert it to an " +"opportunity and decide if it should still be assigned to the same " +"channel/person and if you need to create a new customer." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:38 +msgid "" +"If you already have an opportunity with that customer Odoo will " +"automatically offer you to merge with that opportunity. In the same manner, " +"Odoo will automatically offer you to link to an existing customer if that " +"customer already exists." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:44 +msgid "Merge opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:46 +msgid "" +"Odoo will also automatically propose to merge opportunities if they have the" +" same email address. When merging opportunities, Odoo merges the information" +" into the opportunity which was created first, giving priority to the " +"information present on the first opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:51 +msgid "" +"No information is lost: data from the other opportunity is logged in the " +"chatter and the information fields for easy access." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:57 +msgid "" +"Would you find a duplicate yourself, ...you can also merge opportunities or " +"leads even if the system doesn't propose it." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:60 +msgid "" +"Here’s how, from the list view. Select the opportunities or leads you want " +"to merge and the action button will appear. Then, you can select merge." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:67 +msgid "It is also possible to merge more than 2 opportunities or leads." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:3 +msgid "Generate leads/opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:5 +msgid "" +"Two key ways to generate new leads or opportunities for your business are " +"through email aliases and website contact forms. Odoo automatically creates " +"leads in your CRM whenever someone sends a message to a Sales Team email " +"alias or fills out a contact form on your website." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:10 +msgid "Configure email aliases" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:12 +msgid "" +"Each Sales Team can use its own unique email alias to generate " +"leads/opportunities. Any email sent to a Sales Team's email alias will " +"automatically create a lead (if leads are activated in your CRM settings) or" +" an opportunity in the pipeline for that particular team. Configure custom " +"email aliases on the configuration page for each Sales Team by navigating to" +" :menuselection:`CRM --> Configuration --> Sales Teams`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Configuring Sales Teams" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:23 +msgid "Use Contact Forms on your website" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:25 +msgid "" +"By default, your website's *Contact Us* page displays Odoo's ready-to-use " +"Contact Form. Whenever someone submits this form, a lead or an opportunity " +"is generated in your database." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Default Contact Us page" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:32 +msgid "" +"The Contact Form can be activated or deactivated at any time by going to " +":menuselection:`Website --> Go to Website --> Customize --> Contact Form`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Contact Form toggle" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:39 +msgid "" +"When the Form is deactivated, the *Contact Us* page simply displays a button" +" to email your company directly. Any email sent this way will generate a " +"lead/opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Contact Us Page using email" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:46 +msgid "" +"Choose which Sales Team or salesperson is automatically assigned to the " +"leads/opportunities created from the Contact Form by going to " +":menuselection:`Website --> Configuration --> Settings --> Communication`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Contact Form settings" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:55 +msgid "Customize Contact Forms" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:57 +msgid "" +"Contact Forms can be customized for the specific information your team " +"needs, using the free *Form Builder* module." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:60 +msgid "" +"The *Form Builder* module is installed automatically when a Form element is " +"added to a web page via the Website Builder. It can also be installed " +"manually from the :guilabel:`Apps` page." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Form Builder building blocks" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:68 +msgid "" +"Forms can be created from scratch to serve a wide variety of purposes. " +"However, Odoo's default *Contact Us* page is designed to fit most users' " +"needs. Start with the default form and modify from there." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:73 +msgid "Edit Contact Form fields" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:75 +msgid "" +"In Edit mode on your website, click on any field to start editing it. The " +"following information can be edited for each field on the Contact Form:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:78 +msgid "" +":guilabel:`Type`: Choose a custom field option or an existing field. " +"Examples include phone, file upload, language, etc." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:80 +msgid "" +":guilabel:`Input Type`: Determine the type of entry customers should input. " +"Available options are text,email, telephone, and URL." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:82 +msgid "" +":guilabel:`Input Placeholder`: Type in an example to guide users how to " +"input information where formatting is important, such as a phone number or " +"email address." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:84 +msgid "" +":guilabel:`Label Name`: Type in the display name to show users what " +"information is needed from them." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:86 +msgid "" +":guilabel:`Label Position`: Choose the way the label is aligned with the " +"rest of the form. The label can be hidden, above the field, to the far left " +"of the field, or right adjusted and closer to the field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:89 +msgid "" +":guilabel:`Required`: Toggle this option for information that you absolutely" +" need entered." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:90 +msgid "" +":guilabel:`Hidden`: Toggle this option to hide the field without deleting " +"it." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:91 +msgid "" +":guilabel:`Shown on Mobile`: Toggle this option to show the field to users " +"on mobile devices." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Editable field options" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:97 +msgid "" +"By default, when a Form is submitted, it sends you an email with the " +"customer's inputted information. To have it automatically generate a " +"lead/opportunity instead, edit the Form and select :guilabel:`Create an " +"Opportunity` as the Action." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:102 +msgid "" +"If leads are activated in your CRM settings, selecting :guilabel:`Create an " +"Opportunity` generates a lead instead. To learn more about activating leads " +"in the CRM settings, head over to :doc:`convert`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:3 +msgid "Lead mining" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:5 +msgid "" +"Lead mining is a feature that allows CRM users to generate new leads " +"directly into their Odoo database. To ensure lead qualification, lead mining" +" output is determined by a variety of filtering criteria, such as the " +"country, the company size, and the industry." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:12 +msgid "" +"To get started, go to :menuselection:`CRM --> Configuration --> Settings` " +"and activate :guilabel:`Lead Mining`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "Activate lead mining in Odoo CRM settings." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:20 +msgid "Generate leads" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:22 +msgid "" +"After the :guilabel:`Lead Mining` setting is activated, a new button called " +":guilabel:`Generate Leads` is available to use in the :guilabel:`CRM` " +"pipeline. Lead mining requests are also available through " +":menuselection:`CRM --> Configuration --> Lead Mining Requests`, or through " +":menuselection:`CRM --> Leads --> Leads` where the :guilabel:`Generate " +"Leads` button is also available." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "The Generate Leads button to use the lead mining feature." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:32 +msgid "" +"Click on the :guilabel:`Generate Leads` button, and a window will appear " +"offering a variety of criteria by which to generate leads." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "" +"The pop-up window with the selection criteria in order to generate leads in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:39 +msgid "" +"Choose to generate leads for :guilabel:`Companies` to get company " +"information only, or choose :guilabel:`Companies and their Contacts` to get " +"company information as well as individual employee contact information. When" +" targeting :guilabel:`Companies and their Contacts`, there is an option to " +"filter contacts based on :guilabel:`Role` or :guilabel:`Seniority`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:44 +msgid "Additional filtering options include:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:46 +msgid "" +":guilabel:`Size`: filter leads based on the number of employees at the " +"company" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:47 +msgid "" +":guilabel:`Countries`: filter leads based on the country (or countries) they" +" are located in" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:48 +msgid "" +":guilabel:`States`: further filter leads based on the state they are located" +" in, if applicable" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:49 +msgid "" +":guilabel:`Industries`: filter leads based on the specific industry they " +"work in" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:50 +msgid "" +":guilabel:`Sales Team`: choose which Sales Team the leads will be assigned " +"to" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:51 +msgid "" +":guilabel:`Salesperson`: choose which person(s) on the Sales Team the leads " +"will be assigned to" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:52 +msgid "" +":guilabel:`Default Tags`: choose which tags are applied directly to the " +"leads once found" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:55 +msgid "" +"Make sure to be aware of the latest EU regulations when receiving contact " +"information. Get more information about the General Data Protection " +"Regulation on `Odoo GDPR `_." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:59 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:36 +msgid "Pricing" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:61 +msgid "" +"Lead mining is an *In-App Purchase* feature and each generated lead costs " +"one credit." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:63 +msgid "" +"Choosing to generate :guilabel:`Companies and their Contacts` costs one " +"additional credit for each contact generated." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:67 +msgid "" +"See here for full pricing information: `Lead Generation by Odoo IAP " +"`_." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:70 +msgid "" +"To buy credits, navigate to :menuselection:`CRM --> Configuration --> " +"Settings`. In the :guilabel:`Lead Generation` section, under the " +":guilabel:`Lead Mining` feature, click on :guilabel:`Buy Credits`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "Buy credits from the lead mining settings." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:78 +msgid "" +"Credits may also be purchased by navigating to the :menuselection:`Settings " +"--> General Settings`. In the :guilabel:`In-App Purchases` section, under " +"the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "Buy credits in the Odoo IAP settings." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:88 +msgid "" +"Users of Odoo Online (SaaS) Enterprise automatically have free trial credits" +" in their database to test any IAP features." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:92 +msgid ":doc:`../../../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:3 +msgid "Send quotations" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:5 +msgid "" +"When you qualify a lead into an opportunity you will most likely need to " +"send them a quotation. You can directly do this in the CRM App with Odoo." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:12 +msgid "Create a new quotation" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:14 +msgid "" +"By clicking on any opportunity or lead, you will see a *New Quotation* " +"button, it will bring you into a new menu where you can manage your quote." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:21 +msgid "" +"You will find all your quotes to that specific opportunity under the " +"*Quotations* menu on that page." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:28 +msgid "Mark them won/lost" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:30 +msgid "" +"Now you will need to mark your opportunity as won or lost to move the " +"process along." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:33 +msgid "" +"If you mark them as won, they will move to your *Won* column in your Kanban " +"view. If you however mark them as *Lost* they will be archived." +msgstr "" + +#: ../../content/applications/sales/crm/optimize.rst:5 +msgid "Optimize your Day-to-Day work" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:3 +msgid "How to motivate and reward my salespeople?" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:5 +msgid "" +"Challenging your employees to reach specific targets with goals and rewards " +"is an excellent way to reinforce good habits and improve your salespeople " +"productivity. The Gamification module gives you simple and creative ways to " +"motivate and evaluate your employees with real-time recognition and badges " +"inspired by game mechanics." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:13 +msgid "" +"Install the *Gamification* module, or the *CRM gamification* one, which adds" +" some useful data (goals and challenges) that can be used on *CRM/Sale*." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "View of the gamification module being installed in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:21 +msgid "Create a challenge" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:23 +msgid "" +"Now, create your first challenge by going to :menuselection:`Settings --> " +"Gamification Tools --> Challenges`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:27 +msgid "" +"As the gamification tool is a one-time technical setup, you need to activate" +" the technical features in order to access the configuration. To do so, go " +"to *Settings* and *Activate the developer mode*." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "View if the gamification tools menu in Odoo Settings" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:35 +msgid "" +"A challenge is a mission that you send to your sales team. It can include " +"one or several goals, set for a specific period of time. Configure your " +"challenge as follows:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:38 +msgid "Assign the salespeople to be challenged;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:39 +msgid "Assign a responsible;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:40 +msgid "Set up the periodicity along with the start and the end date;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:41 +msgid "Select your goals;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:42 +msgid "Set up your rewards (badges)." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:45 +msgid "" +"Badges are granted when a challenge is finished. This is either at the end " +"of a running period (eg: end of the month for a monthly challenge), at the " +"end date of a challenge (if no periodicity is set), or when the challenge is" +" manually closed." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:49 +msgid "" +"In the example below, 2 employees are being challenged with a *Monthly Sales" +" Target*. The challenge is based on 2 goals: the total amount invoiced and " +"number of new leads generated. At the end of the month, the winner will be " +"granted with a badge." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "" +"View of the challenge form and a challenge being created for Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:58 +msgid "Set up goals" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:60 +msgid "" +"The users can be evaluated using goals and numerical objectives to reach." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:62 +msgid "" +"**Goals** are assigned through *challenges* that evaluate (see image above) " +"and compare members of a team throughout time." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:66 +msgid "" +"You can create a new goal on the fly from a *Challenge* by clicking on *Add " +"new item*, under *Goals*. Select the business object according to your " +"company's needs. Examples: number of new leads, time to qualify a lead, " +"total amount invoiced in a specific week, month or any other time frame " +"based on your management preferences, etc." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "" +"View of the goal definition form and a goal definition being created for " +"Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:73 +msgid "" +"Goals may include your database setup as well (e.g. set your company data " +"and a timezone, create new users, etc.)." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:77 +msgid "Set up rewards" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:79 +msgid "" +"For non-numerical achievements, **Badges** can be granted to users. From a " +"simple thank you to an exceptional achievement, a badge is an easy way to " +"express gratitude to a user for their good work. To create and grant badges " +"to your employees based on their performance, go to :menuselection:`Settings" +" --> Gamification Tools --> Badges`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "View of the badges page in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:3 +msgid "Enrich your contacts base with Partner Autocomplete" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:5 +msgid "" +"Parter Autocomplete helps you to enrich your contacts database with " +"corporate data. Select one of the companies suggested in the dropdown, and " +"quickly get all the information you need." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:11 +msgid "" +"Go to :menuselection:`Settings --> Contacts` and activate the *Partner " +"Autocomplete* feature." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 +msgid "View of settings page and the activations of the feature in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:18 +msgid "Enrich your contacts with corporate data" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:22 +msgid "" +"From any module, once you start to create a new contact typing the name of " +"it, the system will suggest a potential match. If you select it, the contact" +" will be populated with corporate data." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:23 +msgid "" +"For example, after typing *Odoo*, you will get the following information:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 +msgid "Creating a new contact in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 +msgid "" +"View of the information being shown about odoo with the autocomplete option " +"in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:33 +msgid "" +"Partner Autocomplete also works if you enter a VAT number instead of a " +"company name." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:39 +msgid "" +"*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires" +" prepaid credits to be used. Each request will consume one credit." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:41 +msgid "" +"To buy credits, go to :menuselection:`Settings --> Contacts --> Partner " +"Autocomplete or Odoo IAP --> View My Services` and select a package." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:44 +msgid "" +"If you run out of credits, the only information that will be populated when " +"clicking on the suggested company will be the website link and the logo." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:46 +msgid "" +"If you are on Odoo Online and you have the Enterprise version, you benefit " +"from free trial credits to test the feature." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:48 +msgid "" +"Learn about our *Privacy Policy* `here " +"`_." +msgstr "" + +#: ../../content/applications/sales/crm/performance.rst:5 +msgid "Analyze performance" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:3 +msgid "How to use Google Spreadsheet in Addition to my Data?" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:5 +msgid "" +"Create custom dashboards in Google Spreadsheet that retrieves data directly " +"from Odoo using spreadsheet formula. You can use it to create sales " +"commission plans, budgets, project forecasts, etc. Formulas are written in " +"Python but programming skills are not required." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:12 +msgid "" +"From the *General Settings*, activate *Google Drive* and *Google " +"Spreadsheet*. The options *Authorization Code* and *Get Authorization Code* " +"are now available." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst-1 +msgid "Enable the Google Drive and Google Spreadsheet features in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:19 +msgid "Now, link your Google account with Odoo by following these steps:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:21 +msgid "Get Authorization Code" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:22 +msgid "Select your Google account" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:23 +msgid "Enter your password" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:24 +msgid "Copy the code" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:25 +msgid "Paste it into the Authorization Code field" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:28 +msgid "Create a new Spreadsheet" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:30 +msgid "" +"From the *CRM* app, for example, go to *Favorites* and click on *Add to " +"Google Spreadsheet*." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst-1 +msgid "" +"From the CRM application, for example, click on add to Google Spreadsheet in" +" Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:36 +msgid "A new spreadsheet will be automatically created in your Google Drive." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:39 +msgid "" +"When you opening this new file, a second sheet is created automatically by " +"Odoo with a tutorial/documentation on *How to use Google Spreadsheet*." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:43 +msgid "Link a Spreadsheet with Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:45 +msgid "From this new file, configure your database." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:46 +msgid "" +"Go to :menuselection:`Odoo --> Server Settings --> Database Name --> " +"Username --> Password`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst-1 +msgid "Menu called Odoo is shown on the settings bar in the Spreadsheet" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:53 +msgid "Applications" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:55 +msgid "" +"You have two different formulas available when using Google Spreadsheet in " +"Odoo: *retrieve data* and *retrieve grouped sums*." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:59 +msgid "" +"Google Drive limits the execution time of scripts; if the data you requested" +" takes too long to be delivered, you might get an error. There is no " +"specific size limit, since the time for Odoo to respond depends on several " +"factors - although reading data regarding several thousand records is " +"usually fine." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:66 +msgid "Retrieve Data" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:70 +msgid "" +"The theoretical formula is :command:`= oe_browse " +"(table;columns;filters;orderby:limit)`. Used it if you want to display the " +"information without grouping it (e.g.: each sales order in the database)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:71 +msgid "Find some the arguments in the table below." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst-1 +msgid "Table with examples of arguments to use in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:78 +msgid "Retrieve Grouped Sums" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:81 +msgid "" +"The theoretical formula is :command:`= oe_read_group " +"(table;columns;group_by;filters;orderby:limit)`. Use it when you want to " +"display a sum of data (e.g.: total invoiced)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:82 +msgid "Find some arguments in the table below." +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst-1 +msgid "Table with examples of grouped sum arguments to use in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:89 +msgid "Other uses" +msgstr "" + +#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:91 +msgid "" +"Mix Odoo data with spreadsheet data, add traditional formulas, and create " +"Dynamic Tabled and Graphs." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:3 +msgid "Check your Win/Loss Ratio" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:5 +msgid "" +"To see how well you are doing with your pipeline, take a look at the " +"Win/Loss ratio." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:8 +msgid "" +"To access this report, go to your *Pipeline* view under the *Reporting* tab." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:11 +msgid "" +"From there you can filter to which opportunities you wish to see, yours, the" +" ones from your sales channel, your whole company, etc. You can then click " +"on filter and check Won/Lost." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:18 +msgid "You can also change the *Measures* to *Total Revenue*." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:23 +msgid "You also have the ability to switch to a pie chart view." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline.rst:5 +msgid "Organize the pipeline" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:3 +msgid "Manage lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:5 +msgid "" +"While working with your opportunities, you might lose some of them. You will" +" want to keep track of the reasons you lost them and also which ways Odoo " +"can help you recover them in the future." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:10 +msgid "Mark a lead as lost" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:12 +msgid "" +"While in your pipeline, select any opportunity you want and you will see a " +"*Mark Lost* button." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:15 +msgid "" +"You can then select an existing *Lost Reason* or create a new one right " +"there." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:22 +msgid "Manage & create lost reasons" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:24 +msgid "" +"You will find your *Lost Reasons* under :menuselection:`Configuration --> " +"Lost Reasons`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:26 +msgid "" +"You can select & rename any of them as well as create a new one from there." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:30 +msgid "Retrieve lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:32 +msgid "" +"To retrieve lost opportunities and do actions on them (send an email, make a" +" feedback call, etc.), select the *Lost* filter in the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:39 +msgid "You will then see all your lost opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 +msgid "" +"If you want to refine them further, you can add a filter on the *Lost " +"Reason*." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:44 +msgid "For Example, *Too Expensive*." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:50 +msgid "Restore lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:52 +msgid "" +"From the Kanban view with the filter(s) in place, you can select any " +"opportunity you wish and work on it as usual. You can also restore it by " +"clicking on *Archived*." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:59 +msgid "" +"You can also restore items in batch from the Kanban view when they belong to" +" the same stage. Select *Restore Records* in the column options. You can " +"also archive the same way." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:66 +msgid "To select specific opportunities, you should switch to the list view." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 +msgid "" +"Then you can select as many or all opportunities and select the actions you " +"want to take." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:78 +msgid ":doc:`../performance/win_loss`" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3 +msgid "Multiple sales teams" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:5 +msgid "" +"Use the *Sales Teams* feature to manage several sales teams, departments, or" +" channels, each with their own unique sales processes." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:10 +msgid "Create a new sales team" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:12 +msgid "" +"To create a new sales team, go to :menuselection:`CRM --> Configuration --> " +"Sales Teams`, then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:15 +msgid "" +"On the creation page, set an :guilabel:`Email Alias` to automatically " +"generate a lead/opportunity for this sales team every time a message is sent" +" to that unique email address. Choose whether to accept emails from " +":guilabel:`Everyone`, :guilabel:`Authenticated Partners`, or " +":guilabel:`Followers Only`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:20 +msgid "" +"Set an :guilabel:`Invoicing Target` if this team has specific monthly " +"revenue goals. Set a :guilabel:`Domain` to assign leads/opportunities to " +"this sales team based on specific filters, such as country, language, or " +"campaign." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "Create a sales team in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:29 +msgid "Add members to a sales team" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:31 +msgid "" +"To add team members, click :guilabel:`Add` under the :guilabel:`Members` tab" +" when editing the sales team's configuration page. Select a salesperson from" +" the drop-down menu or create new salesperson. Set a maximum number of leads" +" that can be assigned to this salesperson in a 30-day period to ensure that " +"they do not overwork." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "Add a salesperson in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:40 +msgid "" +"One person can be added as a team member or :guilabel:`Team Leader` to " +"multiple sales teams, allowing them to access all of the pipelines that they" +" need to." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:44 +msgid "Sales team dashboard" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:46 +msgid "" +"To view the sales team dashboard, go to :menuselection:`CRM --> Sales --> " +"Teams`. Odoo users will see any teams that they are a part of as dashboard " +"tiles." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:49 +msgid "" +"Each tile gives an overview of the sales team's open opportunities, " +"quotations, sales orders, and expected revenue, as well as a bar graph of " +"new opportunities per week and an invoicing progress bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "Sales team overview dashboard in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:57 +msgid "" +"Click on the three dots in the corner of a tile to open a navigational menu " +"that lets users quickly view documents or reports, create new quotations or " +"opportunities, pick a color for this team, or access the team's " +"configuration page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "" +"Click the Three Dot Menu in Odoo CRM dashboard to view documents and create " +"opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:65 +msgid "" +"Click on the :guilabel:`Pipeline` button to go directly to that team's CRM " +"pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads.rst:5 +msgid "Assign and track leads" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:3 +msgid "Assign leads with predictive lead scoring" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:5 +msgid "" +"The Odoo *CRM* app can automatically assign leads/opportunities to sales " +"teams and salespeople. A standard practice is to assign leads based on the " +"probability of winning each lead. Companies can prioritize the leads that " +"are more likely to result in successful deals by quickly assigning them to " +"the appropriate salespeople." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:10 +msgid "" +"Odoo automatically calculates the probability of winning each lead using a " +"method called *predictive lead scoring*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:14 +msgid "Predictive lead scoring" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:16 +msgid "" +"Predictive lead scoring is a machine-learning model that uses historical " +"data from Odoo *CRM* to score open leads/opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:19 +msgid "" +"As a company processes opportunities through the CRM pipeline, Odoo collects" +" data on which opportunities are won and lost. Predictive lead scoring uses " +"this data to predict the probability of winning each new lead or " +"opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:23 +msgid "" +"The more opportunities that are sent through the CRM pipeline, the more data" +" Odoo collects, resulting in more accurate probabilities." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:26 +msgid "" +"Specifically, Odoo's predictive lead scoring uses the *naive Bayes* " +"probability model:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:28 +msgid "" +"\\begin{equation}\n" +"P(A | B) = \\frac{P(A) \\times P(B | A)}{P(B)}\n" +"\\end{equation}\n" +"\n" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:33 +msgid "" +"The probability of success of each opportunity is displayed on the " +"opportunity form, and it updates automatically as the opportunity progresses" +" through the CRM pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "The probability of success displayed on the opportunity form." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40 +msgid "" +"When an opportunity moves to the next stage, its probability of success " +"automatically increases according to the predictive lead scoring algorithm." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:46 +msgid "" +"Predictive lead scoring is always active in Odoo *CRM*. However, the " +"variables used to calculate the probability of success can be customized in " +"the settings." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:49 +msgid "" +"To customize the variables used by predictive lead scoring, go to " +":menuselection:`CRM --> Configuration --> Settings`. Under " +":guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update " +"Probabilities` button." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:53 +msgid "" +"Then, click on the drop-down menu to choose which variables the predictive " +"lead scoring feature will take into account." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "" +"The Update Probabilities window in the Predictive Lead Scoring settings." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60 +msgid "Any number of the following variables can be activated:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62 +msgid "" +":guilabel:`State`: the geographical state from which the opportunity " +"originates" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:63 +msgid "" +":guilabel:`Country`: the geographical country from which the opportunity " +"originates" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:64 +msgid "" +":guilabel:`Phone Quality`: whether or not a phone number is listed for the " +"opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65 +msgid "" +":guilabel:`Email Quality`: whether or not an email address is listed for the" +" opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:66 +msgid "" +":guilabel:`Source`: the source of an opportunity (e.g. search engine, social" +" media)" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:67 +msgid ":guilabel:`Language`: the spoken language specified on the opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:68 +msgid ":guilabel:`Tags`: the tags placed on the opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:71 +msgid "" +"The variables `Stage` and `Team` are always in effect. `Stage` refers to the" +" CRM pipeline stage that an opportunity is in. `Team` refers to the sales " +"team that is assigned to an opportunity. Predictive lead scoring *always* " +"takes into account these two variables, regardless of which optional " +"variables are selected." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76 +msgid "" +"Next, click on the date field next to the option :guilabel:`Consider leads " +"created as of the:` to select the date from which predictive lead scoring " +"will begin its calculations." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79 +msgid "Lastly, click :guilabel:`Confirm` to save changes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82 +msgid "Change the probability manually" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84 +msgid "" +"An opportunity's probability of success can be changed manually on the " +"opportunity form. Click on the probability number to edit it." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:88 +msgid "" +"Manually changing the probability removes the automatic probability updates " +"for that opportunity. The probability will no longer update automatically as" +" the opportunity moves through each stage of the pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92 +msgid "" +"To reactivate automatic probability, click on the gear icon next to the " +"probability percentage." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "" +"The gear icon used to reactivate automatic probability on an opportunity " +"form." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:99 +msgid "Assign leads based on probability" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:101 +msgid "" +"Odoo *CRM* can assign leads/opportunities to sales teams and salespeople " +"based on specified rules. Create assignment rules based on the leads' " +"probability of success to prioritize those that are more likely to result in" +" deals." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:106 +msgid "Configure rule-based assignment" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108 +msgid "" +"To activate *rule-based assignment*, navigate to :menuselection:`CRM --> " +"Configuration --> Settings`, and activate :guilabel:`Rule-Based Assignment`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:111 +msgid "" +"The rule-based assignment feature can be set to run :guilabel:`Manually`, " +"meaning an Odoo user must manually trigger the assignment, or " +":guilabel:`Repeatedly`, meaning Odoo will automatically trigger the " +"assignment according to the chosen time period." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115 +msgid "" +"To set up automatic lead assignment, select :guilabel:`Repeatedly` for the " +":guilabel:`Running` section. Then, customize how often Odoo will trigger the" +" automatic assignment in the :guilabel:`Repeat every` section." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "The Rule-Based Assignment setting in CRM settings." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:123 +msgid "" +"If rule-based assignment is set to run :guilabel:`Repeatedly`, the " +"assignment can still be triggered manually using the circular arrow icon in " +"the :guilabel:`Rule-Based Assignment` settings (or using the " +":guilabel:`Assign Leads` button on the sales team configuration page)." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128 +msgid "Configure assignment rules" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:130 +msgid "" +"Next, configure the *assignment rules* for each sales team and/or " +"salesperson. These rules determine which leads Odoo assigns to which people." +" To get started, navigate to :menuselection:`CRM --> Configuration --> Sales" +" Teams`, and select a sales team." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:134 +msgid "" +"On the sales team configuration form, under :guilabel:`Assignment Rules`, " +"click on :guilabel:`Edit Domain` to configure the rules that Odoo uses to " +"determine lead assignment for this sales team. The rules can include " +"anything that may be relevant for this company or team, and any number of " +"rules can be added." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:139 +msgid "" +"Click :guilabel:`Add Filter` to start creating assignment rules. Click on " +"the :guilabel:`+` sign on the right of the assignment rule to add another " +"line. Click on the :guilabel:`x` symbol to remove the line." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:143 +msgid "" +"To create an assignment rule based on an opportunity's probability of " +"success, click on the far left drop-down menu of an assignment rule line, " +"and select :guilabel:`Probability`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:146 +msgid "" +"From the middle drop-down menu, select the desired equation symbol—most " +"likely the symbol for *greater than*, *less than*, *greater than or equal " +"to*, or *less than or equal to*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:149 +msgid "" +"In the far right space, enter the desired number value of the probability. " +"Finally, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:153 +msgid "" +"To configure an assignment rule such that a sales team receives leads that " +"have a probability of success of 20% or greater, create a :guilabel:`Domain`" +" line that reads: `Probability >= 20`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:0 +msgid "" +"Sales team domain set to probability greater than or equal to twenty " +"percent." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:160 +msgid "" +"Separate assignment rules can also be configured for individual team " +"members. From the sales team configuration page, click on a team member in " +"the :guilabel:`Members` tab, then edit the :guilabel:`Domain` section. Click" +" :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:164 +msgid "" +"If automatic lead assignment is configured in the settings, both the sales " +"team and individual team members have the option to :guilabel:`Skip auto " +"assignment`. Check this box to omit a particular sales team or salesperson " +"from being assigned leads automatically by Odoo's rule-based assignment " +"feature. If :guilabel:`Skip auto assignment` is activated, the sales team or" +" salesperson can still be assigned leads manually." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:170 +msgid "" +"To manually assign leads to this sales team, click on the :guilabel:`Assign " +"Leads` button at the top of the sales team configuration page. This will " +"assign any leads that are currently unassigned and match this team's " +"specified domain." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:3 +msgid "Track your prospects visits" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:5 +msgid "" +"Tracking your website pages will give you much more information about the " +"interests of your website visitors." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:8 +msgid "" +"Every tracked page they visit will be recorded on your lead/opportunity if " +"they use the contact form on your website." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:14 +msgid "" +"To use this feature, install the free module *Lead Scoring* under your " +"*Apps* page (only available in Odoo Enterprise)." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:21 +msgid "Track a webpage" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:23 +msgid "" +"Go to any static page you want to track on your website and under the " +"*Promote* tab you will find *Optimize SEO*" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:29 +msgid "There you will see a *Track Page* checkbox to track this page." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:35 +msgid "See visited pages in your leads/opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:37 +msgid "" +"Now each time a lead is created from the contact form it will keep track of " +"the pages visited by that visitor. You have two ways to see those pages, on " +"the top right corner of your lead/opportunity you can see a *Page Views* " +"button but also further down you will see them in the chatter." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:43 +msgid "" +"Both will update if the viewers comes back to your website and visits more " +"pages." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:52 +msgid "" +"The feature will not repeat multiple viewings of the same pages in the " +"chatter." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:55 +msgid "Your customers will no longer be able to keep any secrets from you!" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:6 +msgid "Point of Sale" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:8 +msgid "" +"With **Odoo Point of Sale**, run your shops and restaurants easily. The app " +"works on any device with a web browser, even if you are temporarily offline." +" Product moves are automatically registered in your stock, you get real-time" +" statistics, and your data is consolidated across all shops." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:13 +msgid "" +"`Odoo Tutorials: Point of Sale Tutorials `_" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:14 +msgid ":doc:`IoT Boxes Documentations `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:19 +msgid "Start a session" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:21 +msgid "" +"From the **POS dashboard**, click :guilabel:`New Session` and at the " +":guilabel:`Opening Cash Control` screen, click :guilabel:`Open Session` to " +"start a POS session, or click :guilabel:`Continue Selling` if the session is" +" already opened." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:26 +msgid "" +":doc:`Multiple users ` can be logged into the " +"same session at the same time. However, the session can only be opened once " +"on the same browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:32 +msgid "Sell products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:34 +msgid "" +"Click on products to add them to the cart. To change the **quantity**, click" +" :guilabel:`Qty` and enter the number of products using the keypad. To add a" +" **discount** or modify the product **price**, click respectively " +":guilabel:`Disc` or :guilabel:`Price` and enter the amounts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:38 +msgid "" +"Once an order is completed, proceed to checkout by clicking " +":guilabel:`Payment`. Select the **payment method**, enter the received " +"amount, and click :guilabel:`Validate`. Click :guilabel:`New Order` to move " +"on to the next customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "POS session interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:47 +msgid "You can use both `,` and `.` on your keyboard as decimal separators." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:48 +msgid "" +"**Cash** is selected by default if you enter the amount without choosing a " +"payment method." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:53 +msgid "Set customers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:55 +msgid "" +"You can create and set customers from an :ref:`open POS session " +"`. Registering your customer is necessary to " +":doc:`collect their loyalty points and grant them rewards " +"`, automatically apply the :doc:`attributed " +"pricelist `, or :ref:`generate and print " +"an invoice `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:61 +msgid "" +"To access the list of customers, click :guilabel:`Customer` on the POS " +"interface. Then, select a customer or create a new one by clicking " +":guilabel:`Create`, completing the form, and saving. Lastly, click " +":guilabel:`Set Customer` to set the selected customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:68 +msgid "Customer notes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:70 +msgid "" +"You can add **customer notes** about specific products directly from an open" +" :ref:`POS session `. For instance, to provide cleaning " +"and maintenance tips. They can also be used to track a customer's particular" +" request, such as not wanting the product to be assembled for them." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:74 +msgid "" +"To do so, select a product and click :guilabel:`Customer Note` on the pad. " +"Doing so opens a pop-up window in which you can add or modify content for " +"the note." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:78 +msgid "" +"Product notes from an :doc:`imported SO ` " +"are displayed identically in the cart." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "" +"Customer note button and notes (SO and POS session) on products in the cart" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:84 +msgid "" +"Customer notes appear on customers' receipts and invoices similarly to how " +"they appear in the cart, under the related product." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "" +"Customer receipt with notes from an SO and from the customer note feature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:93 +msgid "Return and refund products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:95 +msgid "To return and refund a product," +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:97 +msgid ":ref:`start a session ` from the **POS dashboard**;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:98 +msgid "click :guilabel:`Refund` and select the corresponding order;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:99 +msgid "select the product and the quantity to refund using the keypad;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:100 +msgid "click :guilabel:`Refund` to go back to the previous screen;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:101 +msgid "" +"once the order is completed, click :guilabel:`Payment` to proceed to the " +"refund;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:102 +msgid "" +"click :guilabel:`Validate` and :guilabel:`New Order` to move on to the next " +"customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:105 +msgid "" +"You can filter the **orders list** by :guilabel:`Receipt Number`, " +":guilabel:`Date` or :guilabel:`Customer` using the search bar." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:107 +msgid "" +"You can also refund a product by selecting the returned product from an open" +" session, and setting a negative quantity that equals the number of returned" +" products. To do so, click :guilabel:`Qty` and :guilabel:`+/-`, followed by " +"the quantity of returned products." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:114 +msgid "Close the POS session" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:116 +msgid "" +"To close your session, click :guilabel:`Close` in the upper right corner of " +"your screen; doing so opens the :guilabel:`Closing Control` pop-up screen. " +"From this screen, you can retrieve various information:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:120 +msgid "" +"the number of orders made and the total amount made during the session;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:121 +msgid "" +"the total of all the transactions made during the session grouped by payment" +" method;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:122 +msgid "the expected amounts grouped by payment method." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:124 +msgid "" +"Before closing this window, count your cash using the calculator icon. Doing" +" so opens a pop-up window that computes the total amount in the cash drawer " +"depending on the coins and bills counted and added manually. Then, click " +":guilabel:`Confirm` or :guilabel:`Discard` to close the window. The computed" +" amount is set in the :guilabel:`Counted` column, and the :guilabel:`Money " +"Details` are specified in the **Notes** section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "How to close a POS session." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:134 +msgid "" +"Once you are done controlling the amounts, click :guilabel:`Close Session` " +"to close and go back to the **POS dashboard**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:138 +msgid "" +"You can let the session open by clicking :guilabel:`Keep Session Open` or " +"abort and keep selling by clicking :guilabel:`Continue Selling`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:140 +msgid "" +"Depending on your setup, you might not be allowed to close a session if the " +"expected cash revenue does not equal the counted cash. To close the session," +" check :guilabel:`Accept payments difference and post a profit/loss journal " +"entry`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:145 +msgid "" +"It is strongly advised to close your POS session at the end of each day." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:146 +msgid "" +"To look at all your previous sessions, go to :menuselection:`Point of Sale " +"--> Orders --> Sessions`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:11 +msgid "Access POS settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:13 +msgid "" +"To access the general POS settings, go to :menuselection:`Point of Sale --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:16 +msgid "" +"To access the settings of a specific point of sale, go to " +":menuselection:`Point of Sale --> Configuration --> Point of Sale`. " +"Alternatively, from the Point of Sale dashboard, click the vertical ellipsis" +" (:guilabel:`⋮`) button on a POS card, then on :guilabel:`Settings`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:21 +msgid "Make products available" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:23 +msgid "" +"To make products available for sale, go to :menuselection:`Point of Sale -->" +" Products --> Products`, and select a product to open the product form. In " +"the :guilabel:`Sales` tab, enable :guilabel:`Available in POS`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst-1 +msgid "Making a product available in your POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:5 +msgid "Self-signed certificate for ePOS printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:7 +msgid "" +"ePOS printers are designed to work seamlessly with Point of Sale systems. " +"Once connected, the two devices automatically share information, enabling " +"the direct printing of tickets from the POS system to the ePOS printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:12 +msgid "" +"These `Epson ePOS printers `_ are compatible with " +"Odoo:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:15 +msgid "TM-H6000IV-DT (Receipt printer only)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:16 +msgid "TM-T70II-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:17 +msgid "TM-T88V-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:18 +msgid "TM-L90-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:19 +msgid "TM-T20II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:20 +msgid "TM-T70-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:21 +msgid "TM-T82II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:22 +msgid "TM-T83II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:23 +msgid "TM-T88V-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:24 +msgid "TM-U220-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:25 +msgid "TM-m10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:26 +msgid "TM-m30" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:27 +msgid "TM-P20 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:28 +msgid "TM-P60II (Receipt: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:29 +msgid "TM-P60II (Peeler: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:30 +msgid "TM-P80 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:32 +msgid "" +"To work with Odoo, some models that can be used without an :doc:`IoT box " +"<../../../productivity/iot/config/connect>` may require :doc:`the HTTPS " +"protocol ` to establish a secure connection between the browser and " +"the printer. However, trying to reach the printer's IP address using HTTPS " +"leads to a warning page on most web browsers. In that case, you can " +"temporarily :ref:`force the connection `, which " +"allows you to reach the page in HTTPS and use the ePOS printer in Odoo as " +"long as the browser window stays open." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:40 +msgid "" +"The connection is lost after closing the browser window. Therefore, this " +"method should only be used as a **workaround** or as a pre-requisite for the" +" :ref:`following instructions `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 +msgid "Generate, export, and import self-signed certificates" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 +msgid "" +"For a long-term solution, you must generate a **self-signed certificate**. " +"Then, export and import it into your browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 +msgid "" +"**Generating** an SSL certificate should only be done **once**. If you " +"create another certificate, devices using the previous one will lose HTTPS " +"access." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 +msgid "Windows 10 & Linux OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62 +msgid "Generate a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 +msgid "" +"Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force " +"the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to " +"[IP address] (unsafe)`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "warning page about the connection privacy on Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72 +msgid "Warning page on Google Chrome, Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74 +msgid "" +"Then, sign in using your printer credentials to access the ePOS printer " +"settings. To sign in, enter `epson` in the :guilabel:`ID` field and your " +"printer serial number in the :guilabel:`Password` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78 +msgid "" +"Click :guilabel:`Certificate List` in the :guilabel:`Authentication` " +"section, and click :guilabel:`create` to generate a new **Self-Signed " +"Certificate**. The :guilabel:`Common Name` should be automatically filled " +"out. If not, fill it in with the printer IP address number. Select the years" +" the certificate will be valid in the :guilabel:`Validity Period` field, " +"click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the " +"printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 +msgid "" +"The self-signed certificate is generated. Reload the page and click " +":guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure " +"**Selfsigned Certificate** is correctly selected in the :guilabel:`Server " +"Certificate` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 +msgid "Export a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 +msgid "" +"The export process is heavily dependent on the :abbr:`OS (Operating System)`" +" and the browser. Start by accessing your ePOS printer settings on your web " +"browser by navigating to its IP address (e.g., `https://192.168.1.25`). " +"Then, force the connection as explained in the **Generate a self-signed " +"certificate tab**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 +msgid "If you are using **Google Chrome**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 +msgid "" +"click :guilabel:`Not secure` next to the search bar, and " +":guilabel:`Certificate is not valid`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection to the printer not secure button in Google Chrome browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 +msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105 +msgid "" +"add `.crt` at the end of the file name to ensure it has the correct " +"extension;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 +msgid "" +"select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom " +"of the pop-up window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125 +msgid "save, and the certificate is exported." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 +msgid "" +"Make sure that the certificate ends with the extension `.crt`. Otherwise, " +"some browsers might not see the file during the import process." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 +msgid "If you are using **Mozilla Firefox**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 +msgid "click the **lock-shaped** icon on the left of the address bar;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 +msgid "" +"go to :menuselection:`Connection not secure --> More information --> " +"Security tab --> View certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection is not secure button in Mozilla Firefox browser" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123 +msgid "scroll down to the :guilabel:`Miscellaneous` section;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124 +msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 +msgid "Import a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 +msgid "" +"The import process is heavily dependent on the :abbr:`OS (Operating System)`" +" and the browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 +msgid "Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 +msgid "" +"Windows 10 manages certificates, which means that self-signed certificates " +"must be imported from the certification file rather than the browser. To do " +"so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 +msgid "" +"open the Windows File Explorer and locate the downloaded certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 +msgid "" +"right-click on the certification file and click :guilabel:`Install " +"Certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 +msgid "" +"select where to install the certificate and for whom - either for the " +":guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, " +"click :guilabel:`Next`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 +msgid "" +"on the `Certificate Store` screen, tick :guilabel:`Place all certificates in" +" the following store`, click :guilabel:`Browse...`, and select " +":guilabel:`Trusted Root Certification Authorities`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:151 +msgid "click :guilabel:`Finish`, accept the pop-up security window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 +msgid "restart the computer to make sure that the changes are applied." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 +msgid "Linux" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 +msgid "open Chrome;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 +msgid "" +"go to :menuselection:`Settings --> Privacy and security --> Security --> " +"Manage certificates`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 +msgid "" +"go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select " +"the exported certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 +msgid "accept all warnings;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:164 +msgid "click :guilabel:`ok`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 +msgid "restart your browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:170 +msgid "open Firefox;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:171 +msgid "" +"go to :menuselection:`Settings --> Privacy & Security --> Security --> View " +"Certificates... --> Import`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:173 +msgid "select the exported certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 +msgid "tick the checkboxes and validate;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 +msgid "Mac OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 +msgid "To secure the connection on a Mac:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 +msgid "" +"open Safari and navigate to your printer's IP address. Doing so leads to a " +"warning page;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 +msgid "" +"on the warning page, go to :menuselection:`Show Details --> visit this " +"website --> Visit Website`, validate;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:184 +msgid "reboot the printer so you can use it with any other browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 +msgid "Android OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:188 +msgid "" +"To import an SSL certificate into an Android device, first create and export" +" it from a computer. Next, transfer the `.crt` file to the device using " +"email, Bluetooth, or USB. Once the file is on the device," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:192 +msgid "open the settings and search for `certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 +msgid "click :guilabel:`Certificate AC` (Install from device storage);" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:194 +msgid "select the certificate file to install it on the device." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:197 +msgid "" +"The specific steps for installing a certificate may vary depending on the " +"version of Android and the device manufacturer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:202 +msgid "" +"If you need to export SSL certificates from an operating system or web " +"browser that has not been mentioned, search for `export SSL certificate` + " +"`the name of your browser or operating system` in your preferred search " +"engine." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:205 +msgid "" +"Similarly, to import SSL certificates from an unmentioned OS or browser, " +"search for `import SSL certificate root authority` + `the name of your " +"browser or operating system` in your preferred search engine." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:210 +msgid "Check if the certificate was imported correctly" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:212 +msgid "" +"To confirm your printer's connection is secure, connect to its IP address " +"using HTTPS. For example, navigate to `https://192.168.1.25` in your " +"browser. If the SSL certificate has been applied correctly, you should no " +"longer see a warning page, and the address bar should display a padlock " +"icon, indicating that the connection is secure." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:3 +msgid "Secure connection (HTTPS)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:5 +msgid "" +"If **Direct Devices** is enabled in a Point of Sale settings (for example, " +"if you use an ePos printer), HTTP becomes the default protocol." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:9 +msgid "Force your Point of Sale to use a secure connection (HTTPS)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:11 +msgid "" +"Add a new **key** in the **System Parameters** to force your Point of Sale " +"to use a secure connection with the HTTPS protocol." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:14 +msgid "" +"To do so, activate the :ref:`developer mode `, go to " +":menuselection:`Settings --> Technical --> Parameters --> System " +"Parameters`, then create a new parameter, add the following values and click" +" on *Save*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:18 +msgid "**Key**: `point_of_sale.enforce_https`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:19 +msgid "**Value**: `True`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:22 +msgid ":doc:`epos_ssc`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:3 +msgid "Log in with employee" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:5 +msgid "" +"With Odoo *Point of Sale*, you can manage multiple cashiers. This feature " +"allows you to keep track of who is working, when and how much each cashier " +"made for that session." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:9 +msgid "" +"There are three ways to switch cashiers in Odoo: by *selecting the cashier*," +" by *entering a PIN code* or by *scanning a barcode*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:13 +msgid "" +"To manage multiple cashiers, you need several employees (at least two)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:18 +msgid "Set up log in with employees" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:20 +msgid "" +"To enable the feature, go to your *PoS settings* and check log in with " +"employees on your *PoS form*. Then, add the employees that have access to " +"the cash register." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:27 +msgid "Now, you can switch cashier easily." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:30 +msgid "Switch without pin codes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:32 +msgid "" +"The easiest way to switch cashiers is without a code. To do so, click on the" +" cashier name in your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:38 +msgid "Now, you just have to click on your name." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:46 +msgid "Switch cashier with pin codes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:48 +msgid "" +"You can set a pin code on each cashier. To set up a pin code, go to the " +"employee form and add a security PIN, in the *HR settings tab*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:54 +msgid "Now, when switching cashier, a PIN password will be asked." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:62 +msgid "Switch cashier with barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:64 +msgid "" +"You can ask your employees to log themselves with their badges. To do so, " +"set up a barcode at the same place you add the PIN code. Print the badge and" +" when they will scan it, the cashier will be switched to that employee." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:73 +msgid "Find who was the cashier" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:75 +msgid "" +"Once you have closed your *PoS session*, you can have an overview of the " +"amount each cashier sold for. To do so, go to the orders menu." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:81 +msgid "Now, you can open the order and have a summary of the sold products." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:5 +msgid "Payment methods" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:7 +msgid "" +"To add a payment method, you first need to create it. Go to " +":menuselection:`Point of Sale --> Configuration --> Payment Methods --> " +"Create`, and set a name. Check :guilabel:`Identify Customer` to allow this " +"payment method *exclusively* for registered customers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:11 +msgid "" +"Then, select the :guilabel:`Journal`. Choose :guilabel:`Cash` to use this " +"payment method for cash payments, or :guilabel:`Bank` to use it for card " +"payments." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst-1 +msgid "Creating a new payment method for a POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:18 +msgid "" +"Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a" +" Payment Terminal` field in which you can add your :doc:`payment terminal's " +"information `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:23 +msgid ":doc:`payment_methods/terminals`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:25 +msgid "" +"Once the payment method is created, you can select it in your POS settings. " +"To do so, go to the :ref:`POS' settings `, click " +":guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` " +"section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:5 +msgid "Payment terminals" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:7 +msgid "" +"Connecting and integrating a payment terminal with your POS system allows " +"you to accept multiple payment options, including credit and debit cards, " +"making the payment process more efficient." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 +msgid "" +"Go to the :doc:`application settings <../configuration>`, scroll down to the" +" :guilabel:`Payment Terminals` section, and tick your terminal's checkbox." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst-1 +msgid "checkbox in the settings to enable a payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:19 +msgid "Then, follow the corresponding documentation to configure your device:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21 +msgid ":doc:`Adyen configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:22 +msgid ":doc:`Ingenico configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23 +msgid ":doc:`SIX configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24 +msgid ":doc:`Vantiv configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25 +msgid ":doc:`Worldline configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:27 +msgid "" +"Once the terminal is configured, you can :doc:`create the corresponding " +"payment method and add it to the POS <../payment_methods>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:3 +msgid "Adyen" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:5 +msgid "" +"Connecting an **Adyen payment terminal** allows you to offer a fluid payment" +" flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:9 +msgid "" +"Adyen works only with businesses processing **more** than **10 million " +"annually** or invoicing a **minimum** of **1,000** transactions **per " +"month**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:15 +msgid "" +"Start by creating your Adyen account on `Adyen's website " +"`_. Then, board your terminal following the steps " +"described on your terminal's screen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:19 +msgid "" +"`Adyen Docs - Payment terminal quickstart guides " +"`_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:23 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:36 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:63 +msgid "Configure the payment method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:25 +msgid "" +"First, go to :menuselection:`Point of Sale --> Configuration --> Settings " +"--> Payment Terminals`, and enable :guilabel:`Adyen`. Then, go to " +":menuselection:`Configuration --> Payment Methods` and create a new payment " +"method. Select :guilabel:`Adyen` in the :guilabel:`Use a Payment Terminal` " +"field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:31 +msgid "" +"The selected journal **must** be a bank journal for the :guilabel:`Use a " +"payment terminal` field to appear." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:34 +msgid "" +"Finally, fill the mandatory fields with an :guilabel:`Adyen API key`, and an" +" :guilabel:`Adyen Terminal Identifier`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:38 +msgid "Generate an Adyen API key" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:40 +msgid "" +"The **Adyen API key** is a key used to authenticate your requests. To " +"generate an API key, go to your **Adyen account**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:43 +msgid "" +"Then, go to :menuselection:`Developers --> API credentials`. Create a new " +"credential or click on an existing one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:46 +msgid "" +"Click on :guilabel:`Generate an API key` and copy-paste that key onto the " +"Odoo mandatory field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:49 +msgid "" +"`Adyen Docs - API credentials `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:53 +msgid "Locate the Adyen terminal identifier" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:55 +msgid "" +"The **Adyen Terminal Identifier** is your terminal's serial number, which is" +" used to identify the hardware." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:58 +msgid "" +"To find this number, go to your **Adyen account**. Then, go to " +":menuselection:`Point of Sale --> Terminals`, select the terminal to link, " +"and copy-paste its serial number onto the Odoo mandatory field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:63 +msgid "Set the Event URLs" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:65 +msgid "" +"For Odoo to know when a payment is made, you must set the terminal **Event " +"URLs**. To do so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:67 +msgid "log in to `Adyen's website `_;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:68 +msgid "" +"go to :menuselection:`Adyen's dashboard --> Point of Sale --> Terminals` and" +" select the connected terminal;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:70 +msgid "from the terminal settings, click :guilabel:`Integrations`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:71 +msgid "" +"set the :guilabel:`Switch to decrypted mode to edit this setting` field as " +":guilabel:`Decrypted`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:72 +msgid "" +"click the **pencil icon** button and enter your server address, followed by " +"`/pos_adyen/notification` in the :guilabel:`Event URLs` field; and" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:74 +msgid "" +"click :guilabel:`Save` at the bottom of the screen to save the changes." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:77 +msgid "Add a new payment method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:79 +msgid "" +"To add a new **payment method** to a point of sale, go to " +":menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, " +"select the POS and go to :menuselection:`Payments --> Payment Methods`, and " +"add your new method for Adyen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:86 +msgid "Pay with a payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:86 +msgid "" +"When processing a payment, select :guilabel:`Adyen` as the payment method. " +"Check the amount and click on :guilabel:`Send`. Once the payment is " +"successful, the status changes to :guilabel:`Payment Successful`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 +msgid "" +"In case of connection issues between Odoo and the payment terminal, force " +"the payment by clicking on :guilabel:`Force Done`, which allows you to " +"validate the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 +msgid "" +"This option is only available after receiving an error message informing you" +" that the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:95 +msgid "To cancel the payment request, click on :guilabel:`cancel`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:3 +msgid "Ingenico" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:5 +msgid "" +"Connecting a payment terminal allows you to offer a fluid payment flow to " +"your customers and ease the work of your cashiers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:8 +msgid "" +"Please note that Ingenico is currently only available for customers in the " +"Benelux." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:15 +msgid "Connect an IoT Box" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:17 +msgid "" +"Connecting an Ingenico Payment Terminal to Odoo is a feature that requires " +"an IoT Box. For more information on how to connect an IoT Box to your " +"database, please refer to the :doc:`IoT documentation " +"`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:22 +msgid "Configure the Lane/5000 for Ingenico BENELUX" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:24 +msgid "" +"Click on the F button of the terminal, then go in the :menuselection:`PoS " +"Menu --> Settings` and enter the settings password." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:27 +msgid "" +"Now, click on connection change and TCP/IP. Type the IP of your *IoT Box* " +"(you can find it on the form view of your IoT Box). Then, enter 9000 as " +"port. The terminal will restart. Once it is done, go on your *IoT Box* form " +"in Odoo and verify that the terminal has been found." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:38 +msgid "" +"First, go in the general settings of the POS app, and activate the Ingenico " +"setting." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:44 +msgid "" +"Go back in :menuselection:`Point of Sale --> Configuration --> Point of " +"Sale`, go in the payments section and access your payment methods. Create a " +"new payment method for Ingenico, select the payment terminal option " +"Ingenico, and select your payment terminal device." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55 +msgid "" +"In your *PoS interface*, when processing a payment, select a *Payment " +"Method* using a payment terminal. Check that the amount in the tendered " +"column is the one that has to be sent to the payment terminal and click on " +"*Send*. When the payment is successful, the status will change to *Payment " +"Successful*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:64 +msgid "" +"If you want to cancel the payment request, click on cancel. You can still " +"retry to send the payment request." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:67 +msgid "" +"If there is any issue with the payment terminal, you can still force the " +"payment using the *Force Done*. This will allow you to validate the order in" +" Odoo even if the connection between the terminal and Odoo has issues." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:73 +msgid "" +"This option will only be available if you received an error message telling " +"you the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:76 +msgid "" +"Once your payment is processed, on the payment record, you’ll find the type " +"of card that has been used and the transaction ID." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:3 +msgid "SIX" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:5 +msgid "" +"Connecting a SIX payment terminal allows you to offer a fluid payment flow " +"to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:9 +msgid "" +"Starting in July 2022, it will **not** be possible anymore to connect and " +"use a Six payment terminal in PoS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:11 +msgid "" +"Even though Worldline has recently acquired SIX Payment Services and both " +"companies use Yomani payment terminals, the firmware they run is different. " +"Terminals received from Worldline are therefore not compatible with this " +"integration." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:16 +msgid "Configure the Payment Method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:21 +msgid "" +"First, make sure that the :guilabel:`POS Six` module is installed. For this," +" go to :guilabel:`Apps`, remove the :guilabel:`Apps` filter, and search for " +"*POS Six*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "The POS Six module." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:28 +msgid "" +"Back in :menuselection:`Point of Sale --> Configuration --> Payment " +"Methods`, click :guilabel:`Create` to create a new payment method for SIX, " +"select the payment terminal option :guilabel:`SIX`, and enter the payment " +"terminal IP address." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "Create a new payment method for the SIX payment terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:37 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:40 +msgid "Pay with a Payment Terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:39 +msgid "" +"In the :abbr:`PoS (Point of Sale)` interface, at the moment of the payment, " +"select a payment method using a payment terminal. Verify that the amount in " +"the tendered column is the one that has to be sent to the payment terminal " +"and click on :guilabel:`Send`. To cancel the payment request, click on " +":guilabel:`Cancel`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "The PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:48 +msgid "" +"When the payment is done, the status will change to :guilabel:`Payment " +"Successful`. If needed, reverse the last transaction by clicking on " +":guilabel:`Reverse`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "The Reverse button on the PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55 +msgid "" +"If there is any issue with the payment terminal, you can still force the " +"payment using the :guilabel:`Force Done` button. This will allow you to " +"validate the order in Odoo even if there are connection issues between the " +"payment terminal and Odoo." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:3 +msgid "Vantiv" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:5 +msgid "" +"Connecting a Vantiv payment terminal allows you to offer a fluid payment " +"flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:9 +msgid "" +"Please note MercuryPay only operates with US and Canadian banks, making this" +" procedure only suitable for North American businesses." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:18 +msgid "" +"First, go in the general settings of the POS app, and activate the Vantiv " +"setting." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:24 +msgid "" +"Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, " +"go in the payments section and access your payment methods. Create a new " +"payment method for Vantiv, select the payment terminal option Vantiv, and " +"create new Vantiv credentials." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:32 +msgid "" +"To create new Vantiv credentials, fill in your merchant ID and password, " +"then save. Make sure the credentials you just created are selected, then " +"save the payment method." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:42 +msgid "" +"In your PoS interface, at the moment of the payment, select your Vantiv " +"payment method and… that’s all." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:3 +msgid "Worldline" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:9 +msgid "Please note that Worldline is currently only available in the Benelux." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:17 +msgid "" +"Connecting a Worldline Payment Terminal to Odoo is a feature that requires " +"an IoT Box. For more information on how to connect one to your database, " +"please refer to the :doc:`IoT documentation " +"`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:22 +msgid "Configure the protocol" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:24 +msgid "" +"From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> " +"0 --> 9`. Enter the technician password **\"1235789\"** and click on " +":menuselection:`OK --> 4 --> 2`. Then, click on :menuselection:`Change --> " +"CTEP (as Protocole ECR) --> OK`. Click on **OK** thrice on the subsequent " +"screens (*CTEP ticket ECR*, *ECR ticket width*, and *Character set*). " +"Finally, press **Stop** three times; the terminal automatically restarts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:31 +msgid "Set the IP address" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:33 +msgid "" +"From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> " +"0 --> 9`. Enter the technician password **\"1235789\"** and click on " +":menuselection:`OK --> 4 --> 9`. Then, click on :menuselection:`Change --> " +"TCP/IP` (*TCP physical configuration* screen) :menuselection:`--> OK --> OK`" +" (*TCP Configuration client* screen)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:38 +msgid "Finally, set up the hostname and port number." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:41 +msgid "Hostname" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:44 +msgid "" +"To set up the hostname, enter your IoT box's IP address' sequence numbers " +"and press **OK** at each \".\" until you reach the colon symbol." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:45 +msgid "Then, press **OK** twice." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 +msgid "Here's an IP address sequence: `10.30.19.4:8069`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 +msgid "" +"On the *Hostname screen*, type :menuselection:`10 --> OK --> 30 --> OK --> " +"19 --> OK --> 4 --> OK --> OK`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:53 +msgid "" +"Your IoT box's IP address is available in your IoT Box application's " +"database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:56 +msgid "Port number" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:58 +msgid "" +"On the *Port number* screen, enter **9001** (or **9050** for Windows) and " +"click on :menuselection:`OK` (*ECR protocol SSL no*) :menuselection:`--> " +"OK`. Click on **Stop** three times; the terminal automatically restarts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:65 +msgid "" +"From the Point of Sale application, go to :menuselection:`Configuration --> " +"Settings --> Payment terminals` and activate the *Worldline* payment " +"terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:71 +msgid "" +"Then, go to :menuselection:`Configuration --> Payment methods` and create a " +"new payment method for *Worldline*. Select the payment terminal *Worldline* " +"and your payment terminal device on your *Payment Method form*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:78 +msgid "Technician password: `1235789`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:79 +msgid "" +"To reach Wordline's technical assistance, call `02 727 61 11` and choose " +"\"merchant\". Your call is automatically transferred to the desired service." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:81 +msgid "" +"Configure the cashier terminal if you have both a customer and a cashier " +"terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:82 +msgid "" +"To avoid blocking the terminal, check the initial configuration beforehand." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:83 +msgid "" +"Set a fixed IP to your IoT Box’s router to prevent losing the connexion." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:88 +msgid "" +"When processing a payment, select *Worldline* as payment method. Check the " +"amount and click on *Send*. Once the payment is successful, the status " +"changes to *Payment Successful*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91 +msgid "" +"Once your payment is processed, the type of card used and the transaction ID" +" appear on the payment record." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:98 +msgid "" +"In case of connexion issues between Odoo and the payment terminal, force the" +" payment by clicking on *Force Done*, which allows you to validate the " +"order. This option is only available after receiving an error message " +"informing you that the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:101 +msgid "To cancel the payment request, click on **cancel**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing.rst:5 +msgid "Pricing features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:3 +msgid "Cash rounding" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:5 +msgid "" +"**Cash rounding** is required when the lowest physical denomination of " +"currency, or the smallest coin, is higher than the minimum unit of account." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:9 +msgid "" +"For example, some countries require their companies to round up or down the " +"total amount of an invoice to the nearest five cents, when the payment is " +"made in cash." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:13 +msgid "" +"Each point of sale in Odoo can be configured to apply cash rounding to the " +"totals of its bills or receipts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:19 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Settings` and " +"enable *Cash Rounding*, then click on *Save*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:25 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, " +"open the point of sale you want to configure, and enable the *Cash Rounding*" +" option." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:29 +msgid "" +"To define the **Rounding Method**, open the drop-down list and click on " +"*Create and Edit...*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:32 +msgid "" +"Define here your *Rounding Precision*, *Profit Account*, and *Loss Account*," +" then save both the Rounding Method and your Point of Sale settings." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:39 +msgid "" +"All total amounts of this point of sale now add a line to apply the rounding" +" according to your settings." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:46 +msgid "" +"Odoo Point of Sale only supports the :guilabel:`Add a rounding line` " +"rounding strategy." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:3 +msgid "Discount tags (barcode scanner)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:5 +msgid "" +"If you want to sell your products with a discount, for a product getting " +"close to its expiration date for example, you can use discount tags. They " +"allow you to scan discount barcodes." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:10 +msgid "To use discount tags you will need to use a barcode scanner." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:13 +msgid "Barcode Nomenclature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:15 +msgid "To use discounts tags, we need to learn about barcode nomenclature." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:17 +msgid "" +"Let's say you want to have a discount for the product with the following " +"barcode:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:23 +msgid "" +"You can find the *Default Nomenclature* under the settings of your PoS " +"interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:32 +msgid "" +"Let's say you want 50% discount on a product you have to start your barcode " +"with 22 (for the discount barcode nomenclature) and then 50 (for the %) " +"before adding the product barcode. In our example, the barcode would be:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:41 +msgid "Scan the products & tags" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:43 +msgid "You first have to scan the desired product (in our case, a lemon)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:48 +msgid "" +"And then scan the discount tag. The discount will be applied and you can " +"finish the transaction." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:3 +msgid "Discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:5 +msgid "" +"By offering discounts, you can entice your customers and drastically " +"increase your revenue. It is vital to offer discounts, whether they are " +"time-limited, seasonal or manually given." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:9 +msgid "" +"To manage discounts, Odoo has powerful features that help set up a pricing " +"strategy tailored to every business." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:13 +msgid "Apply manual discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:15 +msgid "" +"If you seldom use discounts, applying manual ones might be the easiest " +"solution for your Point of Sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:18 +msgid "" +"You can either apply a discount on the whole order or on specific products " +"inside an order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:22 +msgid "Apply a discount on a product" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:24 +msgid "From your PoS session interface, use the *Disc* button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the discount button for manual discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:30 +msgid "" +"Then, you can input a discount over the product that is currently selected." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:34 +msgid "Apply a global discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:36 +msgid "" +"To apply a discount on the whole order, go to :menuselection:`Point of Sales" +" --> Configuration --> Point of Sale` and select your PoS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:39 +msgid "" +"Once on your PoS form, select *Global Discounts*, under the *Pricing* " +"category." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the feature to enable for global discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:45 +msgid "Now, you have a new *Discount* button appearing on your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the button to use for global discount via the pos interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:51 +msgid "Click on it and enter the wanted discount." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the discount offered in the payment summary" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:58 +msgid "" +"On this example, there is a global discount of 50% as well as a specific 50%" +" discount on oranges." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:62 +msgid "Apply time-limited discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:64 +msgid "" +"To activate time-limited discounts, you must activate the *Pricelists* " +"feature. To do so, go to :menuselection:`Point of Sales --> Configuration " +"--> Point of Sale` and open your PoS. Then, enable the pricelist feature." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the pricelist feature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:73 +msgid "" +"Once activated, you must choose the pricelists you want to make available in" +" the PoS and define a default one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:77 +msgid "Create a pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:79 +msgid "" +"By default, Odoo has a *Public Pricelist* configured. To create more, go to " +":menuselection:`Point of Sale --> Products --> Pricelists`. Then click on " +"create." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:83 +msgid "" +"When creating a pricelist, you can set several criteria to use a specific " +"price: period, min. quantity, etc. You can also decide to apply that " +"pricelist on specific products or on the whole range." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of a time-limited pricelist for two products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:92 +msgid "Using a pricelist with the PoS interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:94 +msgid "" +"On the PoS interface, a new button appears. Use it to select a pricelist." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "" +"View of the button to use for time-limited discounts via the pos interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:101 +msgid "" +"Click on it to instantly update the prices with the selected pricelist. " +"Then, you can finalize the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:3 +msgid "Tax rates (fiscal positions)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:5 +msgid "" +"In Odoo, *Fiscal Positions* let you apply different taxes based on the " +"customer location. In a *Point of Sale*, such as a restaurant, it can be " +"used to apply different taxes depending if the customer eats in or takes " +"away." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:11 +msgid "Set up fiscal positions for PoS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:13 +msgid "" +"To enable this feature, go to :menuselection:`Point of Sale --> " +"Configuration --> Point of Sale` and check *Fiscal Position per Order*. Now," +" you can choose the fiscal positions you want for your *PoS*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:21 +msgid "You need to create your fiscal positions before using this feature." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:24 +msgid "Using fiscal positions" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:26 +msgid "" +"Once on your *PoS* interface, click on the *Tax* button. Now, choose the " +"fiscal position you need for the current order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:33 +msgid "Set up a default fiscal position" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:35 +msgid "" +"If you want to use a default fiscal position, meaning that a preexisting " +"value is always automatically assigned, go to :menuselection:`Point of Sale " +"--> Configuration --> Point of Sale` and enable *Fiscal Position*. Now, " +"choose one to set as the default one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:43 +msgid "" +"Now, the *tax* button is replaced by a *on site* button when on the *PoS* " +"interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:3 +msgid "Loyalty programs" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:5 +msgid "" +"Encourage your customers to continue to shop at your point of sale with a " +"*Loyalty Program*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:11 +msgid "" +"To activate the *Loyalty Program* feature, go to :menuselection:`Point of " +"Sale --> Configuration --> Point of sale` and select your PoS interface. " +"Under the Pricing features, select *Loyalty Program*" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:19 +msgid "From there you can create and edit your loyalty programs." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:24 +msgid "" +"You can decide what type of program you wish to use, if the reward is a " +"discount or a gift, make it specific to some products or cover your whole " +"range. Apply rules so that it is only valid in specific situation and " +"everything in between." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:30 +msgid "Use the loyalty program in your PoS interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:32 +msgid "" +"When a customer is set, you will now see the points they will get for the " +"transaction and they will accumulate until they are spent. They are spent " +"using the button *Rewards* when they have enough points according to the " +"rules defined in the loyalty program." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:40 +msgid "" +"You can see the price is instantly updated to reflect the pricelist. You can" +" finalize the order in your usual way." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:44 +msgid "" +"If you select a customer with a default pricelist, it will be applied. You " +"can of course change it." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:3 +msgid "Pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:5 +msgid "" +"You probably know the concept of happy hour: during a certain period of " +"time, the barman gives a discount on some drinks (usually 50% off or a buy " +"one get one free). When the period is over, prices go back to normal. But " +"how does that relate with Odoo?" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:10 +msgid "" +"In Odoo, you can set up happy hours. It’s one of the many possible uses of " +"*Pricelists*. Those *Pricelists* allow the creation of multiple prices for " +"the same product: a regular one and a special one for happy hours. Available" +" in the *PoS* app, those are really convenient." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:17 +msgid "Set up Pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:19 +msgid "" +"To set up a *Pricelist*, go to :menuselection:`Point of Sale --> " +"Configuration --> Configuration` and enable the *Pricelist* feature. Then, " +"go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and" +" enable *Pricelist* for the *PoS*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:26 +msgid "" +"Now, you can create *Pricelists* by clicking on the *Pricelists* link. Then," +" set it up by choosing the product category you want to include in your " +"happy hour and the discount." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:33 +msgid "" +"Go back to your *PoS* settings and add the Happy Hour pricelist to the list." +" You can even choose a default pricelist if needed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:39 +msgid "" +"From now on, on the *PoS* interface, a new button is available, allowing you" +" to choose among the different *pricelists* you added before." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:46 +msgid ":doc:`../../sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:3 +msgid "Receipts and invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:6 +msgid "Receipts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:8 +msgid "" +"Set up receipts by going to :menuselection:`Point of Sale --> Configuration " +"--> Point of Sale`, selecting a POS, and scrolling down to the " +":guilabel:`Bills & Receipts` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:11 +msgid "" +"To **customize** the **header** and **footer**, activate :guilabel:`Header &" +" Footer` and fill in both fields with the information to be printed on the " +"receipts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:14 +msgid "" +"To **print receipts** automatically once the payment is registered, enable " +"the :guilabel:`Automatic Receipt Printing` setting." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "POS receipt" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:21 +msgid ":doc:`restaurant/bill_printing`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:24 +msgid "Reprint a receipt" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:26 +msgid "" +"From the POS interface, click :guilabel:`Orders`, open the dropdown " +"selection menu next to the search bar, and change the default :guilabel:`All" +" active orders` filter to :guilabel:`Paid`. Then, select the corresponding " +"order and click :guilabel:`Print Receipt`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "Print receipt button from the backend" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:34 +msgid "" +"You can filter the list of orders using the search bar. Type in your " +"reference and click :guilabel:`Receipt Number`, :guilabel:`Date`, or " +":guilabel:`Customer`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:40 +msgid "Invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:42 +msgid "" +"Some of your customers might request an invoice when buying from your Point " +"of Sale, you can easily manage it directly from the PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:46 +msgid "Activate invoicing" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:48 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and" +" select your Point of Sale:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:53 +msgid "" +"Under the *Bills & Receipts* you will see the invoicing option, tick it. " +"Don't forget to choose in which journal the invoices should be created." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:60 +msgid "Select a customer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:62 +msgid "From your session interface, use the customer button" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:66 +msgid "" +"You can then either select an existing customer and set it as your customer " +"or create a new one by using this button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:71 +msgid "" +"You will be invited to fill out the customer form with its information." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:74 +msgid "Invoice your customer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:76 +msgid "" +"From the payment screen, you now have an invoice option, use the button to " +"select it and validate." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:81 +msgid "You can then print the invoice and move on to your next order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:84 +msgid "Retrieve invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:86 +msgid "" +"Once out of the PoS interface (:menuselection:`Close --> Confirm` on the top" +" right corner) you will find all your orders in :menuselection:`Point of " +"Sale --> Orders --> Orders` and under the status tab you will see which ones" +" have been invoiced. When clicking on a order you can then access the " +"invoice." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:3 +#: ../../content/applications/sales/subscriptions/reporting.rst:5 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:6 +msgid "View statistics" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:8 +msgid "" +"To access your statistics, go to :menuselection:`Point of Sale --> Reporting" +" --> Orders`. Or, from the **POS dashboard**, click the vertical ellipsis " +"(:guilabel:`⋮`) button, :guilabel:`Reporting`, and :guilabel:`Orders`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:12 +msgid "" +"These statistics are available in a graph or pivot view that you can filter " +"or group depending on your needs." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:5 +msgid "Restaurant features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:7 +msgid "" +"Managing a restaurant or a bar comes with specific needs. The Point of Sale " +"application provides various features that allow performing all the required" +" tasks in such businesses." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:10 +msgid "Once the POS is set to be used in a restaurant or a bar, you can:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:12 +msgid "" +":doc:`organize your floors and tables to reflect your interior " +"`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:13 +msgid ":ref:`take orders `;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:14 +msgid "" +":doc:`communicate with the kitchen or the bar through the POS " +"`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:15 +msgid "" +":doc:`print bills in advance and split them `;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:16 +msgid ":doc:`collect tips `; and" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:17 +msgid "" +":doc:`set different taxes for takeaway food `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:22 +msgid "" +"To activate the features, go to :menuselection:`Point of Sale --> " +"Configuration --> Point of Sale`, select your POS, and click " +":menuselection:`Edit --> Is a Bar/Restaurant --> Save`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:26 +msgid "" +"These specific features can be identified by the cutlery-shaped icon located" +" to the right of the feature name." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3 +msgid "Bills" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:5 +msgid "" +"Typical practices in restaurants or bars are to request the bill before " +"proceeding to payment or splitting it based on the items ordered. Odoo POS " +"provides two features to perform these tasks seamlessly: **Bill Printing** " +"and **Bill Splitting**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:12 +msgid "" +"To activate the bill printing and splitting features, go to " +":menuselection:`Point of Sale --> Configuration --> Point of sale` and " +"select your POS. Then, scroll down to the :guilabel:`Bills & Receipts` " +"section and enable :guilabel:`Bill Printing` and :guilabel:`Bill Splitting`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst-1 +msgid "" +"activate the bill printing and bill splitting features in the POS settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:21 +msgid "Bill printing" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:23 +msgid "" +"From an open session, click :menuselection:`Bill --> Print` at any moment to" +" generate and print a bill." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:27 +msgid "" +"The printed bill is **not** final and will be updated to reflect any changes" +" to the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:30 +msgid "Bill splitting" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:32 +msgid "" +"From an open session, click :guilabel:`Split` to select the items to " +"regroup. Once everything is selected, click :guilabel:`Payment` and proceed " +"to checkout for these items. Repeat for each guest." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:36 +msgid "" +"Once you return to the table, the selected items are no longer on order, as " +"they have been paid for." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:38 +msgid "The feature is available as soon as at least two items are ordered." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:41 +msgid ":doc:`floors_tables`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:3 +msgid "Floors and tables management" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:6 +msgid "Add a floor" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:8 +msgid "" +"Once your *Point of Sale* has been configured, select *Table Management* " +"under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. " +"Then, click on *Floors* to create and name your floor and tables." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"View of the table management feature. Way to manage and create floors for a " +"pos" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"Backend view of a restaurant floor. Table name and number of sits for each " +"table" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:21 +msgid "Don’t forget to link your floor to your point of sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:24 +msgid "Add tables" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:26 +msgid "" +"To add tables, you can also open your PoS interface to see your floor(s)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the floors menu to manage several floors at the same time" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:33 +msgid "" +"Then, click on *Edit Mode* (pencil icon on the upper right corner) to be " +"allowed to create, move, modify tables, etc." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"View of the floor management. Add tables, the number of sits, their name and" +" their shape" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:41 +msgid "" +"To make your table easier to be found, you can rename them, change their " +"shape, size or even color. It is also possible to add the maximum number of " +"sits the table can have." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:48 +msgid "Register your table(s) orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:50 +msgid "" +"To register an order, click on the respective table. By doing so, you are " +"taken to your main interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the pos interface to register orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:58 +msgid "Transfer customer(s)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:60 +msgid "" +"If your customers want to move to another table after they already ordered, " +"use the transfer button. This way, the order is also moved to the new table." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:64 +msgid "To do so, select the table your customer is currently on." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the restaurant tables, one having a pending order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:70 +msgid "" +"Now, click on the transfer button and select the table to which you are " +"transferring your customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"View of the pos interface and transfer button. How to transfer customers from one table\n" +"to another" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:79 +msgid "Register an additional order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:81 +msgid "" +"When registering an order, use the + button to simultaneously proceed to " +"another one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:84 +msgid "" +"Then, you can shift between your orders and process the payment when needed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the - button, allowing employees to close/remove an order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:92 +msgid "The - button allows you to remove the order you are currently on." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:3 +msgid "Orders printing" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:5 +msgid "" +"To ease the workflow between the front of house and the back of the house, " +"printing the orders taken on the PoS interface right in the kitchen or bar " +"can be a tremendous help." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:10 +msgid "Activate the bar/kitchen printer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:12 +msgid "" +"To activate the *Order printing* feature, go to :menuselection:`Point of " +"Sales --> Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:16 +msgid "" +"Under the IoT Box / Hardware Proxy category, you will find *Order Printers*." +" Note that you need an IoT Box to connect your Printer to the PoS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:20 +msgid "Add a printer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:22 +msgid "" +"In your configuration menu you will now have a *Order Printers* option where" +" you can add the printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:29 +msgid "Print a kitchen/bar order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:34 +msgid "Select or create a printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:37 +msgid "Print the order in the kitchen/bar" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:39 +msgid "On your PoS interface, you now have a *Order* button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:44 +msgid "" +"When you press it, it will print the order on your kitchen/bar printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:3 +msgid "Tips" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:5 +msgid "" +"As it is customary to tip in many countries all over the world, it is " +"important to have the option in your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:9 +msgid "Configure Tipping" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:11 +msgid "" +"To activate the *Tips* feature, go to :menuselection:`Point of Sale --> " +"Configuration --> Point of sale` and select your PoS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:14 +msgid "" +"Under the Bills & Receipts category, you will find *Tips*. Select it and " +"create a *Tip Product* such as *Tips* in this case." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:21 +msgid "Add Tips to the bill" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:23 +msgid "Once on the payment interface, you now have a new *Tip* button" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:28 +msgid "Add the tip your customer wants to leave and process to the payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop.rst:5 +msgid "Shop features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:3 +msgid "Barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:5 +msgid "" +"Using a barcode scanner to process point-of-sale orders improves your " +"efficiency in providing quicker customer service. Barcode scanners can be " +"used both to scan products or to log employees into a POS session." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:12 +msgid "" +"To use a barcode scanner, you must enable the feature in the Inventory app. " +"Go to :menuselection:`Inventory --> Configuration --> Settings`, in the " +":guilabel:`Barcode` section, tick :guilabel:`Barcode Scanner` and save." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst-1 +msgid "barcode setting in the Inventory application" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:21 +msgid "" +":doc:`Set up a barcode " +"scanner<../../../inventory_and_mrp/inventory/barcode/setup/hardware>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:22 +msgid "" +":doc:`Activate barcode " +"scanners<../../../inventory_and_mrp/inventory/barcode/setup/software>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:24 +msgid "" +"Once enabled in **Inventory**, you can use the barcode feature in **Point of" +" Sale** with products that have a barcode number assigned." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:28 +msgid "Assign barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:31 +msgid "To your products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:33 +msgid "" +"To use this feature in POS, your products must have barcodes assigned. To do" +" so, go to :menuselection:`Point of Sale --> Products --> Products` and open" +" a **product form**. Add a barcode number in the :guilabel:`Barcode` field " +"in the :guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:38 +msgid "To your employees" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:40 +msgid "" +"To add an identification number to an employee, go to the **Employees** app " +"and open an **employee form**. Choose an identification number for your " +"employee and fill in the :guilabel:`PIN Code` field in the :guilabel:`HR " +"Settings` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:45 +msgid "Use barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:48 +msgid "Scan products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:50 +msgid "" +"Scan a product's barcode using a barcode scanner. Doing so adds it directly " +"to the cart. To change the quantity, scan a product as many times as needed," +" or click :guilabel:`Qty` and enter the number of products using the keypad." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:54 +msgid "" +"You can also enter the barcode number manually in the search bar to look for" +" the product. Then, click it to add it to the cart." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:58 +msgid "Log employees" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:60 +msgid "" +"You can also use a barcode scanner to log your employees. To do so, " +":ref:`restrict access ` to the POS and :ref:`use " +"barcodes to log your employees in ` your POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:3 +msgid "Sales orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:5 +msgid "" +"When working in retail, you might need to order products directly from your " +"Point of sale. Fortunately, Odoo Point of Sale is fully integrated with Odoo" +" Sales, meaning that you can create a sales order and pay for it directly " +"from your point of sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:10 +msgid "Select a sales order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:12 +msgid "" +"From the **Point of Sale** application, open a new session. Then, click on " +":guilabel:`Quotations/Orders` to get the complete list of quotations and " +"sales orders created on the sales application." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 +msgid "Quotations and sales order button on the Point of Sale interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:21 +msgid "" +"To ease finding the right sales order, you can filter that list on the " +"**customer** or on the **order reference**. You can also set the customer " +"before clicking on :guilabel:`Quotations/Orders` to reduce the list to one " +"particular customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:26 +msgid "Apply a down payment or settle the order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:28 +msgid "From the list of sales order, select one to make a payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 +msgid "list view of sales orders and quotations" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:34 +msgid "You can either:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:36 +msgid "" +"Settle the order **partially**: after clicking on :guilabel:`Apply a down " +"payment`, enter the percentage of down payment you want the customer to pay." +" Then, click on :guilabel:`ok` and proceed with the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:39 +msgid "" +"Settle the order **completely**: click on :guilabel:`Settle the order` to " +"pay for the total of the sales order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:43 +msgid "" +"Once you settle a sales order, the applied down payment is automatically " +"deducted from the total amount." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:47 +msgid ":doc:`/applications/sales/sales/invoicing/down_payment`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:3 +msgid "Serial numbers and lots" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:5 +msgid "" +"Working with **serial numbers** and **lots** allows tracking your products' " +"movements. When products are tracked, the system identifies their location " +"based on their last movement." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:8 +msgid "" +"To enable traceability, go to :menuselection:`Point of Sale --> Products -->" +" Products`. Then, select a product and check the :guilabel:`Tracking By " +"Unique Serial Number` or the :guilabel:`Tracking By Lots` box in the " +":guilabel:`Inventory` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 +msgid "Enable traceability settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:17 +msgid "Serial numbers and lots importation" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:19 +msgid "" +"You can import serial numbers in Point of Sale. To do so, select a **sales " +"order** or a **quotation** containing tracked products. Then, agree to load " +"the **Lots or Serial Numbers** linked to the :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 +msgid "Pop-up window for serial number import" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:28 +msgid "" +"The imported tracking numbers appear below the tracked products. You can " +"modify them by clicking on the list-view button next to the products." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:37 +msgid ":doc:`../shop/sales_order`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:40 +msgid "Serial numbers and lots creation" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:42 +msgid "" +"If a tracked product is available in your POS, adding the product to the " +"cart opens a pop-up window where you can type or scan the product's serial " +"or lot numbers. To add more than one of the same tracked products, click on " +"**enter** to validate and start a new line." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 +msgid "adding new serial and lots numbers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:52 +msgid "" +"Changing a tracked product's quantity using the numpad turns the list-view " +"button red. Click on it to add the missing lot and serial numbers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:54 +msgid "" +":guilabel:`Lot & Serial Number(s)` are :guilabel:`required` on tracked " +"products but not mandatory. Meaning that not attributing some or any does " +"**not** prevent from completing the sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:59 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:60 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots`" +msgstr "" + +#: ../../content/applications/sales/rental.rst:3 +msgid "Rental" +msgstr "" + +#: ../../content/applications/sales/rental.rst:5 +msgid "**Odoo Rental** is a comprehensive solution to manage your rentals." +msgstr "" + +#: ../../content/applications/sales/rental.rst:7 +msgid "" +"From a single view, you can send out quotations, confirm orders, schedule " +"rentals, register when products are picked up and returned, and invoice your" +" customers." +msgstr "" + +#: ../../content/applications/sales/rental.rst:11 +msgid "`Odoo Rental: product page `_" +msgstr "" + +#: ../../content/applications/sales/rental.rst:12 +msgid "`Odoo Tutorials: Rental `_" +msgstr "" + +#: ../../content/applications/sales/rental.rst:17 +msgid "Rental Pricing" +msgstr "" + +#: ../../content/applications/sales/rental.rst:22 +msgid "" +"Go to :menuselection:`Rental --> Products`, select or create a product, and " +"click on the product's *Rental* tab. Under *Rental Pricing*, click on *Add a" +" price*. Then choose a *Unit* of time (hours, days, weeks, or months), a " +"*Duration*, and a *Price*. You can add as many price lines as necessary, " +"usually to give out discounts for longer rental durations." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "Example of rental pricing configuration in Odoo Rental" +msgstr "" + +#: ../../content/applications/sales/rental.rst:32 +msgid "" +"Under *Reservations*, you can add fines for any *Extra Hour* or *Extra Day*." +" You can also set a *Security Time*, expressed in hours, to make the product" +" temporarily unavailable between two rental orders." +msgstr "" + +#: ../../content/applications/sales/rental.rst:37 +msgid "" +"If you want to rent a product created outside of the Rental app, do not " +"forget to tick *Can be Rented* under the product's name. By default, this " +"option is ticked when you create a product directly from the Rental app." +msgstr "" + +#: ../../content/applications/sales/rental.rst:42 +msgid "Computing" +msgstr "" + +#: ../../content/applications/sales/rental.rst:44 +msgid "" +"Odoo always uses two rules to compute the price of a product when you create" +" a rental order:" +msgstr "" + +#: ../../content/applications/sales/rental.rst:46 +msgid "Only one price line is used." +msgstr "" + +#: ../../content/applications/sales/rental.rst:47 +msgid "The cheapest line is selected." +msgstr "" + +#: ../../content/applications/sales/rental.rst:50 +msgid "Consider the following rental pricing configuration for a product:" +msgstr "" + +#: ../../content/applications/sales/rental.rst:52 +msgid "1 day: $100" +msgstr "" + +#: ../../content/applications/sales/rental.rst:53 +msgid "3 days: $250" +msgstr "" + +#: ../../content/applications/sales/rental.rst:54 +msgid "1 week: $500" +msgstr "" + +#: ../../content/applications/sales/rental.rst:56 +msgid "" +"A customer wants to rent this product for eight days. What price will they " +"pay?" +msgstr "" + +#: ../../content/applications/sales/rental.rst:58 +msgid "" +"After an order is created, Odoo selects the second line as this is the " +"cheapest option. The customer has to pay three times '3 days' to cover the " +"rental's eight days, for a total of $750." +msgstr "" + +#: ../../content/applications/sales/rental.rst:64 +msgid "Customer signature" +msgstr "" + +#: ../../content/applications/sales/rental.rst:66 +msgid "" +"You can ask your customers to sign a rental agreement outlining the " +"arrangement between you and your customers before they pick up products to " +"make sure your products are returned on time and in their original " +"condition. To do so, go to :menuselection:`Rental --> Configuration --> " +"Settings`, activate *Digital Documents*, and *Save*." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "Digital Documents settings in Odoo Rental" +msgstr "" + +#: ../../content/applications/sales/rental.rst:76 +msgid "" +"This feature requires the :doc:`Sign <../finance/sign>` app. If necessary, " +"Odoo installs it after activating *Digital Documents*." +msgstr "" + +#: ../../content/applications/sales/rental.rst:79 +msgid "" +"Once the app settings are saved, you have the option to change the default " +"*Rental Agreement* from the dropdown menu. You can pick any document already" +" uploaded to the *Sign* app, or upload a new one to the *Sign* app by " +"clicking on *Upload Template*." +msgstr "" + +#: ../../content/applications/sales/rental.rst:83 +msgid "" +"To request a customer signature, select a confirmed rental order, click on " +"*Sign Documents*, choose the document template and click on *Sign Documents*" +" again. On the next window, select your customer and click on *Sign Now* to " +"start the signing process with your customer. Once the document is " +"completed, click on *Validate & Send Completed Document*." +msgstr "" + +#: ../../content/applications/sales/rental.rst:89 +msgid "`Odoo Tutorials: Sign `_" +msgstr "" + +#: ../../content/applications/sales/rental.rst:94 +msgid "Pickup and Return receipt" +msgstr "" + +#: ../../content/applications/sales/rental.rst:96 +msgid "" +"You can print and give your customers receipts when they pick up and/or " +"return products. To do so, open any rental order, click on *Print* and " +"select *Pickup and Return Receipt*. Odoo then generates a PDF detailing all " +"information about the current status of the rented items: which were picked " +"up, when they are expected to be returned, which were returned, and " +"potential rental delay costs." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "Printing a Pickup and Return receipt in Odoo Rental" +msgstr "" + +#: ../../content/applications/sales/sales.rst:10 +msgid "" +"**Odoo Sales** is the application to run your sales process (from quotation " +"to sales order) and deliver and invoice what has been sold." +msgstr "" + +#: ../../content/applications/sales/sales.rst:14 +msgid "" +"`Odoo Tutorials: Sales Tutorials `_" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector.rst:5 +msgid "Amazon Connector" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:3 +msgid "Amazon Connector Features" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:5 +msgid "" +"The **Amazon Connector** synchronizes the orders between Amazon and your " +"Odoo database, which reduces considerably the amount of time spent on your " +"Amazon Seller Central dashboard, making your daily routine a lot easier." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:10 +msgid "Supported Features" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:12 +msgid "The connector is able to:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:14 +msgid "" +"Synchronize (Amazon to Odoo) all confirmed orders (both FBA and FBM) and " +"their order items which include:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:17 +msgid "the product’s name, description and quantity" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:18 +msgid "the shipping costs for the product" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:19 +msgid "the gift wrapping charges" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:21 +msgid "" +"Create on Odoo any missing partner related to an order (contact types " +"supported: contact and delivery)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:23 +msgid "" +"Notify Amazon of a shipping confirmed on Odoo (FBM) in order to get paid." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:25 +msgid "Support multiple seller accounts." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:26 +msgid "Support multiple marketplaces per seller account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:29 +msgid "Fulfilled By Amazon (FBA)" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:29 +msgid "Fulfilled By Merchant (FBM)" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:31 +msgid "**Orders**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:31 +msgid "Synchronize shipped and canceled orders" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:31 +msgid "Synchronize unshipped and canceled orders" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:34 +msgid "**Shipping**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:34 +msgid "Charges" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:35 +msgid "Delivery created" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "**Gift Wrapping**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:43 +msgid "Handled by Amazon" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "Gift wrapping charges" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:38 +msgid "Gift message" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "**Stock Management**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "One stock move created per sales order item" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "Handled by the delivery" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:43 +msgid "**Confirmation**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:43 +msgid "Notify Amazon when confirming delivery" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:48 +msgid "" +"The connector is designed to synchronize orders' data as detailed above. " +"Other actions, such as downloading monthly fees reports, handling disputes, " +"or issuing refunds must be managed from Amazon Seller Central, as usual." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:55 +msgid "Supported Marketplaces" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:57 +msgid "" +"The Amazon Connector currently supports 9 marketplaces. If a marketplace is " +"not listed below, it may be possible for you to :ref:`add it as an " +"unsupported marketplace `." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:62 +msgid "**North America region**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:64 +msgid "Canada" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:64 +msgid "Amazon.ca" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:66 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:66 +msgid "Amazon.com.mx" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:68 +msgid "US" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:68 +msgid "Amazon.com" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:72 +msgid "**Europe region**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:74 +msgid "Germany" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:74 +msgid "Amazon.de" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:76 +msgid "Spain" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:76 +msgid "Amazon.es" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:78 +msgid "France" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:78 +msgid "Amazon.fr" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:80 +msgid "UK" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:80 +msgid "Amazon.co.uk" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:82 +msgid "Italy" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:82 +msgid "Amazon.it" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:84 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:84 +msgid "Amazon.nl" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:88 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:114 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:59 +msgid ":doc:`setup`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:89 +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:119 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:60 +msgid ":doc:`manage`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:3 +msgid "Manage Amazon orders in Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:6 +msgid "Synchronization of orders" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:8 +msgid "" +"Orders are automatically fetched from Amazon and synchronized in Odoo at " +"regular intervals. The synchronization is based on the Amazon status: only " +"orders whose status has changed since the last synchronization are fetched " +"from Amazon. For **FBA** (Fulfilled by Amazon), only **Shipped** and " +"**Canceled** orders are fetched. For **FBM** (Fulfilled by Merchant), the " +"same is done for **Unshipped** and **Canceled** orders. For each " +"synchronized order, a sales order and a customer are created in Odoo if they" +" are not yet registered." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:15 +msgid "" +"When an order is canceled in Amazon and was already synchronized in Odoo, " +"the corresponding sales order is automatically canceled in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:19 +msgid "" +"To force the synchronization of an order whose status has not changed since " +"the last synchronization, activate the :ref:`developer mode `, navigate to your Amazon account and modify the date under " +":menuselection:`Orders Follow-up --> Last Order Sync`. Pick a date anterior " +"to the last status change of the order that you wish to synchronize and " +"save." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:25 +msgid "" +"To synchronize immediately the orders of your Amazon account switch to " +":ref:`developer mode `, head to your Amazon account and " +"click on **SYNC ORDERS**. The same can be done with pickings by clicking on " +"**SYNC PICKINGS**." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:30 +msgid "Manage deliveries in FBM" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:32 +msgid "" +"When a **FBM** (Fulfilled by Merchant) order is synchronized in Odoo, a " +"picking is created along with the sales order and the customer. You can " +"either ship all the ordered products to your customer at once or ship " +"products partially by using backorders." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:36 +msgid "" +"When a picking related to the order is confirmed, a notification is sent to " +"Amazon who will, in turn, notify the customer that the order (or a part of " +"it) is on its way." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:40 +msgid "" +"Amazon requires to provide a tracking reference with each delivery. You'll " +"need to assign a carrier. If the carrier doesn't automatically provide a " +"tracking reference, you'll need to set one manually. This concerns all " +"marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:45 +msgid "" +"If your chosen carrier isn't one supported by Odoo, you can still create a " +"carrier bearing its name (e.g. create a carrier named `Colissimo`). This " +"name is case insensitive, but be careful about typos, as Amazon won't " +"recognize them." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:48 +msgid "" +"Create a delivery carrier named `Self Delivery` to inform Amazon that you " +"make your own deliveries. You still have to enter a tracking reference." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:50 +msgid "" +"Keep in mind that the customer is notified by email about the delivery, and " +"the carrier and tracking reference are displayed in the email to the " +"customer." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:54 +msgid "" +":doc:`../../../inventory_and_mrp/inventory/shipping/setup/third_party_shipper`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:57 +msgid "Follow deliveries in FBA" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:59 +msgid "" +"When a **FBA** (Fulfilled by Amazon) order is synchronized in Odoo, a stock " +"move is recorded for each sales order item so that it is saved in your " +"system. Inventory managers can find such moves in :menuselection:`Inventory " +"--> Reporting --> Product Moves`. They pick up products in a specific " +"inventory location called **Amazon**. This location represents your stock in" +" Amazon's warehouses and allows you to manage the stock of your products " +"under the FBA program." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:66 +msgid "" +"To follow your Amazon (FBA) stock in Odoo, you can make an inventory " +"adjustment after replenishing it. You can also trigger an automated " +"replenishment from reordering rules on the Amazon location." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:71 +msgid "" +"The Amazon location is configurable by Amazon account managed in Odoo. All " +"accounts of the same company use the same location by default. It is however" +" possible to follow the stock by marketplace. First, remove the marketplace " +"for which you want to follow the stock separately from the list of " +"synchronized marketplaces. Then, create another registration for this " +"account and remove all marketplaces, except the one to isolate from the " +"others. Finally, assign another stock location to the second registration of" +" your account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:79 +msgid "Issue invoices and register payments" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:81 +msgid "" +"You can issue invoices for Amazon orders in Odoo. Click **Create Invoice** " +"in the sales order to do so. You can also do it in batch from the list view " +"of orders. Then, confirm and send the invoices to your customers." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:86 +msgid "" +"To display only Amazon-related orders on the list view, you can filter " +"orders based on the sales team." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:89 +msgid "" +"As the customer has paid Amazon as an intermediary, you should register " +"invoice payments in a payment journal dedicated to Amazon (e.g. Amazon " +"Payments, with a dedicated intermediary account). You can do the same with " +"the vendor bill received from Amazon and dedicated to commissions. When you " +"receive the balance on your bank account at the end of the month and record " +"your bank statements in Odoo, you simply credit the Amazon intermediary " +"account by the amount received." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:96 +msgid "Follow your Amazon sales in sales reporting" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:98 +msgid "" +"As a sales team is set on your account under the tab **Order Follow-up**, " +"this helps you give quick glances at the figures in just a few clicks in " +"Sales reporting. By default, your account's sales team is shared between all" +" of your company's accounts." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:102 +msgid "" +"If you wish, you can change the sales team on your account for another to " +"perform a separate reporting for the sales of this account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:106 +msgid "" +"It is also possible to perform reporting on a per-marketplace basis in a " +"similar fashion. First, remove the marketplace you wish to track separately " +"from the list of synchronized marketplaces. Then, create another " +"registration for this account and remove all marketplaces, except the one to" +" isolate from the others. Finally, assign another sales team to one of the " +"two registrations of your account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:113 +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:118 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:58 +msgid ":doc:`features`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:3 +msgid "Configure Amazon Connector in Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:6 +msgid "Register your Amazon account in Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:10 +msgid "" +"To register your seller account in Odoo, navigate to :menuselection:`Sales " +"--> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon " +"Accounts` and click on :guilabel:`CREATE`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:13 +msgid "" +"Choose a meaningful name for your account (e.g. `Europe`), and select your " +":guilabel:`Sign-up Marketplace`. This is the original sign-up marketplace of" +" your seller account (e.g. if you created your account on Amazon Germany, " +"your sign-up marketplace will be `amazon.de`)" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:17 +msgid "" +"Upon saving, a button to :guilabel:`link with Amazon` appears. Click on it " +"to be redirected to the Amazon login page, or directly to the consent page " +"if you are already logged in. There, confirm that you want Amazon to give " +"Odoo access to your account and related data." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:21 +msgid "Amazon redirects you to Odoo, with your account registered." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:23 +msgid "" +"Once the account is registered, the marketplaces available to this account " +"are synchronized and listed under the :guilabel:`Marketplaces` tab. If you " +"wish, you can remove some items from the list of synchronized marketplaces " +"to disable their synchronization." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:28 +msgid "Match database products in Amazon" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:30 +msgid "" +"When an Amazon order is synchronized, up to three sales order items are " +"created in Odoo for each product sold on Amazon: one for the marketplace " +"product, one for the shipping charges (if any) and one for the gift wrapping" +" charges (if any)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:36 +msgid "" +"The selection of a database product for a sales order item is done by " +"matching its **internal reference** with the **SKU** for marketplace items, " +"the **shipping code** for delivery charges, and the **gift wrapping** code " +"for gift wrapping charges." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:40 +msgid "" +"For marketplace products, pairings are saved as **Amazon Offers** which are " +"listed under the **Offers** stat button on the account form. Offers are " +"automatically created when the pairing is established and are used for " +"subsequent orders to lookup SKUs. If no offer with a matching SKU is found, " +":ref:`the internal reference is used instead `." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:46 +msgid "" +"It is possible to force the pairing of a marketplace item with a specific " +"product by changing either the product or the SKU of an offer. The offer can" +" be manually created if it was not automatically done yet. This is useful if" +" you do not use the internal reference as the SKU or if you sell the product" +" under different conditions." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:51 +msgid "" +"If no database product with a matching internal reference is found for a " +"given SKU or gift wrapping code, a default database product **Amazon Sale** " +"is used. The same is done with the default product **Amazon Shipping** and " +"the shipping code." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:56 +msgid "" +"To modify the default products, activate the :ref:`developer mode " +"` and navigate to :menuselection:`Sales --> Configuration " +"--> Settings --> Connectors --> Amazon Sync --> Default Products`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:61 +msgid "Configure taxes of products" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:63 +msgid "" +"To allow for tax reporting of Amazon sales with Odoo, the taxes applied to " +"the sales order items are those set on the product or determined by the " +"fiscal position. Make sure to have set the correct taxes on your products in" +" Odoo or to have it done by a fiscal position, to avoid discrepancies in the" +" subtotals between Seller Central and Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:69 +msgid "" +"As Amazon does not necessarily apply the same taxes as those configured in " +"Odoo, it may happen that order totals differ by a few cents from that on " +"Seller Central. Those differences can be resolved with a write-off when " +"reconciling the payments in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:76 +msgid "Add an unsupported marketplace" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:78 +msgid "" +"Some Amazon Marketplaces, such as Amazon Brazil, are not created by default " +"as they are not officially supported by Odoo but might be compatible with " +"your seller account. These marketplaces can be added manually should you " +"wish to use them. See :ref:`here ` for the " +"exhaustive list of natively supported marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:84 +msgid "" +"To find out if a marketplace is eventually compatible, check the `Amazon " +"Documentation `_. The marketplace must belong to the " +"same region as that of your seller account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:88 +msgid "" +"To add a new marketplace, activate the :ref:`developer mode `." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:90 +msgid "" +"Once that is done, go to :menuselection:`Sales --> Configuration --> " +"Settings --> Connectors --> Amazon Sync --> Amazon Marketplaces`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:93 +msgid "" +"From there, create a new marketplace record. Enter the Marketplace ID and " +"select the Amazon Region for your marketplace as described in the `Amazon " +"Documentation for marketplace IDs `_, and the Seller Central URL as described in" +" the `Amazon Documentation for seller central URLs `_." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:99 +msgid "" +"Set the name of the record to ``Amazon.`` to easily retrieve " +"it (e.g.: ``Amazon.se``). The :guilabel:`API Identifier`, the " +":guilabel:`Region` and the :guilabel:`Seller Central URL` fields should " +"respectively hold the *MarketplaceId*, the selected Amazon region and the " +"*Seller Central URL* values from the Amazon Documentation." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:104 +msgid "" +"Once the marketplace is saved, update the Amazon Account configuration by " +"going to :menuselection:`Sales --> Configuration --> Settings --> Connectors" +" --> Amazon Sync --> Amazon Accounts`. Open the account on which you wish to" +" use the new marketplace, go to the :guilabel:`Marketplaces` tab and click " +"on :guilabel:`Update available marketplaces` (an animation should confirm " +"the success of the operation). Newly added marketplaces are automatically " +"added to the list of synchronized marketplaces. If the new marketplace is " +"not added to the list, it means that it is either incompatible or " +"unavailable for your seller account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:113 +msgid "" +"As manually added marketplaces are not officially supported by Odoo, there " +"is no guarantee that adding one as described above will work, nor can this " +"be considered as a bug when contacting Odoo Support." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:3 +msgid "Install the Amazon Selling Partner API Update" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:5 +msgid "" +"Starting July 2022, due to a change in Amazon's API, the Amazon Connector " +"needs to be updated to continue to exchange information with Amazon. This " +"also makes it easier for you to set up the Connector." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:10 +msgid "" +"If your Odoo database is created after the update was released, the update " +"module is installed automatically. To check if this module is already " +"installed, go to :guilabel:`Apps`, remove the ``Apps`` filter and search for" +" ``Amazon``. If the module :guilabel:`Amazon/Selling Partner API Patch` is " +"present and marked as installed, your Odoo database is already up-to-date " +"and you can proceed with the :doc:`setup ` step of the Amazon " +"Connector." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:17 +msgid "Update Odoo to the latest release" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:19 +msgid "" +"The new authentication mechanism is made available through a new Odoo " +"module; to be able to install it, you must make sure that your Odoo source " +"code is up-to-date." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:22 +msgid "" +"If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up-to-" +"date and you can proceed to the next step." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:25 +msgid "" +"If you use Odoo with an on-premise setup or through a partner, then you must" +" update your installation as detailed in :doc:`this documentation page " +"` or by contacting your integrating " +"partner." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:31 +msgid "Update the list of available modules" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:33 +msgid "" +"New modules must be *discovered* by your Odoo instance to be available in " +"the **Apps** menu." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:36 +msgid "" +"To do so, activate the :ref:`developer mode `, and go to " +":menuselection:`Apps --> Update Apps List`. A wizard will ask for " +"confirmation." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:40 +msgid "Install the Amazon/Selling Partner API Patch" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:43 +msgid "" +"You should never install new modules in your production database without " +"first testing them in a duplicate or staging environment. For Odoo.com " +"customers, a duplicate database can be created from the database management " +"page. For Odoo.sh users, you should use a staging or duplicate database. For" +" on-premise users, you should use a staging environment---contact your " +"integrating partner for more information regarding how to test a new module " +"in your particular setup." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:49 +msgid "" +"The module should now be available in your :guilabel:`Apps` menu. Remove the" +" ``Apps`` filter and search for ``Amazon``; the module " +":guilabel:`Amazon/Selling Partner API Patch` should be available for " +"installation. If you cannot find the module after having updated the list of" +" available modules, it means your Odoo source code is not up-to-date; refer " +"to step one of this page." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/update.rst:54 +msgid "" +"Once the module is installed, link your Amazon account by following the " +"instructions on the :doc:`setup ` page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector.rst:5 +msgid "eBay Connector" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:3 +msgid "How to list a product?" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:6 +msgid "Listing without variation" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:8 +msgid "" +"In order to list a product, you need to check the **use eBay** field on a " +"product form. The eBay tab will be available." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:14 +msgid "" +"When the **Use Stock Quantity** field is checked, the quantity sets on eBay " +"will be the Odoo **Forecast Quantity**." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:17 +msgid "" +"The **Description Template** allows you to use templates for your listings. " +"The default template only use the **eBay Description** field of the product." +" You can use html inside the **Description Template** and in the **eBay " +"Description**." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:21 +msgid "" +"To use pictures in your listing, you need to add them as **Attachments** on " +"the product template." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:24 +msgid "Listing with variations" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:26 +msgid "" +"When the **use eBay** on a product with variations is checked and with " +"**Fixed Price** as **Listing Type**, the eBay form is slightly different. In" +" the variants array, you can choose which variant will be listed on eBay as " +"well as set the price and the quantity for each variant." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:35 +msgid "Listing with item specifics" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:37 +msgid "" +"In order to add item specifics, you should create a product attribute with " +"one value in the **Variants** tab on the product form." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:44 +msgid "Product Identifiers" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:46 +msgid "" +"Products identifiers such as EAN, UPC, Brand or MPN are required in most of " +"the eBay category. The module manages the EAN and UPC identifiers with the " +"**Barcode** field of the product variant. If the **Barcode** field is empty " +"or is value is not valid, the EAN and UPC values will be set as 'Does not " +"apply' as recommended by eBay. The Brand and MPN values are working as item " +"specifics and should be define in the **Variants** tab on the product form. " +"If these values are not set, 'Does not apply' will be used for the eBay " +"listing." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:3 +msgid "How to configure eBay in Odoo?" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:6 +msgid "Create eBay tokens" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:8 +msgid "" +"In order to create your tokens, you need to create a developer account on " +"the `developer portal `_. Once you are " +"logged in, you can create **Sandbox Keys** and **Production Keys** by " +"clicking on the adequate buttons." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:16 +msgid "" +"After the creation of the keys, you can get the user token. To do so, click " +"on the **Get a User Token** link in the bottom of the page. Go through the " +"form, log in with you eBay account and you will get the keys and token " +"needed to configure the module in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:22 +msgid "Set up tokens in Odoo?" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:24 +msgid "" +"To set up the eBay integration, go to :menuselection:`Sales --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:29 +msgid "" +"First choose if you want to use the production or the sandbox eBay Site. " +"Then fill in the fields **Developer Key**, **Token**, **App Key**, **Cert " +"Key**. Apply the changes." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:33 +msgid "" +"Once the page is reloaded, you need to synchronize information from eBay. " +"Push on **Sync countries and currencies**, then you can fill in all the " +"other fields." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:36 +msgid "" +"When all the fields are filled in, you can synchronize the categories and " +"the policies by clicking on the adequate buttons." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:40 +msgid "Accept account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:42 +msgid "" +"Since September 2021, **eBay requires supporting customer account " +"deletion/closure notifications**. As such, when eBay receives an account " +"request for deletion, all eBay partners must confirm the reception of the " +"request and take further action if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:46 +msgid "" +"Odoo has a notification endpoint to receive those notifications, confirm the" +" reception of the request, and handle the first set of actions to anonymize " +"the account details in **Contacts** and remove the customer's access to the " +"portal." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:51 +msgid "" +"Make sure to correctly :ref:`set up your subscription to the marketplace " +"account deletion notifications ` as eBay may temporarily disable the related eBay account " +"until the subscription is completed." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:58 +msgid "Retrieve endpoint details from Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:60 +msgid "" +"The endpoint details can be found in :menuselection:`Sales --> Configuration" +" --> Settings --> eBay`. Click on *Generate Token* to retrieve your " +"**Verification Token**." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Button to generate an eBay verification token in Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:70 +msgid "Subscribe to account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:72 +msgid "" +"Log in on the `developer portal of eBay `_ " +"and go to **Alerts & Notifications**." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Overview of the Alerts & Notifications dashboard of eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:79 +msgid "" +"To subscribe to deletion/closure notifications, eBay needs a few details:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:81 +msgid "" +"An **email address** to send notifications to if the endpoint is " +"unreachable." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:82 +msgid "The **endpoint details**:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:84 +msgid "The URL to Odoo's account deletion notification endpoint" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:85 +msgid "A verification token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Dedicated fields to enter the endpoint details" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:92 +msgid "" +"You can edit the last two fields once the email address field is filled out." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:95 +msgid "Verify the connectivity with the endpoint" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:97 +msgid "" +"After setting the retrieved endpoint details in eBay's dashboard, consider " +"testing the connectivity with the **Send Test Notification** button." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:100 +msgid "" +"You should get the following confirmation message: \"A test notification was" +" sent successfully!\"" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Button to send test notification" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:107 +msgid "Using the updated synchronisation method" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:109 +msgid "" +"If you have a lot of products, the eBay API can sometimes refuse some " +"synchronization calls due to a time-based limit on the number of requests " +"that eBay enforces." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:112 +msgid "" +"To fix this issue, a new implementation mechanism has been developed; " +"however this updated mechanism is disabled by default to avoid having the 2 " +"systems running in parallel in existing installations." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:116 +msgid "To switch to the new synchronization mechanism:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:118 +msgid "Activate the :ref:`developer mode `." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:119 +msgid "Go to :menuselection:`Settings --> Technical --> Scheduled Actions`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:120 +msgid "" +"Archive the old synchronization actions (both are named *Ebay: update " +"product status*)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:121 +msgid "" +"Activate the new synchronization actions (*Ebay: get new orders* which runs " +"every 15min by default and *Ebay: synchronise stock (for 'get new orders' " +"synchronisation)* which runs once a day per default)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:124 +msgid "" +"Ensure that the **Next Execution Date** for both these actions are in the " +"near future" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:126 +msgid "" +"Starting with the next execution date, the new method will be used instead " +"of the old one." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing.rst:5 +msgid "Invoicing Method" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:3 +msgid "Down payments" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:5 +msgid "" +"A down payment is a partial payment made by the buyer when a sales contract " +"is concluded. This implies both parties' (seller and buyer) full commitment " +"to honor the contract." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:8 +msgid "" +"With a down payment, the buyer pays a portion of the total amount owed while" +" agreeing to pay the remaining amount at a later date. In turn, the seller " +"provides goods or services to the buyer after accepting the down payment, " +"trusting that the remaining amount will be paid later on." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:13 +msgid "Initial down payment request" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:15 +msgid "" +"When a sales order is confirmed, the option to create an invoice becomes " +"available, via the :guilabel:`Create Invoice` button, located in the upper-" +"left corner of the sales order form. When clicked, a :guilabel:`Create " +"invoices` pop-up appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:20 +msgid "" +"Invoices are automatically created in drafts, so they can be reviewed before" +" validation." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:22 +msgid "" +"On the :guilabel:`Create invoices` pop-up, there are 3 options to choose " +"from in the :guilabel:`Create Invoice` field:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 +msgid ":guilabel:`Regular invoice`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 +msgid "" +"If :guilabel:`Regular Invoice` is selected the other fields disappear, as " +"they only pertain to down payment configurations." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:29 +msgid ":guilabel:`Down payment (percentage)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:30 +msgid ":guilabel:`Down payment (fixed amount)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:32 +msgid "" +"In terms of a down payment, it can either be a fixed amount or a percentage " +"of the total amount." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:34 +msgid "" +"Once the desired down payment option is selected in the :guilabel:`Create " +"Invoice` field, designate the desired amount (either as a percentage or " +"fixed amount) in the :guilabel:`Down Payment Amount` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:38 +msgid "" +"Then, select the appropriate income account for the invoice in the " +":guilabel:`Income Account` field, and add a tax amount, if necessary, in the" +" :guilabel:`Customer Taxes` field. These settings will be reused for future " +"down payments." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "How to configure a down payment on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:47 +msgid "" +"When a down payment is first requested, a new product called :guilabel:`Down" +" payment` is created. This product is registered as a :guilabel:`Service` " +"product, with an invoicing policy of :guilabel:`Ordered quantities`. This " +"product can be edited and modified at any time." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:52 +msgid "" +"If :guilabel:`Delivered quantities` is chosen as the invoicing policy, an " +"invoice will **not** be able to be created." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:56 +msgid "Request a 50% down payment" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:58 +msgid "" +"For the following example, the flow involves a 50% amount down payment on a " +"product with :guilabel:`Ordered quantities` as the invoicing policy." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:62 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:184 +msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:64 +msgid "" +"When the order is confirmed (via the :guilabel:`Confirm` button), it's time " +"to create/view the invoice, by clicking :guilabel:`Create Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:67 +msgid "" +"Then, on the :guilabel:`Create invoices` pop-up window that appears, select " +":guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down " +"Payment Amount` field. Lastly, click :guilabel:`Create and View Invoice` to " +"create and view the invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "Create invoices pop up window in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:75 +msgid "Doing so reveals the draft invoice, which mentions the down payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "A sample draft invoice with down payment mentioned in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:81 +msgid "" +"From there, the invoice can be confirmed/posted, and the payment can be " +"registered. Return to the sales order, via the breadcrumbs." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:84 +msgid "" +"On the sales order, the option to view what the customer will see is " +"available, via the :guilabel:`Customer Preview` smart button, and the " +":guilabel:`Invoice` button reveals the drafted invoice. In either case, the " +"down payment is mentioned on both the sales order and draft invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "How the down payment is mentioned on the sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:92 +msgid "" +"To confirm and register the first payment of the down payment, click the " +":guilabel:`Invoices` smart button to return to the invoice. On the " +":guilabel:`Customer Invoice` page, click :guilabel:`Confirm`, then " +":guilabel:`Register Payment` to open a :guilabel:`Register Payment` pop-up " +"form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "How the register payment pop up looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:101 +msgid "" +"On this form, select the appropriate :guilabel:`Journal` and confirm that " +"the down payment amount is correct in the :guilabel:`Amount` field. Then, " +"make any other modifications to the other fields, if necessary, before " +"clicking :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105 +msgid "" +"Odoo returns to the invoice, which now has a green :guilabel:`In Payment` " +"banner visible in the upper-right corner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"How the initial down payment invoice has a green paid banner in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112 +msgid "" +"Now, when the customer wants to pay the remaining amount of the order, " +"another invoice must be created. To do that, return to the sales order, and " +"click :guilabel:`Create Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:115 +msgid "" +"On the :guilabel:`Create invoices` pop-up window, there is now an option to " +":guilabel:`Deduct down payments`, which is selected by default." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"The deduct down payment option on the create invoices pop up in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:122 +msgid "" +"If the remaining amount is ready to be paid, the :guilabel:`Regular Invoice`" +" option should be selected, and the :guilabel:`Deduct down payments` option " +"should *stay* selected. Then, click :guilabel:`Create and View Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 +msgid "" +"Doing so reveals a separate :guilabel:`Invoices` page, listing all the " +"invoices for that specific sales order. Each invoice line item displays all " +"the necessary information related to each invoice, along with the current " +":guilabel:`Payment Status`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "The down payment invoices page in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:134 +msgid "" +"To complete the flow, select the invoice with the :guilabel:`Not Paid` " +"status, which opens that invoice. On the invoice page, click " +":guilabel:`Confirm`, then :guilabel:`Register Payment`, and confirm that the" +" remaining :guilabel:`Amount` is correct. Then, click :guilabel:`Create " +"Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:138 +msgid "" +"That pop-up window disappears, and a green :guilabel:`In Payment` banner is " +"now present on the invoice. The line items on the invoice show that the " +"total amount has been paid, including mentions of the down payment, and the " +"flow is complete." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:142 +msgid "" +"This flow is also possible with the :guilabel:`Fixed amount` down payment " +"option." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:145 +msgid "" +"If a down payment is used with a product that has a :guilabel:`Delivered " +"quantities` invoicing policy, the down payments will **not** be able to be " +"deducted when it comes time to invoice the customer. This is because, due to" +" the invoicing policy, the product(s) would have to be delivered *before* " +"creating the final invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:150 +msgid "" +"If nothing has been delivered, a :guilabel:`Credit Note` is created, which " +"cancels the draft invoice that was created after the down payment. To " +"utilize the :guilabel:`Credit Note` option, the *Inventory* application must" +" be installed, in order to confirm the delivery. Otherwise, the delivered " +"quantity can be entered manually directly on the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:156 +msgid "Income account and customer taxes modifications" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158 +msgid "" +"To adjust the income account and customer taxes attached to a down payment, " +"navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> " +"Products --> Products`), search for the `Down Payment` product in the search" +" bar, and select it to reveal the product detail page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:162 +msgid "" +"On the :guilabel:`Down Payment` product page, click :guilabel:`Edit`, then " +"scroll down to the :guilabel:`General Information` tab. In this tab, the " +"customer taxes can be modified in the :guilabel:`Customer Taxes` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "How to modify the income account link to down payments" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 +msgid "" +"To change or adjust the income account attached to the :guilabel:`Down " +"Payment` product page, the *Accounting* app **must** be installed. With the " +"*Accounting* app installed, the :guilabel:`Accounting` tab becomes available" +" on the product page. That tab will **not** be accessible without the " +"*Accounting* app installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:175 +msgid "" +"In the :guilabel:`Accounting` tab, the income account can be changed in the " +":guilabel:`Income Account` field, in the :guilabel:`Receivables` section. " +"Once all desired changes are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:3 +msgid "Re-invoice expenses to customers" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:5 +msgid "" +"It often happens that your employees have to spend their personal money " +"while working on a project for your client. Let's take the example of a " +"consultant paying for a hotel to work on the site of your client. As a " +"company, you would like to be able to invoice that expense to your client." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:12 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:64 +msgid "Expenses configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:14 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:66 +msgid "" +"To track & invoice expenses, you will need the expenses app. Go to " +":menuselection:`Apps --> Expenses` to install it." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:17 +msgid "" +"You should also activate the analytic accounts feature to link expenses to " +"the sales order, to do so, go to :menuselection:`Invoicing --> Configuration" +" --> Settings` and activate *Analytic Accounting*." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:22 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:74 +msgid "Add expenses to your sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:24 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:76 +msgid "" +"From the expense app, you or your consultant can create a new one, e.g. the " +"hotel for the first week on the site of your customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:27 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:79 +msgid "" +"You can then enter a relevant description and select an existing product or " +"create a new one from right there." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:33 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:85 +msgid "Here, we are creating a *Hotel* product:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:38 +msgid "" +"Under the invoicing tab, select *Delivered quantities* and either *At cost* " +"or *Sales price* as well depending if you want to invoice the cost of your " +"expense or a previously agreed on sales price." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:45 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:97 +msgid "" +"To modify or create more products go to :menuselection:`Expenses --> " +"Configuration --> Expense products`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:48 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:100 +msgid "" +"Back on the expense, add the original sale order in the expense to submit." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:54 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:106 +msgid "It can then be submitted to the manager, approved and finally posted." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:65 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:117 +msgid "It will then be in the sales order and ready to be invoiced." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:3 +msgid "Invoice based on delivered or ordered quantities" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:5 +msgid "" +"Different business policies might require different options for invoicing:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:7 +msgid "" +"The **Invoice what is ordered** rule is used as **default mode** in Odoo " +"Sales, which means that customers will be invoiced once the sales order is " +"confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:10 +msgid "" +"The **Invoice what is delivered** rule will invoice customers once the " +"delivery is done. This rule concerns businesses that sell materials, liquids" +" or food in large quantities. In these cases, the quantity might diverge a " +"little bit and it is, therefore, preferable to invoice the quantity actually" +" delivered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:15 +msgid "" +"Being able to have different invoicing options allow you more flexibility. " +"Indeed, you need to know exactly how to invoice your customers for different" +" situations." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:19 +msgid "Activate these features" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:21 +msgid "" +"Go to :menuselection:`Sales --> Configuration --> Settings` and under " +"**Invoicing policy** choose the rule you want to apply." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 +msgid "How to choose your invoicing policy on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:30 +msgid "" +"If you decide to choose the **Invoice what is delivered** rule, you will not" +" be able to activate the feature called **Automatic invoice**, which " +"automatically generates invoices when the online payment is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:35 +msgid "Choose an invoicing policy on a product form" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:37 +msgid "" +"From any product page, under the **Sales tab**, you will find the invoicing " +"policy, which can be manually changed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 +msgid "How to change your invoicing policy on a product form on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:46 +msgid "Impact on sales flow" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:48 +msgid "" +"On Odoo Sales, the basic sales flow will be to create a quotation, send it " +"to your customer, wait for confirmation, confirm the sales order and create " +"an invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:51 +msgid "" +"**Invoice what is ordered**: No impact on this basic sales flow. Indeed, you" +" can invoice as soon as the sale is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:54 +msgid "" +"**Invoice what is delivered**: Small impact on sales flow because you will " +"have to manually enter the delivered quantity on the sales order or to " +"install the **Inventory App** to confirm the delivered quantity before " +"creating an invoice, with the **Sales App**. Indeed, if you try to create an" +" invoice without validating the delivered quantity, you will receive an " +"error message as below." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:0 +msgid "" +"How the choice of your invoicing policy impacts your sales flow on Odoo " +"Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:65 +msgid "" +"Once the quotation is confirmed and that the status went from **Quotation " +"sent** to **Sales order**, you are able to see your delivered and invoiced " +"quantities directly from your sales order (it is true for both rules)." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 +msgid "How to see your delivered and invoiced quantities on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:74 +msgid "" +"Odoo will automatically add the quantities to the invoice (even if it is a " +"partial delivery)." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:76 +msgid "" +"Finally, to create an invoice, you will have different possibilities: " +"regular invoice or down payment (percentage or fixed amount)." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:80 +msgid "" +"Be sure to check out our documentation about down payment here: " +":doc:`down_payment`, to master this incredible feature." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:3 +msgid "Invoice project milestones" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:5 +msgid "" +"Milestone invoicing can be used for expensive or large-scale projects, with " +"each milestone representing a clear sequence of work that will incrementally" +" build up to the completion of the contract. This invoicing method is " +"comfortable both for the company which is ensured to get a steady cash flow " +"throughout the project lifetime and for the client who can monitor the " +"project's progress and pay in several installments." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:13 +msgid "Create milestone products" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:15 +msgid "" +"In Odoo, each milestone of your project is considered as a product. To " +"configure products to work this way, go to any product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:18 +msgid "" +"You have to set the product type as *Service* under general information and " +"select *Milestones* in the sales tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:25 +msgid "Invoice milestones" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:27 +msgid "" +"From the sales order, you can manually edit the quantity delivered as you " +"complete a milestone." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:33 +msgid "You can then invoice that first milestone." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:3 +msgid "Pro-forma invoices" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:5 +msgid "" +"A *pro-forma invoice* is an abridged or estimated invoice sent in advance of" +" a delivery of goods. It notes the kind and quantity of goods, their value, " +"and other important information, such as weight and transportation charges." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:9 +msgid "" +"Pro-forma invoices are commonly used as preliminary invoices with a " +"quotation. They are also used for customs purposes during importation. They " +"differ from a normal invoice in that they are not a demand (or request) for " +"payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:14 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 +msgid "Activate the feature" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:16 +msgid "" +"In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature " +"**must** be activated. To do that, navigate to :menuselection:`Sales app -->" +" Configuration --> Settings`, and in the :guilabel:`Quotations & Orders` " +"section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, " +"click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst-1 +msgid "The Pro-Forma Invoice feature setting in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:26 +msgid "Send a pro-forma invoice" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:28 +msgid "" +"With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send" +" a pro-forma invoice is now available on any quotation or sales order, via " +"the :guilabel:`Send Pro-Forma Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst-1 +msgid "" +"The Send Pro-Forma Invoice button on a typical sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:35 +msgid "" +"When the :guilabel:`Send Pro-Forma Invoice` button is clicked, an email pop-" +"up appears. The :guilabel:`Recipients` field is auto-populated with the " +"customer from the sales order or quotation. Then, if needed, modify the " +":guilabel:`Subject` field and the body of the email. The pro-forma invoice " +"is automatically added as an attachment to the email." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:40 +msgid "" +"When ready, click :guilabel:`Send`, and Odoo instantly sends the email, with" +" the attached pro-forma invoice, to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst-1 +msgid "" +"The email pop-up window that appears with pro-forma invoice attached in Odoo" +" Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:48 +msgid "" +"To preview what the pro-forma invoice looks like, click on the PDF at the " +"bottom of the email pop-up window *before* clicking :guilabel:`Send`. When " +"clicked, the pro-forma invoice is downloaded instantly. Open that PDF to " +"view (and review) the pro-forma invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:0 +msgid "Sample pro-forma invoice PDF from Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/subscriptions.rst:3 +msgid "Sell subscriptions" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/subscriptions.rst:5 +msgid "" +"Selling subscription products will give you predictable revenue, making " +"planning ahead much easier." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/subscriptions.rst:9 +msgid "Make a subscription from a sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/subscriptions.rst:11 +msgid "" +"From the sales app, create a quotation to the desired customer, and select " +"the subscription product your previously created from the Subscriptions App." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/subscriptions.rst:14 +msgid "" +"When you confirm the sale the subscription will be created automatically. " +"You will see a direct link from the sales order to the Subscription in the " +"upper right corner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:3 +msgid "Invoice based on time and materials" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:5 +msgid "" +"Time and Materials is generally used in projects in which it is not possible" +" to accurately estimate the size of the project, or when it is expected that" +" the project requirements would most likely change." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:9 +msgid "" +"This is opposed to a fixed-price contract in which the owner agrees to pay " +"the contractor a lump sum for the fulfillment of the contract no matter what" +" the contractors pay their employees, sub-contractors, and suppliers." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:14 +msgid "" +"For this documentation I will use the example of a consultant, you will need" +" to invoice their time, their various expenses (transport, lodging, ...) and" +" purchases." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:19 +msgid "Invoice time configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:21 +msgid "" +"To keep track of progress in the project, you will need the *Project* app. " +"Go to :menuselection:`Apps --> Project` to install it." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:24 +msgid "" +"In *Project* you will use timesheets, to do so go to :menuselection:`Project" +" --> Configuration --> Settings` and activate the *Timesheets* feature." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:32 +msgid "Invoice your time spent" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:34 +msgid "" +"From a product page set as a service, you will find two options under the " +"invoicing tab, select both *Timesheets on tasks* and *Create a task in a new" +" project*." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:41 +msgid "You could also add the task to an existing project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:43 +msgid "" +"Once confirming a sales order, you will now see two new buttons, one for the" +" project overview and one for the current task." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:49 +msgid "" +"You will directly be in the task if you click on it, you can also access it " +"from the *Project* app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:52 +msgid "" +"Under timesheets, you can assign who works on it. You can or they can add " +"how many hours they worked on the project so far." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:58 +msgid "From the sales order, you can then invoice those hours." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:69 +msgid "" +"You should also activate the analytic accounts feature to link expenses to " +"the sales order, to do so, go to :menuselection:`Accounting --> " +"Configuration --> Settings` and activate *Analytic Accounting*." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:90 +msgid "" +"under the invoicing tab, select *Delivered quantities* and either *At cost* " +"or *Sales price* as well depending if you want to invoice the cost of your " +"expense or a previously agreed on sales price." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:120 +msgid "Invoice purchases" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:122 +msgid "" +"The last thing you might need to add to the sale order is purchases made for" +" it." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:125 +msgid "" +"You will need the *Purchase Analytics* feature, to activate it, go to " +":menuselection:`Invoicing --> Configuration --> Settings` and select " +"*Purchase Analytics*." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:129 +msgid "" +"While making the purchase order don't forget to add the right analytic " +"account." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:135 +msgid "" +"Once the PO is confirmed and received, you can create the vendor bill, this " +"will automatically add it to the SO where you can invoice it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices.rst:5 +msgid "Products & Prices" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices.rst:5 +msgid "Manage your pricing" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:3 +msgid "How to sell in foreign currencies" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:5 +msgid "Pricelists can also be used to manage prices in foreign currencies." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:7 +msgid "" +"Check *Allow multi currencies* in :menuselection:`Invoicing/Accounting --> " +"Settings`. As admin, you need *Adviser* access rights on " +"Invoicing/Accounting apps." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:10 +msgid "" +"Create one pricelist per currency. A new *Currency* field shows up in " +"pricelist setup form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:13 +msgid "" +"To activate a new currency, go to :menuselection:`Accounting --> " +"Configuration --> Currencies`, select it in the list and press *Activate* in" +" the top-right corner. Now it will show up in currencies drop-down lists." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:17 +msgid "Prices in foreign currencies can be defined in two fashions." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:20 +msgid "Automatic conversion from public price" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:22 +msgid "" +"The public price is in your company's main currency (see " +":menuselection:`Accounting --> Settings`) and is set in product detail form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:28 +msgid "" +"The conversion rates can be found in :menuselection:`Accounting --> " +"Configuration --> Currencies`. They can be updated from Yahoo or the " +"European Central Bank at your convenience: manually, daily, weekly, etc. See" +" :menuselection:`Accounting --> Settings`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:40 +msgid "Set your own prices" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:42 +msgid "" +"This is advised if you don't want your pricing to change along with currency" +" rates." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:49 +msgid ":doc:`pricing`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:3 +msgid "How to adapt your prices to your customers and apply discounts" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:5 +msgid "" +"Odoo has a powerful pricelist feature to support a pricing strategy tailored" +" to your business. A pricelist is a list of prices or price rules that Odoo " +"searches to determine the suggested price. You can set several criteria to " +"use a specific price: periods, min. sold quantity (meet a minimum order " +"quantity and get a price break), etc." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:10 +msgid "" +"As pricelists only suggest prices, they can be overridden by vendors " +"completing sales orders. Choose your pricing strategy from " +":menuselection:`Sales --> Settings`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:18 +msgid "" +"*A single sale price per product:* doesn't let you adapt prices, it use " +"default product price ;" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:20 +msgid "" +"*Different prices per customer segment:* you will set several prices per " +"products ;" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:21 +msgid "" +"*Advanced pricing based on formula:* will let you apply discounts, margins " +"and roundings." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:24 +msgid "Several prices per product" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:26 +msgid "" +"To apply several prices per product, select *Different prices per customer " +"segment* in :menuselection:`Sales --> Settings`. Then open the *Sales* tab " +"in the product detail form. You can settle following strategies." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:31 +msgid "Prices per customer segment" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:33 +msgid "" +"Create pricelists for your customer segments: e.g. registered, premium, etc." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38 +msgid "" +"The default pricelist applied to any new customer is *Public Pricelist*. To " +"segment your customers, open the customer detail form and change the *Sale " +"Pricelist* in the *Sales & Purchases* tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:46 +msgid "Temporary prices" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:48 +msgid "Apply deals for bank holidays, etc. Enter start and end dates dates." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:54 +msgid "" +"Make sure you have default prices set in the pricelist outside of the deals " +"period. Otherwise you might have issues once the period over." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:58 +msgid "Prices per minimum quantity" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:64 +msgid "" +"The prices order does not matter. The system is smart and applies first " +"prices that match the order date and/or the minimal quantities." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:68 +msgid "Discounts, margins, roundings" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:70 +msgid "" +"*Advanced pricing based on formula* allows to set price change rules. " +"Changes can be relative to the product list/catalog price, the product cost " +"price, or to another pricelist. Changes are calculated via discounts or " +"surcharges and can be forced to fit within floor (minimum margin) and " +"ceilings (maximum margins). Prices can be rounded to the nearest cent/dollar" +" or multiple of either (nearest 5 cents, nearest 10 dollars)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:77 +msgid "" +"Once installed go to :menuselection:`Sales --> Configuration --> Pricelists`" +" (or :menuselection:`Website Admin --> Catalog --> Pricelists` if you use " +"e-Commerce)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:85 +msgid "" +"Each pricelist item can be associated to either all products, to a product " +"internal category (set of products) or to a specific product. Like in second" +" option, you can set dates and minimum quantities." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:92 +msgid "" +"Once again the system is smart. If a rule is set for a particular item and " +"another one for its category, Odoo will take the rule of the item." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:94 +msgid "Make sure at least one pricelist item covers all your products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:96 +msgid "There are 3 modes of computation: fix price, discount & formula." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:101 +msgid "Here are different price settings made possible thanks to formulas." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:104 +msgid "Discounts with roundings" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:106 +msgid "e.g. 20% discounts with prices rounded up to 9.99." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:112 +msgid "Costs with markups (retail)" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:114 +msgid "e.g. sale price = 2*cost (100% markup) with $5 of minimal margin." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:120 +msgid "Prices per country" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:122 +msgid "" +"Pricelists can be set by countries group. Any new customer recorded in Odoo " +"gets a default pricelist, i.e. the first one in the list matching the " +"country. In case no country is set for the customer, Odoo takes the first " +"pricelist without any country group." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:126 +msgid "The default pricelist can be replaced when creating a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128 +msgid "You can change the pricelists sequence by drag & drop in list view." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:131 +msgid "Compute and show discount % to customers" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:133 +msgid "" +"In case of discount, you can show the public price and the computed discount" +" % on printed sales orders and in your eCommerce catalog. To do so:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:136 +msgid "" +"Check *Allow discounts on sales order lines* in :menuselection:`Sales --> " +"Configuration --> Settings --> Quotations & Sales --> Discounts`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:138 +msgid "Apply the option in the pricelist setup form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145 +msgid ":doc:`currencies`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:146 +msgid ":doc:`/applications/websites/ecommerce/maximizing_revenue/pricing`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products.rst:5 +msgid "Manage your products" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:3 +msgid "How to import Products with Categories and Variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:5 +msgid "" +"Import templates are provided in the **Import Tool** of the most common data" +" to import (contacts, products, bank statements, etc.). You can open them " +"with any spreadsheet software (Microsoft Office, OpenOffice, Google Drive, " +"etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:11 +msgid "How to customize the file" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:13 +msgid "" +"Remove columns you don't need. However, we advise you to not remove the *ID*" +" column (see why below)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:15 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:16 +msgid "" +"Don't change the labels of columns you want to import. Otherwise, Odoo won't" +" recognize them anymore, and you will have to map them on your own in the " +"import screen." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:18 +msgid "" +"Feel free to add new columns, but the fields need to exist in Odoo. If Odoo " +"fails in matching the column name with a field, you can match it manually " +"when importing by browsing a list of available fields." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:24 +msgid "Why an “ID” column?" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:26 +msgid "" +"The ID is a truly unique identifier for the line item. Feel free to use one " +"from your previous software to ease the transition into Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:29 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:31 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:32 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:35 +msgid "How to import relation fields" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:37 +msgid "" +"An Odoo object is always related to many other objects (e.g., a product is " +"linked to product categories, attributes, vendors, etc.). To import those " +"relations, you need to import the records of the related object first from " +"their own list menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:41 +msgid "" +"You can do this using the name of the related record or its ID. The ID is " +"expected when two records have the same name. In such a case, add \" / ID\" " +"at the end of the column title (e.g., for product attributes: Product " +"Attributes / Attribute / ID)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:3 +msgid "Automatically get product images with Google Images" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:5 +msgid "" +"The product images are very useful in Odoo, for example, to quickly find a " +"product or check if you scanned the right one, but it can be a bit painful " +"to set up especially if you have a lot of products. **Google Custom Search**" +" allows finding images automatically for your product, based on their " +"barcode, keeping your focus on what matters in your business." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:15 +msgid "This functionnality requires configuration both on Google and on Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:17 +msgid "" +"With a free Google account, you can get up to 100 free images per day. If " +"you need a higher rate, you'll have to upgrade to a billing account." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:23 +msgid "Google API dashboard" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:25 +msgid "" +"Go to the `Google Cloud Platform API & Services " +"`_ page to generate Google Custom " +"Search API credentials. Log in with your Google account." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:28 +msgid "" +"Select or create an API project to store the credentials. Give it an " +"explicit name (e.g. Odoo Images)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:31 +msgid "" +"In the credentials section, click on **Create Credentials** and select **API" +" Keys**." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "API & Services page on Google Cloud Platform" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:37 +msgid "Save your **API Key**. You'll need it for the next step in Odoo!" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:39 +msgid "" +"Use the search bar to look for **Google Custom Search API** and select it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Search bar containing \"Custom Search API\" on Google Cloud Platform" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:45 +msgid "Enable the API." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"\"Custom Search API\" tile with Enable button highlighted on Google Cloud " +"Platform" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:54 +msgid "Google Programmable Search dashboard" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:56 +msgid "" +"Go to `Google Programmable Search Engine " +"`_ and click on **Get " +"Started**. Log in with your Google account." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"Google Programmable Search Engine page with the **Get Started** button on the up-right\n" +"of the page" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:64 +msgid "" +"Fill the language and the name of the search engine. Give it an explicit " +"name (e.g. Odoo Images)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:68 +msgid "" +"Google doesn't allow to create a search engine without having entered at " +"least one specific site to search on. You can put any website (e.g. " +"www.google.com) for this step, we will remove it later." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:72 +msgid "" +"Validate the form by clicking on **Create**. Then, go to the edition mode of" +" the search engine that you created (either by clicking on **Control Panel**" +" on the confirmation page or by clicking on the name of your Search Engine " +"on the Home page)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:76 +msgid "" +"In the **basics** tab, make sure to enable **Image search**, **SafeSearch** " +"and **Search the entire web**." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:80 +msgid "" +"Once **Search the entire web** is enabled, you can safely delete the site " +"that you put at the previous step." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:83 +msgid "" +"Save your **Search Engine Id**. You’ll need it for the next step in Odoo!" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:88 +msgid "Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:90 +msgid "" +"Go to :menuselection:`Settings --> General Settings --> Integrations`, " +"activate **Google Images** and save." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:93 +msgid "" +"Go back to :menuselection:`Settings --> General Settings--> Integrations`, " +"enter your **API Key** and **Search Engine ID** in **Google Images** " +"settings and save again." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:99 +msgid "Automatically get your product images in Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:101 +msgid "" +"The action to automatically get your product images in Odoo appears in any " +"Products or Product Variants list view. Here is a step-by-step guide from " +"the Inventory app." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:104 +msgid "" +"Go to the Products menu (:menuselection:`Products --> Products` or " +":menuselection:`Products --> Product Variants`) from any application that " +"uses products like Inventory or Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:107 +msgid "On the list view, select the products that needs an image." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:110 +msgid "" +"Only the 10,000 first selected products or product variants will be " +"processed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:113 +msgid "" +"Only the products or product variants with a barcode and without an image " +"will be processed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:114 +msgid "" +"If you select a product that has one or more variants from the Products " +"view, each variant matching the previous criteria will be processed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:117 +msgid "" +"In the action menu, select **Get Pictures from Google Images** and validate " +"by clicking on **Get picture**." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:120 +msgid "You should see your images appearing incrementally." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:123 +msgid "" +"Only the 10 first images are fetched immediatly. If you selected more than " +"10, the rest will be fetched as a background job." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:125 +msgid "" +"The background job process about 100 images in a minute. If you reach the " +"quota authorized by Google (either with a free or a paid plan), the " +"background job will put itself on hold for 24 hours and continue where it " +"stopped the day before." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:130 +msgid "" +"`Create, modify, or close your Google Cloud Billing account " +"`_" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:3 +msgid "Product variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:5 +msgid "" +"Product variants are used to give single products a variety of different " +"characteristics, such as size and color. Products using variants can be " +"managed at the product template level (for all attributes and variants of " +"that product), and/or at the variant level (for individual variants)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:9 +msgid "" +"As an example, a company selling t-shirts may have the following product:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:11 +msgid "T-shirt" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:13 +msgid "Color: Blue, Red, White, Black" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:14 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:131 +msgid "Size: S, M, L, XL, XXL" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:16 +msgid "" +"In this example, the **T-Shirt** is the product template, and **T-Shirt, S, " +"Blue** is a product variant. **Color** and **size** are the attributes. " +"**S** and **Blue** are values." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:19 +msgid "" +"The above example has a total of 20 different product variants (5 sizes x 4 " +"colors). Each one of these has its own inventory, sales, etc." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:26 +msgid "Activating product variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:28 +msgid "" +"To use product variants, go to :menuselection:`Sales --> Configuration --> " +"Settings --> Product Catalog`, and enable the :guilabel:`Variants` feature. " +"Finally, click :guilabel:`Save` to apply the setting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "Activating product variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:37 +msgid "Creating attributes" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:39 +msgid "" +"Attributes need to be created before product variants can be set up. " +"Attributes can be accessed via :menuselection:`Sales --> Configuration --> " +"Products --> Attributes`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:43 +msgid "" +"The order of attributes on the :guilabel:`Attributes` page dictates how they" +" appear on the :guilabel:`Product Configurator`, :guilabel:`Point of Sale` " +"dashboard, and :guilabel:`eCommerce` pages." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:47 +msgid "" +"To create a new attribute, click :guilabel:`Create`. First, choose an " +"attribute name, such as \"Color\" or \"Size.\"" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "Attribute creation window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:54 +msgid "" +"Then, select a :guilabel:`Display Type`, which determines how this product " +"will be shown on the :guilabel:`eCommerce` page, :guilabel:`Point of Sale` " +"dashboard, and :guilabel:`Product Configurator`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:58 +msgid ":guilabel:`Radio`: options appear in a bullet style list." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:59 +msgid ":guilabel:`Select`: options appear in a dropdown menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:60 +msgid "" +":guilabel:`Color`: options appear as small colored squares, which reflect " +"any HTML color codes set." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "Display Types on Product Configurator." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:67 +msgid "" +"The :guilabel:`Variants Creation Mode` informs Odoo when to automatically " +"create a new variant once an attribute is added to a product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:70 +msgid "" +":guilabel:`Instantly`: creates all possible variants as soon as attributes " +"and values are added to a product template." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:72 +msgid "" +":guilabel:`Dynamically`: creates variants only when corresponding attributes" +" and values are added to a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:74 +msgid ":guilabel:`Never`: never automatically creates variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:77 +msgid "" +"Once added to a product, an attribute's :guilabel:`Variants Creation Mode` " +"cannot be edited." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:79 +msgid "" +"Values should be added to an attribute before saving, but more values can be" +" added at any time, if needed. To add a value, click :guilabel:`Add a line`." +" From there, you can:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:82 +msgid "Type in the value's name." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:83 +msgid "" +"Check a box to indicate whether or not the value is custom (i.e. the " +"customer provides unique specifications)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:85 +msgid "" +"Specifically for colors, add an HTML color code to make it even easier for " +"salespeople and customers to know what they're selecting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:88 +msgid "" +"A color code can be selected either by dragging the slider around or by " +"entering a specific HTML color code (e.g. #FF0077)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "Selecting a color." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:95 +msgid "Finally, click :guilabel:`Save` to finish creating the attribute." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:98 +msgid "" +"Attributes can also be created directly from the product template by adding " +"a new line and typing the name into the :guilabel:`Variants` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:101 +msgid "" +"After an attribute is added to a product, a new tab appears on the " +"attribute's page called :guilabel:`Related Products`. This tab lists every " +"product in the database that is currently using the attribute." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:106 +msgid "Creating product variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:108 +msgid "" +"After creating an attribute, use the attribute to create a product variant " +"by going to :menuselection:`Sales --> Products --> Products`. Then, select " +"an existing product and click :guilabel:`Edit`, or create a new product by " +"clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:112 +msgid "" +"The :guilabel:`Variants` smart button at the top of the product template " +"indicates the number of currently configured variants on the product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:115 +msgid "" +"To add a new variant, click on the :guilabel:`Variants` tab, then click on " +":guilabel:`Add a line` to add any attributes and values. When all the " +"attributes and values have been added, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:120 +msgid "" +"Similar product variant creation processes are accessible through the " +"Purchase, Inventory, and eCommerce applications." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:124 +msgid "Managing product exclusions" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:126 +msgid "" +"The following examples are all based on a product template that has two " +"attributes:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:128 +msgid "T-Shirt" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:130 +msgid "Color: Blue, Red, White" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:133 +msgid "" +"With the above product template, there are 15 different t-shirt variants in " +"three different colors and five different sizes. If the white t-shirts are " +"not available in the XXL size, then that variant can be deactivated." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:137 +msgid "" +"To deactivate a particular product variant, go to :menuselection:`Sales --> " +"Products --> Products` and select the relevant product. Next, click on the " +":guilabel:`Configure` button next to the relevant attribute value. Then " +"select the relevant value (in this example, the :guilabel:`White Color` " +"attribute), and then click on :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:142 +msgid "" +"In the :guilabel:`Exclude for` section, click :guilabel:`Add a line` and " +"select any product(s) and/or specific attribute values that are currently " +"unavailable. Finally, click :guilabel:`Save` to apply the setting, and Odoo " +"will automatically show the product variant as unavailable on the eCommerce " +"page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "Excluding attributes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:152 +msgid "Setting a price per variant" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:154 +msgid "" +"Extra costs can be added to a product's standard price for specific product " +"variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:156 +msgid "" +"To do this, open :menuselection:`Sales --> Products --> Products`, and click" +" on the relevant product. Next, click on :guilabel:`Configure Variants` to " +"access the list of product variant values." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:160 +msgid "" +"Then, click on a variant value, and :guilabel:`Edit`. In the " +":guilabel:`Value Price Extra` field, type in the additional cost for this " +"particular value. This amount is added to the standard price. Finally, click" +" :guilabel:`Save` to apply the extra price to the value." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "Value Price Extra setting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:169 +msgid "Impact of variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:171 +msgid "" +":guilabel:`Barcode`: barcodes are associated with each variant instead of " +"the product template. Each individual variant can have its own unique " +"barcode/SKU." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:174 +msgid "" +":guilabel:`Price`: every product variant has its own public price, which is " +"the sum of the product template price and any extra charges for particular " +"attributes. For example, a red shirt's cost is $23 because the shirt's " +"template price is $20, plus an additional $3 for the red color variant. " +"Pricelist rules can be configured to apply to the product template or to the" +" variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:180 +msgid "" +":guilabel:`Inventory`: inventory is counted for each individual product " +"variant. On the product template form, the inventory reflects the sum of all" +" variants, but the actual inventory is computed by individual variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:184 +msgid "" +":guilabel:`Picture`: each product variant can have its own specific picture." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:187 +msgid "" +"Changes to the product template automatically apply to every variant of that" +" product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:3 +msgid "Process returns and refunds" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:5 +msgid "" +"The :guilabel:`Sales` app provides two different ways to process returns " +"based on whether an invoice has been sent or not." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:9 +msgid "Before invoicing" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:11 +msgid "" +"Returns are completed using *Reverse Transfers* when a customer decides to " +"return a product before an invoice has been sent or validated." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:15 +msgid "" +"In order to use Reverse Transfers, the :guilabel:`Inventory` app must also " +"be installed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:17 +msgid "" +"To start a return, open the :guilabel:`Sales` app, navigate to the " +"customer's sales order, and click on the :guilabel:`Delivery` smart button " +"to open the associated delivery order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:20 +msgid "" +"On the validated delivery order, click :guilabel:`Return` to open the " +":guilabel:`Reverse Transfer` pop-up window. By default, the " +":guilabel:`Quantity` matches the validated quantities from the delivery " +"order. Update the quantities if necessary. Click on the trash icon next to a" +" line item to remove it from the return." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"The \"Reverse Transfer\" pop-up window, to make a return before invoicing " +"the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:29 +msgid "" +"Next, click :guilabel:`Return` to confirm the return. This generates a new " +"warehouse operation for the incoming returned product(s). Upon receiving the" +" return, the warehouse team validates the warehouse operation. Then, on the " +"original sales order, the :guilabel:`Delivered` quantity will reflect the " +"difference between the initial validated quantities and the returned " +"quantities." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"The updated \"Delivered\" quantity on the sales order after the reverse " +"transfer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:38 +msgid "" +"When an invoice is created, the customer receives an invoice only for the " +"products they are keeping." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:42 +msgid "After invoicing" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:44 +msgid "" +"Sometimes, customers return an item after they receive and/or pay for their " +"invoice. In these cases, a return using only *Reverse Transfers* is " +"insufficient since validated or sent invoices cannot be changed. However, " +"*Reverse Transfers* can be used in conjunction with *Credit Notes* to " +"complete the customer's return." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:49 +msgid "" +"To start a return, navigate to the relevant sales order. If there is a " +"payment registered on the sales order, then the payment details will appear " +"in the Chatter, and the invoice (accessible through the :guilabel:`Invoices`" +" smart button) will have a green banner across it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:53 +msgid "" +"From the sales order, click on the :guilabel:`Delivery` smart button to view" +" the validated delivery order. Then, click :guilabel:`Return` to open the " +":guilabel:`Reverse Transfer` pop-up window. Next, edit the " +":guilabel:`Product` or :guilabel:`Quantity` as needed for the return, and " +"then click :guilabel:`Return`. This generates a new warehouse operation for " +"the incoming returned product(s), which is validated by the warehouse team " +"once the return is received. Then, on the sales order, the " +":guilabel:`Delivered` quantity will reflect the difference between the " +"initial validated quantities and the returned quantities." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:61 +msgid "" +"To process a refund, navigate to the relevant invoice (from the sales order," +" click on the :guilabel:`Invoices` smart button). Click :guilabel:`Add " +"Credit Note` from the validated invoice." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"The \"Credit Note\" pop-up window, to issue a credit to the customer after " +"invoicing." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:68 +msgid "" +"A :guilabel:`Reason` for the credit and a :guilabel:`Specific Journal` to " +"use to process the credit can be specified. If a :guilabel:`Specific " +"Reversal Date` is selected, then a :guilabel:`Refund Date` must also be " +"selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:72 +msgid "" +"After the information is filled in, click :guilabel:`Reverse`. Then, " +":guilabel:`Edit` the draft as needed, and finally, click :guilabel:`Confirm`" +" to confirm the credit note." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations.rst:5 +msgid "Send Quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:3 +msgid "Use quotations deadline to stimulate your customers" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:5 +msgid "" +"When sending quotations, it is important to set a deadline to encourage your" +" customers to act. Indeed, this will stimulate them because they will be " +"afraid of missing a good deal and it will also allow you to protect yourself" +" in case you have to fulfill an order at a price that is no longer " +"profitable for you." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:11 +msgid "Set a deadline" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:13 +msgid "" +"With Odoo Sales, it is possible to instantly add an **Expiration Date** from" +" the quotation or the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst-1 +msgid "How to configure deadlines on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:22 +msgid "Use deadline in your quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:24 +msgid "" +"It is also possible to add a deadline to every quotation template created. " +"Whenever a specific quotation template is used in a quote, its associated " +"deadline will be automatically applied. Be sure to check out our " +"documentation about :doc:`quote_template` to excel in their use." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst-1 +msgid "How to use deadline in a quotation template on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:34 +msgid "" +"By clicking on the **Customer Preview** button, you will be able to see when" +" the offer expires. For your information, the number of days will be the " +"same as those mentioned in the quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:0 +msgid "How customers will see deadlines on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:44 +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:50 +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:51 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:65 +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:115 +msgid ":doc:`quote_template`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:3 +msgid "Deliver and invoice to different addresses" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:5 +msgid "" +"With Odoo Sales, you can configure different addresses for delivery and " +"invoicing. For some customers, it will be very practical to define specific " +"billing and shipping addresses. Indeed, not everyone will have the same " +"delivery location as the invoicing location." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:12 +msgid "" +"Go to :menuselection:`Sales --> Configuration --> Settings` and activate the" +" **Customer Addresses** feature." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "How to enable different customer addresses on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:21 +msgid "Add addresses from a quotation" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:23 +msgid "" +"When you create a quotation, you must add a customer. This customer can be a" +" company or a person with specific billing and shipping addresses already " +"defined and registered in the system, or it can be a new customer. In this " +"case, you have to **Create and edit** the contact form for your new customer" +" and link it, if necessary, to a company. In this contact form, you will be " +"able to add, delete and modify invoice and delivery addresses." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "How to add addresses from a quotation on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:35 +msgid "" +"If you select a customer with defined invoice and delivery addresses, Odoo " +"will automatically use them to fill in the fields. Now, if you want to " +"change it instantly, it is possible to do so directly from the quotation or " +"the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:40 +msgid "Add addresses from a contact form" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:42 +msgid "" +"Previously, we talked about the contact form that you can fill in directly " +"from a quotation or a sales order to add billing and shipping addresses to " +"customers. But, if you go to :menuselection:`Sales --> Orders --> " +"Customers`, you can create or modify every customer you want and add, delete" +" or modify invoice and delivery addresses instantly there, before creating a" +" quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "How to add addresses from a contact form on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:54 +msgid "Deal with different addresses" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:56 +msgid "" +"Like for the previous example, go to :menuselection:`Sales --> Orders --> " +"Customers` and create a new customer. There, you can add company information" +" but, more importantly, you can enter billing and shipping addresses under " +"the **Contacts & Addresses** tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "How to manage different customer addresses on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:65 +msgid "" +"Once done, you can return to your Sales dashboard and create a new " +"quotation. Now, if you enter your new customer, you will see that the other " +"fields will fill in by themself with the information previously saved for " +"billing and shipping addresses." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "Automatic quotation fields filling on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:74 +msgid "" +"With Odoo Sales, it is now very convenient to play with various addresses in" +" terms of invoice and delivery features." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:3 +msgid "Get paid to confirm an order" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:5 +msgid "" +"In general, online payments are considered as a fast and secure alternative " +"to traditional payment methods. It is generally cheaper, easier and faster " +"than other payment methods. It is particularly useful and efficient for " +"international transactions. With Odoo Sales, you can use online payments to " +"get automatic orders confirmation. Online payments are made instantly, so " +"it's very convenient and saves lots of time in a basic sales process." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:12 +msgid "Enable online payment" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:14 +msgid "" +"Go to :menuselection:`Sales --> Configuration --> Settings` and activate the" +" **Online Payment** feature." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "How to enable online payment on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:22 +msgid "" +"There, you will have direct access to the **Payment Acquirers** page. It " +"will allow you to select and configure your acquirers of choice. Before " +"creating or modifying a payment acquirer, be sure to check out our " +"documentation about how to be paid with payment acquirers such as " +":doc:`/applications/finance/payment_acquirers/paypal`, " +":doc:`/applications/finance/payment_acquirers/authorize`, and others in the " +":doc:`/applications/finance/payment_acquirers` documentation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:30 +msgid "" +"If you are familiar with this documentation: :doc:`quote_template`; you can " +"activate or not the **Online Payment** feature for each template you use, " +"under their confirmation tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:35 +msgid "Register a payment" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:37 +msgid "" +"After opening quotations from their received email, your customers will have" +" different possibilities to make their online payments. For example:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "How to register a payment on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:46 +msgid "" +"By clicking on the **Customer Preview** button, you will be able to see what" +" your customers will have to choose when it comes to payment." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:51 +msgid ":doc:`/applications/finance/payment_acquirers`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:52 +msgid ":doc:`/applications/finance/payment_acquirers/paypal`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:53 +msgid ":doc:`/applications/finance/payment_acquirers/authorize`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:3 +msgid "Get a signature to confirm an order" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:5 +msgid "" +"Online signatures are like electronic \"fingerprints\". By using them on " +"Odoo, you will get automatic orders confirmation. You and your customers " +"will save a lot of time by using this feature compared to a traditional " +"process." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:10 +msgid "Activate online signature" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:12 +msgid "" +"Go to :menuselection:`Sales --> Configuration --> Settings` and activate the" +" **Online Signature** feature." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 +msgid "How to enable online signature on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:21 +msgid "" +"If you are familiar with this documentation: :doc:`quote_template`, you can " +"activate or not the **Online Signature** feature for each quotation template" +" you use, under their confirmation tab. Example:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:31 +msgid "Confirm an order with a signature" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:33 +msgid "" +"When you send quotations to clients, they can instantly accept and sign it " +"online. When they click on **Sign & Pay**, they have the choice to draw " +"their own signature, automatically fill in the field with an automated " +"signature or load a file from their computer. Here below, it is an example " +"of an automated signature:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 +msgid "How to confirm an order with a signature on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:43 +msgid "" +"Once signed, you will have the possibility to choose your payment methods. " +"Then, when the quotation will be paid and confirmed, a delivery order will " +"be created automatically by Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:47 +msgid "" +"Be careful that delivery orders are only generated for storable products and" +" if the **Inventory app** is already installed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:3 +msgid "Add optional products" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:5 +msgid "" +"The use of optional products is a marketing strategy for cross-selling " +"products along with a core product. The aim is to offer useful and related " +"products to your customers. For instance, if a customer wants to buy a car, " +"he has the choice to order an automatic opening trunk and massaging seats, " +"or not to order such high-quality products and simply buy his car." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:11 +msgid "Add optional products to your quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:13 +msgid "" +"With Odoo Sales, it is possible to add or modify optional products directly " +"on quotations (under the **Optional Products** tab, as you can see below)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 +msgid "How to add optional products to your quotations on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:22 +msgid "" +"By clicking on the **Customer Preview** button, you will be able to see what" +" your customers will have as possibilities after opening a quotation from " +"their received email." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:0 +msgid "Preview your quotations on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:30 +msgid "" +"In practice, your customers will be able to add different optional products " +"to their order by using associated carts, with a user-friendly layout. More " +"than that, if a customer selects all the optional products suggested, these " +"additional items will automatically fill in the quotation managed by the " +"salesman." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 +msgid "How to select optional products on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:40 +msgid "" +"Like this, salespeople will see each movement made by the customer and " +"tracking the order will be all the better." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 +msgid "How to follow each movement made by your customers on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:49 +msgid "Add optional products to your quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:51 +msgid "" +"Be sure to check out our documentation about :doc:`quote_template` to " +"understand how you can enable, create, design and manage your own quotation " +"templates before reading this part." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:54 +msgid "" +"For quotation templates, you also have an **Optional Products** tab where " +"you can add related products or services." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 +msgid "How to add optional products to your quotation templates on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:62 +msgid "" +"With Odoo Sales, it is now very easy to understand your customer's needs." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:3 +msgid "Use product variants on quotations and sales orders" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:5 +msgid "" +"Product variants can be added to quotations and sales orders using the " +"Product Configurator, Variant Grid Entry, or both." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:11 +msgid "" +"To enable product variants on quotations and sales orders, go to " +":menuselection:`Sales --> Configuration --> Settings --> Product Catalog` " +"and activate one or both of the :guilabel:`Product Configurator` and " +":guilabel:`Variant Grid Entry` settings. Finally, click :guilabel:`Save` to " +"apply the settings." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "Activating entry type settings." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:20 +msgid "" +"After saving the settings, configure the product form. Head over to " +":menuselection:`Sales --> Products --> Products` and select any product (or " +"click :guilabel:`Create` to create a new one). On the product form, click " +":guilabel:`Edit`, and then click on the :guilabel:`Variants` tab. Under " +":guilabel:`Sales Variant Selection`, choose either :guilabel:`Product " +"Configurator` or :guilabel:`Order Grid Entry`. This selection determines " +"which method is used to add the product to quotations or sales orders. " +"Finally, click :guilabel:`Save` to apply the setting." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "Sales variant selection." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:32 +msgid "" +"The product must have at least two variants (one attribute with two values) " +"created in order for the :guilabel:`Sales Variant Selection` option to " +"appear. Click :guilabel:`Add a line` under :guilabel:`Attribute` to add " +"attributes and values to this product and create product variants." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:37 +msgid "Use the Product Configurator" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:39 +msgid "" +"The :guilabel:`Product Configurator` appears on a quotation or sales order " +"when products are added that have both variants configured and the " +":guilabel:`Product Configurator` option selected." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:42 +msgid "" +"The :guilabel:`Product Configurator` lets salespeople choose exactly which " +"product variant to add to the quotation or sales order using a format " +"similar to online shopping. Color options display any HTML color codes set " +"up in the :guilabel:`Color` attribute. Features with an additional cost will" +" display the additional cost next to their name. Once the desired product " +"variant attributes are selected, click :guilabel:`Add` to add the product " +"variant to the quotation or sales order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "Product Configurator and Price Extras." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:52 +msgid "" +"By default, the product variant attributes are displayed on the quotation or" +" sales order in the :guilabel:`Description` column, but the " +":guilabel:`Product Variant` column can be added through the additional " +"options menu (3 vertical dots icon)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:57 +msgid "Use Variant Grid Entries" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:59 +msgid "" +":guilabel:`Variant Grid Entries` appear on a quotation or sales order when " +"products are added that have both variants configured and the " +":guilabel:`Order Grid Entry` option selected. Grid entry can streamline the " +"process of creating large, varied quotations by letting salespeople enter " +"exact quantities of each product variant all at once." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:64 +msgid "" +":guilabel:`Variant Grid Entry` displays a grid of every variant available " +"for the selected product. Choose the exact quantities of each product " +"variant for a quotation or sales order by typing in the number or using the " +"arrows. :guilabel:`Not Available` is displayed when a particular variant has" +" been deactivated in the database. Once all the product variants and their " +"quantities have been set, click :guilabel:`Confirm` to add them to the " +"quotation or sales order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "Variant Grid Entry pop-up." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:74 +msgid "" +"Each product variant appears as an individual line item on the quotation or " +"sales order, because each of these items has its own stock." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "Line items for grid variants." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3 +msgid "Use quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:5 +msgid "" +"By creating custom quotation templates, you will save a lot of time. Indeed," +" with the use of templates, you will be able to send complete quotations at " +"a fast pace." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:11 +msgid "" +"To enable this feature, go to :menuselection:`Sales --> Configuration --> " +"Settings` and activate **Quotation Templates**." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "How to enable quotation templates on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:19 +msgid "" +"For even more convenience, it is also recommended to add the **Quotation " +"Builder** feature which will help you design your quotation templates very " +"easily. This option will automatically install the Odoo Website App." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "How to enable quotation builder on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:29 +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:47 +msgid "Create your first template" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:31 +msgid "" +"Quotation templates are under :menuselection:`Sales --> Configuration`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:33 +msgid "" +"You can create a new template or edit an existing one. Once named, you will " +"be able to select products and quantities as well as the expiration time of " +"the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Create a new quotation template on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:42 +msgid "Design your template" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:44 +msgid "" +"You will have the possibility to design your template and edit the customer " +"interface in order to manage what clients will see before accepting and " +"paying the quotation. For example, you will be able to describe your " +"company, your services and your products. To do so, you can click on " +"**Edit** and you will be brought to the quotation builder." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Design your quotation template on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:54 +msgid "" +"You can easily edit the content of your template by dragging & dropping " +"different building blocks to organize your quotation. For example, you can " +"add a content block to describe your products." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "" +"Drag & drop building blocks to create your quotation template on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:63 +msgid "Use a quotation template" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:65 +msgid "When creating a quotation, you can choose a specific template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Select a specific template on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:73 +msgid "" +"You can select any template of your choice and suggest it as the default " +"template in the **Sales** settings." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:77 +msgid "Confirm the quotation" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:79 +msgid "" +"Templates facilitate the confirmation process by allowing customers to sign " +"electronically or to pay online. You can activate these two options directly" +" in the quotation template itself." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "" +"Allow your customers to sign electronically or to pay online on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:88 +msgid "" +"Every quotation will now have this setting. Of course you can always change " +"it and make it specific for each quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:92 +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:116 +msgid ":doc:`get_signature_to_validate`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:93 +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:117 +msgid ":doc:`get_paid_to_validate`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:3 +msgid "Add terms & conditions" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:5 +msgid "" +"Specifying terms and conditions is essential to set out important " +"contractual points such as payment terms, limitation of liability and " +"delivery terms between customers and sellers. Every seller must declare all " +"formal information concerning products and company policy. On the other " +"hand, each customer must take note of all these conditions before committing" +" to anything. With Odoo Sales, it is very easy to include your default terms" +" and conditions on every quotation, sales order, and invoice that you " +"manage." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:13 +msgid "Default Terms & Conditions" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:18 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and " +"activate *Default Terms & Conditions*." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst-1 +msgid "How to enable Default Terms & Conditions on Odoo Sales?" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:27 +msgid "" +"Please note that this feature is activated via the settings of the " +"**Invoicing App** and **not** via the settings of the **Sales App**. " +"Moreover, you don't need to install the invoicing application since it is " +"done automatically with the installation of the sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:32 +msgid "DT&C on your quotations, sales orders, and invoices" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:34 +msgid "" +"In the settings of the **Invoicing App**, you have the possibility to insert" +" your default terms and conditions." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst-1 +msgid "Default Terms & Conditions on quotation on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:42 +msgid "They appear subsequently on every quotation, sales order, and invoice." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:45 +msgid "DT&C on your quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:47 +msgid "" +"According to your business needs, you can specify your terms and conditions " +"on your quotation templates. This is interesting if you have different terms" +" and conditions within your company." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst-1 +msgid "" +"Add Default Terms & Conditions to your quotation templates on Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:56 +msgid "" +"Be sure to check out our documentation about quotation templates: " +":doc:`quote_template`, to master each step of this amazing feature." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:60 +msgid "General Terms & Conditions" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:63 +msgid "GT&C on your website" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:65 +msgid "" +"Use the **Website App** and create your own general terms and conditions " +"page. For example, here is the Odoo terms and conditions page:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst-1 +msgid "General Terms & Conditions on your website" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:73 +msgid "" +"You can refer to this page in the footer of all your documents. The layout " +"is available in the **General Settings** under the **Business Documents** " +"category. For example, this footer appears in every document from Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst-1 +msgid "General Terms & Conditions in your business documents" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:83 +msgid "GT&C as attachment in your emails" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:85 +msgid "" +"Attach an external document with your general terms and conditions when you " +"are about to send your quotation by email to your customers." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst-1 +msgid "General Terms & conditions as attachment in your email" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:94 +msgid "GT&C as attachment in your quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:96 +msgid "" +"Create and edit email templates to set a default attachment for all " +"quotation emails that you will send in the future. To do so, you have to go " +"to :menuselection:`Sales --> Configuration --> Quotation templates` and " +"create a new quotation template or modify an existing one. Under the " +"confirmation tab, you are now able to activate online signatures, online " +"payments and to set a confirmation mail in which you have the possibility to" +" configure the default attachment. There, you can put your general terms & " +"conditions." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst-1 +msgid "General Terms & conditions as attachment in your quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:109 +msgid "" +"To customize your email templates, activate the **developer mode** and go to" +" :menuselection:`Settings --> Technical --> Email --> Templates`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:112 +msgid "With Odoo Sales it is now very simple to deal with terms & conditions." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:8 +msgid "Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:10 +msgid "" +"**Odoo Subscriptions** is used to run recurring businesses: sell new " +"contracts, upsell customers, keep the churn under control and have reporting" +" on the main KPIs: MRR, ARR, retention, churn, upselling, etc." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:15 +msgid "" +"`Odoo Tutorials: Subscriptions " +"`_" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:3 +msgid "Add subscription products" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:5 +msgid "" +"To properly sell your subscriptions using our amazing **Odoo Subscriptions**" +" application, you must follow these steps:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:8 +msgid "**Create your own subscription templates**" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:9 +msgid "**Create your own subscription products with the right settings**" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:11 +msgid "" +"As a result, you will be able to manage your subscriptions like any other " +"product, create your quotations and continue the sales flow to track the " +"number of subscriptions you sell and manage the revenue they generate." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:18 +msgid "" +"Go to :menuselection:`Subscriptions --> Subscription products` to learn how " +"you can configure your own subscription products. You have the possibility " +"to create a new product or edit an existing one. Once named, be careful to " +"select the option *Can be sold* and deselect *Can be purchased*. For the " +"product type, it is recommended to use *Service* for subscription products " +"as they are non-material products that you provide to your customers. " +"Finally, you can adapt your prices and also add an internal reference." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst-1 +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:0 +msgid "View of a subscription product form in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:30 +msgid "" +"In the Sales tab, underneath the Subscriptions section, make sure the " +"*Subscription products* option is activated. In fact, if you create a " +"subscription product from the **Odoo Subscriptions** application, this " +"option is selected by default. However, if you create a product from another" +" application, it is not the case." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:39 +msgid "You can also choose the subscription templates you want to use." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:46 +msgid "" +"Be sure to check out our documentation on how to create, edit and manage " +"your own :doc:`Subscription templates " +"<../../subscriptions/configuration/subscription_templates>` before creating " +"your own subscription products. Once created, check out our documentation on" +" how to :doc:`Create a quotation using subscription products " +"<../../subscriptions/sales_flow/create_a_quotation>`, to complete the sales " +"flow." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:53 +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:83 +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:120 +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:105 +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:79 +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:80 +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:83 +msgid ":doc:`../../subscriptions/configuration/subscription_templates`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_products.rst:54 +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:85 +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:122 +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:107 +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:82 +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:85 +msgid ":doc:`../../subscriptions/sales_flow/create_a_quotation`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:3 +msgid "Use subscription templates" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:5 +msgid "" +"The subscription business model is becoming more popular. Are you wondering " +"why?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:7 +msgid "For **customers**, value lies in **convenience**:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:9 +msgid "" +"Subscriptions simplify the business process. Indeed, subscribers never have " +"to remember to renew their orders every month, which gives them the " +"assurance that they will have everything they need before they actually need" +" it." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:12 +msgid "Subscriptions help customers stay on budget." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:14 +msgid "" +"For **businesses**, value lies in the **ability to predict recurring " +"revenue**:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:16 +msgid "" +"Subscriptions reduce customer churn rate and significantly increase customer" +" retention." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:17 +msgid "" +"Subscriptions provide much higher payment security for your business. They " +"stabilize and maintain recurring revenue streams by guaranteeing monthly " +"revenues and adding value to your business." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:27 +msgid "" +"**Odoo Subscriptions** help you save time and money. Subscription templates " +"can help you generate recurring invoices and manage renewals at a fast pace." +" With Odoo you have the possibility to create, edit, and manage your own " +"subscription templates." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:34 +msgid "" +"Go to :menuselection:`Subscriptions --> Configuration --> Subscription " +"templates`. By default, Odoo suggests you two types of subscription (MON - " +"Monthly subscription *vs* YEA - Yearly subscription). You can also create " +"your own ones." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst-1 +msgid "Default subscription templates on Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:43 +msgid "" +"The **Odoo Subscriptions** application automatically installs **Odoo Sales**" +" and **Odoo Invoicing** as they work integrated." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:49 +msgid "" +"You can create a new template or edit an existing one. The first thing you " +"need to do is give your template a name. After that, choose an *Invoicing " +"period* and specify whether you would like to invoice your customers per " +"*Days*, *Weeks*, *Months* or *Years*. On *Duration*, determine if the " +"subscription must go on *Forever* (until it’s manually closed), or for a " +"*Fixed amount* of time. Among the payment options, an additional field " +"called *Invoice email* appears when you choose *Send*, *Send & try to " +"charge* or *Send after successful payment*. This field allows you to add an " +"invoice email template to your subscription templates." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst-1 +msgid "Create your own subscription templates on Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:61 +msgid "" +"For each template, you can also choose if you want your customers to be able" +" to close their subscriptions or not. If enabled, you can set an *Automatic " +"closing* limit and specify the *Group of subscription* and *Journal* " +"options." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:66 +msgid "" +"On each template, you can add your **Terms and Conditions**. Specifying " +"terms and conditions is essential to set out important contractual points " +"between the customers and the sellers (payment, refund policy, cancellation," +" complaints, etc.)." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:0 +msgid "Terms & conditions on Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:74 +msgid "" +"Finally, if you want to know the basic running health status of your " +"subscriptions, you also have access to a specific tab called **Health " +"Check**. There, you can edit and create your own filters to define what is a" +" subscription in good health *vs* bad health. The system automatically " +"summarizes all the records corresponding to these filters and you are able " +"to manage them in one click." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:0 +msgid "Health check on Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:85 +msgid "" +"After creating your own subscription templates, be sure to check out our " +"documentation on how to create, edit and manage your own :doc:`Subscription " +"products <../../subscriptions/configuration/subscription_products>`, to " +"complete the sales flow." +msgstr "" + +#: ../../content/applications/sales/subscriptions/configuration/subscription_templates.rst:91 +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:84 +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:121 +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:106 +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:80 +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:81 +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:84 +msgid ":doc:`../../subscriptions/configuration/subscription_products`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up.rst:5 +msgid "Follow-up" +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:3 +msgid "Set up automatic alerts" +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:5 +msgid "" +"Now that your subscriptions are up and running, you want to stay up-to-date " +"with your customers. Some automation would be appreciated since you would " +"not want to go through the list of all your subscribers to check how things " +"are going. This is what the *Automatic Alerts* feature is for." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:9 +msgid "" +"For example, when customers subscribe to your magazine, you would probably " +"want to send them an email to welcome them and express your gratitude. Or, " +"if the satisfaction rate of your customers drops below 50%, you would " +"probably want to schedule a call with them to understand the reasons for " +"their dissatisfaction." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:14 +msgid "" +"With **Odoo Subscriptions**, you can set automatic emails, create a \"Call\"" +" task for one of your salespeople so that he/she can try to understand your " +"customer's dissatisfaction, and finally, why not automatically send " +"satisfaction surveys so customers can evaluate your services? All of that is" +" now possible." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:20 +msgid "Create a new automatic alert" +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:22 +msgid "" +"The following example shows how to create a new automatic alert to send " +"satisfaction surveys to your customers, by email, after one month of " +"subscription. To do so, go to :menuselection:`Subscriptions --> " +"Configuration --> Alerts`, and create a new alert." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst-1 +msgid "New automatic alert in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:30 +msgid "" +"On the *Apply on* section, first give the alert a name. Then, you can choose" +" to apply this alert on a subscription template, on a specific customer, or " +"even on a specific product. If you want to add more specifications, you can " +"also specify the value of your MRR, the change rate of your MRR over a " +"certain period of time, the value of the satisfaction rate, and even the " +"stage to which you want to apply this alert." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:37 +msgid "" +"In this example, the alert is applied to a specific product, and the stage " +"goes from *Undefined* to *In Progress*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:40 +msgid "" +"For the *Action* section, specify the *Action* and the *Trigger on*. If the " +"*Trigger on* is set to *Modification*, the action is triggered every time " +"there is a change or anything added to the subscription, and all the " +"conditions on the *Apply on* section are met. Now, if the *Trigger on* is " +"set to *Timed condition*, it means that the action is triggered based on the" +" type of *Trigger date*. After that, you can choose your *Action*. You have " +"the choice between *Create next activity*, *Set a tag on the subscription*, " +"*Set a stage on the subscription*, *Mark as To Renew*, *Send an email to the" +" customer* and *Send an SMS Text Message to the customer*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:50 +msgid "" +"In the example above, the *Trigger on* is set to *Timed condition*, " +"therefore, a *Trigger date* and *Delay after trigger* need to be specified. " +"And because the *Send an email to the customer* action was adopted, an " +"*Email template* can be chosen." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:54 +msgid "" +"As a result, this alert will send a rating survey after one month, to the " +"customers who have purchased that specific product. The survey will appear " +"in the chatter of your respective subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst-1 +msgid "Satisfaction survey in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:63 +msgid "Modify an existing automatic alert" +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:65 +msgid "" +"By default, Odoo suggests you an automatic alert called *Take action on less" +" satisfied clients*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst-1 +msgid "Modify an existing automatic alert in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:71 +msgid "" +"This alert is applied to the *Rating Satisfaction* of your customers, and " +"the action is triggered on *Timed condition*. If their satisfaction rate is " +"lower than 50%, a salesperson contacts the customer. This action is " +"automatically assigned to the salesperson who manages the subscription, and " +"the due date is 5 days after the triggering of this action. This alert " +"ensures that your clients are happy and that you are taking actions if they " +"are not. It helps to keep your customer retention rates very high." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:79 +msgid "" +"By editing the alert, you can modify the *Apply on*, the *Action* and " +"*Activity* sections, and adapt them to your own needs." +msgstr "" + +#: ../../content/applications/sales/subscriptions/follow_up/automatic_alerts.rst:86 +msgid ":doc:`../../subscriptions/reporting/subscription_reports`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:3 +msgid "Generate subscription reports" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:5 +msgid "" +"As we know, understanding how our business is going, and where it is going, " +"is key to success. And particularly so when we offer subscription services " +"or products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:8 +msgid "" +"Before getting to the heart of the matter, it is very important to recall " +"certain essential concepts to the proper understanding of the following " +"reports:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:11 +msgid "" +"**Monthly Recurring Revenue (MRR)**: MRR is arguably the most important " +"metric for subscription businesses. It shows the monthly revenue earned with" +" subscription-based products or services. It is a consistent number used to " +"track all recurring revenue over time, in monthly increments." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:15 +msgid "" +"**Annual Run-Rate (ARR)**: ARR is the yearly version of MRR, which is based " +"on the current MRR, to estimate the coming year's performance. However, this" +" estimation does not take variations and growth into account." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst-1 +msgid "Difference between MRR and ARR in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:23 +msgid "" +"**Non-Recurring Revenue (NRR)**: NRR shows the revenue earned for everything" +" else than subscription-based products or services. This includes gains of a" +" rare or unique nature that are unlikely to occur in the ordinary course of " +"businesses." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:27 +msgid "" +"**Customer Retention**: Practices to engage existing customers to continue " +"buying products or services from your business. Customer retention can be a " +"challenge, because you must prove you are worthy of your customers' trust." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:31 +msgid "" +"**Churn Rate**: Also known as the Rate of Attrition or Customer Churn, the " +"churn rate can be defined, in this case, as the percentage of subscribers " +"who discontinued their subscriptions within a given time period. We can " +"distinguish two types of Churn:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:35 +msgid "**Logo Churn**: It corresponds to the subscription cancellation rate." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:37 +msgid "" +"**Revenue Churn**: It corresponds to the monthly recurring revenue loss " +"rate." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:40 +msgid "Let's imagine a 2$ increase in a subscription service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:42 +msgid "" +"We lost 3 customers out of the initial 20, which generates a **Logo Churn** " +"of 15%." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:0 +msgid "" +"Therefore, the 56$ of MRR difference out of the initial 600$ causes a " +"**Revenue Churn**" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:0 +msgid "of 9,33%." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:0 +msgid "Difference between logo churn and revenue churn in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:50 +msgid "" +"Reminder: even though they seem to evolve in the same direction most of the " +"time, it might not be the case all the time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:53 +msgid "" +"**Customer Lifetime Value (CLV)**: Indicates how much revenue can be " +"expected for a customer during his/her entire contract. This approach " +"emphasizes the importance of customer retention, shifting our focus from a " +"quarterly or yearly approach to a long-term one." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:57 +msgid "" +"Check out the different kinds of reports you can access from the **Odoo " +"Subscriptions** application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:61 +msgid "Subscriptions analysis report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:63 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Subscriptions`. From " +"there, you can change the *Measures*. By default, Odoo uses the *Monthly " +"Recurring Revenue*. In addition to that, you can choose *Quantity*, " +"*Recurring Price*, *Yearly Recurring Revenue* and *Count*. For this example," +" *Quantity* is added. This way, you can review both of these measures at the" +" same time. You can even *Group By Start Date* and, more precisely, by " +"*Week*, to get a clear view of your report." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst-1 +msgid "Subscriptions analysis report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:74 +msgid "Retention analysis report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:76 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Retention`. The " +"default measure applied is *Count*, but you can change to the appropriate " +"one for you. For the example below, *Monthly Recurring Revenue* was chosen, " +"and the *Month* periodicity remains intact. By using these criteria, you can" +" see the progression of the retention from its start." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst-1 +msgid "Retention analysis report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:86 +msgid "Revenue KPIs report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:88 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Revenue KPIs`. From " +"there, you can check different KPIs: *Monthly Recurring Revenue*, *Net " +"Revenue*, *Non-Recurring Revenue*, *Revenue per Subscription*, *Annual Run-" +"Rate*, *Lifetime Value*, and more. You can also filter this information on " +"subscriptions, companies, and sales teams. This is useful if you are looking" +" for specific information." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst-1 +msgid "Revenue KPIs report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:98 +msgid "" +"The example below shows the *Monthly Recurring Revenue* detailed report. At " +"the moment, there is no data, which is the typical scenario for a new " +"business. But, as your company grows over the months, these graphs get " +"populated with more and more data. Once again, you can filter these specific" +" KPIs on subscriptions, companies, and sales teams." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst-1 +msgid "Detailed MRR report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:108 +msgid "Salesperson dashboard report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst:110 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Salesperson " +"Dashboard`. This page gives you a summary of your *Monthly Recurring " +"Revenue*, *Non-Recurring Revenue*, *Subscription modifications*, and *Non-" +"Recurring Invoices* for each of your salespeople. You can choose the period " +"you want to apply and the salesperson you want to analyze." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reporting/subscription_reports.rst-1 +msgid "Salesperson dashboard report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow.rst:5 +msgid "Sales flow" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:3 +msgid "Close a subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:5 +msgid "" +"Losing a customer is always difficult, especially if you put a lot of effort" +" into getting them to sign up for your products/services. However, many " +"companies come up with dubious methods to reduce the probability of this " +"happening." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:14 +msgid "" +"If you adopt such methods, you are among companies that actively and " +"indirectly spread the phobia of subscriptions, who do not think about how " +"negatively dissatisfied customers could impact their business and, who " +"frustrate the customers in a way or another. However, at some point, it is " +"understandable that you do not want your customers to be involved in your " +"subscription status." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:19 +msgid "" +"If you do not adopt such methods, you are among companies that continue to " +"evolve in a long-term subscription business model, especially in an era of " +"ultra-fast communications between dissatisfied customers, and who retain " +"their customers by making it easier for them to leave if they want to. By " +"giving them the opportunity to close their own subscriptions, your customers" +" do not feel trapped because they subscribed to your products/services." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:25 +msgid "" +"In summary, the **Odoo Subscriptions** application gives you the " +"**possibility to choose what you want to apply**. Indeed, you can decide " +"whether to give your customers the option to close their subscriptions " +"whenever they want to or to restrict this possibility. It depends on you and" +" we will show you how to do that in our amazing application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:33 +msgid "" +"Go to :menuselection:`Subscriptions --> Configuration --> Subscription " +"templates`. From there, you can create a new *Subscription template* or " +"modify an existing one. When editing your template, underneath the Invoicing" +" tab, you have the possibility to activate the option *Closable by " +"customer*. Once enabled, this option gives your customers the right to close" +" their own subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst-1 +msgid "Configuration to close your subscription with Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:43 +msgid "" +"Be sure to check out our documentation on how to :doc:`Use subscription " +"templates <../../subscriptions/configuration/subscription_templates>` to " +"fully understand the importance of this feature in a basic flow using the " +"**Odoo Subscriptions** application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:49 +msgid "Close your first subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:52 +msgid "Administrator view" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:54 +msgid "" +"Once confirmed, a quotation becomes a sales order and a new subscription is " +"automatically created. Therefore, this subscription has the status *In " +"progress*. From there, you have the possibility to close the subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst-1 +msgid "" +"Close your subscription from an administration point of view with Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:62 +msgid "" +"By using the smart button *Close*, you have to enter a close reason. For " +"example, \"Subscription too expensive\", \"Subscription does not meet my " +"requirements\", \"Subscription reached its end date\", etc. Immediately " +"after confirming your close reason, you can observe that the status of the " +"subscription is now *Closed* and that the close reason is mentioned on the " +"subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst-1 +msgid "What happens when you close your subscription with Odoo Subscriptions?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:72 +msgid "Customer view" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:74 +msgid "" +"As previously explained in the *Administrator view* part, from the " +"subscription form, you also have the possibility to visualize what your " +"customers see when managing their subscriptions thanks to the *Customer " +"preview* button. In this example, the customer has the choice to close " +"his/her subscription whenever he/she wants to, due to the *Close " +"Subscription* button." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst-1 +msgid "" +"Close your subscription from a customer point of view with Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:83 +msgid "" +"By using this button, the customer can specify the reason for cancelling " +"his/her subscription and he/she can even leave a message." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst-1 +msgid "" +"What happens when customers close their subscription with Odoo " +"Subscriptions?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:90 +msgid "" +"By confirming the cancellation, the customer is redirected to his/her " +"portal. The administrator is informed of this modification. Indeed, the " +"status of the subscription becomes *Closed* and a note appears in the " +"chatter with the new stage, the end date, the close reason, and the closing " +"text added by the customer." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst-1 +msgid "" +"What happens when customers close their subscription in Odoo Subscriptions?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/closing.rst:100 +msgid "" +"Before closing a subscription, check out our documentation on how to " +":doc:`Create a quotation using subscription products " +"<../../subscriptions/sales_flow/create_a_quotation>` to understand how " +"subscriptions are managed in the **Odoo Subscriptions** application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:3 +msgid "Create a quotation using subscription products" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:5 +msgid "" +"Selling a digital product or service gives instant gratification. However, " +"you have to work hard for a new customer to make a purchase. It costs time " +"and money. By convincing customers to sign up for a subscription, you " +"maximize your income and streamline your cash flow. You can sell any type of" +" product or service through a subscription business model." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:15 +msgid "" +"Here is a scenario using **Odoo Subscriptions** to create a quotation " +"including subscription products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:19 +msgid "Create your first quotation" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:21 +msgid "" +"Before creating your first quotation, be sure to check out our documentation" +" on how to create and manage your own :doc:`Subscription templates " +"<../../subscriptions/configuration/subscription_templates>` and on how to " +"add :doc:`Subscription products " +"<../../subscriptions/configuration/subscription_products>` to your " +"templates." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:30 +msgid "" +"These steps are **mandatory** to make a basic sales flow using **Odoo " +"Subscriptions**." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:32 +msgid "" +"Go to **Odoo Sales** and create a new quotation. Then, choose a customer and" +" add a product. Be careful to select a product that you previously " +"configured as a *Subscription product*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst-1 +msgid "View of a quotation form in Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:39 +msgid "" +"When your quotation is ready, you have the possibility to send it to your " +"customers or to confirm it. It is better to first *Send by email* the " +"quotation to your customers to have their confirmation and, then, *Confirm* " +"it in **Odoo Sales**. By clicking on *Customer preview*, you have an idea of" +" what your customers will see when receiving your quotation." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst-1 +msgid "Customer preview of a quotation form in Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:48 +msgid "" +"From there, your customers have three choices: *Sign & Pay* the quotation, " +"give you a *Feedback* or *Reject* the quotation. It appears that they are " +"very happy and accept the option *Sign & Pay*. Then, they have to validate " +"the order with a signature and by choosing a payment method. When it is " +"done, you can check out the quotation in **Odoo Sales** and *Confirm* it." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:54 +msgid "Manage your subscriptions from your SO" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:56 +msgid "" +"Once confirmed, the quotation becomes a sales order and a new button " +"appears, *Subscriptions*. Indeed, a subscription is automatically created." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst-1 +msgid "Quotation form in Odoo Sales with a button \"Subscriptions\"" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:63 +msgid "" +"By clicking on the *Subscriptions* button, you can see that the status of " +"the subscription is *In progress*. From there, you will have three options: " +":doc:`Renew <../../subscriptions/sales_flow/renewals>`, :doc:`Close " +"<../../subscriptions/sales_flow/closing>` or :doc:`Upsell " +"<../../subscriptions/sales_flow/upselling>` your subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst-1 +msgid "Use of the intelligent button \"Subscriptions\" in Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:73 +msgid "" +"In the top-right corner, you can see the status of the subscription. When a " +"subscription is new and created from **Odoo Subscriptions**, the status is " +"*Draft*. When a sales order has been validated, the status is *In progress*." +" Finally, when a customer decides to close his subscription, the status " +"becomes *Closed*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:81 +msgid ":doc:`../../subscriptions/sales_flow/renewals`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:82 +msgid ":doc:`../../subscriptions/sales_flow/closing`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/create_a_quotation.rst:83 +msgid ":doc:`../../subscriptions/sales_flow/upselling`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:3 +msgid "Renew a subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:5 +msgid "" +"The key feature of a subscription business model is the recurring nature of " +"payments. In this model, customers pay a recurring amount in exchange for " +"access to a product or a service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:14 +msgid "" +"Each subscriber experiences this renewal process monthly, annually, or " +"sometimes more, depending on the duration of the contract. Most subscription" +" companies choose to automate their renewal processes but, in some cases, " +"manual subscription renewals are still the preferred option." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:18 +msgid "" +"With **Odoo Subscriptions**, you can have all your subscriptions in one " +"application, suggest an automatic subscription renewal to your customers (as" +" well as a manual one) and, finally, filter all your subscriptions and " +"easily find those to renew (with the help of the tag *To renew*)." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:23 +msgid "Renew your first subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:25 +msgid "" +"Before renewing a subscription, be sure to check out our documentation on " +"how to :doc:`Create a quotation " +"<../../subscriptions/sales_flow/create_a_quotation>` using subscription " +"products. Indeed, once confirmed, a quotation becomes a sales order and a " +"new subscription is automatically created. Therefore, this subscription has " +"the status *In progress*. From there, you have the possibility to renew the " +"subscription. In the Other Info tab, underneath the To Renew section, you " +"can activate the *To renew* option. When activated, a yellow tag " +"automatically appears in the upper right corner of the subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst-1 +msgid "Renew your subscription with Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:38 +msgid "" +"The *To renew* tag is automatically ticked when a payment fails. This " +"indicator also appears on the customer portal. To visualize that, you just " +"have to click on the *Customer preview* button. The tag *To renew* appears " +"on the top right corner." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:0 +msgid "Customer preview of a renewal with Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:46 +msgid "" +"When a subscription needs to be renewed, you have the possibility to use a " +"new button called *Renewal quotation*. By clicking on it, a new quotation is" +" created. From there, start a basic sales flow allowing you to send the " +"quotation by email to your customers or to confirm it. It is better to first" +" *Send by email* the quotation to your customers in order to have their " +"confirmation and, then, *Confirm* it in **Odoo Sales**." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:53 +msgid "" +"In the Chatter of this new quotation, it is mentioned that \"This renewal " +"order has been created from the previous subscription\". Once confirmed by " +"your customers, this quotation becomes a sales order and a new sale is " +"mentioned in the upper right corner of the subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:0 +msgid "Renew a quotation with Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:61 +msgid "" +"By clicking on the *Sales* button, you have a summary of your sales orders " +"in a list view. The only difference between your two quotations is the " +"description underneath the *Subscription Management* category. There, you " +"can easily visualize which one is your renewal." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:0 +msgid "Renewal as Subscription Management form in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:70 +msgid "Visualize your subscriptions to renew" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst:72 +msgid "" +"Finally, if you want to visualize all your subscriptions and easily find " +"those to renew, you can go to your *Subscriptions dashboard* and use the " +"filter *To renew*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/renewals.rst-1 +msgid "" +"List view of all subscriptions and use of the filter to renew in Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:3 +msgid "Upsell a subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:5 +msgid "" +"Subscriptions are recurrent and go on indefinitely. As time passes by, our " +"customers may want to modify them. We must then be able to adapt the prices " +"or change the products’ quantities to accommodate their needs. Two " +"situations can happen:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:9 +msgid "" +"**Loyal customers:** This kind of customers already trust you as a brand. " +"Therefore, you are confident regarding what you offer since they keep paying" +" for your products and services. Consequently, it is easier to sell them " +"something additional than it would be to a new customer." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:14 +msgid "" +"**New customers:** For this kind of customers, you have to come with " +"something new, something attractive. What about discounts? Typically, every " +"subscription ends after a certain given time. Making these types of offers " +"for new customers strengthens your relationships with them and also " +"increases their retention." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:27 +msgid "" +"As previously explained, to upsell a subscription to new customers, it is " +"recommended to offer *Discounts*. To activate this option, go to " +":menuselection:`Sales --> Configuration --> Settings` and, under the " +"*Pricing* category, you have the possibility to grant discounts on sales " +"order lines." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst-1 +msgid "Activation of the discount option in Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:36 +msgid "Upsell your first subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:38 +msgid "" +"Before upselling a subscription, be sure to check out our documentation on " +"how to :doc:`Create a quotation " +"<../../subscriptions/sales_flow/create_a_quotation>` using subscription " +"products. Indeed, once confirmed, a quotation becomes a sales order and a " +"new subscription is automatically created. Therefore, this subscription has " +"the status *In progress*. From there, you have the possibility to upsell " +"your subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst-1 +msgid "Upsell your subscription with Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:48 +msgid "" +"By using the smart button *Upsell*, you are able to create a new quotation " +"with new subscription products and send it to your customers for approval." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst-1 +msgid "" +"Add products to your subscription via the upsell option in Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:56 +msgid "" +"When the quotation is confirmed by your customers, the products are added to" +" the initial subscription. Quotation prices are, then, prorated to the " +"remaining time of the current invoicing period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:60 +msgid "" +"Of course, before sending this new quotation to your customers, you can " +"change the unit price, taxes, and, even the discount you want to offer. The " +"smart button *Customer preview* is useful for mimicking the customer's " +"reaction. In this case, we can confidently say that the customer will *Sign " +"and pay* this new quotation. When it is done, you have to go back in edit " +"mode, confirm the quotation, and click on the smart button *Subscriptions* " +"to visualize all updates. From there, you can see that an additional line " +"has been added to the subscription with the new extra service the customer " +"wanted to purchase." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst-1 +msgid "Visualize all your subscriptions updates with Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:72 +msgid "" +"In addition, by clicking on the *Sales* button, you have a summary of your " +"sales orders in a list view." +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst-1 +msgid "List view of all sales orders created for a subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/sales_flow/upselling.rst:79 +msgid "" +"The only difference between your two sales orders is the description " +"underneath the *Subscription Management* category. There, you can easily " +"visualize which one is your upselling." +msgstr "" diff --git a/locale/pl/LC_MESSAGES/services.po b/locale/pl/LC_MESSAGES/services.po new file mode 100644 index 000000000..c4843fe8e --- /dev/null +++ b/locale/pl/LC_MESSAGES/services.po @@ -0,0 +1,1700 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"PO-Revision-Date: 2021-11-02 08:49+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications/services.rst:5 +msgid "Services" +msgstr "" + +#: ../../content/applications/services/field_service.rst:8 +msgid "Field Service" +msgstr "" + +#: ../../content/applications/services/field_service.rst:11 +msgid "" +"`Odoo Tutorials: Field Service `_" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:3 +msgid "User default warehouse" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:5 +msgid "" +"Setting up a **default warehouse** can be useful for field technicians who " +"keep a supply in their van or those who always resupply from the same " +"warehouse. It also allows field workers to switch between warehouses from " +"their profiles." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:9 +msgid "" +"Products in sales orders created during field interventions are always " +"pulled from the default warehouse, keeping the inventory accurate." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:13 +msgid ":doc:`../../inventory_and_mrp/inventory`" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:16 +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:13 +msgid "Configuration" +msgstr "Konfiguracja" + +#: ../../content/applications/services/field_service/default_warehouse.rst:18 +msgid "" +"To set up a user default warehouse, the :doc:`storage locations " +"<../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations>`" +" feature needs to be activated in the **Inventory** app. It is also " +"necessary to have more than one warehouse in your database." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:23 +msgid "" +"You can either set it up :ref:`for your profile `, or :ref:`for all users `." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:27 +msgid "" +":doc:`../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations`" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:32 +msgid "For your profile" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:34 +msgid "" +"To set up a default warehouse for yourself, click your **profile icon** in " +"the upper right corner of the screen, then, go to :menuselection:`My Profile" +" --> Preferences --> Default Warehouse`. Select the default warehouse from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:41 +msgid "For all users" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:43 +msgid "" +"To set up a default warehouse for a specific user, go to " +":menuselection:`Settings --> Users --> Manage users`, select a user, then go" +" to the :guilabel:`Preferences` tab. Scroll down to :guilabel:`Inventory`, " +"and select the default warehouse from the drop-down menu." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst-1 +msgid "Selection of a default warehouse on a user profile." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:51 +msgid "Use in field service tasks" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:53 +msgid "" +"Once a default warehouse has been configured for a user, the materials used " +"for a sales order related to a Field Service task are pulled from that " +"specific warehouse. Open the related sales order, go to the :guilabel:`Other" +" Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse " +"is applied correctly." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:58 +msgid "" +"Once the Field Service task is marked as done, the stock of the default " +"warehouse is automatically updated." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:3 +msgid "Onsite interventions planning" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:6 +msgid "From a sales order" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:8 +msgid "" +"Allowing your sales team to open onsite interventions creates a seamless " +"experience for your customers. They can receive a quotation they first have " +"to approve before the work even starts." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:11 +msgid "" +"Go to :menuselection:`Field Service --> Configuration --> Products` and " +"create or edit a product." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:13 +msgid "" +"Under the :guilabel:`General Information` tab, select :guilabel:`Service` as" +" :guilabel:`Product Type`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:15 +msgid "" +"Under the :guilabel:`Sales` tab, select :guilabel:`Timesheets on tasks` as " +":guilabel:`Service Invoicing Policy`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:17 +msgid "" +"Select :guilabel:`Create a task in an existing project` as " +":guilabel:`Service Tracking`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:18 +msgid "Select your :guilabel:`Project`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:19 +msgid "If you use them, select your :guilabel:`Worksheet Template`, and save." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "" +"Product configuration to create tasks from sales orders in Odoo Field " +"Service" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:25 +msgid "" +"From the :doc:`Sales <../../sales/sales>` app, create a quotation with the " +"product and confirm it. A task is automatically set up under your Field " +"Service project. It is directly accessible from the sales order." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "Field Service task on a sales order in Odoo Sales" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:34 +msgid "From helpdesk tickets" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:36 +msgid "" +"The integration with the :doc:`Helpdesk <../helpdesk>` app lets your " +"helpdesk team manage intervention requests directly. Planning field service " +"tasks from tickets speeds up your processes." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:40 +msgid "Configure the helpdesk team" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:42 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select" +" a team and enable :guilabel:`Onsite Interventions`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "Onsite interventions settings in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:49 +msgid "" +"The helpdesk tickets of the team now display the :guilabel:`Plan " +"Intervention` button. Click on it to create a new task under your field " +"service project." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:8 +msgid "Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:11 +msgid "`Odoo Tutorials: Helpdesk `_" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:3 +msgid "After Sales Features" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:5 +msgid "" +"As your business grows, having the right tool to support your helpdesk team " +"on recording, tracking and managing issues raised easy and efficiently, is " +"key. Odoo’s Helpdesk application allows you to generate credit notes, manage" +" returns, products, repairs, grant coupons, and even plan onsite " +"interventions from a ticket’s page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:11 +msgid "Set up the after sales services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:13 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and " +"enable the after sales options: *Refunds, Returns, Coupons, Repairs and " +"Onsite Interventions*." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:20 +msgid "Generate credit notes from tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:22 +msgid "" +"You can use a credit note to refund a customer or adjust the amount due. For" +" that, simply go to your ticket page, click on *Refund* and select the " +"corresponding *Invoice*. Clicking on *Reverse* generates a credit note, and " +"you can *Post* it while still being in the *Helpdesk* app." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:30 +msgid "Allow product returns from tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:32 +msgid "" +"The process of a product return from your customer back to your warehouse is" +" taken into action when, at the ticket page, you choose the option *Return*." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:39 +msgid "Grant coupons from tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:41 +msgid "" +"First, be sure to have your *Coupon Program* planned in the *Sales* or " +"*Website* application. Then, in *Helpdesk*, open your ticket, click on " +"*Coupon*, and choose the respective one." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:48 +msgid "Repairs from tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:50 +msgid "" +"Clicking on *Repair* option, on your ticket page, a new repair order form is" +" shown. Fill in the information as needed and choose the next step." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:57 +msgid "Plan onsite interventions from tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:59 +msgid "" +"At the ticket's page click on *Plan Intervention*, and set up your onsite " +"intervention exactly the same way as if you were on the *Field Service* " +"application." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:67 +msgid "" +"`Coupons `_" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3 +msgid "Allow customers to close their tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5 +msgid "" +"Allowing customers to close their own tickets gives them autonomy and " +"minimizes misunderstandings around when an issue is considered solved or " +"not. This results in operational capacity for support teams, and higher " +"satisfaction for the customer." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:10 +msgid "Enable ticket closing" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12 +msgid "" +"Start by navigating to :menuselection:`Helpdesk --> Configuration --> " +"Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit`" +" and enable :guilabel:`Ticket closing` by checking the field box." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1 +msgid "Ticket closing feature in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19 +msgid "" +"To designate which stage the ticket migrates to once it is closed, navigate " +"to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` " +"and clicking :guilabel:`Tickets` on the team's card." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:23 +msgid "" +"There are two options: create a new Kanban stage or work with an existing " +"one. For both scenarios, click the :guilabel:`Settings (gear)` icon next to " +"the stage name, select :guilabel:`Edit Stage`, and enable :guilabel:`Closing" +" Stage`. After checking the field box, click :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:29 +msgid "" +"If a closing stage is not specified, by default, the ticket is moved to the " +"last stage in the kanban. If more than one stage is set as a closing stage, " +"the ticket is placed in the first closing stage column." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:33 +msgid "" +"With the ticket closing settings now complete, customers can now view the " +"option to :guilabel:`Close this ticket` when they log into their portal." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1 +msgid "Customer view of ticket closing in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:40 +msgid "Get reports on tickets closed by customers" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:42 +msgid "" +"To analyze the tickets that have been closed by customers, go to " +":menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the " +":guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set" +" the custom filter parameters to :guilabel:`Closed by partner` and " +":guilabel:`is true`. Finally, click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1 +msgid "" +"Filter for tickets closed by customers on Odoo Helpdesk's reporting page." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview.rst:5 +#: ../../content/applications/services/timesheets/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:3 +msgid "Forum and eLearning" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:6 +msgid "Forum" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:8 +msgid "" +"To go above and beyond email, live chat, web forms, and phone lines, offer " +"your customers a support forum. This way, customers might become more " +"attached to your company as they would be investing time to get into details" +" of your business. You also encourage the exchange of experiences and " +"knowledge, supporting the feeling of belonging to a community (your " +"community!)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:14 +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:52 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:10 +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:11 +msgid "Set up" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:16 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and " +"enable *Help Center*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1 +msgid "" +"Overview of the settings page of a helpdesk team emphasizing the help center feature in\n" +"Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:23 +msgid "" +"Create, or edit a forum by clicking on the external link. Among the editing " +"options, choose if you would like the *Forum Mode* to be *Questions*: only " +"one answer is allowed per question or *Discussions*: multiple answers are " +"allowed per question." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1 +msgid "Overview of a forum’s settings page in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:31 +msgid "" +"From now on, logged in users can start their discussions. To keep track of " +"posts, go to :menuselection:`Website --> Forum --> Posts`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1 +msgid "" +"Overview of the Forums page of a website to show the available ones in Odoo " +"Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:38 +msgid "" +"Turn tickets into forum posts by simply clicking on *Share on the Forum* on " +"the ticket's page." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:45 +msgid "eLearning" +msgstr "e-learning" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:47 +msgid "" +"In addition to a forum, offer online courses. When doing so, you link your " +"customers and users’ needs and questions to useful content, helping to boost" +" efficiency as they can also find their answers there." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:54 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and " +"enable *eLearning*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1 +msgid "" +"Overview of the settings page of a customer care team emphasizing the feature elearning in\n" +"Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:61 +msgid "" +"Once the structure and content of your course are ready, *Publish* it by " +"clicking on *Unpublished*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1 +msgid "View of a course being published for Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:67 +msgid "" +"To keep track of your course statistics, go to *eLearning* and *View " +"Course*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst-1 +msgid "View of the elearning applications dashboard for Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73 +msgid "Todo" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73 +msgid "" +"DETAILS/INFO SHOULD COME FROM ELEARNING DOCS. THEREFORE, LINK DOCS ONCE " +"AVAILABLE!" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:3 +msgid "Getting Started" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:5 +msgid "" +"Helpdesk teams provide your customers with support to queries or errors they" +" might encounter while using your product/service. Therefore, a successful " +"scheme where you can organize multiple teams with their customized pipeline," +" visibilities settings, and ticket traceability is essential." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:10 +msgid "Set up teams" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:12 +msgid "" +"To modify or create teams, go to :menuselection:`Helpdesk --> Configuration " +"--> Helpdesk Teams`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:14 +msgid "" +"Setting up multiple teams allows you to group tickets by your channels " +"(example: BE/US), or by your support services' types (example: IT, " +"accounting, admin, etc.)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "View of the helpdesk teams page in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:21 +msgid "Team’s productivity and visibility" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:23 +msgid "" +"Teams can have individual *Assignment Methods* to ensure that tickets get " +"redirected to the right person:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:26 +msgid "" +"*Manually*: tickets are manually assigned, allowing employees to manage " +"their own workload and target tickets they are experts at;" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:28 +msgid "" +"*Random*: tickets are randomly assigned and everyone gets the same amount. " +"This method ensures that all tickets are handled as the assignment happens " +"automatically;" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:30 +msgid "" +"*Balanced*: tickets are assigned to the person with the least amount of " +"tickets so that everyone fairly gets the same amount. Thereby, you ensure " +"that all tickets get to be taken care of." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "" +"View of a helpdesk team settings page emphasizing the productivity and visibility features\n" +"in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:40 +msgid "" +"For the *Random* and *Balanced* assignment methods, you can set the *Team " +"Members* among whom tickets are assigned. Leave the field empty to include " +"all employees (with the proper access rights)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:43 +msgid "" +"The *Team Visibility* feature allows you to specify who can see and access " +"the team’s tickets. Therefore, ticket’s with sensible information are only " +"seen by the right people. Leave the field empty to include all employees " +"(with the proper access rights)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:46 +msgid "Set up stages and share it among teams" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:48 +msgid "" +"To set up stages, go to :menuselection:`Helpdesk --> Configuration --> " +"Stages`. Then, create and/or edit stages as you need and set specific teams " +"to use certain stages under *Team*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "" +"View of a stage’s setting page emphasizing the option to add teams in Odoo " +"Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:55 +msgid "" +"Stages can be shared between one or multiple teams, allowing you to adapt " +"the pipeline to your individual needs. They also apply a visibility and " +"access rule, as other teams are not able to see or use the stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "View of a team’s kanban view in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:64 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:3 +msgid "Ratings" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:5 +msgid "" +"Allow customers to rate their experience with your helpdesk teams to " +"strengthen your credibility and gain their trust. Reviews can also influence" +" a customer’s decision and open space for feedback that can help you improve" +" the quality of your services." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:12 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and " +"enable *Ratings on tickets*. The feature automatically adds a default email " +"template on the non-folded *closing stage(s)* of that team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "" +"Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature\n" +"in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:21 +msgid "" +"To edit the email template and the stage(s) set as the closing ones, go to " +"the Kanban view of your helpdesk team and click on *Settings*, then on *Edit" +" Stage*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "" +"Overview of a helpdesk team kanban view emphasizing the menu edit stage in " +"Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:28 +msgid "" +"Now, once a ticket reaches the stage(s) designated as the *Closing Stage*, " +"an email is sent to the customer." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "" +"View of a standard helpdesk customer review email template for Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:35 +msgid "" +"Ratings can be seen on the chatter of each ticket, under the *See Customer " +"Satisfaction* link on the main dashboard, and through *Reporting*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:39 +msgid "Ratings visible on the customer portal" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:41 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and " +"enable *Display Rating on Customer Portal*. Now, by clicking on the helpdesk" +" team’s name on their ticket, customers can see its ratings." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "" +"View of the helpdesk ticket from a user’s portal emphasizing the link to the helpdesk team\n" +"in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:51 +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:88 +#: ../../content/applications/services/helpdesk/overview/sla.rst:47 +msgid ":doc:`../advanced/close_tickets`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:3 +msgid "Start Receiving Tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:5 +msgid "" +"Offering a variety of channels from where your customers can contact you " +"grants them flexibility and the right to choose the best one for themselves." +" And, in order to make sure inquiries across all channels get addressed, it " +"is essential to have a solution where all interactions come in one place." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:11 +msgid "Channels options to submit tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:13 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, and " +"enable the following features as you want them to be available to your " +"users." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of a helpdesk teams setting page emphasizing the channels options in " +"Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:21 +msgid "Email Alias" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:24 +msgid "" +"Let your customers submit tickets by sending an email to your support email " +"address. The subject line of the email becomes the title of the ticket and " +"the content is shown in the Chatter." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:26 +msgid "" +"Select *Configure domain name* to be redirected to *Settings* and, from " +"there, enable *External Email Servers* to determine or change your *Alias " +"Domain*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of the settings page of a helpdesk team emphasizing the email alias feature\n" +"in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:35 +msgid "" +"Using your own email server is required to send and receive emails in Odoo " +"Community and Enterprise. Online users benefit from a ready-to-use email " +"server." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:39 +msgid "Website Form" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:41 +msgid "" +"Allow your customers to submit a ticket by filling in a form through your " +"website." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:42 +msgid "" +"Once the feature is activated, get redirected to your website by clicking on" +" *Go to Website*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of the settings page of a helpdesk team emphasizing the Go to Website button in\n" +"Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:49 +msgid "" +"From the website page customize the form as you like. Then, publish it by " +"clicking on *Unpublished*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "View of the website form to submit a ticket for Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:56 +msgid "Live Chat" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:59 +msgid "" +"Through live interactions with your website visitors, helpdesk tickets can " +"be instantly created and redirected to the right person." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:61 +msgid "" +"Click on your helpdesk team's name - for the example below: *Customer Care* " +"- and :doc:`set up your channel `." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of the settings page of a helpdesk team emphasizing the live chat features and links\n" +"in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:68 +msgid "" +"Now, your operators can create tickets by using the :doc:`command " +"` */helpdesk " +"(subject_of_ticket)*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:72 +msgid "Prioritize tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:74 +msgid "" +"Use the stars to prioritize your tickets. The most urgent ones appear at the" +" top of your list on the Kanban view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:77 +msgid "1 star = *Low priority*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:78 +msgid "2 stars = *High priority*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:79 +msgid "3 stars = *Urgent*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of a team’s kanban view and the prioritized tasks in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:87 +#: ../../content/applications/services/helpdesk/overview/reports.rst:60 +msgid ":doc:`sla`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:89 +msgid ":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:3 +msgid "Reports for a Better Support" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:5 +msgid "" +"An efficient customer service solution should have a built-in reporting " +"option. Reports allow you to track trends, identify areas for improvement, " +"manage employees’ workloads and, most importantly, meet your customer’s " +"expectations." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:10 +msgid "Cases" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:12 +msgid "Some examples of the reports Odoo Helpdesk can generate include:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:14 +msgid "The number of tickets *grouped by* team and ticket type." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:17 +msgid "" +"In this manner, you are able to evaluate which ticket types have been the " +"most frequent ones, plus the workload of your teams." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:19 +msgid "" +"Apply *Time Ranges* if you would like to make comparisons to a *Previous " +"Period* or a *Previous Year*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "" +"View of a helpdesk ticket analysis by team and ticket type in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:25 +msgid "The number of tickets closed per day, per team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:27 +msgid "" +"Get an overview of how many requests each team is closing per day in order " +"to measure their performance. Identify productivity levels to understand how" +" many requests they are able to handle." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "" +"View of a helpdesk ticket analysis by team and close date in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:35 +msgid "" +"Filter it by *Assignee* to see Key Performance Indicators (KPI) per agent." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:37 +msgid "" +"The number of hours tickets are taking to be solved, grouped by team and " +"ticket type." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:39 +msgid "" +"Check if your expectations are met by *measuring* the *Time to close " +"(hours)*. Your customers not only expect fast responses but they also want " +"their issues to be handled quickly." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "" +"View of helpdesk ticket analysis of the hours to close by ticket type and team in\n" +"Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:48 +msgid "Save filters" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:50 +msgid "" +"Save the filters you use the most and avoid having to reconstruct them every" +" time they are needed. To do so, set the groups, filters, and measures " +"needed. Then, go to *Favorites*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "" +"View of helpdesk ticket analysis emphasizing the option to add a filter as a favorite one\n" +"in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:59 +msgid ":doc:`receiving_tickets`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:3 +msgid "Service Level Agreements (SLA)" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:5 +msgid "" +"Service Level Agreements (SLA) are commitments you make with your customers " +"to outline how a service is delivered. It bolsters trust between you and " +"your customers as it makes clear what needs to be done, to what standard, " +"and when." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:10 +msgid "Create your policies" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:13 +msgid "" +"First, enable the feature on the settings of the team you would like " +"policies to be applied, going to :menuselection:`Helpdesk --> Configuration " +"--> Helpdesk Teams`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:15 +msgid "" +"Create your policies through the team’s settings page or go to " +":menuselection:`Helpdesk --> Configuration --> SLA Policies`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of an SLA form in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:23 +msgid "" +"Choose to which **Team** the policy is relevant and the **Minimum Priority**" +" a ticket needs to have for the policy to be applied." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:27 +msgid "" +"**Target** is the stage a ticket needs to reach within the period defined to" +" satisfy the SLA. The period is based on the ticket’s creation date, and a " +"deadline is set on the ticket’s form once it matches an SLA policy rule. If " +"a ticket has more than one policy applied to it, the closest deadline of all" +" SLAs is the one considered." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:29 +msgid "" +"When a ticket has satisfied an SLA policy, the SLA tag appears in green and " +"the deadline field is not shown anymore." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:37 +msgid "SLA Analysis" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:39 +msgid "" +"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply" +" *Filters* and *Group by* to identify tickets that should be prioritized and" +" keep track of upcoming deadlines." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "" +"View of the SLA status analysis page emphasizing the group by option in Odoo" +" Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5 +msgid "Timesheet and Invoice" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:3 +msgid "Invoice Time Spent on Tickets (Prepaid Support Services)" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:5 +msgid "" +"Have the option to work with prepaid support services, meaning that a sales " +"order and a corresponding invoice are issued and, once the service is done, " +"you can deduct the time spent. Odoo allows it to happen because the " +"applications are fully integrated, resulting in faster responses to your " +"customer needs." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:14 +msgid "Step 1: Set up a helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:17 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, create" +" or edit an existing team, and enable *Timesheet on Ticket* and *Time " +"Reinvoicing*." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:20 +msgid "" +"Select or create a project under *Timesheet on Ticket*. The selected/created" +" is the one at which employees timesheet on by default. However, it can be " +"ultimately modified on each ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst-1 +msgid "" +"View of a helpdesk team settings page emphasizing the timesheet on ticket and time\n" +"reinvoicing features in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:28 +msgid "Step 2: Set up a service" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:31 +msgid "" +"Go to :menuselection:`Sales --> Configuration --> Settings` and enable " +"*Units of Measure* to optionally be able to choose *hours* (for example) as " +"the unit of measure of your service." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:33 +msgid "" +"Then, go to :menuselection:`Sales --> Products --> Products`, create or edit" +" an existing one, and set its *Product Type* as *Service*." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst-1 +msgid "" +"View of a product's form emphasizing the product type and unit of measure fields in Odoo\n" +"Sales" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:40 +msgid "" +"Now, select the invoicing management you would like to have under the " +"*Sales* tab. We recommend the following configuration:" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst-1 +msgid "" +"View of a product form and the invoicing options under the tab sales in Odoo" +" Sales" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:47 +msgid "" +"This configuration ensures that the customer is invoiced by the number of " +"hours predicted in the sales order, meaning that less or extra hours " +"recorded are not taken into account. It also ensures that every time a sales" +" order is confirmed, a new task is created under the right project, " +"automating the process." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:53 +msgid "" +"We recommend setting up a specific project, as it was done for this flow " +"example. The important thing to remember is that the sales order item needs " +"to be set on the corresponding project or task, in order to reinvoice the " +"time spent on a ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:58 +msgid "Prevision an invoice and record time" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:61 +msgid "Step 1: Place an order" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:63 +msgid "" +"Go to :menuselection:`Sales --> Orders --> Orders` and create one for the " +"helpdesk service product you have previously set up, with the customer who " +"needs the ticket to be opened. Set the number of hours needed to assist the " +"customer and *Confirm* the order." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst-1 +msgid "View of a sales order emphasizing the order lines in Odoo Sales" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:72 +msgid "Step 2: Invoice the customer" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:74 +msgid "In *Sales*, select the respective sales order to *Create Invoice*." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst-1 +msgid "" +"View of a sales order emphasizing the create invoice button in Odoo Sales" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:82 +msgid "Step 3: Link the task to the ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:84 +msgid "" +"Now, in *Helpdesk*, create or edit the respective ticket and link it to the " +"task created by the confirmation of the sales order." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst-1 +msgid "View of a helpdesk ticket emphasizing the field task in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:92 +msgid "Step 4: Record the time spent" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:94 +msgid "" +"Still on the respective helpdesk ticket, record the hours performed under " +"the *Timesheets* tab." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst-1 +msgid "" +"View of a helpdesk ticket emphasizing the timesheets tab in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:100 +msgid "" +"Note that the hours recorded on the ticket form are shown on the *Delivered*" +" column in the sales order." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst-1 +msgid "View of a sales order emphasizing the delivered column in Odoo Sales" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:108 +msgid "" +"Hours recorded on the ticket are automatically shown in *Timesheets* and on " +"the dedicated task." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:111 +msgid ":doc:`reinvoice_from_project`" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:112 +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:104 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:3 +msgid "Invoice Time Spent on Tickets (Postpaid Support Services)" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:5 +msgid "" +"The :guilabel:`Timesheets` integration provides more control and " +"transparency over how clients are charged, and what they're specifically " +"billed for." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:8 +msgid "" +"In Odoo, the Helpdesk agent can use the ticket to record timesheets. Once a " +"ticket is solved, the client can be billed for the time spent on the ticket." +" Odoo will pull from the ticket's timesheet to accurately bill the client." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15 +msgid "" +"To turn on the :guilabel:`Timesheets` feature, go to " +":menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, select a " +"Helpdesk team, and then, click :guilabel:`Edit`. Next, enable the options " +":guilabel:`Timesheets` and :guilabel:`Time Billing`. Then, click " +":guilabel:`Save` to apply these changes to the Helpdesk team settings." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:20 +msgid "" +"Once the :guilabel:`Timesheets` feature is enabled, a :guilabel:`Project` " +"drop-down option will appear below :guilabel:`Timesheets`. The " +":guilabel:`Project` drop-down option will automatically be set to a project " +"that Odoo created for the Helpdesk team. The tickets' timesheets will be " +"stored in the selected project." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:26 +msgid "Create a sales order" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:28 +msgid "" +"After a ticket comes into the pipeline, go to :menuselection:`Sales --> " +"Create`. Then, add the customer from the ticket to the :guilabel:`Customer` " +"field in the new quotation. In the :guilabel:`Order Lines` tab, create or " +"select a product to charge the customer for the time spent on their Helpdesk" +" ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:33 +msgid "" +"If creating a new product from the sales order form, first give the product " +"a name by typing it in the :guilabel:`Product` column. Then, click " +":guilabel:`Create and edit`." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:36 +msgid "" +"First, in the :guilabel:`General Information` tab, set the " +":guilabel:`Product Type` to :guilabel:`Service` and the :guilabel:`Sales " +"Price` to the Helpdesk agent's service rate. Then, set the " +":guilabel:`Invoicing Policy` to :guilabel:`Based on Timesheets`. Finally, " +"click :guilabel:`Save` to create the new product and add it to the " +"quotation." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:41 +msgid "" +"Once the product is added, click :guilabel:`Confirm` to turn the quotation " +"into a sales order." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst-1 +msgid "Create a sales order and add a product." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:48 +msgid "Record a timesheet" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:50 +msgid "" +"To record a timesheet, jump back to the Helpdesk ticket by going to the " +":guilabel:`Helpdesk` dashboard, clicking :guilabel:`Tickets` on the team's " +"card, and locating the correct ticket. Then, click :guilabel:`Edit` and use " +"the :guilabel:`Timesheets` tab to record the time spent on the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst-1 +msgid "Record time spent on a ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:60 +msgid "" +"The ticket's timesheets can be recorded before or after the sales order is " +"made, the order doesn't matter." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:64 +msgid "Link the Helpdesk ticket to the SO" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:66 +msgid "" +"To link the :guilabel:`Sales Order` to the ticket, start on the ticket form " +"and click :guilabel:`Edit`. Next, select the :guilabel:`Sales Order` that " +"was created earlier from the :guilabel:`Sales Order Item` drop-down menu. " +"Odoo will automatically filter the options to only show sales orders that " +"are connected to the ticket's customer. Lastly, click :guilabel:`Save` to " +"connect the ticket and the :guilabel:`Sales Order Item`." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst-1 +msgid "Link the SO item to the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:77 +msgid "" +"The :guilabel:`Sales Order Item` can be connected to the ticket before or " +"after any timesheets are recorded, the order doesn't matter." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:81 +msgid "Modify billing rates" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:83 +msgid "" +"If a timesheet entry is recorded, but the agent does not want to bill the " +"client for that time, go to the :guilabel:`Timesheets` tab and toggle on the" +" visibility of the :guilabel:`Sales Order Item` column. When filling out the" +" information for the timesheet entry, make sure to leave the non-billable " +"timesheet entry's :guilabel:`Sales Order Item` field blank." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:88 +msgid "" +"If the agent wants to charge a different rate for a timesheet entry, first, " +"add a new product to the connected :abbr:`SO (Sales Order)` priced at the " +"new rate. Then, select the new product in the timesheet entry's " +":guilabel:`Sales Order Item` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:93 +msgid "Create the invoice" +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:95 +msgid "" +"When the Helpdesk ticket is completed and the client is ready to be billed " +"for time, begin by clicking the :guilabel:`Sales Order` smart button on the " +"ticket form to navigate to the sales order. The :guilabel:`Delivered` column" +" should match the number of hours recorded on the ticket's timesheet. After " +"checking and filling out the relevant information, click :guilabel:`Create " +"Invoice` to bill the client for the time spent on the ticket. Odoo will " +"automatically generate an invoice to send to the client and the Helpdesk " +"ticket can officially be closed." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:103 +msgid ":doc:`invoice_time`" +msgstr "" + +#: ../../content/applications/services/project.rst:8 +msgid "Project" +msgstr "" + +#: ../../content/applications/services/project.rst:10 +msgid "" +"Odoo Project is a tool to manage your ongoing projects. Schedule tasks, " +"assign activities to coworkers, and keep track of each project's " +"profitability." +msgstr "" + +#: ../../content/applications/services/project.rst:14 +#: ../../content/applications/services/timesheets.rst:11 +msgid "" +"`Odoo Tutorials: Project and Timesheets " +"`_" +msgstr "" + +#: ../../content/applications/services/project/tasks.rst:5 +msgid "Tasks" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:3 +msgid "Create Project's Tasks from an Email Alias" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:5 +msgid "" +"When you already have an email address that customers know from the top of " +"their heads, changing it is the last thing you want to do. Instead, link " +"that address to your project and transform those conversations into " +"structured work. It automatically creates a task in the first stage of a " +"project." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:11 +msgid "Set up an incoming email server" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:14 +msgid "" +"On the *Settings* application, enable *External Email Servers* and define " +"the incoming email alias you would like to use." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:15 +msgid "" +"**For more information**: " +":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:18 +msgid "Configure the email alias in your project" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:22 +msgid "" +"Now that you have the incoming email server set up, go to " +":menuselection:`Project --> Configuration --> Projects --> Edit`. Under the " +"*Emails* tab, define the wanted email alias and choose the policy to receive" +" a message." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:23 +msgid "In addition, you can now directly set it when creating a new project." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst-1 +msgid "" +"In the settings of your project, define the emails alias under the tab email" +" in Odoo Project" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:30 +msgid "" +"All the recipients of the email (To/Cc/Bcc) are automatically added as " +"followers of the task." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:32 +msgid "The email can be seen under the name of your project on the dashboard." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst-1 +msgid "View of the email alias chosen on the dashboard view in Odoo Project" +msgstr "" + +#: ../../content/applications/services/timesheets.rst:8 +msgid "Timesheets" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:3 +msgid "Create Timesheets upon Time Off Validation" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:5 +msgid "" +"Odoo automatically timesheets on project/tasks upon time off requests. This " +"allows for better overall control over the validation of timesheets, as it " +"does not leave place for forgetfulness and questions after hours that have " +"not been timesheeted by the employee." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:9 +msgid "" +"Activate the :ref:`developer mode `, go to *Timesheets*, and" +" change the *Project* and *Task* set by default, if you like." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "" +"View of Timesheets setting enabling the feature record time off in Odoo " +"Timesheets" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:16 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select" +" or create the needed type, and decide if you would like the requests to be " +"validated or not." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "" +"View of a time off types form emphasizing the time off requests and timesheets section in\n" +"Odoo Time Off" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:26 +msgid "" +"Now, once the employee has requested his time off and the request has been " +"validated (or not, depending on the setting chosen), the time is " +"automatically allocated on *Timesheets*, under the respective project and " +"task." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:27 +msgid "" +"On the example below, the user requested *Paid Time off* from July 13th to " +"15th." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "View of the time off request form in Odoo Time Off" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:33 +msgid "" +"Considering that validation is not required, the requested time off is " +"automatically displayed in *Timesheets*. If validation is necessary, the " +"time is automatically allocated after the responsible person for validating " +"does it so." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "" +"Video of timesheets emphasizing the requested time off from the employee in " +"Odoo Timesheets" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:41 +msgid "" +"Click on the magnifying glass, hovering over the concerned cell, to access " +"all the aggregated data on that cell (day), and see details regarding the " +"project/task." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "View of the details of a project/task in Odoo Timeheets" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:7 +msgid "What can I expect from the support service?" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:11 +msgid "5 days a week" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:13 +msgid "" +"Your Odoo Online subscription includes **unlimited 24hr support at no extra " +"cost, Monday to Friday**. Our teams are located around the world to ensure " +"you have support, no matter your location. Your support representative could" +" be communicating to you from San Francisco, Belgium, or India!" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:18 +msgid "" +"Our support team can be contacted through our `online support form " +"`__." +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:22 +msgid "What kind of support is included?" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:24 +msgid "" +"Providing you with relevant material (guidelines, product documentation, " +"etc...)" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:26 +msgid "" +"Answers to issues that you may encounter in your standard Odoo database (eg." +" “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:28 +msgid "Questions related to your account, subscription, or billing" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:29 +msgid "" +"Bug resolution (blocking issues or unexpected behaviour not due to " +"misconfiguration or customization)" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:31 +msgid "" +"Issues that might occur in a test database after upgrading to a newer " +"version" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:33 +msgid "" +"*Odoo Support does not make changes to your production database without your" +" agreement and gives you the material and knowledge to do it yourself!*" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:37 +msgid ":ref:`upgrade/sla`" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:38 +msgid ":doc:`/administration/maintain/supported_versions`" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:42 +msgid "What kind of support is not included?" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:44 +msgid "" +"Questions that require us to understand your business processes in order to " +"help you implement your database" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:46 +msgid "" +"Training on how to use our software (we will direct you to our many " +"resources)" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:47 +msgid "Import of documents into your database" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:48 +msgid "" +"Guidance on which configurations to apply inside of an application or the " +"database" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:49 +msgid "" +"How to set up configuration models (Examples include: Inventory Routes, " +"Payment Terms, Warehouses, etc)" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:51 +msgid "Any intervention on your own servers/deployments of Odoo" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:52 +msgid "" +"Any intervention on your own third party account (Ingenico, Authorize, UPS, " +"etc)" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:53 +msgid "" +"Questions or issues related to specific developments or customizations done " +"either by Odoo or a third party (this is specific only to your database or " +"involving code)" +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:57 +msgid "" +"You can get this type of support with a `Success Pack " +"`__. With a pack, one of our consultants" +" will analyze the way your business runs and tell you how you can get the " +"most out of your Odoo Database. We will handle all configurations and coach " +"you on how to use Odoo." +msgstr "" + +#: ../../content/services/support/what_can_i_expect.rst:63 +msgid ":doc:`/administration/upgrade`" +msgstr "" diff --git a/locale/pl/LC_MESSAGES/settings.po b/locale/pl/LC_MESSAGES/settings.po new file mode 100644 index 000000000..224f45a5d --- /dev/null +++ b/locale/pl/LC_MESSAGES/settings.po @@ -0,0 +1,198 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 14.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-05-18 07:12+0200\n" +"PO-Revision-Date: 2022-03-18 15:03+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications/settings.rst:3 +msgid "Settings" +msgstr "Ustawienia" + +#: ../../content/applications/settings/users_and_features.rst:6 +msgid "Users and Features" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:8 +msgid "" +"As the administrator of your database, you are responsible for its usage. " +"This includes the Apps you install as well as the number of users currently " +"in use." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:12 +msgid "" +"Odoo is many things (ERP, CMS, CRM application, e-Commerce backend, etc.) " +"but it is *not* a smartphone. You should apply caution when adding/removing " +"features (especially Apps) on your database since this may impact your " +"subscription amount significantly (or switch you from a free account to a " +"paying one on our online platform)." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:18 +msgid "" +"This page contains some information as to how you can manage your Odoo " +"instances. Before carrying any of these procedures, we **strongly** advise " +"to test them on a duplicate of your database first. That way, if something " +"goes wrong, your day-to-day business is not impacted." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:23 +msgid "" +"You can find guides on how to duplicate your databases both for :ref:`online" +" ` and :ref:`on premise ` " +"installations." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:27 +msgid "" +"If you have questions about the content of this page or if you encounter an " +"issue while carrying out these procedures, please contact us through our " +"`support form `__." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:33 +msgid "Deactivating Users" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:35 +msgid "" +"Make sure you have sufficient **administrative rights** if you want to " +"change the status of any of your users." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:38 +msgid "" +"In your Odoo instance, click on **Settings**. You will have a section " +"showing you the active users on your database. Click on **Manage Users.**" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:42 +#: ../../content/applications/settings/users_and_features.rst:79 +msgid "|settings|" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:42 +msgid "|browse_users|" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:45 +msgid "You'll then see the list of your users." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:50 +msgid "" +"The pre-selected filter *Internal Users* shows your paying users (different " +"from the *Portal Users* which are free). If you remove this filter, you'll " +"get all your users (the ones you pay for and the portal ones)" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:55 +msgid "" +"In your list of users, click on the user you want to deactivate. As soon as " +"you are on the userform, click on the Action drop down menu, and then click " +"on Archive." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:63 +msgid "The user is now deactivated." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:65 +msgid "**Never** deactivate the main user (*admin*)" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:68 +msgid "Uninstalling Apps" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:70 +msgid "" +"Make sure you first test what you are about to do on a :ref:`duplicate " +"` of your database before making any changes (*especially*" +" installing/uninstalling apps)." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:74 +msgid "" +"In your Odoo instance click on **Settings**; in this app, you will be able " +"to see how many applications you have installed. Click on **Browse Apps** to" +" access the list of your installed applications." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:79 +msgid "|browse_apps|" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:82 +msgid "" +"In your applications' dashboard, you will see all the icons of your " +"applications. Click on the application you want to uninstall. Then, on the " +"form of the application, click on **Uninstall**." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:89 +msgid "" +"Some applications have dependencies, like Invoicing, eCommerce, etc. " +"Therefore, the system will give you a warning message to advise you of what " +"is about to be removed. If you uninstall your application, all its " +"dependencies will be uninstalled as well (and the data in them will " +"permanently disappear). If you are sure you still want to uninstall it, then" +" click **Confirm**." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:96 +msgid "" +"Last, after having checked the warning message (if any), click **Confirm**." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:101 +msgid "You have finished uninstalling your application." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:104 +msgid "Good to know" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:106 +msgid "" +"**Uninstalling apps, managing users, etc. is up to you**: no one else can " +"know if your business flow is broken better than you. If we were to " +"uninstall applications for you, we would never be able to tell if relevant " +"data had been removed or if one of your business flow was broken because we " +"*do not know how you work* and therefore cannot validate these kinds of " +"operations." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:112 +msgid "" +"**Odoo Apps have dependencies**: this means that you may need to install " +"modules that you do not actively use to access some features of Odoo you " +"might need. For example, the Website Builder app is needed to be able to " +"show your customer their Quotes in a web page. Even though you might not " +"need or use the Website itself, it is needed for the Online Quotes feature " +"to work properly." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:119 +msgid "" +"**Always test app installation/removal on a duplicate** (or on a free trial " +"database): that way you can know what other apps may be required, etc. This " +"will avoid surprises when uninstalling or when receiving your invoices." +msgstr "" diff --git a/locale/pl/LC_MESSAGES/sphinx.po b/locale/pl/LC_MESSAGES/sphinx.po new file mode 100644 index 000000000..8a94327c5 --- /dev/null +++ b/locale/pl/LC_MESSAGES/sphinx.po @@ -0,0 +1,239 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-01-02 09:09+0000\n" +"PO-Revision-Date: 2022-03-18 15:03+0000\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../extensions/odoo_theme/layout_templates/footer.html:3 +msgid "Get Help" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/footer.html:5 +msgid "Contact Support" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/footer.html:6 +msgid "Ask the Odoo Community" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/header.html:10 +msgid "Try Odoo for FREE" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:3 +msgid "Odoo Documentation" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:8 +msgid "User Docs" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:9 +msgid "" +"Discover our guide to help you use and configure the platform, by " +"applications." +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:10 +msgid "Top Apps" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:14 +msgid "Accounting" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:19 +msgid "Inventory" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:24 +msgid "Manufacturing" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:29 +msgid "Point of Sale" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:35 +msgid "Install and Maintain" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:36 +msgid "" +"Learn how to install, deploy and upgrade Odoo on premise or on Odoo.sh." +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:37 +#: ../../extensions/odoo_theme/layout_templates/homepage.html:66 +#: ../../extensions/odoo_theme/layout_templates/homepage.html:98 +msgid "Top Links" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:41 +msgid "Installing Odoo" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:46 +msgid "Bugfix updates" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:51 +msgid "Upgrading Odoo" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:56 +msgid "Odoo.sh: The Odoo Cloud Platform" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:64 +msgid "Developer" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:65 +msgid "" +"Learn to develop in Odoo by reading the framework references and programmer " +"tutorials." +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:70 +msgid "Tutorial: Getting started" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:75 +msgid "ORM" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:80 +msgid "Regular Views" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:85 +msgid "QWeb Views" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:90 +msgid "External API" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:96 +msgid "Contributing" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:97 +msgid "" +"You want to contribute to Odoo but don't know where to start? The tutorials " +"and guidelines are there to help you make Odoo even better." +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:102 +msgid "Coding guidelines" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:107 +msgid "Documentation" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/homepage.html:112 +msgid "Content guidelines" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:4 +msgid "Legal" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:10 +#: ../../extensions/odoo_theme/layout_templates/legal.html:17 +msgid "Licenses" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:25 +msgid "Terms and Conditions" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:34 +msgid "Odoo Enterprise Agreement" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:36 +msgid "Applies to self-hosting, Odoo.SH and Odoo Cloud." +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:40 +#: ../../extensions/odoo_theme/layout_templates/legal.html:42 +#: ../../extensions/odoo_theme/layout_templates/legal.html:59 +#: ../../extensions/odoo_theme/layout_templates/legal.html:61 +#: ../../extensions/odoo_theme/layout_templates/legal.html:78 +#: ../../extensions/odoo_theme/layout_templates/legal.html:80 +msgid "Read" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:43 +#: ../../extensions/odoo_theme/layout_templates/legal.html:62 +#: ../../extensions/odoo_theme/layout_templates/legal.html:81 +msgid "English" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:54 +msgid "Odoo Partnership Agreement" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:73 +msgid "Terms Of Sale" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:90 +msgid "See also" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:93 +msgid "Archive of older agreements" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:99 +msgid "Other legal references" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:105 +msgid "Odoo Cloud Service Level Agreement (SLA)" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:110 +msgid "Odoo Cloud Acceptable Use Policy" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:115 +msgid "Odoo SA’s Privacy Policy" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:120 +msgid "Odoo SA’s GDPR Compliance Guide" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:126 +msgid "Contributor License Agreement" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/legal.html:133 +msgid "German Tax Accounting Standards: Odoo’s guide to GoBD Compliance" +msgstr "" + +#: ../../extensions/odoo_theme/layout_templates/page_toc.html:2 +msgid "On this page" +msgstr "" + +#: ../../extensions/odoo_theme/search.html:10 +msgid "Please activate JavaScript to enable the search functionality." +msgstr "" diff --git a/locale/pl/LC_MESSAGES/websites.po b/locale/pl/LC_MESSAGES/websites.po new file mode 100644 index 000000000..9bcd66e78 --- /dev/null +++ b/locale/pl/LC_MESSAGES/websites.po @@ -0,0 +1,3313 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Tadeusz Karpiński , 2023 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"PO-Revision-Date: 2022-03-18 15:03+0000\n" +"Last-Translator: Tadeusz Karpiński , 2023\n" +"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" + +#: ../../content/applications/websites.rst:5 +msgid "Websites" +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:8 +msgid "eCommerce" +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:10 +msgid "" +"Run a modern open-source online store with Odoo eCommerce. Learn how to sell" +" online, promote products and increase your average cart sizes." +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:14 +#: ../../content/applications/websites/website.rst:14 +msgid "" +"Odoo offers a :ref:`free custom domain name ` to " +"all Odoo Online databases for one year. Visitors can then access your " +"website with an address such as ``www.example.com`` rather than the default " +"``example.odoo.com``." +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:19 +msgid ":doc:`Website Documentation `" +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:20 +#: ../../content/applications/websites/website.rst:20 +msgid "`Odoo Tutorials: Website `_" +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:21 +#: ../../content/applications/websites/website.rst:21 +msgid "" +"`Odoo Tutorials: eCommerce `_" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:3 +msgid "How to customize my catalog page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:6 +msgid "Product Catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:8 +msgid "" +"All your published items show up in your catalog page (or *Shop* page)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:13 +msgid "" +"Most options are available in the *Customize* menu: display attributes, " +"website categories, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:20 +msgid "Highlight a product" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:22 +msgid "" +"Boost the visibility of your star/promoted products: push them to top, make " +"them bigger, add a ribbon that you can edit (Sale, New, etc.). Open the Shop" +" page, switch to Edit mode and click any item to start customizing the grid." +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:26 +msgid "" +"See how to do it: " +"https://www.odoo.com/openerp_website/static/src/video/e-commerce/editing.mp4" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:29 +msgid "Quick add to cart" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:31 +msgid "" +"If your customers buy a lot of items at once, make their process shorter by " +"enabling purchases from the catalog page. To do so, add product description " +"and add to cart button. Turn on the following options in *Customize* menu: " +"Product Description, Add to Cart, List View (to display product description " +"better)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:3 +msgid "How to build a product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:5 +msgid "On the website click *New Page* in the top-right corner." +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:7 +msgid "Then click *New Product* and follow the blinking tips." +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:12 +msgid "Here are the main elements of the Product page:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:17 +msgid "Many elements can be made visible from the *Customize* menu." +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:22 +msgid "See how to configure your products from links here below." +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:26 +msgid ":doc:`../managing_products/variants`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:27 +msgid ":doc:`../maximizing_revenue/cross_selling`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:28 +msgid ":doc:`../maximizing_revenue/reviews`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:29 +msgid ":doc:`../maximizing_revenue/pricing`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:30 +msgid ":doc:`../../website/pages/seo`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products.rst:5 +msgid "Manage my products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:3 +msgid "How to display several images per product" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:5 +msgid "" +"By default your product web page displays the main image of your product " +"only. If you like to show your products under several angles, you can turn " +"the image into a carrousel." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:11 +msgid "" +"Check *Several images per product* in :menuselection:`Website Admin --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:13 +msgid "" +"Open a product detail form and upload images from *Images* tab. Hit *Create*" +" in Edit mode to get the upload wizard." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:19 +msgid "Such extra image are common to all the product variants (if any)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:3 +msgid "Manage product variants" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:5 +msgid "" +"Product variants are used to offer variations of the same product to your " +"customers on the product's page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:8 +msgid "" +"Let's say one of your customers selects a T-shirt from your product catalog." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:10 +msgid "" +"Then, they choose the size and color they want. The various size and color " +"combinations are known as product variants." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:14 +msgid "Create attributes & variants" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:16 +msgid "" +"In order to create various attributes and variants for your products, you " +"first need to turn on *Variants* in :menuselection:`Sales --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:19 +msgid "" +"Then, select a product from the Products list (:menuselection:`Sales / " +"Website --> Products --> Products`). When the product detail form opens, " +"click on *Edit*, and go to the *Variants* tab." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:22 +msgid "" +"Here, you can add as many different attributes as you'd like by clicking on " +"*Add a line*." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:24 +msgid "These attributes appear as three different types:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:26 +msgid "Radio buttons" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:27 +msgid "Color buttons" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:28 +msgid "Drop-down menu" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:30 +msgid "" +"Several variants appear as soon as there are two values for one attribute." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:32 +msgid "Don't forget to hit *Save* once all variants have been entered." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "ecommerce product variants values" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:39 +msgid "Edit variants" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:41 +msgid "" +"After you hit *Save*, you are able to see all the variants from the product " +"template detail form via the *Variants* smart button." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "ecommerce product variants smart button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:48 +msgid "" +"Clicking the *Variants* smart button takes you to the Product Variants page," +" where you can edit the following data for each specific variant:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:51 +msgid "Picture(s)" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:52 +msgid "Internal Reference (SKU #)" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:53 +msgid "Barcode" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:54 +msgid "Volume" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:55 +msgid "Weight" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:56 +msgid "Cost" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:59 +msgid "" +"Both the Barcode and the Internal Reference are variant-specific. You need " +"to populate them once the variants are generated." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:63 +msgid "Set specific prices per variant" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:65 +msgid "" +"You can set a specific public price per variant by clicking on *Configure " +"Variants* in the product detail form (top-left corner). That takes you to " +"the *Product Variant Values* page for that product." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "ecommerce product variants configure variants" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:72 +msgid "" +"To set a specific public price for a particular variant, simply click on the" +" variant you want to modify, then click on *Edit*." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:75 +msgid "" +"The *Value Price Extra* field represents the monetary value that is added to" +" the original product price whenever the corresponding attribute value is " +"selected." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "ecommerce value price extra" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:82 +msgid "This is how the *Value Price Extra* looks on your website:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "ecommerce value price extra on the frontend" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:89 +msgid "" +"Pricelist formulas let you set advanced price computation methods for " +"product variants. See :doc:`../maximizing_revenue/pricing`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:93 +msgid "Disable/archive variants" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:95 +msgid "" +"You can disable/archive specific variants so they are no longer available in" +" quotes or on your website (not existing in your stock, deprecated, etc.). " +"Simply select *Archive* in their detail form. You can reactivate them the " +"same way." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "ecommerce product variants archive" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:103 +msgid "" +"To retrieve such items, hit *Archived* in the *Filters* category while " +"searching the variants list." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "ecommerce product variants archive search" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:110 +msgid ":doc:`../../../sales/sales/products_prices/products/variants`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue.rst:5 +msgid "Maximize my revenue" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:3 +msgid "Cross-selling: Accessory and Optional Products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:5 +msgid "" +"Any sales process is an opportunity to maximize revenues. For example, with " +"an extended warranty or some accessories." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:8 +msgid "" +"To do so, you can use **Cross-selling**, a sales technique consisting in " +"selling a customer something in addition to the product or service they were" +" originally shopping for. It is a great way to maximize the value of each " +"one of your customers." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:12 +msgid "It can be done via two different features:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:14 +msgid "" +":ref:`Accessory products ` on the checkout page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:15 +msgid "" +":ref:`Optional products ` on a new :guilabel:`Add to" +" Cart` screen." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:20 +msgid "Accessory Products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:22 +msgid "" +"**Accessory Products** are products that are displayed when customers review" +" their cart before paying. As an example, you could suggest a mouse or a " +"keyboard when someone buys a computer." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:25 +msgid "" +"To add *Accessory Products*, go to :menuselection:`Website --> Products --> " +"Products` and, under the :guilabel:`Sales Tab`, add your products to the " +":guilabel:`Accessory Products` field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst-1 +msgid "Add an accessory product to product form." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:32 +msgid "" +"Now, go to your website and add the product to your cart. On the payment " +"step, you can see your accessory products suggested to the customer." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst-1 +msgid "See of payment view and accessory product suggestion." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:40 +msgid "" +"`Odoo Tutorials: Alternative, Accessory, and Optional Products " +"`_." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:46 +msgid "Optional Products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:48 +msgid "" +"**Optional products** are products directly related to an item. Each time " +"the product is added to a cart, a pop-up appears, suggesting other products " +"to buy." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:51 +msgid "" +"To enable optional products, go to :menuselection:`Website --> Configuration" +" --> Settings` and tick :guilabel:`Optional Products`. Then, go to " +":menuselection:`Website --> Products --> Products` and open the item you " +"want to add an optional product to. In the :guilabel:`Sales tab` of that " +"product, add as many optional products as you want." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst-1 +msgid "Add an optional product to product form." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:60 +msgid "" +"From now, when a customer adds this product to their cart, a pop-up appears " +"and suggests also adding the optional product(s)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst-1 +msgid "Pop-up with optional products appears." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:68 +msgid ":doc:`upselling`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:3 +msgid "Adapt prices to website visitors" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:5 +msgid "" +"This section sheds light on pricing features found in the eCommerce app:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:7 +msgid "force a price by geo-localization," +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:9 +msgid "let the customer choose the currency." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:11 +msgid "" +"As a pre-requisite, check out how to managing product pricing: " +":doc:`/applications/sales/sales/products_prices/prices/pricing`)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:15 +msgid "Geo-IP automatically applies the right price" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:17 +msgid "" +"Assign country groups to your pricelists. That way, visitors who aren't " +"logged in yet will get their own currency when landing on your website." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:20 +msgid "Once logged in, they get the pricelist matching their country." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:23 +msgid "Currency selector" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:25 +msgid "" +"In the case that you sell in several currencies, you can let your customers " +"choose their own. Check the *Selectable* box to add the pricelist to the " +"website drop-down menu, which can be found in *Pricelists* under the " +"*Products* menu, located in the Website application." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:35 +msgid ":doc:`/applications/sales/sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:36 +msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:37 +msgid ":doc:`promo_code`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:3 +msgid "How to create & share promotional codes" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:5 +msgid "" +"Want to boost your sales for Xmas? Share promocodes through your marketing " +"campaigns and apply any kind of discounts." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:9 +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:13 +#: ../../content/applications/websites/website/configuration/multi_website.rst:18 +msgid "Setup" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:11 +msgid "" +"Go to :menuselection:`Sales --> Settings` and choose *Advanced pricing based" +" on formula* for *Sale Price*." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:14 +msgid "" +"Go to :menuselection:`Website Admin --> Catalog --> Pricelists` and create a" +" new pricelist with the discount rule (see :doc:`pricing`). Then enter a " +"code." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:21 +msgid "" +"Make the promocode field available on your *Shopping Cart* page (option in " +"*Customize* menu). Add a product to cart to reach it." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:27 +msgid "" +"Once turned on you see a new section on the right side. On clicking *Apply* " +"prices get automatically updated in the cart." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:33 +msgid "" +"The promocode used by the customer is stored in the system so you can " +"analyze the performance of your marketing campaigns." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:39 +msgid "Show sales per pricelists..." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:43 +msgid ":doc:`pricing`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:3 +msgid "How to enable comments & rating" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:5 +msgid "" +"Publishing and monitoring customer experience will help you gain the trust " +"of new customers and better engage with your community. In 2 clicks, allow " +"your customer to share their feedback!" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:15 +msgid "" +"Activate comments & rating from the *Customize* menu of the product web " +"page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:21 +msgid "" +"Visitors must log in to share their comments. Make sure they are able to do " +"so (see Portal documentation)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:25 +msgid "Review the posts in real time" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:27 +msgid "" +"Whenever a post is published, the product manager and all the product " +"followers get notified in their Inbox (*Discuss* menu)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:34 +msgid "" +"By default the user who created the product is automatically set as " +"follower." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:36 +msgid "" +"Click the product name to open the detail form and review the comment (in " +"the product discussion thread)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:43 +msgid "Moderate & unpublish" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:45 +msgid "" +"You can easily moderate by using the chatter, either in the product detail " +"form or on the web page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:48 +msgid "" +"To unpublish the post, open the product web page and click the *Published* " +"button to turn it red (*Unpublished*)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:56 +msgid "..tip::" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:55 +msgid "" +"You can access the web page from the detail form by clicking the *Published*" +" smart button (and vice versa)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:3 +msgid "How to sell pricier alternative products (upselling)" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:5 +msgid "" +"In order to maximize your revenue, suggesting pricier alternative products " +"is strongly advised for basic items. That way, your customer will spend more" +" time browsing your catalog." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:12 +msgid "To do so:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:14 +msgid "" +"Select such *Alternative Products* in the *Sales* tab of the product detail " +"form. 3 alternatives are fine! Don't publish too many otherwise your " +"customers will be confused." +msgstr "" + +#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:20 +msgid "" +"Turn on *Alternative Products* from the *Customize* menu of the product web " +"page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience.rst:5 +msgid "Get paid" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:3 +msgid "Manage orders paid with Payment Acquirers" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:5 +msgid "" +"The moment a payment is officially authorized by a Payment Acquirer, Odoo " +"*automatically* confirms the order, which triggers the delivery. And, if you" +" invoice based on ordered quantities, you are requested to invoice the " +"order, as well." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:9 +msgid "" +"Let’s take a closer look at how to manage orders paid with Payment " +"Acquirers." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:12 +msgid "Checking the status of a payment" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:14 +msgid "" +"To check the status of a payment, go to :menuselection:`Website --> Orders " +"--> Orders`. Then, simply click on the order you wish to check on." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:17 +msgid "" +"Once you are on the Sales Order page, you will find the payment is confirmed" +" with an automatic note in the *Chatter*." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst-1 +msgid "payment is confirmed in the chatter of sales order" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:24 +msgid "" +"If the user decides to create an invoice, the payment is directly " +"reconciled. This note in the *Chatter* includes a link to the Payment entry," +" which contains various details about the transaction, along with a link to " +"the related Journal Entry." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst-1 +msgid "page with details surrounding the specific transaction" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:32 +msgid "" +"Specific messages are provided to your customers for every payment status " +"whenever they are redirected to Odoo after the transaction. To edit these " +"messages, go to the *Messages* tab of the payment method." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:38 +msgid "Automatically generate invoices at order" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:40 +msgid "" +"When the order is confirmed, you can also choose to have an invoice " +"automatically issued and paid. This fully-automated feature is designed for " +"businesses that invoice orders right away." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:47 +msgid "To do automatically generate invoices at order:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:45 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Settings --> Invoicing`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:46 +msgid "" +"Then, under the **Invoicing Policy** option, select *Invoice what is " +"ordered*." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:47 +msgid "Then activate *Automatic Invoices* and *Save*." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst-1 +msgid "example of automatic invoice" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:54 +msgid "Capture payment after the delivery" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:56 +msgid "" +"If the acquirer handling the payment is configured to capture amounts " +"manually, the order is confirmed, but the amount is kept on hold. Once the " +"delivery is processed, you can capture the payment from the related Sales " +"Order." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:61 +msgid ":doc:`../../../finance/payment_acquirers`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:62 +msgid "" +":ref:`Payment Acquirers: Place a hold on a card " +"`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:3 +msgid "How customers can access their customer account" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:5 +msgid "" +"It has never been so easy for your customers to access their customer " +"account. Forget endless signup forms, Odoo makes it as easy as ABC. They are" +" suggested to sign up (name, email, password) when the order is placed, and " +"not before. Indeed, nothing is more annoying than going through a signup " +"process before buying something." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:14 +msgid "Sign up" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:16 +msgid "" +"The invitation to sign up shows up when the customer wants to visualize the " +"order from order confirmation email." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:23 +msgid "Customer account" +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:25 +msgid "" +"Once logged in the customer will access the account by clicking *My Account*" +" in the login dropdown menu." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:31 +msgid "" +"THere they find all their history. The main address (billing) can also be " +"modified." +msgstr "" + +#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:37 +msgid "" +"If the customer is set as a contact of a company in your address book, they " +"will see all the documents whose the customer belongs to this company." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:6 +msgid "Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:8 +msgid "" +"Live Chat has the highest satisfaction rating of any communication tool. It " +"allows fast responses and it is accessible and convenient, as your customers" +" can keep doing what they are doing while interacting with you. Remember: " +"your customers want to talk to you, so let's make it easy." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:13 +msgid "`Live Chat: product page `_" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:14 +msgid ":doc:`livechat/ratings`" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:15 +msgid ":doc:`livechat/responses`" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:18 +msgid "Set up" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:20 +msgid "" +"Once *Live Chat* is installed on your database, if your website was created " +"with Odoo, the application is automatically added to it. All that is left to" +" do is to go to :menuselection:`Website --> Configuration --> Settings --> " +"Live Chat`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of the settings page and the live chat feature for Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:28 +msgid "" +"Select the channel to be linked to your website or create one on the fly." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of a live chat channel form for Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:33 +msgid "For both scenarios, under:" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:36 +msgid "" +"- **Operators**: add agents to respond to the chat requests. Add as many as " +"you like, and keep in mind that operators that do not show any activity in " +"Odoo for more than 30min are considered disconnected." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:39 +msgid "" +"- **Options**: set the default text to be shown on the live chat button; an " +"automated welcome message to be seen by visitors when a conversation is " +"initiated, and the text that prompts the user to initiate a chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:42 +msgid "" +"- **Channel Rules**: choose an action for a given URL, and/or per country. " +"In the example below, the chat window automatically pops-up 3 seconds after " +"users (from any country) land on the contact us page." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of a channel’s rules form for Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:48 +msgid "" +"GeoIP, which refers to the process of finding a computer terminal’s " +"geographical location by its IP address, must be installed on your server. " +"Otherwise, under *Channel Rules*, countries are not taken into account." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:53 +msgid "External options" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:56 +msgid "" +"If your website was not created with Odoo, you can find the code to be added" +" to your own, under the *Widget* tab." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:57 +msgid "" +"Odoo also offers an URL you can send to users so they can have access to a " +"single live chat page." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of the widget tab for Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:63 +msgid "Managing chat requests" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:65 +msgid "" +"Conversations initiated by visitors pop up as a direct message, and are " +"shown in *Discuss*. Therefore, inquiries can be answered wherever you are in" +" Odoo." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "" +"View of the discuss application with a message sent through live chat in " +"Odoo" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:72 +msgid "" +"Conversations are dispatched based on the current workload of the online " +"operators." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:75 +msgid "Leave or join a channel" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:77 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Settings`, access your " +"channel under *Live Chat*, and *Join Channel* or *Leave Channel*." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "" +"View of a channel form and the option to join a channel for Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:3 +msgid "Ratings" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:5 +msgid "" +"Giving users the opportunity to rate their interactions can help you " +"improving the experience you offer. That means staying on top of your " +"customers' needs, besides keeping track of your operators’ performances." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:10 +msgid "Customer Rating" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:12 +msgid "" +"Once the user chooses to close the chat window, he can rate his interaction." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:14 +msgid "" +"If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing " +"for an explanation is shown." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:15 +msgid "A copy of the conversation can also be sent by email." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of the chat window from a user’s side for Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:22 +msgid "The rating is shown on the chat window itself for the operator." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "" +"View of a chat window from an operator’s side highlighting a rating for Odoo" +" Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:28 +msgid "And under :menuselection:`Report --> Customer Ratings`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of the customer ratings page in Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:35 +msgid "Make the rating public" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:37 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Settings`, access your " +"channel form, click on *Go to Website* and on *Unpublished*, to publish the " +"rating of that channel on your website." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of the public ratings in the website for Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:45 +msgid ":doc:`responses`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:3 +msgid "Commands and Canned Responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:5 +msgid "" +"Using canned responses can help you save time and have a previous, well-" +"thought response, to some of your most common questions and comments." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:9 +msgid "Use commands" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:11 +msgid "" +"Commands are shortcuts that do specific actions within the chat window:" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:13 +msgid "**/help**: shows a help message." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:14 +msgid "**/helpdesk**: creates a helpdesk ticket." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:15 +msgid "**/helpdesk_search**: searches for a helpdesk ticket." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:16 +msgid "**/history**: shows the last 15 visited pages." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:17 +msgid "**/lead**: creates a new lead." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:18 +msgid "**/leave**: leaves the channel." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:0 +msgid "" +"- For *helpdesk tickets*: make sure the application is installed on your " +"database and the option *Live Chat* under :menuselection:`Helpdesk --> " +"Configuration --> Helpdesk Teams` is enabled." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:0 +msgid "" +"- For *leads*: the *CRM* application must be installed on your database." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:26 +msgid "" +"To access the ticket or lead created from the chat, click on the shortcut " +"link." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of the chat window with a helpdesk ticket created in Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:33 +msgid "" +"Helpdesk tickets created from the chat automatically add the conversation as" +" a description of the ticket. The same goes for the creation of a lead." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:37 +msgid "Send canned responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:40 +msgid "" +"Canned responses allow you to have a full piece of text being placed when " +"you type a shortcut word. To create them, go to :menuselection:`Live Chat " +"--> Configuration --> Canned Responses`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:41 +msgid "" +"To use them during a conversation, simply type **:** followed by the " +"shortcut word you created." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of a chat window and the use of a canned response in Odoo Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:48 +msgid ":doc:`ratings`" +msgstr "" + +#: ../../content/applications/websites/website.rst:8 +msgid "Website" +msgstr "" + +#: ../../content/applications/websites/website.rst:10 +msgid "" +"Discover the best **Open-Source Website Builder** and learn how to build " +"beautiful websites that convert visitors into leads or revenues." +msgstr "" + +#: ../../content/applications/websites/website/configuration.rst:5 +#: ../../content/applications/websites/website/configuration/recaptcha.rst:16 +#: ../../content/applications/websites/website/reporting/link_tracker.rst:10 +msgid "Configuration" +msgstr "Konfiguracja" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:3 +msgid "Multiple websites" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:8 +msgid "" +"Odoo’s Multi-Websites opens up broad possibilities of diversification and " +"customer segmentation for your business. A multiplied audience and boosted " +"revenue are now just a few clicks away!" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:12 +msgid "" +"Each website can work in a fully independent way, with its theme, branding, " +"domain name, header & footer, pages, languages, products, blog posts, forum," +" slides, events, live chat channels, etc. Let’s go for a tour!" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:20 +msgid "" +"To create a new website, go to :menuselection:`Website --> Configuration -->" +" Settings`. The button, *Create a new website*, lays in the first section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:28 +msgid "" +"In the upcoming prompt, set a name for your new website and a specific " +"domain name. Leave empty to publish the new website under the default domain" +" of your Odoo database. You can later set some country groups to redirect " +"visitors to it using Geo IP." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:36 +msgid "" +"Then, select a theme. This new website might have an entirely different " +"purpose or audience than the first one. So feel free to go for a different " +"theme!" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:40 +msgid "" +"Once the theme is selected, you can start to build the homepage of your " +"website. Follow the purple drops; they will help you in the first steps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:48 +msgid "" +"If you run Odoo Online, don’t forget to redirect any new domain name to your" +" Odoo database (``CNAME``) and to authorize it Odoo-side. See :ref:`domain-" +"name/existing`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:52 +msgid "Create the menu" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:54 +msgid "" +"The new website has a default menu with all the installed applications. To " +"edit it, click :menuselection:`Pages --> Edit Menu`. Moving forward you only" +" edit the menu of the current website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:59 +msgid "Switch from one website to another" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:62 +msgid "" +"As easy as ABC! There is a website switcher in the right corner of the edit " +"bar. Switching to another website will connect to the domain of this " +"website. If you use another domain for the website, the user is requested to" +" sign in." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:71 +msgid "" +"When switching, you are redirected to the same domain path on the other " +"website (e.g., ``/shop/myproduct``). If this URL is not used, you will be " +"redirected to a 404 page but prompted to create a new page from there." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:76 +msgid "Add features" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:78 +msgid "" +"The website apps you install (e.g., Slides, Blogs) are made available on all" +" your websites. You can, of course, keep them hidden in one website by " +"removing the menu item." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:82 +msgid "" +"Each website comes with a high range of specific options in the settings. " +"First, select the website to configure." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:88 +msgid "" +"Then, take a look at the options flagged with the earth icon. It means they " +"only impact the very website you are working on." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:94 +msgid "You can, for instance, set specific :" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:96 +msgid "languages," +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:98 +msgid "domain names," +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:100 +msgid "social media links," +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:102 +msgid "customer portal mode (B2C vs. B2B)," +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:104 +msgid "dedicated live chat channels," +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:106 +msgid "etc." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:108 +msgid "The other options are global and apply to all your websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:111 +msgid "Manage domain names" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:113 +msgid "" +"As said earlier, your websites can either share the same domain name or use " +"a specific one. If you share it and want to adapt the content per region, " +"set country groups in the setting of each website. Visitors will be " +"redirected to the right website using GeoIP." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:122 +msgid "" +"Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, " +"don’t forget to install *GeoIP* library. See :doc:`on-premise_geo-ip-" +"installation`" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:127 +msgid ":doc:`/administration/maintain/domain_names`" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:129 +msgid "" +"If you setup an extra website and specify the domain name you will have to " +"do three things to get this feature to work:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:132 +msgid "" +"Setup an A-record in the DNS configuration of your hosting provider so that " +"\"www.mywebsite2.ext\" is redirected to the IP of your Odoo instance." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:134 +msgid "" +"Create an extra Nginx ``server`` block in which you set the ``server_name`` " +"that you've set in the :guilabel:`Website domain` field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:136 +msgid "" +"Reload and restart your Nginx instance to use the new ``server`` block." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:139 +msgid "Customize the visitor experience" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:142 +msgid "" +"The customer experience can be customized very profoundly thanks to the menu" +" \\*Customize\\*. All the visual options available there are specific to " +"each website. Go through the different pages to adapt them to this new " +"audience. Focus on workflows, and automatic pages (eCommerce checkout, " +"blogs, events, etc.) as the number of available options is higher there." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:152 +msgid "Publish specific content per website" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:155 +msgid "" +"Like static pages, any content created from the front-end (product, blog " +"post, etc.) is always only published in the current website. You can change " +"that from the edit form view in the backend and leave the *Website* field " +"blank. This will publish it in all the websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:163 +msgid "" +"Here are all the objects that you can link to *either one or all the " +"websites*:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:166 +msgid "Products" +msgstr "Produkty" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:168 +msgid "Product Categories for eCommerce" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:170 +msgid "Blogs" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:172 +msgid "Slide Channels" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:174 +msgid "Forums" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:176 +msgid "Events" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:178 +msgid "Job Positions" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:181 +msgid "" +"When you create the record from the backend and publish it, typically a " +"product or an event, it is made available in all websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:185 +msgid "Publish a page in all websites" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:187 +msgid "" +"A new static page is created and only made available in the current website." +" You can duplicate it to other websites from :menuselection:`Website --> " +"Configuration --> Pages`. To do so, leave the *Website* field empty." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:191 +msgid "" +"If you want to duplicate it in just one other website, duplicate the page " +"and set the new website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:197 +msgid "" +"When you edit the page again, the change only affects the current website. A" +" new page is duplicated and tied up to the website. The original page still " +"being linked to all websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:202 +msgid "" +"By grouping pages by URL in the page manager, you quickly find the original " +"page behind each edited page." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:209 +msgid "Multi-companies" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:211 +msgid "" +"Each website can be linked to a specific company of your system, in a multi-" +"companies environment." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:217 +msgid "" +"With such a configuration, only company-related data appear on the website " +"(products, jobs, events, etc.)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:220 +msgid "" +"Website editors can only view and edit the pages of the records they have " +"access to, typically the ones belonging to their current company (and to " +"their subsidiaries, or child companies in Odoo language). And so is it for " +"visitors." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:226 +msgid "" +"If websites are multi-companies, you don’t change company when switching " +"websites. To change the company and see the related content, use the company" +" selector in the menu." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:232 +msgid "Configure your eCommerce website" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:234 +msgid "" +"eCommerce is a crucial feature in the multi-websites environment. We made it" +" so that the entire flow can be customized to fit the very audience of each " +"website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:239 +msgid "Products only available on one website" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:241 +msgid "" +"We already saw earlier how to publish a specific record in only one website." +" You will find the \\*Website\\* field in the eCommerce tab of the product " +"edit form. Empty means available in all websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:249 +msgid "Products available on *some* websites" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:251 +msgid "" +"To make a product available on some websites, but not all of them, you " +"should duplicate the product for each website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:254 +msgid "" +"If you need a unique reference to manage in your inventory, you should " +"install *Manufacturing\\ and create *Kits* BoMs (bills of materials). Each " +"kit will link each published “virtual” product to the main reference managed" +" in your inventory. That way, any item sold from your website will be " +"converted into the storable item in the delivery order." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:261 +msgid "Pricelists" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:263 +msgid "" +"To manage specific prices by websites, you can activate *Multiple Sales " +"Prices per Product* in Website settings." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:266 +msgid "" +"Then, go to :menuselection:`Website --> Products --> Pricelists` to create " +"additional pricelists. You can also choose to have a pricelist available " +"*only* on a specific website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:270 +msgid ":doc:`../../ecommerce/maximizing_revenue/pricing`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:275 +msgid "" +"Leaving the field empty means that you make it work in all websites if " +"*Selectable* is selected. Otherwise, it makes it only available for backend " +"operations of Sales and Point of Sale applications." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:280 +msgid "Payment Acquirers and Delivery Methods" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:282 +msgid "" +"By default, published payment acquirers and delivery methods are deployed in" +" all websites. You could already use specific payment acquirers per country " +"using Geo IP by defining countries in their configuration. Now you can also " +"do it per website by filling in the *Website* field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:288 +msgid "Customer accounts" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:290 +msgid "" +"There is a setting to choose how to manage customer accounts in Website " +"settings. You can either allow customers to use one account through all the " +"websites or compel them to create one account for each website. This last " +"option is convenient if your websites shouldn’t be related to each other in " +"the visitor mind." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:300 +msgid "Technical hints for customization" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:302 +msgid "" +"If you want to publish custom objects on the website, here are a few tips to" +" make it work with multi websites:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:306 +msgid "Sitemap: don’t forget the domain in the route to only publish" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:306 +msgid "available records in each website’s sitemap." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:310 +msgid "Access: you should call the method" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:309 +msgid "" +"*can_access_from_current_website* in the controller to make sure the visitor" +" can see a record in the current website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:314 +msgid "Search: when a list of records is displayed, don’t forget to specify" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:313 +msgid "the domain to only display records available for the current website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:3 +msgid "Geo IP Installation (On-Premises Database)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:6 +msgid "Installation" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:9 +msgid "" +"Please note that the installation depends on your computer's operating " +"system and distribution. We will assume that a Linux operating system is " +"being used." +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:15 +msgid "Install `geoip2 `__ Python library" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:17 +msgid "" +"Download the `GeoLite2 City database " +"`_. You should end up with a" +" file called ``GeoLite2-City.mmdb``" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:22 +msgid "Move the file to the folder ``/usr/share/GeoIP/``" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:24 +msgid "Restart the server" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:27 +msgid "" +"If you can't/don't want to locate the geoip database in " +"``/usr/share/GeoIP/``, you can use the ``--geoip-db`` option of the Odoo " +"command line interface. This option takes the absolute path to the GeoIP " +"database file and uses it as the GeoIP database. For example:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:39 +msgid "" +"``GeoIP`` Python library can also be used. However this version is " +"discontinued since January 1. See `GeoLite Legacy databases are now " +"discontinued `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:44 +msgid "How To Test GeoIP Geolocation In Your Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:46 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:47 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:48 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:54 +msgid "" +"You should end up with a dictionary indicating the location of the IP " +"address." +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:60 +msgid "" +"If the curly braces are empty ``{}``, it can be for any of the following " +"reasons :" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:62 +msgid "" +"The browsing IP address is the localhost (``127.0.0.1``) or a local area " +"network one (``192.168.*.*``)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:64 +msgid "" +"If a reversed proxy is used, make sure to configure it correctly. See " +":option:`proxy mode `" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:66 +msgid "``geoip2`` is not installed or the GeoIP database file wasn't found" +msgstr "" + +#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:67 +msgid "The GeoIP database was unable to resolve the given IP address" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:3 +msgid "reCAPTCHA v3 on forms" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:5 +msgid "" +"Google's reCAPTCHA protects website forms against spam and abuse. It " +"attempts to distinguish between human and bot submissions." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:9 +msgid "" +"reCAPTCHA v3 works in the background and does not interrupt visitors. " +"However, if the check fails, visitors cannot submit the form." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:13 +msgid "" +"`Google's reCAPTCHA v3 guide " +"`_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:19 +msgid "On Google" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:21 +msgid "" +"Open `the reCAPTCHA website registration page " +"`_. Log in or create a Google" +" account if necessary." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:24 +msgid "On the website registration page:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:26 +msgid "Give the website a :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:27 +msgid "Leave the :guilabel:`reCAPTCHA type` on :guilabel:`Score based (v3)`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:28 +msgid "" +"Enter one or more :guilabel:`Domains` (e.g., *example.com* or " +"*subdomain.example.com*)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:29 +msgid "" +"Under :guilabel:`Google Cloud Platform`, a project is automatically selected" +" if one was already created with the logged-in Google account. If not, one " +"is automatically created. Click :guilabel:`Google Cloud Platform` to select " +"a project yourself or rename the automatically created project." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:33 +msgid "Agree to the terms of service." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:34 +msgid "Click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst-1 +msgid "reCAPTCHA website registration example" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:39 +msgid "" +"A new page with the generated keys is then displayed. Leave it open for " +"convenience, as copying the keys to Odoo is required next." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:43 +msgid "On Odoo" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:45 +msgid "" +"From the database dashboard, click :guilabel:`Settings`. Under " +":guilabel:`Integrations`, enable :guilabel:`reCAPTCHA` if needed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:49 +msgid "" +"Do not disable the :guilabel:`reCAPTCHA` feature or uninstall the " +":guilabel:`Google reCAPTCHA integration` module, as many other modules would" +" also be removed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:52 +msgid "" +"Open the Google reCAPTCHA page, copy the :guilabel:`Site key`, and paste it " +"into the :guilabel:`Site Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:54 +msgid "" +"Open the Google reCAPTCHA page, copy the :guilabel:`Secret key`, and paste " +"it into the :guilabel:`Secret Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:56 +msgid "" +"Change the default :guilabel:`Minimum score` (`0.5`) if necessary, using a " +"value between `1.0` and `0.0`. The higher the threshold is, the more " +"difficult it is to pass the reCAPTCHA, and vice versa." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:59 +msgid "Click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:61 +msgid "" +"All pages using the :guilabel:`Form`, :guilabel:`Newsletter Block`, and " +":guilabel:`Newsletter Popup` snippets on the website are now protected by " +"reCAPTCHA." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:65 +msgid "" +"If the reCAPTCHA check fails, the following error message is displayed:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:0 +msgid "Google reCAPTCHA verification error message" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:70 +msgid "" +"reCAPTCHA v3 is free for up to `1 million assessments per month " +"`_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:73 +msgid "" +"Analytics and additional settings are available on `Google's reCAPTCHA " +"administration page `_. For " +"example, you can receive email alerts if Google detects suspicious traffic " +"on your website or view the percentage of suspicious requests, which could " +"help you determine the right minimum score." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:78 +msgid "" +"You can notify visitors that reCAPTCHA protects a form. To do so, open the " +"website editor and navigate to the form. Then, click somewhere on the form, " +"and on the right sidebar's :guilabel:`Customize` tab, toggle :guilabel:`Show" +" reCAPTCHA Policy` found under the :guilabel:`Form` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:0 +msgid "reCAPTCHA policy message displayed on a form" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:3 +msgid "Translations" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:5 +msgid "" +"In addition to creating great modern websites, Odoo gives you the " +"possibility to translate it in different languages." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:9 +msgid "Process" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:11 +msgid "" +"Once your website is created, you have the opportunity to translate it in as" +" many different languages as you want." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:14 +msgid "You can only translate your website manually, follow the next step." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:16 +msgid "" +"Now go to your website. On the bottom right corner of the page, click on " +"**Add a language**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:22 +msgid "" +"Choose the language in which you want to translate your website and then " +"click on **Load.**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:28 +msgid "" +"You will see that Now, next to English there is also French, which means " +"that the page for the translation has been created. You can also see that " +"some of the text has been translated automatically." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:35 +msgid "" +"To translate the content of the website, click on **Translate** (here " +"**Traduire** since we want to translate the website in French)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:3 +msgid "Unsplash (free images)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:6 +msgid "Generate an Unsplash access key" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:9 +msgid "" +"**As an Odoo Online user**, you are ready to use Unsplash. You won't need to" +" follow this guide to set up Unsplash information since you will use our own" +" Odoo Unsplash key in a transparent way." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:13 +msgid "Generate an Unsplash access key for non-Odoo Online users" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:15 +msgid "Create an account on `Unsplash.com `_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:17 +msgid "" +"Go to your `applications dashboard " +"`_ and click on **New " +"Application**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:23 +msgid "Accept the conditions and click on **Accept terms**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:28 +msgid "" +"You will be prompted to insert an **Application name** and a " +"**Description**. Please prefix your application name by \"**Odoo:** \" so " +"that Unsplash can recognize it as an Odoo instance. Once done, click on " +"**Create application**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:35 +msgid "" +"You should be redirected to your application details page. Scroll down a bit" +" to find your **access key**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:42 +msgid "" +"**As a non-Odoo Online user**, you won't be able to register for a " +"production Unsplash key and will be limited to your test key that has a " +"restriction of 50 Unsplash requests per hour." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:46 +msgid "Generate an Unsplash application ID" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:49 +msgid "You should first create and set up your Unsplash application." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:51 +msgid "" +"Go to your `applications dashboard " +"`_ and click on your newly created " +"Unsplash application under **Your applications**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:57 +msgid "" +"You will be redirected to your application details page. The **application " +"ID** will be visible in your browser's URL. The URL should be something like" +" ``https://unsplash.com/oauth/applications/``" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:65 +msgid "" +"**As a non-Odoo Online user**, you won't be able to register for a " +"production Unsplash key and will be limited to your test key that has a 50 " +"Unsplash requests per hour restriction." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:5 +msgid "Pages" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:3 +msgid "Search Engine Optimisation (SEO)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:5 +msgid "" +"Search Engine Optimization (SEO) is a set of good practices to optimize your" +" website so that you get a better ranking in search engines like Google. In " +"short, a good SEO allows you to get more visitors." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:9 +msgid "" +"Some examples of SEO rules: your web pages should load fast, your page " +"should have one and only one title ``

``, meta tags (alt-tag, title-tag) " +"should be consistent with the content, your website should have a " +"``/sitemap.xml`` file, etc." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:15 +msgid "" +"To guarantee Odoo Website and Odoo eCommerce users have a great SEO, Odoo " +"abstracts all the technical complexities of SEO and handles everything for " +"you, in the best possible way. This will be explained here below." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:20 +msgid "" +"But first, let see how you can easily boost your ranking by finetuning the " +"content and the meta tags of your website." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:24 +msgid "Meta Tags" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:27 +msgid "Title, Description" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:29 +msgid "" +"Every web page should define the ```` and ``<description>`` meta " +"data. These information elements are used by search engines to promote your " +"website. They are automatically generated based on page title & content, but" +" you can finetune them. Make sure they fit the content of the page, " +"otherwise you will be downgraded by search engines." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:39 +msgid "Keywords" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:41 +msgid "" +"In order to write quality content and boost your traffic, Odoo provides a " +"``<keyword>`` finder. Those keywords are the searches you want to head " +"towards your website. For each keyword, you see how it is used in the " +"content (H1, H2, page title, page description, page content) and what are " +"the related searches in Google. The more keywords are used the better." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:51 +msgid "" +"If your website is in multiple languages, you can use the Promote tool for " +"every language of a single page and set specific title, description and " +"search tags." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:56 +msgid "Content is King" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:58 +msgid "" +"When it comes to SEO, content is usually king. Odoo provides several modules" +" to help you build your website content:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:61 +msgid "**Odoo Blogs**: write great contents." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:63 +msgid "" +"**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their " +"content is automatically indexed on the web page. Example: " +"`odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-" +"channel-1>`_" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:67 +msgid "" +"**Odoo Forum**: let your community create contents for you. Example: " +"`odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com" +" landing pages)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:71 +msgid "" +"**Odoo Mailing List Archive**: publish mailing list archives on your " +"website. Example: `odoo.com/groups/community-59 " +"<https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:77 +msgid "" +"The 404 page is a regular page, that you can edit like any other page in " +"Odoo. That way, you can build a great 404 page to redirect to the top " +"content of your website when visitors get lost in invalid URLs." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:82 +msgid "Use Social Networks" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:84 +msgid "" +"Social media is built for mass sharing. If lots of people share your content" +" on social media, then it's likely more people will link to it, and links " +"are a huge factor for SEO ranking." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:88 +msgid "Odoo embeds several tools to share content through social media:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:91 +msgid "Social Network" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:93 +msgid "" +"Odoo allows to link all your social network accounts in your website footer." +" All you have to do is to refer all your accounts in your company settings." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:100 +msgid "Social Share" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:102 +msgid "" +"Drop the building block *Share* on any page you want your visitors to share." +" By clicking the icon, they are prompted to share the page in their social " +"media wall." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:109 +msgid "" +"Most social media use a picture of the picture to decorate the share post. " +"Odoo uses the website logo by default but you can choose any other image of " +"your page in the Promote tool." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:117 +msgid "Facebook Page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:119 +msgid "" +"Drop the building block *Facebook Page* to display a widget of your Facebook" +" business page and encourage visitors to follow it. You can display the " +"timeline, the next events and the messages." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:124 +msgid "Twitter Scroller" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:126 +msgid "" +"Display the Twitter feeds with customer satifaction on your website. This " +"will increase the number of tweets and shares." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:130 +msgid "Test Your Website" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:132 +msgid "" +"You can compare how your website rank, in terms of SEO, against Odoo using " +"WooRank free services: `woorank.com <https://www.woorank.com>`_" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:137 +msgid "URLs Handling" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:139 +msgid "This section sheds some light on how Odoo makes URLs SEO-friendly." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:142 +msgid "URLs Structure" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:144 +msgid "A typical Odoo URL will look like this:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:146 +msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:148 +msgid "With the following components:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:150 +msgid "**https://** = Protocol" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:152 +msgid "**www.mysite.com** = your domain name" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:154 +msgid "" +"**/fr\\_FR** = page language. This part of the URL is removed if the visitor" +" browses the main language of the website Thus, the main version of this " +"page is: https://www.mysite.com/shop/product/my-great-product-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:159 +msgid "" +"**/shop/product** = every module defines its own namespace (/shop is for the" +" catalog of the eCommerce module, /shop/product is for a product page)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:163 +msgid "" +"**my-great-product** = by default, this is the slugified title of the " +"product this page refers to. But you can customize it for SEO purposes. A " +"product named \"Pain carré\" will be slugified to \"pain-carre\". Depending " +"on the namespace, this could be different objects (blog post, page title, " +"forum post, forum comment, product category, etc.)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:170 +msgid "**-31** = the unique ID of the product" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:172 +msgid "" +"Note that any dynamic component of an URL can be reduced to its ID. As an " +"example, the following URLs all do a 301 redirect to the above URL:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:175 +msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:177 +msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:179 +msgid "" +"http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product " +"name)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:182 +msgid "" +"Some URLs have several dynamic parts, like this one (a blog category and a " +"post):" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:185 +msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:187 +msgid "In the above example:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:189 +msgid "*Company News* is the title of the blog" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:191 +msgid "*The Odoo Story* is the title of a specific blog post" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:193 +msgid "" +"When an Odoo page has a pager, the page number is set directly in the URL " +"(does not have a GET argument). This allows every page to be indexed by " +"search engines. Example:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:197 +msgid "https://www.odoo.com/blog/page/3" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:200 +msgid "Changes in URLs & Titles" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:202 +msgid "" +"When the URL of a page changes (e.g. a more SEO friendly version of your " +"product name), you don't have to worry about updating all links:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:205 +msgid "Odoo will automatically update all its links to the new URL." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:207 +msgid "" +"If external websites still points to the old URL, a 301 redirect will be " +"done to route visitors to the new address of the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:210 +msgid "As an example, this URL:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:212 +msgid "http://mysite.com/shop/product/old-product-name-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:214 +msgid "Will automatically redirect to:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:216 +msgid "http://mysite.com/shop/product/new-and-better-product-name-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:218 +msgid "" +"In short, just change the title of a blog post or the name of a product, and" +" the changes will apply automatically everywhere in your website. The old " +"link still functions when used by external websites, via a 301 redirect, " +"maintaining the SEO link juice." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:224 +msgid "HTTPS" +msgstr "HTTPS" + +#: ../../content/applications/websites/website/pages/seo.rst:226 +msgid "" +"Search engines boost ranking of secure HTTPS/SSL websites. So, by default " +"all Odoo Online instances are fully based on HTTPS. If the visitor accesses " +"your website through a non HTTPS url, it gets a 301 redirect to its HTTPS " +"equivalent." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:232 +msgid "Links: Nofollow Strategy" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:234 +msgid "" +"The more a page is linked from external and quality websites, the better it " +"is for your SEO." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:237 +msgid "Here are Odoo strategies to manage links:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:239 +msgid "" +"Every link you add to your website is \"dofollow\", which means that this " +"link will contribute to the SEO Juice for the linked page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:243 +msgid "" +"Every link posted by a contributor (forum post, blog comment, etc.) that " +"links to your own website is \"dofollow\" too." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:246 +msgid "" +"But every link posted by a contributor that links to an external website is " +"\"nofollow\". In that way, you do not run the risk of people posting links " +"on your website to third-party websites which have a bad reputation." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:251 +msgid "" +"Note that, when using the forum, contributors having a lot of Karma can be " +"trusted. In such case, their links will not have any ``rel=\"nofollow\"`` " +"attribute." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:256 +msgid "Multi-Language Support" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:259 +msgid "Multi-Language URLs" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:261 +msgid "" +"If you run a website in multiple languages, the same content will be " +"available in different URLs, depending on the language used:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:264 +msgid "" +"https://www.mywebsite.com/shop/product/my-product-1 (main language, English " +"here)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:266 +msgid "" +"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French " +"version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:268 +msgid "" +"In this example, fr\\_FR is the language of the page. You can even have " +"several variations of the same language: pt\\_BR (Portuguese from Brazil) , " +"pt\\_PT (Portuguese from Portugal)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:273 +msgid "Language Annotation" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:275 +msgid "" +"To let search engines know that the second URL is the French translation of " +"the first URL, Odoo will add an HTML link element in the header. In the HTML" +" <head> section of the main version, Odoo automatically adds a link element " +"pointing to the translated versions of that webpage;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:280 +msgid "" +"<link rel=\"alternate\" hreflang=\"fr\" " +"href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:283 +msgid "With this approach:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:285 +msgid "" +"Search engines will redirect to the right language according to the visitor " +"language." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:288 +msgid "" +"You do not get penalized by search engines if your page is not translated " +"yet. Indeed, it's not a duplicated content, but a different version of the " +"same content." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:293 +msgid "Language Detection" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:295 +msgid "" +"When a visitor lands for the first time on your website (e.g. " +"yourwebsite.com/shop), they may automatically be redirected to a translated " +"version according to their browser language preference (e.g. " +"yourwebsite.com/fr\\_FR/shop)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:300 +msgid "" +"Next time, it keeps a cookie of the current language to avoid any " +"redirection." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:303 +msgid "" +"To force a visitor to stick to the default language, you can use the code of" +" the default language in your link, example: yourwebsite.com/en\\_US/shop. " +"This will always land visitors to the English version of the page, without " +"using the browser language preferences." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:310 +msgid "Page Speed" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:313 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:315 +msgid "" +"The time to load a page is an important criteria for search engines. A " +"faster website not only improves your visitor's experience, but gives you a " +"better page ranking. Some studies have shown that, if you divide the time to" +" load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor " +"abandonment rate is also divided by two. (25% to 12.5%). One extra second to" +" load a page could `cost $1.6b to Amazon in sales " +"<http://www.fastcompany.com/1825005/how-one-second-could-cost-" +"amazon-16-billion-sales>`__." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:326 +msgid "" +"Fortunately, Odoo does all the magic for you. Below, you will find the " +"tricks Odoo uses to speed up your page loading time. You can compare how " +"your website ranks using these two tools:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:330 +msgid "" +"`Google Page Speed " +"<https://developers.google.com/speed/pagespeed/insights/>`__" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:332 +msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:335 +msgid "Images" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:337 +msgid "" +"When you upload new images, Odoo automatically compresses them to reduce " +"their sizes (lossless compression for .PNG and .GIF and lossy compression " +"for .JPG)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:341 +msgid "" +"From the upload button, you have the option to keep the original image " +"unmodified if you prefer to optimize the quality of the image rather than " +"performance." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:349 +msgid "" +"Odoo compresses images when they are uploaded to your website, not when " +"requested by the visitor. Thus, it's possible that, if you use a third-party" +" theme, it will provide images that are not compressed efficiently. But all " +"images used in Odoo official themes have been compressed by default." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:355 +msgid "" +"When you click on an image, Odoo shows you the Alt and title attributes of " +"the ``<img>`` tag. You can click on it to set your own title and Alt " +"attributes for the image." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:362 +msgid "When you click on this link, the following window will appear:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:367 +msgid "" +"Odoo's pictograms are implemented using a font (`Font Awesome " +"<https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes)." +" Thus, you can use as many pictograms as you want in your page, they will " +"not result in extra requests to load the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:376 +msgid "Static Resources: CSS" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:378 +msgid "" +"All CSS files are pre-processed, concatenated, minified, compressed and " +"cached (server-side and browser-side). The result:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:381 +msgid "only one CSS file request is needed to load a page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:383 +msgid "" +"this CSS file is shared and cached amongst pages, so that when the visitor " +"clicks on another page, the browser doesn't have to even load a single CSS " +"resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:387 +msgid "this CSS file is optimized to be small" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:389 +msgid "" +"**Pre-processed:** The CSS framework used by Odoo is Bootstrap. Although a " +"theme might use another framework, most of `Odoo themes " +"<https://www.odoo.com/apps/themes>`__ extend and customize Bootstrap " +"directly. Since Odoo supports Less and Sass, you can modify CSS rules " +"instead of overwriting them through extra CSS lines, resulting in a smaller " +"file." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:396 +msgid "" +"**Concatenated:** every module or library you might use in Odoo has its own " +"set of CSS, Less or Sass files (eCommerce, blogs, themes, etc.). Having " +"several CSS files is great for the modularity, but not good for the " +"performance because most browsers can only perform 6 requests in parallel " +"resulting in lots of files loaded in series. The latency time to transfer a " +"file is usually much longer than the actual data transfer time, for small " +"files like .JS and .CSS. Thus, the time to load CSS resources depends more " +"on the number of requests to be done than the actual file size." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:406 +msgid "" +"To address this issue, all CSS / Less / Sass files are concatenated into a " +"single .CSS file to send to the browser. So a visitor has **only one .CSS " +"file to load** per page, which is particularly efficient. As the CSS is " +"shared amongst all pages, when the visitor clicks on another page, the " +"browser does not even have to load a new CSS file!" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:413 +msgid "**Both files in the <head>**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:413 +msgid "**What the visitor gets (only one file)**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:415 +msgid "/\\* From bootstrap.css \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:415 +#: ../../content/applications/websites/website/pages/seo.rst:416 +#: ../../content/applications/websites/website/pages/seo.rst:422 +#: ../../content/applications/websites/website/pages/seo.rst:448 +msgid ".text-muted {" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:416 +#: ../../content/applications/websites/website/pages/seo.rst:423 +#: ../../content/applications/websites/website/pages/seo.rst:449 +msgid "color: #666;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:417 +msgid "color: #777;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:417 +msgid "background: yellow" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:418 +msgid "background: yellow;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:418 +#: ../../content/applications/websites/website/pages/seo.rst:419 +#: ../../content/applications/websites/website/pages/seo.rst:424 +#: ../../content/applications/websites/website/pages/seo.rst:450 +msgid "}" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:421 +msgid "/\\* From my-theme.css \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:427 +msgid "" +"The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. " +"By doing this, additional page views from the same visitor will not have to " +"load CSS files at all. But some modules might include huge CSS/Javascript " +"resources that you do not want to prefetch at the first page because they " +"are too big. In this case, Odoo splits this resource into a second bundle " +"that is loaded only when the page using it is requested. An example of this " +"is the backend that is only loaded when the visitor logs in and accesses the" +" backend (/web)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:437 +msgid "" +"If the CSS file is very big, Odoo will split it into two smaller files to " +"avoid the 4095 selectors limit per sheet of Internet Explorer. But most " +"themes fit below this limit." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:441 +msgid "" +"**Minified:** After being pre-processed and concatenated, the resulting CSS " +"is minified to reduce its size." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:445 +msgid "**Before minification**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:445 +msgid "**After minification**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:447 +msgid "/\\* some comments \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:447 +msgid ".text-muted {color: #666}" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:453 +msgid "" +"The final result is then compressed, before being delivered to the browser." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:456 +msgid "" +"Then, a cached version is stored server-side (so we do not have to pre-" +"process, concatenate, minify at every request) and browser-side (so the same" +" visitor will load the CSS only once for all pages they visit)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:462 +msgid "Static Resources: Javascript" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:464 +msgid "" +"As with CSS resources, Javascript resources are also concatenated, minified," +" compressed and cached (server-side and browser-side)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:467 +msgid "Odoo creates three Javascript bundles:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:469 +msgid "" +"One for all pages of the website (including code for parallax effects, form " +"validation, etc.)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:472 +msgid "" +"One for common Javascript code shared among frontend and backend (Bootstrap)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:475 +msgid "" +"One for backend specific Javascript code (Odoo Web Client interface for your" +" employees using Odoo)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:478 +msgid "" +"Most visitors of your website will only need the first two bundles, " +"resulting in a maximum of two Javascript files to load to render one page. " +"As these files are shared across all pages, further clicks by the same " +"visitor will not load any other Javascript resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:484 +msgid "" +"If you work on :ref:`developer mode <developer-mode>`, the CSS and " +"Javascript are neither concatenated, nor minified. Thus, it's much slower. " +"But it allows you to easily debug with the Chrome debugger as CSS and " +"Javascript resources are not transformed from their original versions." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:489 +msgid "CDN" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:491 +msgid "" +"If you activate the CDN feature in Odoo, static resources (Javascript, CSS, " +"images) are loaded from a Content Delivery Network. Using a Content Delivery" +" Network has three advantages:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:495 +msgid "" +"Load resources from a nearby server (most CDN have servers in main countries" +" around the globe)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:498 +msgid "" +"Cache resources efficiently (no computation resources usage on your own " +"server)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:501 +msgid "" +"Split the resource loading on different services allowing to load more " +"resources in parallel (since the Chrome limit of 6 parallel requests is by " +"domain)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:505 +msgid "" +"You can configure your CDN options from the **Website Admin** app, using the" +" Configuration menu. Here is an example of configuration you can use:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:512 +msgid "HTML Pages" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:514 +msgid "" +"The HTML pages can be compressed, but this is usually handled by your web " +"server (NGINX or Apache)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:517 +msgid "" +"The Odoo Website builder has been optimized to guarantee clean and short " +"HTML code. Building blocks have been developed to produce clean HTML code, " +"usually using Bootstrap and the HTML editor." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:521 +msgid "" +"As an example, if you use the color picker to change the color of a " +"paragraph to the primary color of your website, Odoo will produce the " +"following code:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:525 +msgid "``<p class=\"text-primary\">My Text</p>``" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:527 +msgid "" +"Whereas most HTML editors (such as CKEditor) will produce the following " +"code:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:530 +msgid "``<p style=\"color: #AB0201\">My Text</p>``" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:533 +msgid "Responsive Design" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:535 +msgid "" +"Websites that are not mobile-friendly are negatively impacted in search " +"engine rankings. All Odoo themes rely on Bootstrap to render efficiently " +"according to the device: desktop, tablet or mobile." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:542 +msgid "" +"As all Odoo modules share the same technology, absolutely all pages in your " +"website are mobile friendly." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:546 +msgid "Browser Caching" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:548 +msgid "" +"Javascript, images and CSS resources have an URL that changes dynamically " +"when their content change. As an example, all CSS files are loaded through " +"this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css " +"<http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. " +"The ``457-0da1d9d`` part of this URL will change if you modify the CSS of " +"your website." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:555 +msgid "" +"This allows Odoo to set a very long cache delay (XXX) on these resources: " +"XXX secs, while being updated instantly if you update the resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:560 +msgid "Scalability" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:562 +msgid "" +"In addition to being fast, Odoo is also more scalable than traditional CMS " +"and eCommerce (Drupal, Wordpress, Magento, Prestashop)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:565 +msgid "" +"Here is the slide that summarizes the scalability of Odoo Website & " +"eCommerce." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:571 +msgid "Search Engines Files" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:574 +msgid "Sitemap" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:576 +msgid "" +"The sitemap points out pages to index to search engine robots. Odoo " +"generates a ``/sitemap.xml`` file automatically for you. For performance " +"reasons, this file is cached and updated every 12 hours." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:580 +msgid "" +"By default, all URLs will be in a single ``/sitemap.xml`` file, but if you " +"have a lot of pages, Odoo will automatically create a Sitemap Index file, " +"respecting the `sitemaps.org protocol " +"<http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 " +"chunks per file." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:586 +msgid "Every sitemap entry has 4 attributes that are computed automatically:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:588 +msgid "``<loc>`` : the URL of a page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:590 +msgid "" +"``<lastmod>`` : last modification date of the resource, computed " +"automatically based on related object. For a page related to a product, this" +" could be the last modification date of the product or the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:595 +msgid "" +"``<priority>`` : modules may implement their own priority algorithm based on" +" their content (example: a forum might assign a priority based on the number" +" of votes on a specific post). The priority of a static page is defined by " +"it's priority field, which is normalized (16 is the default)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:602 +msgid "Structured Data Markup" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:604 +msgid "" +"Structured Data Markup is used to generate Rich Snippets in search engine " +"results. It is a way for website owners to send structured data to search " +"engine robots; helping them understand your content and create well-" +"presented search results." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:609 +msgid "" +"Google supports a number of rich snippets for content types, including: " +"Reviews, People, Products, Businesses, Events and Organizations." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:612 +msgid "" +"Odoo implements micro data as defined in the `schema.org " +"<http://schema.org>`__ specification for events, eCommerce products, forum " +"posts and contact addresses. This allows your product pages to be displayed " +"in Google using extra information like the price and rating of a product:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:622 +msgid "robots.txt" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:624 +msgid "" +"When indexing your website, search engines take a first look at the general " +"indexing rules of the ``/robots.txt`` file (allowed robots, sitemap path, " +"etc.). Odoo automatically creates it. Its content is:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:628 +msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:631 +msgid "" +"It means that all robots are allowed to index your website and there is no " +"other indexing rule than specified in the sitemap to be found at following " +"address." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:635 +msgid "" +"You can customize the file *robots* in :ref:`developer mode <developer-" +"mode>` from *Settings --> Technical --> User Interface --> Views* (exclude " +"robots, exclude some pages, redirect to a custom Sitemap). Make the Model " +"Data of the view *Non Updatable* to not reset the file after system " +"upgrades." +msgstr "" + +#: ../../content/applications/websites/website/reporting.rst:5 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:3 +msgid "How to track your website's traffic in Google Analytics" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:5 +msgid "To follow your website's traffic with Google Analytics:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:7 +msgid "" +"`Create a Google Analytics account <https://www.google.com/analytics/>`__ if" +" you don't have any." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:10 +msgid "" +"Go through the creation form and accept the conditions to get the tracking " +"ID." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:15 +msgid "Copy the tracking ID to insert it in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:20 +msgid "" +"Go to the *Configuration* menu of your Odoo's Website app. In the settings, " +"turn on Google Analytics and paste the tracking ID. Then save the page." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:27 +msgid "" +"To make your first steps in Google Analytics, refer to `Google Documentation" +" <https://support.google.com/analytics/answer/1008015?hl=en/>`_." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics.rst:32 +msgid ":doc:`google_analytics_dashboard`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:3 +msgid "How to track your website traffic from your Odoo Dashboard" +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:6 +msgid "" +"It is not possible anymore for new Google Analytics accounts to integrate " +"their **Google Analytics Dashboard** inside their **Odoo Dashboard**. Google" +" deprecated **Universal Analytics** which won't be supported anymore in " +"`July 2023 <https://support.google.com/analytics/answer/11583528>`_. They " +"are replacing it with **Analytics 4**. New accounts are already using it." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:12 +msgid "" +"**Analytics 4** `doesn't allow " +"<https://issuetracker.google.com/issues/233738709?pli=1>`_ its dashboard to " +"be integrated in external websites." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:15 +msgid "" +"You now have to check your Analytics data directly in the Google Platform as" +" it won't be possible in Odoo anymore." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:18 +msgid "" +"Accounts created before `October 2020 " +"<https://support.google.com/analytics/answer/11583832>`_ should still be " +"using **Universal Analytics** and be able to integrate their dashboard on " +"external website until the official end of support `around mid 2023 " +"<https://developers.googleblog.com/2022/03/gis-jsweb-authz-" +"migration.html>`_." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:23 +msgid "" +"You can follow your traffic statistics straight from your Odoo Website " +"Dashboard thanks to Google Analytics." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:26 +msgid "" +"A preliminary step is creating a Google Analytics account and entering the " +"tracking ID in your Website's settings (see :doc:`google_analytics`)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:29 +msgid "" +"Go to `Google APIs platform <https://console.developers.google.com>`__ to " +"generate Analytics API credentials. Log in with your Google account." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:32 +msgid "Select Analytics API." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:37 +msgid "" +"Create a new project and give it a name (e.g. Odoo). This project is needed " +"to store your API credentials." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:43 +msgid "Enable the API." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:48 +msgid "Create credentials to use in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:53 +msgid "" +"Select *Web browser (Javascript)* as calling source and *User data* as kind " +"of data." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:59 +msgid "" +"Then you can create a Client ID. Enter the name of the application (e.g. " +"Odoo) and the allowed pages on which you will be redirected. The *Authorized" +" JavaScript origin* is your Odoo's instance URL. The *Authorized redirect " +"URI* is your Odoo's instance URL followed by " +"'/google_account/authentication'." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:69 +msgid "" +"Go through the Consent Screen step by entering a product name (e.g. Google " +"Analytics in Odoo). Feel free to check the customizations options but this " +"is not mandatory. The Consent Screen will only show up when you enter the " +"Client ID in Odoo for the first time." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:74 +msgid "" +"Finally you are provided with your Client ID. Copy and paste it in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:79 +msgid "" +"Open your Website Dashboard in Odoo and link your Analytics account to past " +"your Client ID." +msgstr "" + +#: ../../content/applications/websites/website/reporting/google_analytics_dashboard.rst:85 +msgid "As a last step, authorize Odoo to access Google API." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:3 +msgid "Link trackers" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:5 +msgid "" +"Link Trackers allow you to track your marketing campaigns (emails, banner " +"ads, blog posts, social media posts, affiliate links, etc.). This way, you " +"are able to identify your best traffic sources and make informed decisions " +"about the distribution of your marketing budget." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:12 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Settings` and activate " +"*Link Trackers*." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst-1 +msgid "" +"View of Website settings page emphasizing the link trackers field in Odoo " +"Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:19 +msgid "Set up traceable URLs" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:21 +msgid "" +"Go to :menuselection:`Website --> Go to website --> Promote --> Track this " +"page`. Here, you are able to get a specific tracked URL based on the " +"campaign, medium, and source being used." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst-1 +msgid "View of the link tracker fields for Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:28 +msgid "" +"**URL**: url of the page you want to track (e.g. the home page or a " +"product's page)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:29 +msgid "**Campaign**: context of your link (e.g. a special promotion)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:30 +msgid "" +"**Medium**: channel used to share (deliver) your link (e.g. an email or a " +"Facebook ad)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:31 +msgid "" +"**Source**: platform where the traffic originates (e.g. Google or Twitter)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:33 +msgid "" +"Now, click on *Get tracked link* to generate a URL that you can post or send" +" by the source you have decided on." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:37 +msgid "Follow-up on tracked links" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:39 +msgid "" +"To look at statistics of your links, go to :menuselection:`Website --> Go to" +" website --> Promote --> Track this page`. Besides being able to see the " +"*Most Clicked* and *Recently Used* links, you can also see complete " +"statistics by clicking on *Stats*, including the number of clicks, and the " +"country of origin for those clicks." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst-1 +msgid "" +"View of the tracked list emphasizing the statistics buttons in Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:50 +msgid "You can also access the link tracker on *odoo.com/r* via your browser." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:51 +msgid "" +"Activate the developer mode (:menuselection:`Settings --> Activate the " +"developer mode`) and get access to the *Link Tracker* module and its back-" +"end functionalities." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:53 +msgid "" +"Integrated with :doc:`Google Analytics <google_analytics>`, those trackers " +"allow you to see the number of clicks and visitors to keep you on top of " +"your marketing campaigns." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:55 +msgid "" +"The integration with the :doc:`CRM " +"</applications/sales/crm/track_leads/prospect_visits>` application allows " +"you to understand where your leads and opportunities are coming from." +msgstr "" diff --git a/locale/ro/LC_MESSAGES/finance.po b/locale/ro/LC_MESSAGES/finance.po index 9db2bb42a..abd1d418b 100644 --- a/locale/ro/LC_MESSAGES/finance.po +++ b/locale/ro/LC_MESSAGES/finance.po @@ -5,24 +5,24 @@ # # Translators: # Simonel Criste <simi@erpsystems.ro>, 2023 -# Vacaru Adrian <adrian.vacaru@gmail.com>, 2023 # Fekete Mihai <mihai.fekete@forestandbiomass.ro>, 2023 # Fenyedi Levente, 2023 # Emanuel Bruda, 2023 # Hongu Cosmin <cosmin513@gmail.com>, 2023 # Martin Trigaux, 2023 # Cozmin Candea <office@terrabit.ro>, 2023 -# Dorin Hongu <dhongu@gmail.com>, 2023 # Foldi Robert <foldirobert@nexterp.ro>, 2023 +# Vacaru Adrian <adrian.vacaru@gmail.com>, 2023 +# Dorin Hongu <dhongu@gmail.com>, 2023 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:47+0000\n" -"Last-Translator: Foldi Robert <foldirobert@nexterp.ro>, 2023\n" +"Last-Translator: Dorin Hongu <dhongu@gmail.com>, 2023\n" "Language-Team: Romanian (https://app.transifex.com/odoo/teams/41243/ro/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -584,7 +584,6 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:18 #: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:16 #: ../../content/applications/finance/accounting/reporting/budget.rst:11 -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:19 #: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 #: ../../content/applications/finance/accounting/taxes.rst:53 #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 @@ -7329,33 +7328,26 @@ msgstr "" msgid "" "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " "open the journal you want to edit, and select a currency in the field " -":guilabel:`Currency`. If left empty, all active currencies are handled " -"instead of just one." +":guilabel:`Currency`." msgstr "" -"Pentru a face acest lucru, accesați :menuselection:`Contabilitate --> " -"Configurare --> Jurnale`, deschideți jurnalul pe care doriți să-l editați și" -" selectați o monedă în câmpul :guilabel:`Moneda`. Dacă este lăsat gol, toate" -" monedele active sunt gestionate în locul uneia singure." #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency for the journal to handle." msgstr "Selectați moneda pentru jurnalul care gestionează." -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:114 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 msgid "Multi-currency accounting" msgstr "Contabilitate multi-moneda" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:119 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 msgid "Invoices, bills, and other documents" msgstr "Facturi, facturi și alte documente" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:121 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 msgid "" "For all documents, you can select the currency and journal to use for the " -"transaction." +"transaction on the document itself." msgstr "" -"Pentru toate documentele, puteți selecta moneda și jurnalul pe care să le " -"utilizați pentru tranzacție." #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency and journal to use." @@ -11435,40 +11427,281 @@ msgstr "Intrastat" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 msgid "" -"**Intrastat** is the system for data collection and statistic production of " -"goods traded among the EU Member States. Organizations whose annual trade " -"surpasses a certain threshold must provide data about the goods traded with " -"other EU countries." +"`Intrastat <https://ec.europa.eu/eurostat/statistics-" +"explained/index.php?title=Glossary:Intrastat>`_ is the data collection and " +"statistics production system for goods traded among EU member states. It " +"collects data on:" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:10 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:9 msgid "" -"`Eurostat Statistics Explained - Glossary: Intrastat " -"<https://ec.europa.eu/eurostat/statistics-" -"explained/index.php?title=Glossary:Intrastat>`_" +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:14 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:11 msgid "" -"As of January 1, 2022, the reporting requirements have changed. One main " -"modification concerns the transaction codes which are now switching to a " -"2-digits format. All transactions recorded after this date have to follow " -"the new system’s rules." +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:21 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:13 +msgid "Returns of goods." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:16 msgid "" -"Go to :menuselection:`Accounting --> Settings --> Customer Invoices`, then " -"enable **Intrastat** and *Save*. Once the Intrastat has been activated you " -"are able to choose the **Default incoterm**." +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"<http://data.europa.eu/eli/reg/2019/2152/2022-01-01>`_, preferring instead " +"*intra-Union trade in goods statistics*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:23 +msgid "General configuration" msgstr "" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:25 msgid "" -"If you created your Odoo database prior to **January 13, 2022**, please " -":ref:`upgrade <general/upgrade>` the ``account_intrastat`` module to add the" -" new transaction codes and :ref:`install <general/install>` the " -"``account_intrastat_expiry`` module to archive the old codes." +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the **Customer Invoices** section, tick " +":guilabel:`Intrastat` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:31 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located, and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:34 +msgid "" +"If your warehouses are located in multiple regions, you can define the " +"region code for each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:43 +msgid "Default Incoterm" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "" +"You can set **default Incoterms** for your company by selecting an Intrastat" +" **code** in the :guilabel:`Default Incoterm` field of the **Customer " +"Invoices** section, and then clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "Product configuration" +msgstr "Configurarea produsului" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:54 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:59 +msgid "Commodity code" +msgstr "Cod Marfă" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:61 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature <https://taxation-customs.ec.europa.eu/customs-4/calculation-" +"customs-duties/customs-tariff/combined-nomenclature_en>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:64 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:68 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"<https://www.nbb.be/en/statistics/foreign-trade/nomenclature-and-codes>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:74 +msgid "Country of origin" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:76 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:82 +msgid "Invoices and bills configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:84 +msgid "" +"Once products are properly configured, several settings must be enabled on " +"the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:90 +msgid "Transaction code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:92 +msgid "" +"Transaction codes are used to identify a transaction's nature. To set a " +"transaction code on an invoice line, create an invoice or bill, click the " +":guilabel:`⋮` button, tick :guilabel:`Intrastat`, and use the newly-added " +":guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:101 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"<https://www.nbb.be/doc/dd/onegate/data/new_natures_of_transaction_2022_en.pdf>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:107 +msgid "Partner country" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:109 +msgid "" +"The partner country is the vendor's or customer's country, depending on " +"whether it is an invoice or bill. It is automatically filled in using the " +":guilabel:`Country` field in the **contact form** of the partner." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:113 +msgid "" +"To edit the partner country manually, click on the :guilabel:`Other Info` " +"tab when on an invoice or bill, and select the :guilabel:`Intrastat " +"Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "Transport code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:121 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch). Once you have selected a :ref:`partner" +" country <intrastat/partner-country>`, the :guilabel:`Intrastat Transport " +"Mode` becomes available." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "Value of the goods" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:130 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "Partner configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:138 +msgid "" +"Two fields from the partner's **contact form** are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set <intrastat/partner-country>` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:143 +msgid "Generate the Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:145 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration <intrastat/general-configuration>` and the " +"information on the :ref:`products <intrastat/product-configuration>`, " +":ref:`invoices and bills <intrastat/invoice-bill-configuration>`, and " +":ref:`partners <intrastat/partner>`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"Export the report as a PDF, XLSX, or XML file to submit it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:153 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:155 +msgid "Invoice or bill reference number;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:156 +msgid "" +":guilabel:`System`, which is a code automatically generated depending on " +"whether the document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:158 +msgid "" +":ref:`Country <intrastat/partner-country>`, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:160 +msgid ":ref:`Transaction Code <intrastat/transaction-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:161 +msgid "" +":ref:`Region Code <intrastat/region-code>` (if your company is located in " +"Belgium);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:162 +msgid ":ref:`Commodity Code <intrastat/commodity-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:163 +msgid ":ref:`Origin Country <intrastat/origin-country>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:164 +msgid ":ref:`Partner VAT <intrastat/partner>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid ":ref:`Transport Code <intrastat/transport-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:166 +msgid "" +":ref:`Value <intrastat/value>`, which is always expressed in EUR even if the" +" original invoice or bill used another currency." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 @@ -22872,6 +23105,7 @@ msgid "2-digits comparison" msgstr "" #: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:61 msgid "Template" msgstr "Șablon" @@ -30863,7 +31097,7 @@ msgid "" msgstr "" #: ../../content/applications/finance/payment_acquirers.rst:267 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:40 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:38 msgid "Configuration tab" msgstr "Tabul Configurare" @@ -31028,7 +31262,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/adyen.rst:10 #: ../../content/applications/finance/payment_acquirers/adyen.rst:137 #: ../../content/applications/finance/payment_acquirers/alipay.rst:36 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:53 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:51 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:47 #: ../../content/applications/finance/payment_acquirers/mollie.rst:31 #: ../../content/applications/finance/payment_acquirers/paypal.rst:162 @@ -31412,42 +31646,242 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:31 msgid "" -"If you are trying Authorize.Net as a test, with a *sandbox account*, change " -"the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a" -" test Odoo database, rather than on your main database." +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." msgstr "" -"Daca incercati Authorize.Net ca un test, cu un *cont sandbox*, schimbati " -":guilabel:`State` la :guilabel:`Test Mode`. Va recomandam sa faceti acest " -"pas pe o baza de date de test Odoo, in loc de pe baza de date principala" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:35 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:34 msgid "" -"If you set :guilabel:`Test Mode` on Odoo and use an authorize.net account " -"instead of a sandbox.authorize.net account, it results in the following " -"error: *The merchant login ID or password is invalid or the account is " -"inactive*." +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." msgstr "" -"Daca setati :guilabel:`Test Mode` in Odoo si folositi un cont authorize.net " -"in loc de un cont sandbox.authorize.net, rezulta urmatoarea eroare: *The " -"merchant login ID or password is invalid or the account is inactive*." -#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:41 msgid "Place a hold on a card" msgstr "Aplicati o retinere pe un card" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:45 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 msgid "" -"With Authorize.net, you can enable the :ref:`manual capture " +"With Authorize.Net, you can enable the :ref:`manual capture " "<payment_acquirers/features/manual_capture>`. If enabled, the funds are " "reserved for 30 days on the customer's card, but not charged yet." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:50 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:48 msgid "" "After **30 days**, the transaction is **voided automatically** by " -"Authorize.net." +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:54 +msgid "Import an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:57 +msgid "Export from Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:63 +msgid "" +"`Download the Excel import template " +"<https://docs.google.com/spreadsheets/d/1CMVtBWLLVIrUpYA92paw-" +"cL7-WdKLbaa/edit?usp=share_link&ouid=105295722917050444558&rtpof=true&sd=true>`_" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:65 +msgid "To export a statement:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:67 +msgid "Log in to Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:68 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:69 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:71 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template <authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:84 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:87 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:89 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:90 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:92 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:93 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:95 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"<authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:97 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template <authorize-import-template>`. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:104 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:107 +msgid "Import into Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:109 +msgid "To import the data into Odoo:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:111 +msgid "Open the :ref:`Excel import template <authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:112 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:114 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:117 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:118 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:120 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template <authorize-import-template>` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:125 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template <authorize-import-template>` for each invoice." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 +msgid "Chargeback description" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:133 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:135 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:137 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:139 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:141 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:143 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:148 +msgid "" +"List of `eCheck.Net return codes " +"<https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001293>`_" msgstr "" -"Dupa **30 de zile**, tranzactia este **voided automat** de Authorize.net." #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:3 msgid "Buckaroo" diff --git a/locale/uk/LC_MESSAGES/finance.po b/locale/uk/LC_MESSAGES/finance.po index c6ebed727..0ec9da319 100644 --- a/locale/uk/LC_MESSAGES/finance.po +++ b/locale/uk/LC_MESSAGES/finance.po @@ -6,17 +6,17 @@ # Translators: # Zoriana Zaiats, 2021 # Bohdan Lisnenko, 2021 -# Alina Lisnenko <alina.lisnenko@erp.co.ua>, 2023 # Martin Trigaux, 2023 +# Alina Lisnenko <alina.lisnenko@erp.co.ua>, 2023 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:47+0000\n" -"Last-Translator: Martin Trigaux, 2023\n" +"Last-Translator: Alina Lisnenko <alina.lisnenko@erp.co.ua>, 2023\n" "Language-Team: Ukrainian (https://app.transifex.com/odoo/teams/41243/uk/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -534,7 +534,6 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:18 #: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:16 #: ../../content/applications/finance/accounting/reporting/budget.rst:11 -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:19 #: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 #: ../../content/applications/finance/accounting/taxes.rst:53 #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 @@ -6499,26 +6498,25 @@ msgstr "" msgid "" "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " "open the journal you want to edit, and select a currency in the field " -":guilabel:`Currency`. If left empty, all active currencies are handled " -"instead of just one." +":guilabel:`Currency`." msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency for the journal to handle." msgstr "" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:114 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 msgid "Multi-currency accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:119 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 msgid "Invoices, bills, and other documents" msgstr "" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:121 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 msgid "" "For all documents, you can select the currency and journal to use for the " -"transaction." +"transaction on the document itself." msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 @@ -10245,40 +10243,281 @@ msgstr "Intrastat" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 msgid "" -"**Intrastat** is the system for data collection and statistic production of " -"goods traded among the EU Member States. Organizations whose annual trade " -"surpasses a certain threshold must provide data about the goods traded with " -"other EU countries." +"`Intrastat <https://ec.europa.eu/eurostat/statistics-" +"explained/index.php?title=Glossary:Intrastat>`_ is the data collection and " +"statistics production system for goods traded among EU member states. It " +"collects data on:" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:10 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:9 msgid "" -"`Eurostat Statistics Explained - Glossary: Intrastat " -"<https://ec.europa.eu/eurostat/statistics-" -"explained/index.php?title=Glossary:Intrastat>`_" +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:14 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:11 msgid "" -"As of January 1, 2022, the reporting requirements have changed. One main " -"modification concerns the transaction codes which are now switching to a " -"2-digits format. All transactions recorded after this date have to follow " -"the new system’s rules." +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" msgstr "" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:21 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:13 +msgid "Returns of goods." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:16 msgid "" -"Go to :menuselection:`Accounting --> Settings --> Customer Invoices`, then " -"enable **Intrastat** and *Save*. Once the Intrastat has been activated you " -"are able to choose the **Default incoterm**." +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"<http://data.europa.eu/eli/reg/2019/2152/2022-01-01>`_, preferring instead " +"*intra-Union trade in goods statistics*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:23 +msgid "General configuration" msgstr "" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:25 msgid "" -"If you created your Odoo database prior to **January 13, 2022**, please " -":ref:`upgrade <general/upgrade>` the ``account_intrastat`` module to add the" -" new transaction codes and :ref:`install <general/install>` the " -"``account_intrastat_expiry`` module to archive the old codes." +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the **Customer Invoices** section, tick " +":guilabel:`Intrastat` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:31 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located, and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:34 +msgid "" +"If your warehouses are located in multiple regions, you can define the " +"region code for each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:43 +msgid "Default Incoterm" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "" +"You can set **default Incoterms** for your company by selecting an Intrastat" +" **code** in the :guilabel:`Default Incoterm` field of the **Customer " +"Invoices** section, and then clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "Product configuration" +msgstr "Налаштування товару" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:54 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:59 +msgid "Commodity code" +msgstr "Код товару" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:61 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature <https://taxation-customs.ec.europa.eu/customs-4/calculation-" +"customs-duties/customs-tariff/combined-nomenclature_en>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:64 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:68 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"<https://www.nbb.be/en/statistics/foreign-trade/nomenclature-and-codes>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:74 +msgid "Country of origin" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:76 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:82 +msgid "Invoices and bills configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:84 +msgid "" +"Once products are properly configured, several settings must be enabled on " +"the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:90 +msgid "Transaction code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:92 +msgid "" +"Transaction codes are used to identify a transaction's nature. To set a " +"transaction code on an invoice line, create an invoice or bill, click the " +":guilabel:`⋮` button, tick :guilabel:`Intrastat`, and use the newly-added " +":guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:101 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"<https://www.nbb.be/doc/dd/onegate/data/new_natures_of_transaction_2022_en.pdf>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:107 +msgid "Partner country" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:109 +msgid "" +"The partner country is the vendor's or customer's country, depending on " +"whether it is an invoice or bill. It is automatically filled in using the " +":guilabel:`Country` field in the **contact form** of the partner." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:113 +msgid "" +"To edit the partner country manually, click on the :guilabel:`Other Info` " +"tab when on an invoice or bill, and select the :guilabel:`Intrastat " +"Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "Transport code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:121 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch). Once you have selected a :ref:`partner" +" country <intrastat/partner-country>`, the :guilabel:`Intrastat Transport " +"Mode` becomes available." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "Value of the goods" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:130 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "Partner configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:138 +msgid "" +"Two fields from the partner's **contact form** are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set <intrastat/partner-country>` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:143 +msgid "Generate the Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:145 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration <intrastat/general-configuration>` and the " +"information on the :ref:`products <intrastat/product-configuration>`, " +":ref:`invoices and bills <intrastat/invoice-bill-configuration>`, and " +":ref:`partners <intrastat/partner>`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"Export the report as a PDF, XLSX, or XML file to submit it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:153 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:155 +msgid "Invoice or bill reference number;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:156 +msgid "" +":guilabel:`System`, which is a code automatically generated depending on " +"whether the document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:158 +msgid "" +":ref:`Country <intrastat/partner-country>`, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:160 +msgid ":ref:`Transaction Code <intrastat/transaction-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:161 +msgid "" +":ref:`Region Code <intrastat/region-code>` (if your company is located in " +"Belgium);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:162 +msgid ":ref:`Commodity Code <intrastat/commodity-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:163 +msgid ":ref:`Origin Country <intrastat/origin-country>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:164 +msgid ":ref:`Partner VAT <intrastat/partner>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid ":ref:`Transport Code <intrastat/transport-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:166 +msgid "" +":ref:`Value <intrastat/value>`, which is always expressed in EUR even if the" +" original invoice or bill used another currency." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 @@ -18118,7 +18357,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:686 msgid "Claim" -msgstr "" +msgstr "Претензія" #: ../../content/applications/finance/fiscal_localizations/chile.rst:688 msgid "" @@ -20850,6 +21089,7 @@ msgid "2-digits comparison" msgstr "" #: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:61 msgid "Template" msgstr "Шаблон " @@ -28977,7 +29217,7 @@ msgid "" msgstr "" #: ../../content/applications/finance/payment_acquirers.rst:267 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:40 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:38 msgid "Configuration tab" msgstr "" @@ -29126,7 +29366,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/adyen.rst:10 #: ../../content/applications/finance/payment_acquirers/adyen.rst:137 #: ../../content/applications/finance/payment_acquirers/alipay.rst:36 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:53 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:51 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:47 #: ../../content/applications/finance/payment_acquirers/mollie.rst:31 #: ../../content/applications/finance/payment_acquirers/paypal.rst:162 @@ -29450,34 +29690,241 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:31 msgid "" -"If you are trying Authorize.Net as a test, with a *sandbox account*, change " -"the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a" -" test Odoo database, rather than on your main database." +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:35 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:34 msgid "" -"If you set :guilabel:`Test Mode` on Odoo and use an authorize.net account " -"instead of a sandbox.authorize.net account, it results in the following " -"error: *The merchant login ID or password is invalid or the account is " -"inactive*." +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:41 msgid "Place a hold on a card" msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:45 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 msgid "" -"With Authorize.net, you can enable the :ref:`manual capture " +"With Authorize.Net, you can enable the :ref:`manual capture " "<payment_acquirers/features/manual_capture>`. If enabled, the funds are " "reserved for 30 days on the customer's card, but not charged yet." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:50 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:48 msgid "" "After **30 days**, the transaction is **voided automatically** by " -"Authorize.net." +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:54 +msgid "Import an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:57 +msgid "Export from Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:63 +msgid "" +"`Download the Excel import template " +"<https://docs.google.com/spreadsheets/d/1CMVtBWLLVIrUpYA92paw-" +"cL7-WdKLbaa/edit?usp=share_link&ouid=105295722917050444558&rtpof=true&sd=true>`_" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:65 +msgid "To export a statement:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:67 +msgid "Log in to Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:68 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:69 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:71 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template <authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:84 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:87 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:89 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:90 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:92 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:93 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:95 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"<authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:97 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template <authorize-import-template>`. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:104 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:107 +msgid "Import into Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:109 +msgid "To import the data into Odoo:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:111 +msgid "Open the :ref:`Excel import template <authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:112 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:114 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:117 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:118 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:120 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template <authorize-import-template>` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:125 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template <authorize-import-template>` for each invoice." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 +msgid "Chargeback description" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:133 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:135 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:137 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:139 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:141 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:143 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:148 +msgid "" +"List of `eCheck.Net return codes " +"<https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001293>`_" msgstr "" #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:3 diff --git a/locale/zh_CN/LC_MESSAGES/finance.po b/locale/zh_CN/LC_MESSAGES/finance.po index 782f126ab..fc8f507ec 100644 --- a/locale/zh_CN/LC_MESSAGES/finance.po +++ b/locale/zh_CN/LC_MESSAGES/finance.po @@ -19,7 +19,6 @@ # 黎伟杰 <674416404@qq.com>, 2021 # Connie Xiao <connie.xiao@elico-corp.com>, 2021 # Richard yang <yanglinqiangdata@hotmail.com>, 2021 -# Gary Wei <Gary.wei@elico-corp.com>, 2021 # Cécile Collart <cco@odoo.com>, 2021 # Norman Chang <xromanxmu@gmail.com>, 2021 # 湘子 南 <1360857908@qq.com>, 2021 @@ -31,7 +30,6 @@ # Jeana Jiang, 2022 # 老窦 北京 <2662059195@qq.com>, 2022 # diaojiaolou <124412206@qq.com>, 2022 -# 稀饭~~ <wangwhai@qq.com>, 2022 # 苏州远鼎 <tiexinliu@126.com>, 2022 # Shaw J <arronnjxj@gmail.com>, 2023 # Jeffery CHEN <jeffery9@gmail.com>, 2023 @@ -39,6 +37,8 @@ # Raymond Yu <cl_yu@hotmail.com>, 2023 # Martin Trigaux, 2023 # Datasource International <Hennessy@datasourcegroup.com>, 2023 +# Gary Wei <Gary.wei@elico-corp.com>, 2023 +# 稀饭~~ <wangwhai@qq.com>, 2023 # Emily Jia <eji@odoo.com>, 2023 # #, fuzzy @@ -46,7 +46,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-07 06:24+0000\n" +"POT-Creation-Date: 2023-07-25 07:08+0000\n" "PO-Revision-Date: 2021-11-02 08:47+0000\n" "Last-Translator: Emily Jia <eji@odoo.com>, 2023\n" "Language-Team: Chinese (China) (https://app.transifex.com/odoo/teams/41243/zh_CN/)\n" @@ -570,7 +570,6 @@ msgstr "要编辑现有银行日记账，跳转至：菜单选择：`会计--> #: ../../content/applications/finance/accounting/reporting/analytic/purchases_expenses.rst:18 #: ../../content/applications/finance/accounting/reporting/analytic/timesheets.rst:16 #: ../../content/applications/finance/accounting/reporting/budget.rst:11 -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:19 #: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 #: ../../content/applications/finance/accounting/taxes.rst:53 #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 @@ -6354,28 +6353,26 @@ msgstr "如果为某个**日记账**设置了币种，则该日记账仅处理 msgid "" "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " "open the journal you want to edit, and select a currency in the field " -":guilabel:`Currency`. If left empty, all active currencies are handled " -"instead of just one." +":guilabel:`Currency`." msgstr "" -"要为日记账设置币种，跳转至:menuselection:`会计-->配置-->日记账`，打开要编辑的日记账，在:guilable:`币种`栏中选择币种。如果留空，则处理所有活跃币种，而非某一币种。" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency for the journal to handle." msgstr "为日记账选择要处理的币种。" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:114 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 msgid "Multi-currency accounting" msgstr "多币种会计" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:119 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 msgid "Invoices, bills, and other documents" msgstr "发票、账单和其他文件" -#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:121 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 msgid "" "For all documents, you can select the currency and journal to use for the " -"transaction." -msgstr "对于所有文件，您可以选择用于交易的币种和日记账。" +"transaction on the document itself." +msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 msgid "Select the currency and journal to use." @@ -9892,48 +9889,282 @@ msgstr "内部统计" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 msgid "" -"**Intrastat** is the system for data collection and statistic production of " -"goods traded among the EU Member States. Organizations whose annual trade " -"surpasses a certain threshold must provide data about the goods traded with " -"other EU countries." -msgstr "**内部统计**是欧盟成员国之间贸易商品的数据收集和统计编制系统。年度贸易超过一定阈值的组织必须提供有关与其他欧盟国家贸易的商品的数据。" - -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:10 -msgid "" -"`Eurostat Statistics Explained - Glossary: Intrastat " -"<https://ec.europa.eu/eurostat/statistics-" -"explained/index.php?title=Glossary:Intrastat>`_" +"`Intrastat <https://ec.europa.eu/eurostat/statistics-" +"explained/index.php?title=Glossary:Intrastat>`_ is the data collection and " +"statistics production system for goods traded among EU member states. It " +"collects data on:" msgstr "" -"“欧统局统计解释-词汇表：内部统计<https://ec.europa.eu/eurostat/statistics-" -"explained/index.php?title=Glossary:Intrastat>'_" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:14 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:9 msgid "" -"As of January 1, 2022, the reporting requirements have changed. One main " -"modification concerns the transaction codes which are now switching to a " -"2-digits format. All transactions recorded after this date have to follow " -"the new system’s rules." +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" msgstr "" -"自 2022 年 1 月 1 " -"日起，报告要求已更改。一个主要的修改涉及交易代码，现在切换到2位数字格式。在此日期之后记录的所有交易都必须遵循新系统的规则。" -#: ../../content/applications/finance/accounting/reporting/intrastat.rst:21 +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:11 msgid "" -"Go to :menuselection:`Accounting --> Settings --> Customer Invoices`, then " -"enable **Intrastat** and *Save*. Once the Intrastat has been activated you " -"are able to choose the **Default incoterm**." +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:13 +msgid "Returns of goods." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:16 +msgid "" +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"<http://data.europa.eu/eli/reg/2019/2152/2022-01-01>`_, preferring instead " +"*intra-Union trade in goods statistics*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:23 +msgid "General configuration" msgstr "" -"转到：menuselection：'会计 -->设置 -->客户发票'，然后启用 **内部统计** 和 " -"*保存*。激活内部统计后，您可以选择**默认国际贸易术语**。" #: ../../content/applications/finance/accounting/reporting/intrastat.rst:25 msgid "" -"If you created your Odoo database prior to **January 13, 2022**, please " -":ref:`upgrade <general/upgrade>` the ``account_intrastat`` module to add the" -" new transaction codes and :ref:`install <general/install>` the " -"``account_intrastat_expiry`` module to archive the old codes." +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the **Customer Invoices** section, tick " +":guilabel:`Intrastat` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:31 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located, and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:34 +msgid "" +"If your warehouses are located in multiple regions, you can define the " +"region code for each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:43 +msgid "Default Incoterm" +msgstr "默认国际贸易术语" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "" +"You can set **default Incoterms** for your company by selecting an Intrastat" +" **code** in the :guilabel:`Default Incoterm` field of the **Customer " +"Invoices** section, and then clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "Product configuration" +msgstr "产品配置" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:54 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:59 +msgid "Commodity code" +msgstr "商品代码" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:61 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature <https://taxation-customs.ec.europa.eu/customs-4/calculation-" +"customs-duties/customs-tariff/combined-nomenclature_en>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:64 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:68 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"<https://www.nbb.be/en/statistics/foreign-trade/nomenclature-and-codes>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:74 +msgid "Country of origin" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:76 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:82 +msgid "Invoices and bills configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:84 +msgid "" +"Once products are properly configured, several settings must be enabled on " +"the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:90 +msgid "Transaction code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:92 +msgid "" +"Transaction codes are used to identify a transaction's nature. To set a " +"transaction code on an invoice line, create an invoice or bill, click the " +":guilabel:`⋮` button, tick :guilabel:`Intrastat`, and use the newly-added " +":guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:101 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"<https://www.nbb.be/doc/dd/onegate/data/new_natures_of_transaction_2022_en.pdf>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:107 +msgid "Partner country" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:109 +msgid "" +"The partner country is the vendor's or customer's country, depending on " +"whether it is an invoice or bill. It is automatically filled in using the " +":guilabel:`Country` field in the **contact form** of the partner." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:113 +msgid "" +"To edit the partner country manually, click on the :guilabel:`Other Info` " +"tab when on an invoice or bill, and select the :guilabel:`Intrastat " +"Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "Transport code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:121 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch). Once you have selected a :ref:`partner" +" country <intrastat/partner-country>`, the :guilabel:`Intrastat Transport " +"Mode` becomes available." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "Value of the goods" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:130 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "Partner configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:138 +msgid "" +"Two fields from the partner's **contact form** are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set <intrastat/partner-country>` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:143 +msgid "Generate the Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:145 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration <intrastat/general-configuration>` and the " +"information on the :ref:`products <intrastat/product-configuration>`, " +":ref:`invoices and bills <intrastat/invoice-bill-configuration>`, and " +":ref:`partners <intrastat/partner>`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"Export the report as a PDF, XLSX, or XML file to submit it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:153 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:155 +msgid "Invoice or bill reference number;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:156 +msgid "" +":guilabel:`System`, which is a code automatically generated depending on " +"whether the document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:158 +msgid "" +":ref:`Country <intrastat/partner-country>`, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:160 +msgid ":ref:`Transaction Code <intrastat/transaction-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:161 +msgid "" +":ref:`Region Code <intrastat/region-code>` (if your company is located in " +"Belgium);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:162 +msgid ":ref:`Commodity Code <intrastat/commodity-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:163 +msgid ":ref:`Origin Country <intrastat/origin-country>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:164 +msgid ":ref:`Partner VAT <intrastat/partner>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid ":ref:`Transport Code <intrastat/transport-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:166 +msgid "" +":ref:`Value <intrastat/value>`, which is always expressed in EUR even if the" +" original invoice or bill used another currency." msgstr "" -"如果您在2022年1月13日之前创建了Odoo数据库，请：ref：'升级<一般/升级>'account_intrastat'模块以添加新的交易代码，并：ref：'install<一般/安装>''account_intrastat_expiry'模块以存档旧代码。" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 msgid "Silverfin integration" @@ -20952,6 +21183,7 @@ msgid "2-digits comparison" msgstr "2 位数字比较" #: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:61 msgid "Template" msgstr "模板" @@ -29383,7 +29615,7 @@ msgid "" msgstr "" #: ../../content/applications/finance/payment_acquirers.rst:267 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:40 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:38 msgid "Configuration tab" msgstr "配置选项卡" @@ -29534,7 +29766,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/adyen.rst:10 #: ../../content/applications/finance/payment_acquirers/adyen.rst:137 #: ../../content/applications/finance/payment_acquirers/alipay.rst:36 -#: ../../content/applications/finance/payment_acquirers/authorize.rst:53 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:51 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:47 #: ../../content/applications/finance/payment_acquirers/mollie.rst:31 #: ../../content/applications/finance/payment_acquirers/paypal.rst:162 @@ -29868,37 +30100,242 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:31 msgid "" -"If you are trying Authorize.Net as a test, with a *sandbox account*, change " -"the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a" -" test Odoo database, rather than on your main database." +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." msgstr "" -"如果您使用沙盒账号测试Authorize.Net，请将:guilabel:`状态`更改为:guilabel:`测试模式`。建议您在Odoo数据库而非您的主数据库中执行此操作。" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:35 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:34 msgid "" -"If you set :guilabel:`Test Mode` on Odoo and use an authorize.net account " -"instead of a sandbox.authorize.net account, it results in the following " -"error: *The merchant login ID or password is invalid or the account is " -"inactive*." +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." msgstr "" -"如果在Odoo中设置:guilabel:`测试模式`，并使用Authorize.net账号而非sandbox.authorize.net账号，则会导致以下错误：*商户登录ID或密码无效或非活跃账号*。" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:41 msgid "Place a hold on a card" msgstr "暂挂信用卡" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:45 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:43 msgid "" -"With Authorize.net, you can enable the :ref:`manual capture " +"With Authorize.Net, you can enable the :ref:`manual capture " "<payment_acquirers/features/manual_capture>`. If enabled, the funds are " "reserved for 30 days on the customer's card, but not charged yet." msgstr "" -#: ../../content/applications/finance/payment_acquirers/authorize.rst:50 +#: ../../content/applications/finance/payment_acquirers/authorize.rst:48 msgid "" "After **30 days**, the transaction is **voided automatically** by " -"Authorize.net." -msgstr "在 **30天** 之后，Authorize.net 会自动 **自动取消交易** 。" +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:54 +msgid "Import an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:57 +msgid "Export from Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:63 +msgid "" +"`Download the Excel import template " +"<https://docs.google.com/spreadsheets/d/1CMVtBWLLVIrUpYA92paw-" +"cL7-WdKLbaa/edit?usp=share_link&ouid=105295722917050444558&rtpof=true&sd=true>`_" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:65 +msgid "To export a statement:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:67 +msgid "Log in to Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:68 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:69 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:71 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template <authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:84 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:87 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:89 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:90 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:92 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:93 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:95 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"<authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:97 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template <authorize-import-template>`. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:104 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:107 +msgid "Import into Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:109 +msgid "To import the data into Odoo:" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:111 +msgid "Open the :ref:`Excel import template <authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:112 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:114 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:117 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:118 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:120 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template <authorize-import-template>` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:125 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template <authorize-import-template>` for each invoice." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:0 +msgid "Chargeback description" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:133 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:135 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:137 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:139 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:141 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:143 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/authorize.rst:148 +msgid "" +"List of `eCheck.Net return codes " +"<https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001293>`_" +msgstr "" #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:3 msgid "Buckaroo"