NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[I18N] export 11.0 source terms

Browse Source
This commit is contained in:
Martin Trigaux 2018-09-26 16:13:49 +02:00
parent 3ff4173f79
commit 07375ef322
9 changed files with 623 additions and 891 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.tx/config
View File

@ -72,6 +72,11 @@ file_filter = locale/<lang>/LC_MESSAGES/manufacturing.po
source_file = locale/sources/manufacturing.pot
source_lang = en
[odoo-11-doc.mobile]
file_filter = locale/<lang>/LC_MESSAGES/mobile.po
source_file = locale/sources/mobile.pot
source_lang = en
[odoo-11-doc.point_of_sale]
file_filter = locale/<lang>/LC_MESSAGES/point_of_sale.po
source_file = locale/sources/point_of_sale.pot

341
locale/sources/accounting.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-27 11:08+0200\n"
"POT-Creation-Date: 2018-09-26 16:07+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -17,7 +17,7 @@ msgstr ""
"Content-Transfer-Encoding: 8bit\n"
#: ../../accounting.rst:5
#: ../../accounting/localizations/mexico.rst:281
#: ../../accounting/localizations/mexico.rst:283
msgid "Accounting"
msgstr ""
@ -466,7 +466,7 @@ msgid "Once you filled in your credentials, your bank feeds will be synchronized
msgstr ""
#: ../../accounting/bank/feeds/synchronize.rst:73
#: ../../accounting/localizations/mexico.rst:531
#: ../../accounting/localizations/mexico.rst:533
msgid "FAQ"
msgstr ""
@ -977,6 +977,16 @@ msgstr ""
msgid "If you are working in a multi-company environnement, you'll have to switch the company on your user preferences in order to add, edit or delete bank accounts from another company."
msgstr ""
#: ../../accounting/bank/setup/create_bank_account.rst:0
#: ../../accounting/bank/setup/manage_cash_register.rst:0
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Type"
msgstr ""
#: ../../accounting/bank/setup/create_bank_account.rst:0
msgid "Bank account type: Normal or IBAN. Inferred from the bank account number."
msgstr ""
#: ../../accounting/bank/setup/create_bank_account.rst:0
msgid "ABA/Routing"
msgstr ""
@ -985,6 +995,14 @@ msgstr ""
msgid "American Bankers Association Routing Number"
msgstr ""
#: ../../accounting/bank/setup/create_bank_account.rst:0
msgid "Account Holder Name"
msgstr ""
#: ../../accounting/bank/setup/create_bank_account.rst:0
msgid "Account holder name, in case it is different than the name of the Account Holder"
msgstr ""
#: ../../accounting/bank/setup/create_bank_account.rst:49
msgid "View *Bank Account* in our Online Demonstration"
msgstr ""
@ -1141,11 +1159,6 @@ msgstr ""
msgid "Set active to false to hide the Journal without removing it."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Type"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Select 'Sale' for customer invoices journals."
msgstr ""
@ -1767,549 +1780,549 @@ msgstr ""
msgid "To enable this requirement in Mexico go to configuration in accounting Go in :menuselection:`Accounting --> Settings` and enable the option on the image with this you will be able to generate the signed invoice (CFDI 3.2 and 3.3) and generate the payment complement signed as well (3.3 only) all fully integrate with the normal invoicing flow in Odoo."
msgstr ""
#: ../../accounting/localizations/mexico.rst:66
#: ../../accounting/localizations/mexico.rst:68
msgid "3. Set you legal information in the company"
msgstr ""
#: ../../accounting/localizations/mexico.rst:68
#: ../../accounting/localizations/mexico.rst:70
msgid "First, make sure that your company is configured with the correct data. Go in :menuselection:`Settings --> Users --> Companies` and enter a valid address and VAT for your company. Don’t forget to define a mexican fiscal position on your company’s contact."
msgstr ""
#: ../../accounting/localizations/mexico.rst:75
#: ../../accounting/localizations/mexico.rst:77
msgid "If you want use the Mexican localization on test mode, you can put any known address inside Mexico with all fields for the company address and set the vat to **ACO560518KW7**."
msgstr ""
#: ../../accounting/localizations/mexico.rst:83
#: ../../accounting/localizations/mexico.rst:85
msgid "4. Set the proper \"Fiscal Position\" on the partner that represent the company"
msgstr ""
#: ../../accounting/localizations/mexico.rst:85
#: ../../accounting/localizations/mexico.rst:87
msgid "Go In the same form where you are editing the company save the record in order to set this form as a readonly and on readonly view click on the partner link, then edit it and set in the *Invoicing* tab the proper Fiscal Information (for the **Test Environment** this must be *601 - General de Ley Personas Morales*, just search it as a normal Odoo field if you can't see the option)."
msgstr ""
#: ../../accounting/localizations/mexico.rst:92
#: ../../accounting/localizations/mexico.rst:94
msgid "5. Enabling CFDI Version 3.3"
msgstr ""
#: ../../accounting/localizations/mexico.rst:95
#: ../../accounting/localizations/mexico.rst:97
msgid "This steps are only necessary when you will enable the CFDI 3.3 (only available for V11.0 and above) if you do not have Version 11.0 or above on your SaaS instance please ask for an upgrade sending a ticket to support in https://www.odoo.com/help."
msgstr ""
#: ../../accounting/localizations/mexico.rst:100
#: ../../accounting/localizations/mexico.rst:102
msgid "Enable debug mode:"
msgstr ""
#: ../../accounting/localizations/mexico.rst:105
#: ../../accounting/localizations/mexico.rst:107
msgid "Go and look the following technical parameter, on :menuselection:`Settings --> Technical --> Parameters --> System Parameters` and set the parameter called *l10n_mx_edi_cfdi_version* to 3.3 (Create it if the entry with this name does not exist)."
msgstr ""
#: ../../accounting/localizations/mexico.rst:111
#: ../../accounting/localizations/mexico.rst:113
msgid "The CFDI 3.2 will be legally possible until November 30th 2017 enable the 3.3 version will be a mandatory step to comply with the new `SAT resolution`_ in any new database created since v11.0 released CFDI 3.3 is the default behavior."
msgstr ""
#: ../../accounting/localizations/mexico.rst:120
#: ../../accounting/localizations/mexico.rst:122
msgid "Important considerations when yo enable the CFDI 3.3"
msgstr ""
#: ../../accounting/localizations/mexico.rst:122
#: ../../accounting/localizations/mexico.rst:611
#: ../../accounting/localizations/mexico.rst:124
#: ../../accounting/localizations/mexico.rst:613
msgid "Your tax which represent the VAT 16% and 0% must have the \"Factor Type\" field set to \"Tasa\"."
msgstr ""
#: ../../accounting/localizations/mexico.rst:130
#: ../../accounting/localizations/mexico.rst:132
msgid "You must go to the Fiscal Position configuration and set the proper code (it is the first 3 numbers in the name) for example for the test one you should set 601, it will look like the image."
msgstr ""
#: ../../accounting/localizations/mexico.rst:137
#: ../../accounting/localizations/mexico.rst:139
msgid "All products must have for CFDI 3.3 the \"SAT code\" and the field \"Reference\" properly set, you can export them and re import them to do it faster."
msgstr ""
#: ../../accounting/localizations/mexico.rst:144
#: ../../accounting/localizations/mexico.rst:146
msgid "6. Configure the PAC in order to sign properly the invoices"
msgstr ""
#: ../../accounting/localizations/mexico.rst:146
#: ../../accounting/localizations/mexico.rst:148
msgid "To configure the EDI with the **PACs**, you can go in :menuselection:`Accounting --> Settings --> Electronic Invoicing (MX)`. You can choose a PAC within the **List of supported PACs** on the *PAC field* and then enter your PAC username and PAC password."
msgstr ""
#: ../../accounting/localizations/mexico.rst:152
#: ../../accounting/localizations/mexico.rst:154
msgid "Remember you must sign up in the refereed PAC before hand, that process can be done with the PAC itself on this case we will have two (2) availables `Finkok`_ and `Solución Factible`_."
msgstr ""
#: ../../accounting/localizations/mexico.rst:156
#: ../../accounting/localizations/mexico.rst:158
msgid "You must process your **Private Key (CSD)** with the SAT institution before follow this steps, if you do not have such information please try all the \"Steps for Test\" and come back to this process when you finish the process proposed for the SAT in order to set this information for your production environment with real transactions."
msgstr ""
#: ../../accounting/localizations/mexico.rst:166
#: ../../accounting/localizations/mexico.rst:168
msgid "If you ticked the box *MX PAC test environment* there is no need to enter a PAC username or password."
msgstr ""
#: ../../accounting/localizations/mexico.rst:173
#: ../../accounting/localizations/mexico.rst:175
msgid "Here is a SAT certificate you can use if you want to use the *Test Environment* for the Mexican Accounting Localization."
msgstr ""
#: ../../accounting/localizations/mexico.rst:176
#: ../../accounting/localizations/mexico.rst:178
msgid "`Certificate`_"
msgstr ""
#: ../../accounting/localizations/mexico.rst:177
#: ../../accounting/localizations/mexico.rst:179
msgid "`Certificate Key`_"
msgstr ""
#: ../../accounting/localizations/mexico.rst:178
#: ../../accounting/localizations/mexico.rst:180
msgid "**Password :** 12345678a"
msgstr ""
#: ../../accounting/localizations/mexico.rst:181
#: ../../accounting/localizations/mexico.rst:183
msgid "7. Configure the tag in sales taxes"
msgstr ""
#: ../../accounting/localizations/mexico.rst:183
#: ../../accounting/localizations/mexico.rst:185
msgid "This tag is used to set the tax type code, transferred or withhold, applicable to the concept in the CFDI. So, if the tax is a sale tax the \"Tag\" field should be \"IVA\", \"ISR\" or \"IEPS\"."
msgstr ""
#: ../../accounting/localizations/mexico.rst:190
#: ../../accounting/localizations/mexico.rst:192
msgid "Note that the default taxes already has a tag assigned, but when you create a new tax you should choose a tag."
msgstr ""
#: ../../accounting/localizations/mexico.rst:194
#: ../../accounting/localizations/mexico.rst:196
msgid "Usage and testing"
msgstr ""
#: ../../accounting/localizations/mexico.rst:197
#: ../../accounting/localizations/mexico.rst:199
msgid "Invoicing"
msgstr ""
#: ../../accounting/localizations/mexico.rst:199
#: ../../accounting/localizations/mexico.rst:201
msgid "To use the mexican invoicing you just need to do a normal invoice following the normal Odoo's behaviour."
msgstr ""
#: ../../accounting/localizations/mexico.rst:202
#: ../../accounting/localizations/mexico.rst:204
msgid "Once you validate your first invoice a correctly signed invoice should look like this:"
msgstr ""
#: ../../accounting/localizations/mexico.rst:209
#: ../../accounting/localizations/mexico.rst:211
msgid "You can generate the PDF just clicking on the Print button on the invoice or sending it by email following the normal process on odoo to send your invoice by email."
msgstr ""
#: ../../accounting/localizations/mexico.rst:216
#: ../../accounting/localizations/mexico.rst:218
msgid "Once you send the electronic invoice by email this is the way it should looks like."
msgstr ""
#: ../../accounting/localizations/mexico.rst:223
#: ../../accounting/localizations/mexico.rst:225
msgid "Cancelling invoices"
msgstr ""
#: ../../accounting/localizations/mexico.rst:225
#: ../../accounting/localizations/mexico.rst:227
msgid "The cancellation process is completely linked to the normal cancellation in Odoo."
msgstr ""
#: ../../accounting/localizations/mexico.rst:227
#: ../../accounting/localizations/mexico.rst:229
msgid "If the invoice is not paid."
msgstr ""
#: ../../accounting/localizations/mexico.rst:229
#: ../../accounting/localizations/mexico.rst:231
msgid "Go to to the customer invoice journal where the invoice belong to"
msgstr ""
#: ../../accounting/localizations/mexico.rst:237
#: ../../accounting/localizations/mexico.rst:239
msgid "Check the \"Allow cancelling entries\" field"
msgstr ""
#: ../../accounting/localizations/mexico.rst:242
#: ../../accounting/localizations/mexico.rst:244
msgid "Go back to your invoice and click on the button \"Cancel Invoice\""
msgstr ""
#: ../../accounting/localizations/mexico.rst:247
#: ../../accounting/localizations/mexico.rst:249
msgid "For security reasons it is recommendable return the check on the to allow cancelling to false again, then go to the journal and un check such field."
msgstr ""
#: ../../accounting/localizations/mexico.rst:250
#: ../../accounting/localizations/mexico.rst:252
msgid "**Legal considerations**"
msgstr ""
#: ../../accounting/localizations/mexico.rst:252
#: ../../accounting/localizations/mexico.rst:254
msgid "A cancelled invoice will automatically cancelled on the SAT."
msgstr ""
#: ../../accounting/localizations/mexico.rst:253
#: ../../accounting/localizations/mexico.rst:255
msgid "If you retry to use the same invoice after cancelled, you will have as much cancelled CFDI as you tried, then all those xml are important to maintain a good control of the cancellation reasons."
msgstr ""
#: ../../accounting/localizations/mexico.rst:256
#: ../../accounting/localizations/mexico.rst:258
msgid "You must unlink all related payment done to an invoice on odoo before cancel such document, this payments must be cancelled to following the same approach but setting the \"Allow Cancel Entries\" in the payment itself."
msgstr ""
#: ../../accounting/localizations/mexico.rst:261
#: ../../accounting/localizations/mexico.rst:263
msgid "Payments (Just available for CFDI 3.3)"
msgstr ""
#: ../../accounting/localizations/mexico.rst:263
#: ../../accounting/localizations/mexico.rst:265
msgid "To generate the payment complement you just must to follow the normal payment process in Odoo, this considerations to understand the behavior are important."
msgstr ""
#: ../../accounting/localizations/mexico.rst:266
#: ../../accounting/localizations/mexico.rst:268
msgid "All payment done in the same day of the invoice will be considered as It will not be signed, because It is the expected behavior legally required for \"Cash payment\"."
msgstr ""
#: ../../accounting/localizations/mexico.rst:269
#: ../../accounting/localizations/mexico.rst:271
msgid "To test a regular signed payment just create an invoice for the day before today and then pay it today."
msgstr ""
#: ../../accounting/localizations/mexico.rst:271
#: ../../accounting/localizations/mexico.rst:273
msgid "You must print the payment in order to retrieve the PDF properly."
msgstr ""
#: ../../accounting/localizations/mexico.rst:272
#: ../../accounting/localizations/mexico.rst:274
msgid "Regarding the \"Payments in Advance\" you must create a proper invoice with the payment in advance itself as a product line setting the proper SAT code following the procedure on the official documentation `given by the SAT`_ in the section **Apéndice 2 Procedimiento para la emisión de los CFDI en el caso de anticipos recibidos**."
msgstr ""
#: ../../accounting/localizations/mexico.rst:277
#: ../../accounting/localizations/mexico.rst:279
msgid "Related to topic 4 it is blocked the possibility to create a Customer Payment without a proper invoice."
msgstr ""
#: ../../accounting/localizations/mexico.rst:282
#: ../../accounting/localizations/mexico.rst:284
msgid "The accounting for Mexico in odoo is composed by 3 reports:"
msgstr ""
#: ../../accounting/localizations/mexico.rst:284
#: ../../accounting/localizations/mexico.rst:286
msgid "Chart of Account (Called and shown as COA)."
msgstr ""
#: ../../accounting/localizations/mexico.rst:285
#: ../../accounting/localizations/mexico.rst:287
msgid "Electronic Trial Balance."
msgstr ""
#: ../../accounting/localizations/mexico.rst:286
#: ../../accounting/localizations/mexico.rst:288
msgid "DIOT report."
msgstr ""
#: ../../accounting/localizations/mexico.rst:288
#: ../../accounting/localizations/mexico.rst:290
msgid "1 and 2 are considered as the electronic accounting, and the DIOT is a report only available on the context of the accounting."
msgstr ""
#: ../../accounting/localizations/mexico.rst:291
#: ../../accounting/localizations/mexico.rst:293
msgid "You can find all those reports in the original report menu on Accounting app."
msgstr ""
#: ../../accounting/localizations/mexico.rst:297
#: ../../accounting/localizations/mexico.rst:299
msgid "Electronic Accounting (Requires Accounting App)"
msgstr ""
#: ../../accounting/localizations/mexico.rst:300
#: ../../accounting/localizations/mexico.rst:302
msgid "Electronic Chart of account CoA"
msgstr ""
#: ../../accounting/localizations/mexico.rst:302
#: ../../accounting/localizations/mexico.rst:304
msgid "The electronic accounting never has been easier, just go to :menuselection:`Accounting --> Reporting --> Mexico --> COA` and click on the button **Export for SAT (XML)**"
msgstr ""
#: ../../accounting/localizations/mexico.rst:309
#: ../../accounting/localizations/mexico.rst:311
msgid "**How to add new accounts?**"
msgstr ""
#: ../../accounting/localizations/mexico.rst:311
#: ../../accounting/localizations/mexico.rst:313
msgid "If you add an account with the coding convention NNN.YY.ZZ where NNN.YY is a SAT coding group then your account will be automatically configured."
msgstr ""
#: ../../accounting/localizations/mexico.rst:314
#: ../../accounting/localizations/mexico.rst:316
msgid "Example to add an Account for a new Bank account go to :menuselection:`Accounting --> Settings --> Chart of Account` and then create a new account on the button \"Create\" and try to create an account with the number 102.01.99 once you change to set the name you will see a tag automatically set, the tags set are the one picked to be used in the COA on xml."
msgstr ""
#: ../../accounting/localizations/mexico.rst:324
#: ../../accounting/localizations/mexico.rst:326
msgid "**What is the meaning of the tag?**"
msgstr ""
#: ../../accounting/localizations/mexico.rst:326
#: ../../accounting/localizations/mexico.rst:328
msgid "To know all possible tags you can read the `Anexo 24`_ in the SAT website on the section called **Código agrupador de cuentas del SAT**."
msgstr ""
#: ../../accounting/localizations/mexico.rst:330
#: ../../accounting/localizations/mexico.rst:332
msgid "When you install the module l10n_mx and yous Chart of Account rely on it (this happen automatically when you install setting Mexico as country on your database) then you will have the more common tags if the tag you need is not created you can create one on the fly."
msgstr ""
#: ../../accounting/localizations/mexico.rst:336
#: ../../accounting/localizations/mexico.rst:338
msgid "Electronic Trial Balance"
msgstr ""
#: ../../accounting/localizations/mexico.rst:338
#: ../../accounting/localizations/mexico.rst:340
msgid "Exactly as the COA but with Initial balance debit and credit, once you have your coa properly set you can go to :menuselection:`Accounting --> Reports --> Mexico --> Trial Balance` this is automatically generated, and can be exported to XML using the button in the top **Export for SAT (XML)** with the previous selection of the period you want to export."
msgstr ""
#: ../../accounting/localizations/mexico.rst:347
#: ../../accounting/localizations/mexico.rst:349
msgid "All the normal auditory and analysis features are available here also as any regular Odoo Report."
msgstr ""
#: ../../accounting/localizations/mexico.rst:351
#: ../../accounting/localizations/mexico.rst:353
msgid "DIOT Report (Requires Accounting App)"
msgstr ""
#: ../../accounting/localizations/mexico.rst:353
#: ../../accounting/localizations/mexico.rst:355
msgid "**What is the DIOT and the importance of presenting it SAT**"
msgstr ""
#: ../../accounting/localizations/mexico.rst:355
#: ../../accounting/localizations/mexico.rst:357
msgid "When it comes to procedures with the SAT Administration Service we know that we should not neglect what we present. So that things should not happen in Odoo."
msgstr ""
#: ../../accounting/localizations/mexico.rst:358
#: ../../accounting/localizations/mexico.rst:360
msgid "The DIOT is the Informational Statement of Operations with Third Parties (DIOT), which is an an additional obligation with the VAT, where we must give the status of our operations to third parties, or what is considered the same, with our providers."
msgstr ""
#: ../../accounting/localizations/mexico.rst:363
#: ../../accounting/localizations/mexico.rst:365
msgid "This applies both to individuals and to the moral as well, so if we have VAT for submitting to the SAT and also dealing with suppliers it is necessary to. submit the DIOT:"
msgstr ""
#: ../../accounting/localizations/mexico.rst:367
#: ../../accounting/localizations/mexico.rst:369
msgid "**When to file the DIOT and in what format?**"
msgstr ""
#: ../../accounting/localizations/mexico.rst:369
#: ../../accounting/localizations/mexico.rst:371
msgid "It is simple to present the DIOT, since like all format this you can obtain it in the page of the SAT, it is the electronic format A-29 that you can find in the SAT website."
msgstr ""
#: ../../accounting/localizations/mexico.rst:373
#: ../../accounting/localizations/mexico.rst:375
msgid "Every month if you have operations with third parties it is necessary to present the DIOT, just as we do with VAT, so that if in January we have deals with suppliers, by February we must present the information pertinent to said data."
msgstr ""
#: ../../accounting/localizations/mexico.rst:378
#: ../../accounting/localizations/mexico.rst:380
msgid "**Where the DIOT is presented?**"
msgstr ""
#: ../../accounting/localizations/mexico.rst:380
#: ../../accounting/localizations/mexico.rst:382
msgid "You can present DIOT in different ways, it is up to you which one you will choose and which will be more comfortable for you than you will present every month or every time you have dealings with suppliers."
msgstr ""
#: ../../accounting/localizations/mexico.rst:384
#: ../../accounting/localizations/mexico.rst:386
msgid "The A-29 format is electronic so you can present it on the SAT page, but this after having made up to 500 records."
msgstr ""
#: ../../accounting/localizations/mexico.rst:387
#: ../../accounting/localizations/mexico.rst:389
msgid "Once these 500 records are entered in the SAT, you must present them to the Local Taxpayer Services Administration (ALSC) with correspondence to your tax address, these records can be presented in a digital storage medium such as a CD or USB, which once validated you will be returned, so do not doubt that you will still have these records and of course, your CD or USB."
msgstr ""
#: ../../accounting/localizations/mexico.rst:393
#: ../../accounting/localizations/mexico.rst:395
msgid "**One more fact to know: the Batch load?**"
msgstr ""
#: ../../accounting/localizations/mexico.rst:395
#: ../../accounting/localizations/mexico.rst:397
msgid "When reviewing the official SAT documents on DIOT, you will find the Batch load, and of course the first thing we think is what is that ?, and according to the SAT site is:"
msgstr ""
#: ../../accounting/localizations/mexico.rst:399
#: ../../accounting/localizations/mexico.rst:401
msgid "The \"batch upload\" is the conversion of records databases of transactions with suppliers made by taxpayers in text files (.txt). These files have the necessary structure for their application and importation into the system of the Informative Declaration of Operations with third parties, avoiding the direct capture and consequently, optimizing the time invested in its integration for the presentation in time and form to the SAT."
msgstr ""
#: ../../accounting/localizations/mexico.rst:406
#: ../../accounting/localizations/mexico.rst:408
msgid "You can use it to present the DIOT, since it is allowed, which will make this operation easier for you, so that it does not exist to avoid being in line with the SAT in regard to the Information Statement of Operations with Third Parties."
msgstr ""
#: ../../accounting/localizations/mexico.rst:411
#: ../../accounting/localizations/mexico.rst:413
msgid "You can find the `official information here`_."
msgstr ""
#: ../../accounting/localizations/mexico.rst:413
#: ../../accounting/localizations/mexico.rst:415
msgid "**How Generate this report in odoo?**"
msgstr ""
#: ../../accounting/localizations/mexico.rst:415
#: ../../accounting/localizations/mexico.rst:417
msgid "Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third partied (DIOT)`."
msgstr ""
#: ../../accounting/localizations/mexico.rst:420
#: ../../accounting/localizations/mexico.rst:422
msgid "A report view is shown, select last month to report the immediate before month you are or left the current month if it suits to you."
msgstr ""
#: ../../accounting/localizations/mexico.rst:426
#: ../../accounting/localizations/mexico.rst:428
msgid "Click on \"Export (TXT)."
msgstr ""
#: ../../accounting/localizations/mexico.rst:431
#: ../../accounting/localizations/mexico.rst:433
msgid "Save in a secure place the downloaded file and go to SAT website and follow the necessary steps to declare it."
msgstr ""
#: ../../accounting/localizations/mexico.rst:435
#: ../../accounting/localizations/mexico.rst:437
msgid "Important considerations on your Supplier and Invice data for the DIOT"
msgstr ""
#: ../../accounting/localizations/mexico.rst:437
#: ../../accounting/localizations/mexico.rst:439
msgid "All suppliers must have set the fields on the accounting tab called \"DIOT Information\", the *L10N Mx Nationality* field is filled with just select the proper country in the address, you do not need to do anything else there, but the *L10N Mx Type Of Operation* must be filled by you in all your suppliers."
msgstr ""
#: ../../accounting/localizations/mexico.rst:445
#: ../../accounting/localizations/mexico.rst:447
msgid "There are 3 options of VAT for this report, 16%, 0% and exempt, an invoice line in odoo is considered exempt if no tax on it, the other 2 taxes are properly configured already."
msgstr ""
#: ../../accounting/localizations/mexico.rst:448
#: ../../accounting/localizations/mexico.rst:450
msgid "Remember to pay an invoice which represent a payment in advance you must ask for the invoice first and then pay it and reconcile properly the payment following standard odoo procedure."
msgstr ""
#: ../../accounting/localizations/mexico.rst:451
#: ../../accounting/localizations/mexico.rst:453
msgid "You do not need all you data on partners filled to try to generate the supplier invoice, you can fix this information when you generate the report itself."
msgstr ""
#: ../../accounting/localizations/mexico.rst:454
#: ../../accounting/localizations/mexico.rst:456
msgid "Remember this report only shows the Supplier Invoices that were actually paid."
msgstr ""
#: ../../accounting/localizations/mexico.rst:456
#: ../../accounting/localizations/mexico.rst:458
msgid "If some of this considerations are not taken into account a message like this will appear when generate the DIOT on TXT with all the partners you need to check on this particular report, this is the reason we recommend use this report not just to export your legal obligation but to generate it before the end of the month and use it as your auditory process to see all your partners are correctly set."
msgstr ""
#: ../../accounting/localizations/mexico.rst:467
#: ../../accounting/localizations/mexico.rst:469
msgid "Extra Recommended features"
msgstr ""
#: ../../accounting/localizations/mexico.rst:470
#: ../../accounting/localizations/mexico.rst:472
msgid "Contact Module (Free)"
msgstr ""
#: ../../accounting/localizations/mexico.rst:472
#: ../../accounting/localizations/mexico.rst:474
msgid "If you want to administer properly your customers, suppliers and addresses this module even if it is not a technical need, it is highly recommended to install."
msgstr ""
#: ../../accounting/localizations/mexico.rst:477
#: ../../accounting/localizations/mexico.rst:479
msgid "Multi currency (Requires Accounting App)"
msgstr ""
#: ../../accounting/localizations/mexico.rst:479
#: ../../accounting/localizations/mexico.rst:481
msgid "In Mexico almost all companies send and receive payments in different currencies if you want to manage such capability you should enable the multi currency feature and you should enable the synchronization with **Banxico**, such feature allow you retrieve the proper exchange rate automatically retrieved from SAT and not being worried of put such information daily in the system manually."
msgstr ""
#: ../../accounting/localizations/mexico.rst:486
#: ../../accounting/localizations/mexico.rst:488
msgid "Go to settings and enable the multi currency feature."
msgstr ""
#: ../../accounting/localizations/mexico.rst:492
#: ../../accounting/localizations/mexico.rst:494
msgid "Enabling Explicit errors on the CFDI using the XSD local validator (CFDI 3.3)"
msgstr ""
#: ../../accounting/localizations/mexico.rst:494
#: ../../accounting/localizations/mexico.rst:496
msgid "Frequently you want receive explicit errors from the fields incorrectly set on the xml, those errors are better informed to the user if the check is enable, to enable the Check with xsd feature follow the next steps (with debug mode enabled)."
msgstr ""
#: ../../accounting/localizations/mexico.rst:499
#: ../../accounting/localizations/mexico.rst:501
msgid "Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`"
msgstr ""
#: ../../accounting/localizations/mexico.rst:500
#: ../../accounting/localizations/mexico.rst:502
msgid "Look for the Action called \"Download XSD files to CFDI\""
msgstr ""
#: ../../accounting/localizations/mexico.rst:501
#: ../../accounting/localizations/mexico.rst:503
msgid "Click on button \"Create Contextual Action\""
msgstr ""
#: ../../accounting/localizations/mexico.rst:502
#: ../../accounting/localizations/mexico.rst:504
msgid "Go to the company form :menuselection:`Settings --> Users&Companies --> Companies`"
msgstr ""
#: ../../accounting/localizations/mexico.rst:503
#: ../../accounting/localizations/mexico.rst:505
msgid "Open any company you have."
msgstr ""
#: ../../accounting/localizations/mexico.rst:504
#: ../../accounting/localizations/mexico.rst:527
#: ../../accounting/localizations/mexico.rst:506
#: ../../accounting/localizations/mexico.rst:529
msgid "Click on \"Action\" and then on \"Download XSD file to CFDI\"."
msgstr ""
#: ../../accounting/localizations/mexico.rst:509
#: ../../accounting/localizations/mexico.rst:511
msgid "Now you can make an invoice with any error (for example a product without code which is pretty common) and an explicit error will be shown instead a generic one with no explanation."
msgstr ""
#: ../../accounting/localizations/mexico.rst:514
#: ../../accounting/localizations/mexico.rst:516
msgid "If you see an error like this:"
msgstr ""
#: ../../accounting/localizations/mexico.rst:516
#: ../../accounting/localizations/mexico.rst:518
msgid "The cfdi generated is not valid"
msgstr ""
#: ../../accounting/localizations/mexico.rst:518
#: ../../accounting/localizations/mexico.rst:520
msgid "attribute decl. 'TipoRelacion', attribute 'type': The QName value '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_TipoRelacion' does not resolve to a(n) simple type definition., line 36"
msgstr ""
#: ../../accounting/localizations/mexico.rst:522
#: ../../accounting/localizations/mexico.rst:524
msgid "This can be caused because of a database backup restored in anothe server, or when the XSD files are not correctly downloaded. Follow the same steps as above but:"
msgstr ""
#: ../../accounting/localizations/mexico.rst:526
#: ../../accounting/localizations/mexico.rst:528
msgid "Go to the company in which the error occurs."
msgstr ""
#: ../../accounting/localizations/mexico.rst:533
#: ../../accounting/localizations/mexico.rst:535
msgid "**Error message** (Only applicable on CFDI 3.3):"
msgstr ""
#: ../../accounting/localizations/mexico.rst:535
#: ../../accounting/localizations/mexico.rst:537
msgid ":9:0:ERROR:SCHEMASV:SCHEMAV_CVC_MINLENGTH_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'minLength'] The value '' has a length of '0'; this underruns the allowed minimum length of '1'."
msgstr ""
#: ../../accounting/localizations/mexico.rst:537
#: ../../accounting/localizations/mexico.rst:539
msgid ":9:0:ERROR:SCHEMASV:SCHEMAV_CVC_PATTERN_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'pattern'] The value '' is not accepted by the pattern '[^|]{1,100}'."
msgstr ""
#: ../../accounting/localizations/mexico.rst:540
#: ../../accounting/localizations/mexico.rst:542
msgid "**Solution:** You forget to set the proper \"Reference\" field in the product, please go to the product form and set your internal reference properly."
msgstr ""
#: ../../accounting/localizations/mexico.rst:543
#: ../../accounting/localizations/mexico.rst:568
#: ../../accounting/localizations/mexico.rst:578
#: ../../accounting/localizations/mexico.rst:591
#: ../../accounting/localizations/mexico.rst:602
#: ../../accounting/localizations/mexico.rst:545
#: ../../accounting/localizations/mexico.rst:570
#: ../../accounting/localizations/mexico.rst:580
#: ../../accounting/localizations/mexico.rst:593
#: ../../accounting/localizations/mexico.rst:604
msgid "**Error message**:"
msgstr ""
#: ../../accounting/localizations/mexico.rst:545
#: ../../accounting/localizations/mexico.rst:547
msgid ":6:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}RegimenFiscal': The attribute 'Regimen' is required but missing."
msgstr ""
#: ../../accounting/localizations/mexico.rst:547
#: ../../accounting/localizations/mexico.rst:549
msgid ":5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'RegimenFiscal' is required but missing."
msgstr ""
#: ../../accounting/localizations/mexico.rst:550
#: ../../accounting/localizations/mexico.rst:552
msgid "**Solution:** You forget to set the proper \"Fiscal Position\" on the partner of the company, go to customers, remove the customer filter and look for the partner called as your company and set the proper fiscal position which is the kind of business you company does related to SAT list of possible values, antoher option can be that you forgot follow the considerations about fiscal positions."
msgstr ""
#: ../../accounting/localizations/mexico.rst:557
#: ../../accounting/localizations/mexico.rst:559
msgid "Yo must go to the Fiscal Position configuration and set the proper code (it is the first 3 numbers in the name) for example for the test one you should set 601, it will look like the image."
msgstr ""
#: ../../accounting/localizations/mexico.rst:565
#: ../../accounting/localizations/mexico.rst:567
msgid "For testing purposes this value must be *601 - General de Ley Personas Morales* which is the one required for the demo VAT."
msgstr ""
#: ../../accounting/localizations/mexico.rst:570
#: ../../accounting/localizations/mexico.rst:572
msgid ":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'FormaPago': [facet 'enumeration'] The value '' is not an element of the set {'01', '02', '03', '04', '05', '06', '08', '12', '13', '14', '15', '17', '23', '24', '25', '26', '27', '28', '29', '30', '99'}"
msgstr ""
#: ../../accounting/localizations/mexico.rst:573
#: ../../accounting/localizations/mexico.rst:575
msgid "**Solution:** The payment method is required on your invoice."
msgstr ""
#: ../../accounting/localizations/mexico.rst:580
#: ../../accounting/localizations/mexico.rst:582
msgid ":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': [facet 'enumeration'] The value '' is not an element of the set {'00 :2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' is not a valid value of the atomic type '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'. :5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'Rfc' is required but missing."
msgstr ""
#: ../../accounting/localizations/mexico.rst:585
msgid "**Solution:** You must set the address on your company properly, this is a mandatory group of fields, you can go to your company configuration on :menuselection:`Settings --> Users & Companies --> Companies` and fill all the required fields for your address following the step `3. Set you legal information in the company`."
#: ../../accounting/localizations/mexico.rst:587
msgid "**Solution:** You must set the address on your company properly, this is a mandatory group of fields, you can go to your company configuration on :menuselection:`Settings --> Users & Companies --> Companies` and fill all the required fields for your address following the step :ref:`mx-legal-info`."
msgstr ""
#: ../../accounting/localizations/mexico.rst:593
#: ../../accounting/localizations/mexico.rst:595
msgid ":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' is not a valid value of the atomic type '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'."
msgstr ""
#: ../../accounting/localizations/mexico.rst:596
#: ../../accounting/localizations/mexico.rst:598
msgid "**Solution:** The postal code on your company address is not a valid one for Mexico, fix it."
msgstr ""
#: ../../accounting/localizations/mexico.rst:604
#: ../../accounting/localizations/mexico.rst:606
msgid ":18:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing. :34:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing.\", '')"
msgstr ""
#: ../../accounting/localizations/mexico.rst:608
#: ../../accounting/localizations/mexico.rst:610
msgid "**Solution:** Set the mexican name for the tax 0% and 16% in your system and used on the invoice."
msgstr ""
@ -2789,7 +2802,7 @@ msgid "You can manually close an asset when the depreciation is over. If the las
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Category"
msgid "Asset Category"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
@ -2804,6 +2817,30 @@ msgstr ""
msgid "Date of asset"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Depreciation Dates"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "The way to compute the date of the first depreciation."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "* Based on last day of purchase period: The depreciation dates will be based on the last day of the purchase month or the purchase year (depending on the periodicity of the depreciations)."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "* Based on purchase date: The depreciation dates will be based on the purchase date."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "First Depreciation Date"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Note that this date does not alter the computation of the first journal entry in case of prorata temporis assets. It simply changes its accounting date"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Gross Value"
msgstr ""
@ -2857,7 +2894,7 @@ msgid "Prorata Temporis"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Indicates that the first depreciation entry for this asset have to be done from the purchase date instead of the first January / Start date of fiscal year"
msgid "Indicates that the first depreciation entry for this asset have to be done from the asset date (purchase date) instead of the first January / Start date of fiscal year"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0

12
locale/sources/discuss.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-27 11:08+0200\n"
"POT-Creation-Date: 2018-09-26 16:07+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -25,15 +25,19 @@ msgid "How to use my mail server to send and receive emails in Odoo"
msgstr ""
#: ../../discuss/email_servers.rst:5
msgid "This document is mainly dedicated to Odoo on-premise users who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike in `Odoo Online <https://www.odoo.com/trial>`__ & `Odoo.sh <https://www.odoo.sh>`__."
msgid "This document is mainly dedicated to Odoo on-premise users who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online <https://www.odoo.com/trial>`__ & `Odoo.sh <https://www.odoo.sh>`__."
msgstr ""
#: ../../discuss/email_servers.rst:9
msgid "If no one in your company is used to manage email servers, we strongly recommend that you opt for such convenient Odoo hosting solutions. Indeed their email system works instantly and is monitored by professionals. Nevertheless you can still use your own email servers if you want to manage your email server's reputation yourself."
msgid "If no one in your company is used to manage email servers, we strongly recommend that you opt for those Odoo hosting solutions. Their email system works instantly and is monitored by professionals. Nevertheless you can still use your own email servers if you want to manage your email server's reputation yourself."
msgstr ""
#: ../../discuss/email_servers.rst:15
msgid "You will find here below some useful information to do so by integrating your own email solution with Odoo. .. note::"
msgid "You will find here below some useful information on how to integrate your own email solution with Odoo."
msgstr ""
#: ../../discuss/email_servers.rst:18
msgid "Office 365 email servers don't allow easiliy to send external emails from hosts like Odoo. Refer to the `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to make it work."
msgstr ""
#: ../../discuss/email_servers.rst:24

460
locale/sources/getting_started.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-26 12:01+0200\n"
"POT-Creation-Date: 2018-09-26 16:07+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -17,486 +17,194 @@ msgstr ""
"Content-Transfer-Encoding: 8bit\n"
#: ../../getting_started/documentation.rst:5
msgid "Odoo Online Implementation"
msgid "Basics of the QuickStart Methodology"
msgstr ""
#: ../../getting_started/documentation.rst:7
msgid "This document summarizes **Odoo Online's services**, our Success Pack **implementation methodology**, and best practices to get started with our product."
msgid "This document summarizes Odoo Online's services, our Success Pack implementation methodology, and best practices to get started with our product."
msgstr ""
#: ../../getting_started/documentation.rst:11
msgid "*We recommend that new Odoo Online customers read this document before the kick-off call with our project manager. This way, we save time and don't have to use your hours from the success pack discussing the basics.*"
#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:16
msgid "*If you have not read this document, our project manager will review this with you at the time of the kick-off call.*"
#: ../../getting_started/documentation.rst:14
msgid "Within the context of your project, it is highly recommended to designate and maintain on both sides (your side and ours) **one and only single person of contact** who will take charge and assume responsibilities regarding the project. He also has to have **the authority** in terms of decision making."
msgstr ""
#: ../../getting_started/documentation.rst:20
msgid "Getting Started"
msgid "**The Odoo Consultant ensures the project implementation from A to Z**: From the beginning to the end of the project, he ensures the overall consistency of the implementation in Odoo and shares his expertise in terms of good practices."
msgstr ""
#: ../../getting_started/documentation.rst:22
msgid "Do not wait for the kick-off meeting to begin playing with the software. The more exposure you have with Odoo, the more time you will save later during the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:26
msgid "Once you purchase an Odoo Online subscription, you will receive instructions by email on how to activate or create your database. From this email, you can activate your existing Odoo database or create a new one from scratch."
#: ../../getting_started/documentation.rst:25
msgid "**One and only decision maker on the client side (SPoC)**: He is responsible for the business knowledge transmission (coordinate key users intervention if necessary) and the consistency of the implementation from a business point of view (decision making, change management, etc.)"
msgstr ""
#: ../../getting_started/documentation.rst:31
msgid "If you did not receive this email, e.g. because the payment was made by someone else in your company, contact our support team using our `online support form <https://www.odoo.com/help>`__."
msgid "**Meetings optimization**: The Odoo consultant is not involved in the process of decision making from a business point of view nor to precise processes and company's internal procedures (unless a specific request or an exception). Project meetings, who will take place once or twice a week, are meant to align on the business needs (SPoC) and to define the way those needs will be implemented in Odoo (Consultant)."
msgstr ""
#: ../../getting_started/documentation.rst:38
msgid "Fill in the sign-in or sign-up screens and you will get your first Odoo database ready to be used."
msgstr ""
#: ../../getting_started/documentation.rst:41
msgid "In order to familiarize yourself with the user interface, take a few minutes to create records: *products, customers, opportunities* or *projects/tasks*. Follow the blinking dots, they give you tips about the user interface as shown in the picture below."
#: ../../getting_started/documentation.rst:39
msgid "**Train the Trainer approach**: The Odoo consultant provides functional training to the SPoC so that he can pass on this knowledge to his collaborators. In order for this approach to be successful, it is necessary that the SPoC is also involved in its own rise in skills through self-learning via the `Odoo documentation <http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "|left_pic|"
msgid "2. Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "|right_pic|"
#: ../../getting_started/documentation.rst:49
msgid "To make sure all the stakeholders involved are always aligned, it is necessary to define and to make the project scope evolve as long as the project implementation is pursuing."
msgstr ""
#: ../../getting_started/documentation.rst:50
msgid "Once you get used to the user interface, have a look at the implementation planners. These are accessible from the Settings app, or from the top progress bar on the right hand side of the main applications."
#: ../../getting_started/documentation.rst:53
msgid "**A clear definition of the initial project scope**: A clear definition of the initial needs is crucial to ensure the project is running smoothly. Indeed, when all the stakeholders share the same vision, the evolution of the needs and the resulting decision-making process are more simple and more clear."
msgstr ""
#: ../../getting_started/documentation.rst:58
msgid "These implementation planners will:"
msgstr ""
#: ../../getting_started/documentation.rst:60
msgid "help you define your goals and KPIs for each application,"
msgstr ""
#: ../../getting_started/documentation.rst:62
msgid "guide you through the different configuration steps,"
msgstr ""
#: ../../getting_started/documentation.rst:64
msgid "and provide you with tips and tricks to getting the most out of Odoo."
#: ../../getting_started/documentation.rst:59
msgid "**Phasing the project**: Favoring an implementation in several coherent phases allowing regular production releases and an evolving takeover of Odoo by the end users have demonstrated its effectiveness over time. This approach also helps to identify gaps and apply corrective actions early in the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:66
msgid "Fill in the first steps of the implementation planner (goals, expectations and KPIs). Our project manager will review them with you during the implementation process."
msgid "**Adopting standard features as a priority**: Odoo offers a great environment to implement slight improvements (customizations) or more important ones (developments). Nevertheless, adoption of the standard solution will be preferred as often as possible in order to optimize project delivery times and provide the user with a long-term stability and fluid scalability of his new tool. Ideally, if an improvement of the software should still be realized, its implementation will be carried out after an experiment of the standard in production."
msgstr ""
#: ../../getting_started/documentation.rst:73
msgid "If you have questions or need support, our project manager will guide you through all the steps. But you can also:"
msgstr ""
#: ../../getting_started/documentation.rst:76
msgid "Read the documentation on our website: `https://www.odoo.com/documentation/user <https://www.odoo.com/documentation/user>`__"
msgstr ""
#: ../../getting_started/documentation.rst:79
msgid "Watch the videos on our eLearning platform (free with your first Success Pack): `https://odoo.thinkific.com/courses/odoo-functional <https://odoo.thinkific.com/courses/odoo-functional>`__"
#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:82
msgid "Watch the webinars on our `Youtube channel <https://www.youtube.com/user/OpenERPonline>`__"
msgid "The gap between the reality of an implementation and the expectations of future users is a crucial factor. Three important aspects must be taken into account from the beginning of the project:"
msgstr ""
#: ../../getting_started/documentation.rst:85
msgid "Or send your questions to our online support team through our `online support form <https://www.odoo.com/help>`__."
#: ../../getting_started/documentation.rst:86
msgid "**Align with the project approach**: Both a clear division of roles and responsibilities and a clear description of the operating modes (validation, problem-solving, etc.) are crucial to the success of an Odoo implementation. It is therefore strongly advised to take the necessary time at the beginning of the project to align with these topics and regularly check that this is still the case."
msgstr ""
#: ../../getting_started/documentation.rst:89
msgid "What do we expect from you?"
#: ../../getting_started/documentation.rst:94
msgid "**Focus on the project success, not on the ideal solution**: The main goal of the SPoC and the Consultant is to carry out the project entrusted to them in order to provide the most effective solution to meet the needs expressed. This goal can sometimes conflict with the end user's vision of an ideal solution. In that case, the SPoC and the consultant will apply the 80-20 rule: focus on 80% of the expressed needs and take out the remaining 20% of the most disadvantageous objectives in terms of cost/benefit ratio (those proportions can of course change over time). Therefore, it will be considered acceptable to integrate a more time-consuming manipulation if a global relief is noted. Changes in business processes may also be proposed to pursue this same objective."
msgstr ""
#: ../../getting_started/documentation.rst:91
msgid "We are used to deploying fully featured projects within 25 to 250 hours of services, which is much faster than any other ERP vendor on the market. Most projects are completed between 1 to 9 calendar months."
#: ../../getting_started/documentation.rst:108
msgid "**Specifications are always EXPLICIT**: Gaps between what is expected and what is delivered are often a source of conflict in a project. In order to avoid being in this delicate situation, we recommend using several types of tools\\* :"
msgstr ""
#: ../../getting_started/documentation.rst:95
msgid "But what really **differentiates between a successful implementation and a slow one, is you, the customer!** From our experience, when our customer is engaged and proactive the implementation is smooth."
#: ../../getting_started/documentation.rst:113
msgid "**The GAP Analysis**: The comparison of the request with the standard features proposed by Odoo will make it possible to identify the gap to be filled by developments/customizations or changes in business processes."
msgstr ""
#: ../../getting_started/documentation.rst:100
msgid "Your internal implementation manager"
#: ../../getting_started/documentation.rst:118
msgid "`The User Story <https://help.rallydev.com/writing-great-user-story>`__: This technique clearly separates the responsibilities between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, and the Consultant who will provide a response to the HOW."
msgstr ""
#: ../../getting_started/documentation.rst:102
msgid "We ask that you maintain a single point of contact within your company to work with our project manager on your Odoo implementation. This is to ensure efficiency and a single knowledge base in your company. Additionally, this person must:"
msgstr ""
#: ../../getting_started/documentation.rst:107
msgid "**Be available at least 2 full days a week** for the project, otherwise you risk slowing down your implementation. More is better with the fastest implementations having a full time project manager."
msgstr ""
#: ../../getting_started/documentation.rst:111
msgid "**Have authority to take decisions** on their own. Odoo usually transforms all departments within a company for the better. There can be many small details that need quick turnarounds for answers and if there is too much back and forth between several internal decision makers within your company it could potentially seriously slow everything down."
msgstr ""
#: ../../getting_started/documentation.rst:117
msgid "**Have the leadership** to train and enforce policies internally with full support from all departments and top management, or be part of top management."
msgstr ""
#: ../../getting_started/documentation.rst:121
msgid "Integrate 90% of your business, not 100%"
msgstr ""
#: ../../getting_started/documentation.rst:123
msgid "You probably chose Odoo because no other software allows for such a high level of automation, feature coverage, and integration. But **don't be an extremist.**"
msgstr ""
#: ../../getting_started/documentation.rst:127
msgid "Customizations cost you time, money, are more complex to maintain, add risks to the implementation, and can cause issues with upgrades."
#: ../../getting_started/documentation.rst:126
msgid "`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A simplified version, a prototype of what is expected to agree on the main lines of expected changes."
msgstr ""
#: ../../getting_started/documentation.rst:130
msgid "Standard Odoo can probably cover 90% of your business processes and requirements. Be flexible on the remaining 10%, otherwise that 10% will cost you twice the original project price. One always underestimates the hidden costs of customization."
msgid "**The Mockup**: In the same idea as the Proof of Concept, it will align with the changes related to the interface."
msgstr ""
#: ../../getting_started/documentation.rst:134
msgid "**Do it the Odoo way, not yours.** Be flexible, use Odoo the way it was designed. Learn how it works and don't try to replicate the way your old system(s) work."
#: ../../getting_started/documentation.rst:133
msgid "To these tools will be added complete transparency on the possibilities and limitations of the software and/or its environment so that all project stakeholders have a clear idea of what can be expected/achieved in the project. We will, therefore, avoid basing our work on hypotheses without verifying its veracity beforehand."
msgstr ""
#: ../../getting_started/documentation.rst:138
msgid "**The project first, customizations second.** If you really want to customize Odoo, phase it towards the end of the project, ideally after having been in production for several months. Once a customer starts using Odoo, they usually drop about 60% of their customization requests as they learn to perform their workflows out of the box, or the Odoo way. It is more important to have all your business processes working than customizing a screen to add a few fields here and there or automating a few emails."
#: ../../getting_started/documentation.rst:139
msgid "*This list can, of course, be completed by other tools that would more adequately meet the realities and needs of your project*"
msgstr ""
#: ../../getting_started/documentation.rst:147
msgid "Our project managers are trained to help you make the right decisions and measure the tradeoffs involved but it is much easier if you are aligned with them on the objectives. Some processes may take more time than your previous system(s), however you need to weigh that increase in time with other decreases in time for other processes. If the net time spent is decreased with your move to Odoo than you are already ahead."
#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:155
msgid "Invest time in learning Odoo"
#: ../../getting_started/documentation.rst:145
msgid "The purpose of the QuickStart methodology is to ensure quick ownership of the tool for end users. Effective communication is therefore crucial to the success of this approach. Its optimization will, therefore, lead us to follow those principles:"
msgstr ""
#: ../../getting_started/documentation.rst:157
msgid "Start your free trial and play with the system. The more comfortable you are navigating Odoo, the better your decisions will be and the quicker and easier your training phases will be."
#: ../../getting_started/documentation.rst:150
msgid "**Sharing the project management documentation**: The best way to ensure that all stakeholders in a project have the same level of knowledge is to provide direct access to the project's tracking document (Project Organizer). This document will contain at least a list of tasks to be performed as part of the implementation for which the priority level and the manager are clearly defined."
msgstr ""
#: ../../getting_started/documentation.rst:161
msgid "Nothing replaces playing with the software, but here are some extra resources:"
#: ../../getting_started/documentation.rst:158
msgid "The Project Organizer is a shared project tracking tool that allows both detailed tracking of ongoing tasks and the overall progress of the project."
msgstr ""
#: ../../getting_started/documentation.rst:164
msgid "Documentation: `https://www.odoo.com/documentation/user <https://www.odoo.com/documentation/user>`__"
#: ../../getting_started/documentation.rst:162
msgid "**Report essential information**: In order to minimize the documentation time to the essentials, we will follow the following good practices:"
msgstr ""
#: ../../getting_started/documentation.rst:167
msgid "Introduction Videos: `https://www.odoo.com/r/videos <https://www.odoo.com/r/videos>`__"
#: ../../getting_started/documentation.rst:166
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:170
msgid "Customer Reviews: `https://www.odoo.com/blog/customer-reviews-6 <https://www.odoo.com/blog/customer-reviews-6>`__"
#: ../../getting_started/documentation.rst:168
msgid "Project statuses will only be established when an important milestone is reached;"
msgstr ""
#: ../../getting_started/documentation.rst:174
msgid "Get things done"
#: ../../getting_started/documentation.rst:171
msgid "Training sessions on the standard or customized solution will be organized."
msgstr ""
#: ../../getting_started/documentation.rst:176
msgid "Want an easy way to start using Odoo? Install Odoo Notes to manage your to-do list for the implementation: `https://www.odoo.com/page/notes <https://www.odoo.com/page/notes>`__. From your Odoo home, go to Apps and install the Notes application."
#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
msgstr ""
#: ../../getting_started/documentation.rst:184
msgid "This module allows you to:"
#: ../../getting_started/documentation.rst:177
msgid "Odoo is a software known for its flexibility and its important evolution capacity. However, a significant amount of development contradicts a fast and sustainable implementation. This is the reason why it is recommended to:"
msgstr ""
#: ../../getting_started/documentation.rst:186
msgid "Manage to-do lists for better interactions with your consultant;"
#: ../../getting_started/documentation.rst:182
msgid "**Develop only for a good reason**: The decision to develop must always be taken when the cost-benefit ratio is positive (saving time on a daily basis, etc.). For example, it will be preferable to realize a significant development in order to reduce the time of a daily operation, rather than an operation to be performed only once a quarter. It is generally accepted that the closer the solution is to the standard, the lighter and more fluid the migration process, and the lower the maintenance costs for both parties. In addition, experience has shown us that 60% of initial development requests are dropped after a few weeks of using standard Odoo (see \"Adopting the standard as a priority\")."
msgstr ""
#: ../../getting_started/documentation.rst:188
msgid "Share Odoo knowledge & good practices with your employees;"
msgstr ""
#: ../../getting_started/documentation.rst:190
msgid "Get acquainted with all the generic tools of Odoo: Messaging, Discussion Groups, Kanban Dashboard, etc."
msgstr ""
#: ../../getting_started/documentation.rst:197
msgid "This application is even compatible with the Etherpad platform (http://etherpad.org). To use these collaborative pads rather than standard Odoo Notes, install the following add-on: Memos Pad."
#: ../../getting_started/documentation.rst:194
msgid "**Replace, without replicate**: There is a good reason for the decision to change the management software has been made. In this context, the moment of implementation is THE right moment to accept and even be a change initiator both in terms of how the software will be used and at the level of the business processes of the company."
msgstr ""
#: ../../getting_started/documentation.rst:202
msgid "What should you expect from us?"
msgid "6. Testing and Validation principles"
msgstr ""
#: ../../getting_started/documentation.rst:205
msgid "Subscription Services"
#: ../../getting_started/documentation.rst:204
msgid "Whether developments are made or not in the implementation, it is crucial to test and validate the correspondence of the solution with the operational needs of the company."
msgstr ""
#: ../../getting_started/documentation.rst:208
msgid "Cloud Hosting"
msgstr ""
#: ../../getting_started/documentation.rst:210
msgid "Odoo provides a top notch cloud infrastructure including backups in three different data centers, database replication, the ability to duplicate your instance in 10 minutes, and more!"
msgid "**Role distribution**: In this context, the Consultant will be responsible for delivering a solution corresponding to the defined specifications; the SPoC will have to test and validate that the solution delivered meets the requirements of the operational reality."
msgstr ""
#: ../../getting_started/documentation.rst:214
msgid "Odoo Online SLA: `https://www.odoo.com/page/odoo-online-sla <https://www.odoo.com/page/odoo-online-sla>`__\\"
msgid "**Change management**: When a change needs to be made to the solution, the noted gap is caused by:"
msgstr ""
#: ../../getting_started/documentation.rst:217
msgid "Odoo Online Security: `https://www.odoo.com/page/security <https://www.odoo.com/fr_FR/page/security>`__"
#: ../../getting_started/documentation.rst:218
msgid "A difference between the specification and the delivered solution - This is a correction for which the Consultant is responsible"
msgstr ""
#: ../../getting_started/documentation.rst:220
msgid "Privacy Policies: `https://www.odoo.com/page/odoo-privacy-policy <https://www.odoo.com/page/odoo-privacy-policy>`__"
msgid "**or**"
msgstr ""
#: ../../getting_started/documentation.rst:224
msgid "Support"
#: ../../getting_started/documentation.rst:222
msgid "A difference between the specification and the imperatives of operational reality - This is a change that is the responsibility of SPoC."
msgstr ""
#: ../../getting_started/documentation.rst:226
msgid "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!"
msgid "7. Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:231
msgid "What kind of support is included?"
#: ../../getting_started/documentation.rst:228
msgid "Importing the history of transactional data is an important issue and must be answered appropriately to allow the project running smoothly. Indeed, this task can be time-consuming and, if its priority is not well defined, prevent production from happening in time. To do this as soon as possible, it will be decided :"
msgstr ""
#: ../../getting_started/documentation.rst:233
msgid "Providing you with relevant material (guidelines, product documentation, etc...)"
#: ../../getting_started/documentation.rst:234
msgid "**Not to import anything**: It often happens that after reflection, importing data history is not considered necessary, these data being, moreover, kept outside Odoo and consolidated for later reporting."
msgstr ""
#: ../../getting_started/documentation.rst:235
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?”)"
#: ../../getting_started/documentation.rst:239
msgid "**To import a limited amount of data before going into production**: When the data history relates to information being processed (purchase orders, invoices, open projects, for example), the need to have this information available from the first day of use in production is real. In this case, the import will be made before the production launch."
msgstr ""
#: ../../getting_started/documentation.rst:237
msgid "Questions related to your account, subscription, or billing"
msgstr ""
#: ../../getting_started/documentation.rst:238
msgid "Bug resolution (blocking issues or unexpected behaviour not due to misconfiguration or customization)"
msgstr ""
#: ../../getting_started/documentation.rst:240
msgid "Issues that might occur in a test database after upgrading to a newer version"
msgstr ""
#: ../../getting_started/documentation.rst:242
msgid "*Odoo Support does not make changes to your production database, but gives you the material and knowledge to do it yourself!*"
msgstr ""
#: ../../getting_started/documentation.rst:245
msgid "What kind of support is not included?"
msgstr ""
#: ../../getting_started/documentation.rst:247
msgid "Questions that require us to understand your business processes in order to help you implement your database"
msgstr ""
#: ../../getting_started/documentation.rst:249
msgid "Training on how to use our software (we will direct you to our many resources)"
msgstr ""
#: ../../getting_started/documentation.rst:250
msgid "Importation of documents into your database"
msgstr ""
#: ../../getting_started/documentation.rst:251
msgid "Guidance on which configurations to apply inside of an application or the database"
msgstr ""
#: ../../getting_started/documentation.rst:252
msgid "How to set up configuration models (Examples include: Inventory Routes, Payment Terms, Warehouses, etc)"
msgstr ""
#: ../../getting_started/documentation.rst:254
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 ""
#: ../../getting_started/documentation.rst:258
msgid "You can get this type of support with a `Success Pack <https://www.odoo.com/pricing-packs>`__. 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 ""
#: ../../getting_started/documentation.rst:263
msgid "Our support team can be contacted through our `online support form <https://www.odoo.com/help>`__."
msgstr ""
#: ../../getting_started/documentation.rst:268
msgid "Upgrades"
msgstr ""
#: ../../getting_started/documentation.rst:270
msgid "Once every two months, Odoo releases a new version. You will get an upgrade button within the **Manage Your Databases** screen. Upgrading your database is at your own discretion, but allows you to benefit from new features."
msgstr ""
#: ../../getting_started/documentation.rst:275
msgid "We provide the option to upgrade in a test environment so that you can evaluate a new version or train your team before the rollout. Simply fill our `online support form <https://www.odoo.com/help>`__ to make this request."
msgstr ""
#: ../../getting_started/documentation.rst:280
msgid "Success Pack Services"
msgstr ""
#: ../../getting_started/documentation.rst:282
msgid "The Success Pack is a package of premium hour-based services performed by a dedicated project manager and business analyst. The initial allotted hours you purchased are purely an estimate and we do not guarantee completion of your project within the first pack. We always strive to complete projects within the initial allotment however any number of factors can contribute to us not being able to do so; for example, a scope expansion (or \"Scope Creep\") in the middle of your implementation, new detail discoveries, or an increase in complexity that was not apparent from the beginning."
msgstr ""
#: ../../getting_started/documentation.rst:291
msgid "The list of services according to your Success Pack is detailed online: `https://www.odoo.com/pricing-packs <https://www.odoo.com/pricing-packs>`__"
msgstr ""
#: ../../getting_started/documentation.rst:294
msgid "The goal of the project manager is to help you get to production within the defined time frame and budget, i.e. the initial number of hours defined in your Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:298
msgid "His/her role includes:"
msgstr ""
#: ../../getting_started/documentation.rst:300
msgid "**Project Management:** Review of your objectives & expectations, phasing of the implementation (roadmap), mapping your business needs to Odoo features."
msgstr ""
#: ../../getting_started/documentation.rst:304
msgid "**Customized Support:** By phone, email or webinar."
msgstr ""
#: ../../getting_started/documentation.rst:306
msgid "**Training, Coaching, and Onsite Consulting:** Remote trainings via screen sharing or training on premises. For on-premise training sessions, you will be expected to pay extra for travel expenses and accommodations for your consultant."
msgstr ""
#: ../../getting_started/documentation.rst:311
msgid "**Configuration:** Decisions about how to implement specific needs in Odoo and advanced configuration (e.g. logistic routes, advanced pricing structures, etc.)"
msgstr ""
#: ../../getting_started/documentation.rst:315
msgid "**Data Import**: We can do it or assist you on how to do it with a template prepared by the project manager."
msgstr ""
#: ../../getting_started/documentation.rst:318
msgid "If you have subscribed to **Studio**, you benefit from the following extra services:"
msgstr ""
#: ../../getting_started/documentation.rst:321
msgid "**Customization of screens:** Studio takes the Drag and Drop approach to customize most screens in any way you see fit."
msgstr ""
#: ../../getting_started/documentation.rst:324
msgid "**Customization of reports (PDF):** Studio will not allow you to customize the reports yourself, however our project managers have access to developers for advanced customizations."
msgstr ""
#: ../../getting_started/documentation.rst:328
msgid "**Website design:** Standard themes are provided to get started at no extra cost. However, our project manager can coach you on how to utilize the building blocks of the website designer. The time spent will consume hours of your Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:333
msgid "**Workflow automations:** Some examples include setting values in fields based on triggers, sending reminders by emails, automating actions, etc. For very advanced automations, our project managers have access to Odoo developers."
msgstr ""
#: ../../getting_started/documentation.rst:338
msgid "If any customization is needed, Odoo Studio App will be required. Customizations made through Odoo Studio App will be maintained and upgraded at each Odoo upgrade, at no extra cost."
msgstr ""
#: ../../getting_started/documentation.rst:342
msgid "All time spent to perform these customizations by our Business Analysts will be deducted from your Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:345
msgid "In case of customizations that cannot be done via Studio and would require a developer’s intervention, this will require Odoo.sh, please speak to your Account Manager for more information. Additionally, any work performed by a developer will add a recurring maintenance fee to your subscription to cover maintenance and upgrade services. This cost will be based on hours spent by the developer: 4€ or $5/month, per hour of development will be added to the subscription fee."
msgstr ""
#: ../../getting_started/documentation.rst:353
msgid "**Example:** A customization that took 2 hours of development will cost: 2 hours deducted from the Success Pack for the customization development 2 * $5 = $10/month as a recurring fee for the maintenance of this customization"
msgstr ""
#: ../../getting_started/documentation.rst:358
msgid "Implementation Methodology"
msgstr ""
#: ../../getting_started/documentation.rst:360
msgid "We follow a **lean and hands-on methodology** that is used to put customers in production in a short period of time and at a low cost."
msgstr ""
#: ../../getting_started/documentation.rst:363
msgid "After the kick-off meeting, we define a phasing plan to deploy Odoo progressively, by groups of apps."
msgstr ""
#: ../../getting_started/documentation.rst:369
msgid "The goal of the **Kick-off call** is for our project manager to come to an understanding of your business in order to propose an implementation plan (phasing). Each phase is the deployment of a set of applications that you will fully use in production at the end of the phase."
msgstr ""
#: ../../getting_started/documentation.rst:375
msgid "For every phase, the steps are the following:"
msgstr ""
#: ../../getting_started/documentation.rst:377
msgid "**Onboarding:** Odoo's project manager will review Odoo's business flows with you, according to your business. The goal is to train you, validate the business process and configure according to your specific needs."
msgstr ""
#: ../../getting_started/documentation.rst:382
msgid "**Data:** Created manually or imported from your existing system. You are responsible for exporting the data from your existing system and Odoo's project manager will import them in Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:386
msgid "**Training:** Once your applications are set up, your data imported, and the system is working smoothly, you will train your users. There will be some back and forth with your Odoo project manager to answer questions and process your feedback."
msgstr ""
#: ../../getting_started/documentation.rst:391
msgid "**Production**: Once everyone is trained, your users start using Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:394
msgid "Once you are comfortable using Odoo, we will fine-tune the process and **automate** some tasks and do the remaining customizations (**extra screens and reports**)."
msgstr ""
#: ../../getting_started/documentation.rst:398
msgid "Once all applications are deployed and users are comfortable with Odoo, our project manager will not work on your project anymore (unless you have new needs) and you will use the support service if you have further questions."
msgstr ""
#: ../../getting_started/documentation.rst:404
msgid "Managing your databases"
msgstr ""
#: ../../getting_started/documentation.rst:406
msgid "To access your databases, go to Odoo.com, sign in and click **My Databases** in the drop-down menu at the top right corner."
msgstr ""
#: ../../getting_started/documentation.rst:412
msgid "Odoo gives you the opportunity to test the system before going live or before upgrading to a newer version. Do not mess up your working environment with test data!"
msgstr ""
#: ../../getting_started/documentation.rst:416
msgid "For those purposes, you can create as many free trials as you want (each available for 15 days). Those instances can be instant copies of your working environment. To do so, go to the Odoo.com account in **My Organizations** page and click **Duplicate**."
msgstr ""
#: ../../getting_started/documentation.rst:427
msgid "You can find more information on how to manage your databases :ref:`here <db_management/documentation>`."
msgstr ""
#: ../../getting_started/documentation.rst:431
msgid "Customer Success"
msgstr ""
#: ../../getting_started/documentation.rst:433
msgid "Odoo is passionate about delighting our customers and ensuring that they have all the resources needed to complete their project."
msgstr ""
#: ../../getting_started/documentation.rst:436
msgid "During the implementation phase, your point of contact is the project manager and eventually the support team."
msgstr ""
#: ../../getting_started/documentation.rst:439
msgid "Once you are in production, you will probably have less interaction with your project manager. At that time, we will assign a member of our Client Success Team to you. They are specialized in the long-term relationship with our customers. They will contact you to showcase new versions, improve the way you work with Odoo, assess your new needs, etc..."
msgstr ""
#: ../../getting_started/documentation.rst:446
msgid "Our internal goal is to keep customers for at least 10 years and offer them a solution that grows with their needs!"
msgstr ""
#: ../../getting_started/documentation.rst:449
msgid "Welcome aboard and enjoy your Odoo experience!"
msgstr ""
#: ../../getting_started/documentation.rst:452
msgid ":doc:`../../db_management/documentation`"
#: ../../getting_started/documentation.rst:246
msgid "**To import after production launch**: When the data history needs to be integrated with Odoo mainly for reporting purposes, it is clear that these can be integrated into the software retrospectively. In this case, the production launch of the solution will precede the required imports."
msgstr ""

52
locale/sources/manufacturing.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-12-22 15:27+0100\n"
"POT-Creation-Date: 2018-09-26 16:07+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -41,102 +41,102 @@ msgid "Setting up a Basic BoM"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:16
msgid "If you choose to manage your manufacturing operations using manufacturing orders only, you will define basic bills of materials without routings. For more information about which method of management to use, review the **Getting Started** section of the *Manufacturing* chapter of the documentation."
msgid "If you choose to manage your manufacturing operations using manufacturing orders only, you will define basic bills of materials without routings."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:22
#: ../../manufacturing/management/bill_configuration.rst:19
msgid "Before creating your first bill of materials, you will need to create a product and at least one component (components are considered products in Odoo). You can do so from :menuselection:`Master Data --> Products`, or on the fly from the relevant fields on the BoM form. Review the Inventory chapter for more information about configuring products. Once you have created a product and at least one component, select them from the relevant dropdown menus to add them to your bill of materials. A new bill of materials can be created from :menuselection:`Master Data --> Bills of Materials`, or using the button on the top of the product form."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:32
#: ../../manufacturing/management/bill_configuration.rst:29
msgid "Under the **Miscellaneous** tab, you can fill additional fields. **Sequence** defines the order in which your BoMs will be selected for production orders, with lower numbers having higher priority. **Version** allows you to track changes to your BoM over time."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:38
#: ../../manufacturing/management/bill_configuration.rst:35
msgid "Adding a Routing to a BoM"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:40
#: ../../manufacturing/management/bill_configuration.rst:37
msgid "A routing defines a series of operations required to manufacture a product and the work center at which each operation is performed. A routing may be added to multiple BoMs, though a BoM may only have one routing. For more information about configuring routings, review the chapter on routings."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:46
#: ../../manufacturing/management/bill_configuration.rst:43
msgid "After enabling routings from :menuselection:`Configuration --> Settings`, you will be able to add a routing to a bill of materials by selecting a routing from the dropdown list or creating one on the fly."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:50
#: ../../manufacturing/management/bill_configuration.rst:47
msgid "You may define the work operation or step in which each component is consumed using the field, **Consumed in Operation** under the **Components** tab. Similarly, you can define the operation at which the product will be produced under the **Miscellaneous** tab using the field **Produced at Operation**. If this field is left blank, the products will be consumed/produced at the final operation in the routing."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:61
#: ../../manufacturing/management/bill_configuration.rst:58
msgid "Adding Byproducts to a BoM"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:63
#: ../../manufacturing/management/bill_configuration.rst:60
msgid "In Odoo, a byproduct is any product produced by a BoM in addition to the primary product."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:66
#: ../../manufacturing/management/bill_configuration.rst:63
msgid "To add byproducts to a BoM, you will first need to enable them from :menuselection:`Configuration --> Settings`."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:72
#: ../../manufacturing/management/bill_configuration.rst:69
msgid "Once byproducts are enabled, you can add them to your bills of materials under the **Byproducts** tab of the bill of materials. You can add any product or products as byproducts. Byproducts are produced in the same step of the routing as the primary product of the BoM."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:81
#: ../../manufacturing/management/bill_configuration.rst:78
msgid "Setting up a BoM for a Product With Sub-Assemblies"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:83
#: ../../manufacturing/management/bill_configuration.rst:80
#: ../../manufacturing/management/sub_assemblies.rst:5
msgid "A subassembly is a manufactured product which is intended to be used as a component of another manufactured product. You may wish to employ sub-assemblies to simplify a complex BoM, to more accurately represent your manufacturing flow, or to use the same subassembly in multiple BoMs. A BoM that employs subassemblies is often referred to as a multi-level BoM."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:90
#: ../../manufacturing/management/bill_configuration.rst:87
#: ../../manufacturing/management/sub_assemblies.rst:12
msgid "Multi-level bills of materials in Odoo are accomplished by creating a top-level BoM and subassembly BoMs. Next, the procurement route of the subassembly product is defined. This ensures that every time a manufacturing order for the top-level product is created, a manufacturing order for each subassembly is created as well."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:97
#: ../../manufacturing/management/bill_configuration.rst:94
msgid "Configure the Top-Level Product BoM"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:99
#: ../../manufacturing/management/bill_configuration.rst:96
#: ../../manufacturing/management/sub_assemblies.rst:21
msgid "To configure a multi-level BoM, create the top-level product and its BoM. Include any subassemblies in the list of components. Create a BoM for each subassembly as you would for any product."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:107
#: ../../manufacturing/management/bill_configuration.rst:104
#: ../../manufacturing/management/sub_assemblies.rst:29
msgid "Configure the Subassembly Product Data"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:109
#: ../../manufacturing/management/bill_configuration.rst:106
#: ../../manufacturing/management/sub_assemblies.rst:31
msgid "On the product form of the subassembly, you must select the routes **Manufacture** and **Make To Order**. The **Manufacture** route takes precedence over the **Buy** route, so selecting the latter will have no effect."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:117
#: ../../manufacturing/management/bill_configuration.rst:114
#: ../../manufacturing/management/sub_assemblies.rst:39
msgid "If you would like to be able to purchase the subassembly in addition to manufacturing it, select **Can be Purchased**. All other fields on the subassembly product form may be configured according to your preference."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:123
#: ../../manufacturing/management/bill_configuration.rst:120
msgid "Using a Single BoM to Describe Several Variants of a Single Product"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:125
#: ../../manufacturing/management/bill_configuration.rst:122
#: ../../manufacturing/management/product_variants.rst:5
msgid "Odoo allows you to use one bill of materials for multiple variants of the same product. Simply enable variants from :menuselection:`Configuration --> Settings`."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:132
#: ../../manufacturing/management/bill_configuration.rst:129
#: ../../manufacturing/management/product_variants.rst:12
msgid "You will then be able to specify which component lines are to be used in the manufacture of each product variant. You may specify multiple variants for each line. If no variant is specified, the line will be used for all variants."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:137
#: ../../manufacturing/management/bill_configuration.rst:134
#: ../../manufacturing/management/product_variants.rst:17
msgid "When defining variant BoMs on a line-item-basis, the **Product Variant** field in the main section of the BoM should be left blank. This field is used when creating a BoM for one variant of a product only."
msgstr ""

98
locale/sources/mobile.pot Normal file
View File

@ -0,0 +1,98 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-09-26 16:05+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../mobile/firebase.rst:5
msgid "Mobile"
msgstr ""
#: ../../mobile/firebase.rst:8
msgid "Setup your Firebase Cloud Messaging"
msgstr ""
#: ../../mobile/firebase.rst:10
msgid "In order to have mobile notifications in our Android app, you need an API key."
msgstr ""
#: ../../mobile/firebase.rst:13
msgid "If it is not automatically configured (for instance for On-premise or Odoo.sh) please follow these steps below to get an API key for the android app."
msgstr ""
#: ../../mobile/firebase.rst:18
msgid "The iOS app doesn't support mobile notifications for Odoo versions < 12."
msgstr ""
#: ../../mobile/firebase.rst:22
msgid "Firebase Settings"
msgstr ""
#: ../../mobile/firebase.rst:25
msgid "Create a new project"
msgstr ""
#: ../../mobile/firebase.rst:27
msgid "First, make sure you to sign in to your Google Account. Then, go to `https://console.firebase.google.com <https://console.firebase.google.com/>`__ and create a new project."
msgstr ""
#: ../../mobile/firebase.rst:34
msgid "Choose a project name, click on **Continue**, then click on **Create project**."
msgstr ""
#: ../../mobile/firebase.rst:37
msgid "When you project is ready, click on **Continue**."
msgstr ""
#: ../../mobile/firebase.rst:39
msgid "You will be redirected to the overview project page (see next screenshot)."
msgstr ""
#: ../../mobile/firebase.rst:43
msgid "Add an app"
msgstr ""
#: ../../mobile/firebase.rst:45
msgid "In the overview page, click on the Android icon."
msgstr ""
#: ../../mobile/firebase.rst:50
msgid "You must use \"com.odoo.com\" as Android package name. Otherwise, it will not work."
msgstr ""
#: ../../mobile/firebase.rst:56
msgid "No need to download the config file, you can click on **Next** twice and skip the fourth step."
msgstr ""
#: ../../mobile/firebase.rst:60
msgid "Get generated API key"
msgstr ""
#: ../../mobile/firebase.rst:62
msgid "On the overview page, go to Project settings:"
msgstr ""
#: ../../mobile/firebase.rst:67
msgid "In **Cloud Messaging**, you will see the **API key** and the **Sender ID** that you need to set in Odoo General Settings."
msgstr ""
#: ../../mobile/firebase.rst:74
msgid "Settings in Odoo"
msgstr ""
#: ../../mobile/firebase.rst:76
msgid "Simply paste the API key and the Sender ID from Cloud Messaging."
msgstr ""

4
locale/sources/point_of_sale.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-26 12:01+0200\n"
"POT-Creation-Date: 2018-09-26 16:07+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -779,7 +779,7 @@ msgid "``# groupadd usbusers``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:252
msgid "Then we add the user who will run the OpenERP server to ``usbusers``"
msgid "Then we add the user who will run the Odoo server to ``usbusers``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:254

8
locale/sources/purchase.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-12-22 15:27+0100\n"
"POT-Creation-Date: 2018-09-26 16:07+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1183,7 +1183,7 @@ msgid "Select your supplier in the **Vendor** menu, or create it on-the-fly by c
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Shipment"
msgid "Receipt"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0

534
locale/sources/sales.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-23 12:10+0200\n"
"POT-Creation-Date: 2018-09-26 16:07+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -160,441 +160,321 @@ msgstr ""
msgid "Invoicing Method"
msgstr ""
#: ../../sales/invoicing/services.rst:3
msgid "Services"
#: ../../sales/invoicing/down_payment.rst:3
msgid "Request a down payment"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:3
msgid "How to invoice milestones of a project?"
#: ../../sales/invoicing/down_payment.rst:5
msgid "A down payment is an initial, partial payment, with the agreement that the rest will be paid later. For expensive orders or projects, it is a way to protect yourself and make sure your customer is serious."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:5
msgid "There are different kind of service sales: prepaid volume of hours/days (e.g. support contract), billing based on time and material (e.g. billing consulting hours) or a fixed price contract (e.g. a project)."
#: ../../sales/invoicing/down_payment.rst:10
msgid "First time you request a down payment"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:9
msgid "In this section, we will have a look at how to invoice milestones of a project."
#: ../../sales/invoicing/down_payment.rst:12
msgid "When you confirm a sale, you can create an invoice and select a down payment option. It can either be a fixed amount or a percentage of the total amount."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:12
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. For example, a marketing agency hired for a new product launch could break down a project into the following milestones, each of them considered as one service with a fixed price on the sale order :"
#: ../../sales/invoicing/down_payment.rst:16
msgid "The first time you request a down payment you can select an income account and a tax setting that will be reused for next down payments."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:19
msgid "Milestone 1 : Marketing strategy audit - 5 000 euros"
#: ../../sales/invoicing/down_payment.rst:22
msgid "You will then see the invoice for the down payment."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:21
msgid "Milestone 2 : Brand Identity - 10 000 euros"
#: ../../sales/invoicing/down_payment.rst:27
msgid "On the subsequent or final invoice, any prepayment made will be automatically deducted."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:23
msgid "Milestone 3 : Campaign launch & PR - 8 500 euros"
#: ../../sales/invoicing/down_payment.rst:34
msgid "Modify the income account and customer taxes"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:25
msgid "In this case, an invoice will be sent to the customer each time a milestone will be successfully reached. That 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 times."
#: ../../sales/invoicing/down_payment.rst:36
msgid "From the products list, search for *Down Payment*."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:32
msgid "You can also use milestones to invoice percentages of the entire project. For example, for a million euros project, your company might require a 15% upfront payment, 30% at the midpoint and the balance at the contract conclusion. In that case, each payment will be considered as one milestone."
#: ../../sales/invoicing/down_payment.rst:41
msgid "You can then edit it, under the invoicing tab you will be able to change the income account & customer taxes."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:39
#: ../../sales/invoicing/services/reinvoice.rst:26
#: ../../sales/invoicing/services/reinvoice.rst:95
#: ../../sales/invoicing/services/support.rst:17
#: ../../sales/send_quotations/quote_template.rst:10
msgid "Configuration"
#: ../../sales/invoicing/expense.rst:3
msgid "Re-invoice expenses to customers"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:42
msgid "Install the Sales application"
#: ../../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 an consultant paying an 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 ""
#: ../../sales/invoicing/services/milestones.rst:44
#: ../../sales/invoicing/services/reinvoice.rst:28
msgid "In order to sell services and to send invoices, you need to install the **Sales** application, from the **Apps** icon."
#: ../../sales/invoicing/expense.rst:12
#: ../../sales/invoicing/time_materials.rst:64
msgid "Expenses configuration"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:51
msgid "Create products"
#: ../../sales/invoicing/expense.rst:14
#: ../../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 ""
#: ../../sales/invoicing/services/milestones.rst:53
msgid "In Odoo, each milestone of your project is considered as a product. From the **Sales** application, use the menu :menuselection:`Sales --> Products`, create a new product with the following setup:"
#: ../../sales/invoicing/expense.rst:17
#: ../../sales/invoicing/time_materials.rst:69
msgid "You should also activate the analytic accounts feature to link expenses to the sales order, to do so, go to :menuselection:`Invoicing --> Configuration --> Settings` and activate *Analytic Accounting*."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:57
msgid "**Name**: Strategy audit"
#: ../../sales/invoicing/expense.rst:22
#: ../../sales/invoicing/time_materials.rst:74
msgid "Add expenses to your sales order"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:59
#: ../../sales/invoicing/services/support.rst:50
msgid "**Product Type**: Service"
#: ../../sales/invoicing/expense.rst:24
#: ../../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 ""
#: ../../sales/invoicing/services/milestones.rst:61
msgid "**Invoicing Policy**: Delivered Quantities, since you will invoice your milestone after it has been delivered"
#: ../../sales/invoicing/expense.rst:27
#: ../../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 ""
#: ../../sales/invoicing/services/milestones.rst:64
msgid "**Track Service**: Manually set quantities on order, as you complete each milestone, you will manually update their quantity from the **Delivered** tab on your sale order"
#: ../../sales/invoicing/expense.rst:33
#: ../../sales/invoicing/time_materials.rst:85
msgid "Here, we are creating a *Hotel* product:"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:72
msgid "Apply the same configuration for the others milestones."
#: ../../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 ""
#: ../../sales/invoicing/services/milestones.rst:75
msgid "Managing your project"
#: ../../sales/invoicing/expense.rst:45
#: ../../sales/invoicing/time_materials.rst:97
msgid "To modify or create more products go to :menuselection:`Expenses --> Configuration --> Expense products`."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:78
msgid "Quotations and sale orders"
#: ../../sales/invoicing/expense.rst:48
#: ../../sales/invoicing/time_materials.rst:100
msgid "Back on the expense, add the original sale order in the expense to submit."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:80
msgid "Now that your milestones (or products) are created, you can create a quotation or a sale order with each line corresponding to one milestone. For each line, set the **Ordered Quantity** to ``1`` as each milestone is completed once. Once the quotation is confirmed and transformed into a sale order, you will be able to change the delivered quantities when the corresponding milestone has been achieved."
#: ../../sales/invoicing/expense.rst:54
#: ../../sales/invoicing/time_materials.rst:106
msgid "It can then be submitted to the manager, approved and finally posted."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:91
#: ../../sales/invoicing/expense.rst:65
#: ../../sales/invoicing/time_materials.rst:117
msgid "It will then be in the sales order and ready to be invoiced."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:3
msgid "Invoice based on delivered or ordered quantities"
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:5
msgid "Depending on your business and what you sell, you have two options for invoicing:"
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:8
msgid "Invoice on ordered quantity: invoice the full order as soon as the sales order is confirmed."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:10
msgid "Invoice on delivered quantity: invoice on what you delivered even if it's a partial delivery."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:13
msgid "Invoice on ordered quantity is the default mode."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:15
msgid "The benefits of using *Invoice on delivered quantity* depends on your type of business, when you sell material, liquids or food in large quantities the quantity might diverge a little bit and it is therefore better to invoice the actual delivered quantity."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:21
msgid "You also have the ability to invoice manually, letting you control every options: invoice ready to invoice lines, invoice a percentage (advance), invoice a fixed advance."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:26
msgid "Decide the policy on a product page"
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:28
msgid "From any products page, under the invoicing tab you will find the invoicing policy and select the one you want."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:35
msgid "Send the invoice"
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:37
msgid "Once you confirm the sale, you can see your delivered and invoiced quantities."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:43
msgid "If you set it in ordered quantities, you can invoice as soon as the sale is confirmed. If however you selected delivered quantities, you will first have to validate the delivery."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:47
msgid "Once the products are delivered, you can invoice your customer. Odoo will automatically add the quantities to invoiced based on how many you delivered if you did a partial delivery."
msgstr ""
#: ../../sales/invoicing/milestone.rst:3
msgid "Invoice project milestones"
msgstr ""
#: ../../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 ""
#: ../../sales/invoicing/milestone.rst:13
msgid "Create milestone products"
msgstr ""
#: ../../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 ""
#: ../../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 ""
#: ../../sales/invoicing/milestone.rst:25
msgid "Invoice milestones"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:93
msgid "Let's assume that your first milestone (the strategy audit) has been successfully delivered and you want to invoice it to your customer. On the sale order, click on **Edit** and set the **Delivered Quantity** of the related product to ``1``."
#: ../../sales/invoicing/milestone.rst:27
msgid "From the sales order, you can manually edit the quantity delivered as you complete a milestone."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:99
msgid "As soon as the above modification has been saved, you will notice that the color of the line has changed to blue, meaning that the service can now be invoiced. In the same time, the invoice status of the SO has changed from **Nothing To Invoice** to **To Invoice**"
#: ../../sales/invoicing/milestone.rst:33
msgid "You can then invoice that first milestone."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:104
msgid "Click on **Create invoice** and, in the new window that pops up, select **Invoiceable lines** and validate. It will create a new invoice (in draft status) with only the **strategy audit** product as invoiceable."
#: ../../sales/invoicing/proforma.rst:3
#: ../../sales/invoicing/proforma.rst:22
msgid "Send a pro-forma invoice"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:112
msgid "In order to be able to invoice a product, you need to set up the **Accounting** application and to configure an accounting journal and a chart of account. Click on the following link to learn more: :doc:`../../../accounting/overview/getting_started/setup`"
#: ../../sales/invoicing/proforma.rst:5
msgid "A pro-forma invoice is an abridged or estimated invoice 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. Pro-forma invoices are commonly used as preliminary invoices with a quotation, or for customs purposes in importation. They differ from a normal invoice in not being a demand or request for payment."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:117
msgid "Back on your sale order, you will notice that the **Invoiced** column of your order line has been updated accordingly and that the **Invoice Status** is back to **Nothing to Invoice**."
#: ../../sales/invoicing/proforma.rst:13
#: ../../sales/send_quotations/different_addresses.rst:10
msgid "Activate the feature"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:121
msgid "Follow the same workflow to invoice your remaining milestones."
#: ../../sales/invoicing/proforma.rst:15
msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Pro-Forma Invoice* feature."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:124
msgid ":doc:`reinvoice`"
#: ../../sales/invoicing/proforma.rst:24
msgid "From any quotation or sales order, you know have an option to send a pro-forma invoice."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:125
#: ../../sales/invoicing/services/reinvoice.rst:185
msgid ":doc:`support`"
#: ../../sales/invoicing/proforma.rst:30
msgid "When you click on send, Odoo will send an email with the pro-forma invoice in attachment."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:3
msgid "How to re-invoice expenses to your customers?"
#: ../../sales/invoicing/subscriptions.rst:3
msgid "Sell subscriptions"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.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 an employee paying a parking spot for a meeting with your client. As a company, you would like to be able to invoice that expense to your client."
#: ../../sales/invoicing/subscriptions.rst:5
msgid "Selling subscription products will give you predictable revenue, making planning ahead much easier."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:11
msgid "In this documentation we will see two use cases. The first, very basic, consists of invoicing a simple expense to your client like you would do for a product. The second, more advanced, will consist of invoicing expenses entered in your expense system by your employees directly to your customer."
#: ../../sales/invoicing/subscriptions.rst:9
msgid "Make a subscription from a sales order"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:18
msgid "Use case 1: Simple expense invoicing"
#: ../../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."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:20
msgid "Let's take the following example. You are working on a promotion campaign for one of your customers (``Agrolait``) and you have to print a lot of copies. Those copies are an expense for your company and you would like to invoice them."
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:35
msgid "Create product to be expensed"
#: ../../sales/invoicing/time_materials.rst:3
msgid "Invoice based on time and materials"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:37
msgid "You will need now to create a product called ``Copies``."
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:39
#: ../../sales/invoicing/services/reinvoice.rst:112
msgid "From your **Sales** module, go to :menuselection:`Sales --> Products` and create a product as follows:"
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:42
msgid "**Product type**: consumable"
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:44
msgid "**Invoicing policy**: on delivered quantities (you will manually set the quantities to invoice on the sale order)"
#: ../../sales/invoicing/time_materials.rst:19
msgid "Invoice time configuration"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:51
msgid "Create a sale order"
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:53
msgid "Now that your product is correctly set up, you can create a sale order for that product (from the menu :menuselection:`Sales --> Sales Orders`) with the ordered quantities set to 0. Click on **Confirm the Sale** to create the sale order. You will be able then to manually change the delivered quantities on the sale order to reinvoice the copies to your customer."
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:64
#: ../../sales/invoicing/services/reinvoice.rst:177
msgid "Invoice expense to your client"
#: ../../sales/invoicing/time_materials.rst:32
msgid "Invoice your time spent"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:66
msgid "At the end of the month, you have printed ``1000`` copies on behalf of your client and you want to re-invoice them. From the related sale order, click on **Delivered Quantities**, manually enter the correct amount of copies and click on **Save**. Your order line will turn blue, meaning that it is ready to be invoiced. Click on **Create invoice**."
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:73
msgid "The total amount on your sale order will be of 0 as it is computed on the ordered quantities. It is your invoice which will compute the correct amount due by your customer."
#: ../../sales/invoicing/time_materials.rst:41
msgid "You could also add the task to an existing project."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:77
msgid "The invoice generated is in draft, so you can always control the quantities and change the amount if needed. You will notice that the amount to be invoiced is based here on the delivered quantities."
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:84
msgid "Click on validate to issue the payment to your customer."
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:87
msgid "Use case 2: Invoice expenses via the expense module"
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:89
msgid "To illustrate this case, let's imagine that your company sells some consultancy service to your customer ``Agrolait`` and both parties agreed that the distance covered by your consultant will be re-invoiced at cost."
#: ../../sales/invoicing/time_materials.rst:58
msgid "From the sales order, you can then invoice those hours."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:97
msgid "Here, you will need to install two more modules:"
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:99
msgid "Expense Tracker"
#: ../../sales/invoicing/time_materials.rst:120
msgid "Invoice purchases"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:101
msgid "Accounting, where you will need to activate the analytic accounting from the settings"
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:108
msgid "Create a product to be expensed"
#: ../../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 ""
#: ../../sales/invoicing/services/reinvoice.rst:110
msgid "You will now need to create a product called ``Kilometers``."
#: ../../sales/invoicing/time_materials.rst:129
msgid "While making the purchase order don't forget to add the right analytic account."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:115
msgid "Product can be expensed"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:117
msgid "Product type: Service"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:119
msgid "Invoicing policy: invoice based on time and material"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:121
msgid "Expense invoicing policy: At cost"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:123
msgid "Track service: manually set quantities on order"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:129
msgid "Create a sales order"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:131
msgid "Still from the Sales module, go to :menuselection:`Sales --> Sales Orders` and add your product **Consultancy** on the order line."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:135
msgid "If your product doesn't exist yet, you can configure it on the fly from the SO. Just type the name on the **product** field and click on **Create and edit** to configure it."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:139
msgid "Depending on your product configuration, an **Analytic Account** may have been generated automatically. If not, you can easily create one in order to link your expenses to the sale order. Do not forget to confirm the sale order."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:148
msgid "Refer to the documentation :doc:`../../../accounting/others/analytic/usage` to learn more about that concept."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:152
msgid "Create expense and link it to SO"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:154
msgid "Let's assume that your consultant covered ``1.000km`` in October as part of his consultancy project. We will create a expense for it and link it to the related sales order thanks to the analytic account."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:158
msgid "Go to the **Expenses** module and click on **Create**. Record your expense as follows:"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:161
msgid "**Expense description**: Kilometers October 2015"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:163
msgid "**Product**: Kilometers"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:165
msgid "**Quantity**: 1.000"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:167
msgid "**Analytic account**: SO0019 - Agrolait"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:172
msgid "Click on **Submit to manager**. As soon as the expense has been validated and posted to the journal entries, a new line corresponding to the expense will automatically be generated on the sale order."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:179
msgid "You can now invoice the invoiceable lines to your customer."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:186
msgid ":doc:`milestones`"
msgstr ""
#: ../../sales/invoicing/services/support.rst:3
msgid "How to invoice a support contract (prepaid hours)?"
msgstr ""
#: ../../sales/invoicing/services/support.rst:5
msgid "There are different kinds of service sales: prepaid volume of hours/days (e.g. support contract), billing based on time and material (e.g. billing consulting hours) and a fixed price contract (e.g. a project)."
msgstr ""
#: ../../sales/invoicing/services/support.rst:9
msgid "In this section, we will have a look at how to sell and keep track of a pre-paid support contract."
msgstr ""
#: ../../sales/invoicing/services/support.rst:12
msgid "As an example, you may sell a pack of ``50 Hours`` of support at ``$25,000``. The price is fixed and charged initially. But you want to keep track of the support service you did for the customer."
msgstr ""
#: ../../sales/invoicing/services/support.rst:20
msgid "Install the Sales and Timesheet applications"
msgstr ""
#: ../../sales/invoicing/services/support.rst:22
msgid "In order to sell services, you need to install the **Sales** application, from the **Apps** icon. Install also the **Timesheets** application if you want to track support services you worked on every contract."
msgstr ""
#: ../../sales/invoicing/services/support.rst:33
msgid "Create Products"
msgstr ""
#: ../../sales/invoicing/services/support.rst:35
msgid "By default, products are sold by number of units. In order to sell services ``per hour``, you must allow using multiple unit of measures. From the **Sales** application, go to the menu :menuselection:`Configuration --> Settings`. From this screen, activate the multiple **Unit of Measures** option."
msgstr ""
#: ../../sales/invoicing/services/support.rst:44
msgid "In order to sell a support contract, you must create a product for every support contract you sell. From the **Sales** application, use the menu :menuselection:`Sales --> Products`, create a new product with the following setup:"
msgstr ""
#: ../../sales/invoicing/services/support.rst:48
msgid "**Name**: Technical Support"
msgstr ""
#: ../../sales/invoicing/services/support.rst:52
msgid "**Unit of Measure**: Hours"
msgstr ""
#: ../../sales/invoicing/services/support.rst:54
msgid "**Invoicing Policy**: Ordered Quantities, since the service is prepaid, we will invoice the service based on what has been ordered, not based on delivered quantities."
msgstr ""
#: ../../sales/invoicing/services/support.rst:58
msgid "**Track Service**: Timesheet on contracts. An analytic account will automatically be created for every order containing this service so that you can track hours in the related account."
msgstr ""
#: ../../sales/invoicing/services/support.rst:66
msgid "There are different ways to track the service related to a sales order or product sold. With the above configuration, you can only sell one support contract per order. If your customer orders several service contracts on timesheet, you will have to split the quotation into several orders."
msgstr ""
#: ../../sales/invoicing/services/support.rst:72
msgid "Note that you can sell in different unit of measure than hours, example: days, pack of 40h, etc. To do that, just create a new unit of measure in the **Unit of Measure** category and set a conversion ratio compared to **Hours** (example: ``1 day = 8 hours``)."
msgstr ""
#: ../../sales/invoicing/services/support.rst:78
msgid "Managing support contract"
msgstr ""
#: ../../sales/invoicing/services/support.rst:81
msgid "Quotations and Sales Orders"
msgstr ""
#: ../../sales/invoicing/services/support.rst:83
msgid "Once the product is created, you can create a quotation or a sales order with the related product. Once the quotation is confirmed and transformed into a sales order, your users will be able to record services related to this support contract using the timesheet application."
msgstr ""
#: ../../sales/invoicing/services/support.rst:93
msgid "Timesheets"
msgstr ""
#: ../../sales/invoicing/services/support.rst:95
msgid "To track the service you do on a specific contract, you should use the timesheet application. An analytic account related to the sale order has been automatically created (``SO009 - Agrolait`` on the screenshot here above), so you can start tracking services as soon as it has been sold."
msgstr ""
#: ../../sales/invoicing/services/support.rst:104
msgid "Control delivered support on the sales order"
msgstr ""
#: ../../sales/invoicing/services/support.rst:106
msgid "From the **Sales** application, use the menu :menuselection:`Sales --> Sales Orders` to control the progress of every order. On the sales order line related to the support contract, you should see the **Delivered Quantities** that are updated automatically, based on the number of hours in the timesheet."
msgstr ""
#: ../../sales/invoicing/services/support.rst:116
msgid "Upselling and renewal"
msgstr ""
#: ../../sales/invoicing/services/support.rst:118
msgid "If the number of hours you performed on the support contract is bigger or equal to the number of hours the customer purchased, you are suggested to sell an extra contract to the customer since they used all their quota of service. Periodically (ideally once every two weeks), you should check the sales order that are in such a case. To do so, go to :menuselection:`Sales --> Invoicing --> Orders to Upsell`."
msgstr ""
#: ../../sales/invoicing/services/support.rst:127
msgid "If you use Odoo CRM, a good practice is to create an opportunity for every sale order in upselling invoice status so that you easily track your upselling effort."
msgstr ""
#: ../../sales/invoicing/services/support.rst:131
msgid "If you sell an extra support contract, you can either add a new line on the existing sales order (thus, you continue to timesheet on the same order) or create a new order (thus, people will timesheet their hours on the new contract). To unmark the sales order as **Upselling**, you can set the sales order as done and it will disappear from your upselling list."
msgstr ""
#: ../../sales/invoicing/services/support.rst:138
msgid "Special Configuration"
msgstr ""
#: ../../sales/invoicing/services/support.rst:140
msgid "When creating the product form, you may set a different approach to track the service:"
msgstr ""
#: ../../sales/invoicing/services/support.rst:143
msgid "**Create task and track hours**: in this mode, a task is created for every sales order line. Then when you do the timesheet, you don't record hours on a sales order/contract, but you record hours on a task (that represents the contract). The advantage of this solution is that it allows to sell several service contracts within the same sales order."
msgstr ""
#: ../../sales/invoicing/services/support.rst:150
msgid "**Manually**: you can use this mode if you don't record timesheets in Odoo. The number of hours you worked on a specific contract can be recorded manually on the sales order line directly, in the delivered quantity field."
msgstr ""
#: ../../sales/invoicing/services/support.rst:156
msgid ":doc:`../../../inventory/settings/products/uom`"
#: ../../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 ""
#: ../../sales/products_prices.rst:3
@ -901,10 +781,6 @@ msgstr ""
msgid "In Odoo you can configure different addresses for delivery and invoicing. This is key, not everyone will have the same delivery location as their invoice location."
msgstr ""
#: ../../sales/send_quotations/different_addresses.rst:10
msgid "Activate the feature"
msgstr ""
#: ../../sales/send_quotations/different_addresses.rst:12
msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Customer Addresses* feature."
msgstr ""
@ -1054,6 +930,10 @@ msgstr ""
msgid "If you often sell the same products or services, you can save a lot of time by creating custom quotation templates. By using a template you can send a complete quotation in no time."
msgstr ""
#: ../../sales/send_quotations/quote_template.rst:10
msgid "Configuration"
msgstr ""
#: ../../sales/send_quotations/quote_template.rst:12
msgid "For this feature to work, go to :menuselection:`Sales --> Configuration --> Settings` and activate *Quotations Templates*."
msgstr ""