documentation/locale/th/LC_MESSAGES/accounting.po

# 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 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-19 13:03+0100\n"
"PO-Revision-Date: 2019-10-03 09:45+0000\n"
"Language-Team: Thai (https://www.transifex.com/odoo/teams/41243/th/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: th\n"
"Plural-Forms: nplurals=1; plural=0;\n"

#: ../../accounting.rst:5 ../../accounting/localizations/mexico.rst:319
msgid "Accounting"
msgstr ""

#: ../../accounting/bank.rst:3
msgid "Bank & Cash"
msgstr ""

#: ../../accounting/bank/feeds.rst:3
msgid "Bank Feeds"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:3
#: ../../accounting/others/multicurrencies/how_it_works.rst:145
msgid "Bank Statements"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:4
msgid ""
"Importing your bank statements in Odoo Accounting allows you to keep track "
"of the financial movements that occur on your bank accounts and reconcile "
"them with the transactions recorded in your accounting."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:8
msgid ""
"The easiest way to do so is by synchronizing. To do so, please read the "
"related documentation: :doc:`bank_synchronization`."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:11
msgid ""
"However, if your bank account is not synchronized with Odoo, you still have "
"two options:"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:13
msgid "Import the bank statement files delivered by your bank"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:14
msgid "Register the bank statements manually"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:17
msgid "Import bank statements files"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:18
msgid "Odoo supports multiple file formats to import bank statements:"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:20
msgid "SEPA recommended Cash Management format (CAMT.053)"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:21
msgid "Comma-separated values (.CSV)"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:22
msgid "Open Financial Exchange (.OFX)"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:23
msgid "Quicken Interchange Format (.QIF)"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:24
msgid "Belgium Coded Statement of Account (.CODA)"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:26
msgid ""
"To import them, go to :menuselection:`Accounting --> Overview --> Bank`, "
"click on *Import Statements*, or on the three dots, and then on *Import "
"Statement*."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:33
msgid "Next, select the file you want to import and click on *Import*."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:35
msgid ""
"Odoo opens an **import tool** with which you can set the **Formatting "
"Options** and **map** the different columns you want to import."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:43
msgid ""
"Quicken Interchange Format (.QIF) is an older file format that is not "
"supported since 2005. If possible, prefer OFX files over QIF."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:47
msgid "Register bank statements manually"
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:48
msgid "If needed, you can also record your bank statements manually."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:50
msgid ""
"To do so, go to :menuselection:`Accounting --> Overview --> Bank`, click on "
"*Create Statements*, or on the three dots, and then on *New Statement*."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:53
msgid ""
"Add a new line for each transaction written on the original bank statement."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:55
msgid ""
"To ease the reconciliation process, make sure to fill out the *Partner* "
"field. You can also write the payments’ references in the *Label* field."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:63
msgid ""
"The *Ending Balance* and the *Computed Balance* should have the same amount."
" If it is not the case, make sure that there is no mistake in the "
"transactions’ amounts."
msgstr ""

#: ../../accounting/bank/feeds/bank_statements.rst:67
msgid ":doc:`bank_synchronization`"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:3
msgid "Bank Synchronization: Automatic Import"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:5
msgid ""
"Odoo can synchronize directly with your bank to get all bank statements "
"imported automatically into your database."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:8
msgid ""
"To check if your bank is compatible with Odoo, go to `Odoo Accounting "
"Features <https://www.odoo.com/page/accounting-features>`_, and search for "
"your bank in the *Supported Banks* section."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:16
msgid ""
"The countries which are fully supported include the United States, Canada, "
"New Zealand, Austria, and Belgium."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:19
msgid ""
"More than 30 countries are partially supported, including Colombia, India, "
"France, and Spain."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:21
msgid "To connect to the banks, Odoo uses multiple web-services:"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:23
msgid "**Plaid**: Mainly for the U.S"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:24
msgid "**Yodlee**: Worldwide"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:25
msgid "**Ponto**: For a growing number of European Banks"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:28
#: ../../accounting/bank/feeds/paypal.rst:11
#: ../../accounting/bank/misc/batch.rst:21
#: ../../accounting/bank/misc/interbank.rst:14
#: ../../accounting/bank/reconciliation/use_cases.rst:16
#: ../../accounting/bank/setup/foreign_currency.rst:22
#: ../../accounting/bank/setup/manage_cash_register.rst:9
#: ../../accounting/fiscality/taxes/B2B_B2C.rst:60
#: ../../accounting/fiscality/taxes/retention.rst:23
#: ../../accounting/fiscality/taxes/taxcloud.rst:12
#: ../../accounting/localizations/argentina.rst:24
#: ../../accounting/localizations/colombia.rst:27
#: ../../accounting/localizations/mexico.rst:35
#: ../../accounting/others/adviser/budget.rst:21
#: ../../accounting/others/analytic/purchases_expenses.rst:18
#: ../../accounting/others/analytic/timesheets.rst:16
#: ../../accounting/others/multicurrencies/exchange.rst:16
#: ../../accounting/others/multicurrencies/how_it_works.rst:15
#: ../../accounting/others/multicurrencies/invoices_payments.rst:22
#: ../../accounting/payables/misc/employee_expense.rst:17
#: ../../accounting/payables/pay/check.rst:11
#: ../../accounting/payables/pay/sepa.rst:26
#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:30
#: ../../accounting/payables/supplier_bills/manage.rst:31
#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:13
#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:20
#: ../../accounting/receivables/customer_invoices/payment_terms.rst:37
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:18
#: ../../accounting/receivables/customer_payments/check.rst:39
#: ../../accounting/receivables/customer_payments/check.rst:103
#: ../../accounting/receivables/customer_payments/credit_cards.rst:40
#: ../../accounting/receivables/customer_payments/credit_cards.rst:112
msgid "Configuration"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:31
msgid "Odoo Online Users"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:33
msgid ""
"Make sure the **Automatic Import** feature is activated by going to "
":menuselection:`Accounting --> Configuration --> Settings` in the *Bank & "
"Cash* section."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:37
msgid "Odoo Enterprise Users"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:39
msgid ""
"If you plan to use a bank interface with your Odoo Enterprise subscription, "
"you don’t have to do anything special. Just make sure that your database is "
"registered with your Odoo Enterprise contract."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:43
msgid ""
"you might want to check that you don't have a firewall/proxy blocking the "
"following address:"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:45
msgid "https://onlinesync.odoo.com/"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:48
msgid "Sync your bank feeds"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:50
msgid ""
"First, make sure that the **Automated Bank Synchronization** is activated in"
" your journal."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:52
msgid ""
"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, "
"then open your *Bank Journal*, click on *Edit*, and select **Automated Bank "
"Synchronization** in the *Bank Feed* field."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:59
msgid "You can then connect Odoo to your bank."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:61
msgid ""
"To do so, go to :menuselection:`Accounting --> Configuration --> Add a Bank "
"Account`, and follow the steps."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:64
msgid ""
"Once done, go back to your *Accounting dashboard*. You should now see a "
"**Synchronize Now** button on your *Bank* card. Click on this button and "
"enter your bank credentials."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:71
msgid "After this, your bank feeds will be regularly synchronized."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:74
#: ../../accounting/localizations/mexico.rst:579
msgid "FAQ"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:77
msgid "The synchronization is not working in real-time, is that normal?"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:79
msgid ""
"The process is not intended to work in real-time as third party providers "
"synchronize your accounts at different intervals. To force the "
"synchronization and fetch the statements, go to your *Accounting dashboard*,"
" and click on the *Synchronize Now* button."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:83
msgid ""
"A transaction can be visible in your bank account, but not be fetched if it "
"has the status *Pending*. Only transactions with the *Posted* status will be"
" retrieved. If it is not *Posted* yet, you will have to wait until the "
"status changes."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:88
msgid "Is the Automatic Import feature included in my contract?"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:90
msgid ""
"**Enterprise Version**: Yes, if you have a valid enterprise contract linked "
"to your database."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:91
msgid ""
"**Community Version**: No, this feature is not included in the Community "
"Version."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:92
msgid ""
"**Online Version**: Yes, even if you benefit from the One App Free contract."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:95
msgid "Some banks have a status \"Beta,\" what does this mean?"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:97
msgid ""
"This means that banking institutions are not yet fully supported by our "
"Third Party Provider. Bugs or other problems may arise. Odoo does not "
"support technical problems that occur with banks in the Beta phase, but the "
"user may still choose to connect. Connecting with these banks can aid in the"
" development process since the Provider will have real data & feedback from "
"the connection."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:103
msgid "Why do my transactions only synchronize when I refresh manually?"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:105
msgid ""
"Some banks have additional security measures and require extra steps, such "
"as an SMS/email authentication code or another type of MFA. Because of this,"
" the integrator cannot pull transactions until the security code is "
"provided."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:110
msgid "Not all of my past transactions are in Odoo, why?"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:112
msgid "Transactions can only be fetched up to 3 months in the past."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:115
msgid "Why don’t I see any transactions?"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:116
msgid ""
"When you first connect with your bank, you will be prompted to add each "
"account to its own journal. If you skip this step, you will not be able to "
"see your transactions in Odoo."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:119
msgid ""
"If your bank account is properly linked to a journal and posted transactions"
" are not visible in your database, please `submit a support ticket "
"<https://www.odoo.com/help>`_."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:123
msgid "How can I update my bank credentials?"
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:124
msgid ""
"You can update your credentials in :doc:`Developer mode "
"<../../../general/developer_mode/activate>`."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:127
msgid ""
"Then go to :menuselection:`Accounting --> Configuration --> Online "
"Synchronization`, and open the Institution you want to edit, and click on "
"*Update Credentials*."
msgstr ""

#: ../../accounting/bank/feeds/bank_synchronization.rst:131
msgid ":doc:`bank_statements`"
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:3
msgid "How to synchronize your PayPal account with Odoo?"
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:5
msgid ""
"With Odoo, you can synchronize your PayPal account. That way, you don't have"
" to record all your PayPal transaction in your favorite accounting software."
" The synchronization is done every 4 hours, and you can start reconciling "
"PayPal payments in just a click."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:14
msgid "Install the account_yodlee module"
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:16
msgid ""
"Start by installing the **account_yodlee** module, if it is not already "
"installed. To do that, got the the menu :menuselection:`Accounting --> "
"Configuration --> Settings` of the accounting application. In the section "
"**Bank & Cash**, set the option **Bank Interface - Sync your bank feeds "
"automatically**."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:25
msgid "Click on the apply button once it's done."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:28
msgid "Setup your PayPal account"
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:30
msgid ""
"A PayPal account in Odoo is managed like a bank account. To setup your "
"PayPal account, use the menu :menuselection:`Configuration --> Bank "
"Accounts`. Create a new bank account and name it **PayPal**. In the bank "
"field, you can set **PayPal**."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:38
msgid ""
"Once the PayPal account is created, go back to the **Accounting** dashboard "
"and click on the **Synchronize** button. In the dialog, choose **PayPal** as"
" the online institution and click on the configure button."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:45
msgid "Then, you will have to provide your credentials to connect to PayPal."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:48
msgid ""
"Your Paypal **must be in English** (if it is not the case you must change "
"the langage of your Paypal account) and if you use a Paypal business account"
" you must switch back to the old interface in order for it to work with "
"Online feeds (you can switch from new to old interface in your Paypal "
"account)."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:53
msgid ""
"If you don't do this you will get a message either saying to put Paypal in "
"English or that the site is not supported."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:56
msgid ""
"If you configured your Paypal account correctly you should get to the next "
"step of the Online feeds configuration. There you will have a screen with a "
"date to fetch transaction from and a list of account to choose. You must "
"choose the **Paypal balance** account."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:61
msgid ""
"Once everything is done, you should see your PayPal transactions right in "
"Odoo and you can start reconciling your payments."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:64
msgid ""
"Enjoy a full integration! You don't need to record transaction manually "
"anymore."
msgstr ""

#: ../../accounting/bank/feeds/paypal.rst:68
msgid ""
"You only have to provide your credentials the first time. Once done, Odoo "
"will synchronize with PayPal every 4 hours automatically."
msgstr ""

#: ../../accounting/bank/misc.rst:3 ../../accounting/payables/misc.rst:3
#: ../../accounting/payables/misc/employee_expense.rst:184
msgid "Miscellaneous"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:3
msgid "How to manage batch deposits of checks?"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:5
msgid ""
"When your company's collections group receives checks from customers they "
"will often place this money into their bank account in batches. As this "
"money has been received in a physical form, someone in your company must "
"manually bring the checks to the bank."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:10
msgid ""
"The bank will ask for a deposit ticket (also referred to as deposit slip) to"
" be filled-in with the details of the checks or cash to be included in the "
"transactions."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:14
msgid ""
"The bank statement will reflect the total amount that was deposited and the "
"reference to the deposit ticket, not the individual checks."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:17
msgid ""
"Odoo assists you to prepare and print your deposit tickets, and later on "
"reconcile them with your bank statement easily."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:24
msgid "Install the batch deposit feature"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:26
msgid ""
"In order to use the batch deposit feature, you need the module **Batch "
"Deposit** to be installed."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:31
msgid ""
"Usually, this module is automatically installed if checks are widely used in"
" your country."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:34
msgid ""
"To verify that the **Batch Deposit** feature is installed, go to the "
":menuselection:`Configuration --> Settings` menu of the accounting "
"application. Check the feature: **Allow batch deposit**."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:42
msgid "Activate the feature on your bank accounts"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:44
msgid ""
"Once you have installed this feature, Odoo automatically activate bank "
"deposits on your main bank accounts."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:47
msgid ""
"To control which bank account can do batch deposit and which can not, go to "
"the journal that you defined to pay your checks, usually called 'Checks' or "
"'Bank' (see :doc:`../../receivables/customer_payments/check`, in the "
"Accounting apps, :menuselection:`Configuration --> Accounting --> Journals`."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:52
msgid ""
"In **Advanced Settings** tab, in section **Miscellaneous**, set Debit Method"
" to **Batch Deposit**."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:58
msgid ""
"If you check **Batch Deposit** in your debit method field, it means that "
"payments created using this Journal (called Payment method when you want to "
"make or receive a payment) will be applicable for the creation of Batch "
"Deposits afterwards."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:64
msgid "From checks received to the bank"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:67
msgid "Receive customer checks"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:69
msgid ""
"Once your checks are received, record them on the bank account on which you "
"plan to deposit them. Once you select the bank account (or check journal if "
"you configured Odoo that way), Odoo proposes you to use a batch deposit. "
"Select this option if you plan to deposit the check to your bank."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:78
msgid "In the memo field, you can set the reference of the check."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:82
msgid ""
"payments can be registered from the menu :menuselection:`Sales --> "
"Payments`, or directly on the related invoice, using the **Register "
"Payment** button."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:86
msgid "Prepare a batch deposit"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:88
msgid ""
"From the Accounting application, go to the menu :menuselection:`Sales --> "
"Batch Deposit`, and create a new **Batch Deposit**."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:94
msgid ""
"Select the bank, then select the payments (checks) you want to add in this "
"deposit. By default, Odoo proposes you all the checks that have not been "
"deposited yet. That way you can verify that you do not forget or lost a "
"check."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:102
msgid ""
"You can then print the batch deposit, which will be very useful to prepare "
"the deposit slip that the bank usually requires to complete."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:106
msgid "Reconciling the Deposit with the Bank Statement"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:108
msgid ""
"When you process the bank statement reconciliation you will see the deposit "
"ticket number referenced in the statement. When the reconciliation process "
"is run, the user will be able to select the batch deposit that matches with "
"the bank statement line."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:116
msgid ""
"If you select a batch deposit, Odoo will automatically fill all the checks "
"contained in this deposit for the matching. (2 checks were in the batch "
"deposit in the example below)"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:124
#: ../../accounting/payables/pay/sepa.rst:111
msgid "Troubleshooting"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:127
msgid "I don't see the batch deposit link on bank statements?"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:129
msgid ""
"If you don't have a batch deposit link in your bank statement, there could "
"be two reasons:"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:132
msgid ""
"After having installed the batch deposit features you need to reload the "
"page so that the browser is aware of this new feature. Just click the reload"
" button of your browser."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:136
msgid "You do not have a batch deposit created for this bank account."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:139
msgid "What happens if a check was refused?"
msgstr ""

#: ../../accounting/bank/misc/batch.rst:141
msgid ""
"If you have a smaller amount in your bank statement than the actual amount "
"in your batch deposit, it probably means that one of your check has been "
"refused."
msgstr ""

#: ../../accounting/bank/misc/batch.rst:145
msgid ""
"In this case click on the line related to this check to remove it from the "
"bank statement matching."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:3
msgid "How to do a bank wire transfer from one bank to another?"
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:5
msgid ""
"A company might have several bank accounts or cash registers. Within odoo it"
" is possible to handle internal transfers of money with only a couple of "
"clicks."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:9
msgid ""
"We will take the following example to illustrate. My company has two bank "
"accounts and I want to transfer 50.000 euros from one of our bank accounts "
"to the another one."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:17
msgid "Check your Chart of Accounts and default transfer account"
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:19
msgid ""
"To handle internal transfers you need a transfer account in your charts of "
"account. Odoo will generate an account automatically based on the country of"
" your chart of account. To configure your chart of accounts and check the "
"default transfer account go into the accounting module settings, select "
":menuselection:`Configuration --> Settings`."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:25
msgid ""
"Your chart of accounts will be pre-installed depending on the country "
"specified during your registration, it cannot be changed."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:31
msgid ""
"The default transfer account will automatically be generated as well "
"depending on your country's legislation. If necessary it can be modified "
"from the same page."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:39
msgid "Create a second bank account / Journal"
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:41
msgid ""
"Before we can register an internal transfer we need to add a new bank to our"
" accounting dashboard. To do so enter the accounting module, click on "
":menuselection:`Configuration --> Bank Accounts`. Create a new bank account."
" You should fill in the **Account Number**. You can also create and edit "
"your bank to specify your bank's details."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:50
msgid "By saving the changes you now have 2 bank accounts."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:56
msgid "Register an internal transfer from one bank to another."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:58
msgid ""
"We will now transfer 50.000 euros from our **Bank** to our **Bank BE57 0633 "
"9533 1498** account."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:62
msgid "Log an internal transfer"
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:64
msgid ""
"The first step is to register the internal payment. To do so go into your "
"accounting dashboard, click on the **more** button of one of your banks and "
"select :menuselection:`New --> Internal transfer`."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:71
msgid ""
"Create a new payment. The payment type will automatically be set to internal"
" transfer. Select the **Bank** you want to transfer to, specify the "
"**Amount** and add a **Memo** if you wish."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:76
msgid ""
"The memo is important if you wish to automatically reconcile (see `Import "
"bank statements and reconcile`_)."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:82
msgid "Save and confirm the changes to register the payment."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:84
msgid ""
"In terms of accounting the money is now booked in the transfer account. "
"We'll need to import bank statements to book the money in the final "
"accounts."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:89
msgid "Import bank statements and reconcile"
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:91
msgid ""
"Note that the bank balance computed by Odoo is different that the last "
"statement of your bank."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:97
msgid ""
"That is because we did not import the bank statement confirming the "
"receiving and sending of the money. It's thus necessary to import your bank "
"statement and reconcile the payment with the correct bank statement line. "
"Once you receive your bank statements click the **new statement** button of "
"the corresponding bank to import them."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:106
msgid ""
"Fill in your **Transactions line**. Once done, Odoo will display a "
"**Computed Balance**. that computed balance is the theorical end balance of "
"your bank account. If it's corresponding to the bank statement, it means "
"that no errors were made. Fill in the **Ending balance** and click on the "
"**Reconcile** button."
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:114
msgid "The following window will open:"
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:119
msgid ""
"You need to choose counterparts for the payment. Select the correct bank "
"statement line corresponding to the payment and click on the **reconcile** "
"button. Close the statement to finish the transaction"
msgstr ""

#: ../../accounting/bank/misc/interbank.rst:126
msgid ""
"The same steps will need to be repeated once you receive your second bank "
"statement. Note that if you specify the same amount and the same memo in "
"both bank statements and payment transactions then the reconciliation will "
"happen automatically."
msgstr ""

#: ../../accounting/bank/reconciliation.rst:3
#: ../../accounting/others/reporting/main_reports.rst:153
#: ../../accounting/overview/main_concepts/memento.rst:177
msgid "Bank Reconciliation"
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:3
msgid "Configure model of entries"
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:6
#: ../../accounting/bank/reconciliation/use_cases.rst:6
#: ../../accounting/others/adviser/budget.rst:6
#: ../../accounting/others/analytic/purchases_expenses.rst:6
#: ../../accounting/others/multicurrencies/exchange.rst:6
#: ../../accounting/others/multicurrencies/how_it_works.rst:6
#: ../../accounting/others/multicurrencies/invoices_payments.rst:6
#: ../../accounting/others/reporting/customize.rst:6
#: ../../accounting/overview.rst:3
msgid "Overview"
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:8
msgid ""
"In Odoo you have the possibility to pre-fill some accounting entries in "
"order to easily reconcile recurrent entries such as bank fees."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:11
msgid ""
"We will take the following example to illustrate the concept : Every month "
"my company receives a bank fee cost, which depends of our bank account "
"current balance. This fee is thus variable."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:16
msgid "Create Reconciliation Models"
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:18
msgid ""
"First, we need to configure two model reconciliation entries. To do so, go "
"to the accounting application dashboard. On your bank journal, click on "
":menuselection:`More --> Reconciliation Models`."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:25
msgid ""
"We want to be able to book our bank fees easily. Our bank deducts fees "
"depending on our balance, meaning that it can vary every month."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:28
msgid ""
"We create a button Label called Bank fees, select the correct account to "
"book those fees. Moreover we also need to specify that the amount type is "
"\"Percentage of balance\" with an Amount of 100%. This parameter will tell "
"Odoo to take the entire fee into account."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:36
msgid "Save your changes when you are done."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:39
msgid ""
"If the amount of your bank fee is fixed, you can as well select **Fixed** "
"under amount type and specify the amount in the amount tap."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:43
msgid ""
"You can also use this functionality to handle discounts. Please refer to "
":doc:`../../receivables/customer_invoices/cash_discounts`"
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:47
msgid "Register your payments based on a reconciliation model"
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:49
msgid ""
"Register your payment by importing your bank statements that will be "
"impacted by the payment of the bank fee."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:52
msgid ""
"When doing the reconciliation, you can select an open balance and click the "
"**Reconciliation Model** button (in this case, **Bank Fees**) to get all the"
" relevant data instantly."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:59
msgid "Finally, click on **Reconcile** to finish the process."
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:62
#: ../../accounting/bank/reconciliation/use_cases.rst:108
msgid ":doc:`../feeds/bank_synchronization`"
msgstr ""

#: ../../accounting/bank/reconciliation/configure.rst:63
msgid ":doc:`use_cases`"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:3
msgid "Use cases in the bank reconciliation process?"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:8
msgid ""
"Matching your bank statements with your accounting records can be a tedious "
"task. You need to find the corresponding invoices, compare the amounts and "
"partners' details with those in the bank statement. These steps can take a "
"lot of time. Luckily, with Odoo you can very easily match your invoices or "
"any other payment document with your bank statements."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:10
msgid "Two options of the reconciliation process exist in Odoo."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:12
msgid "We can directly specify the payment on the invoice"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:13
msgid "We can reconcile open invoices with bank statements"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:18
msgid ""
"No special configuration is necessary to record invoices. All we need to do "
"is to install the accounting app."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:25
msgid "Use cases"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:28
msgid "Case 1: Payments registration"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:30
msgid ""
"We received the proof of payment of our invoice in the amount of 2100 euros "
"issued to Smith & Co."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:33
msgid ""
"We start at our issued Invoice of 2100 euros for Smith & Co. Because the "
"sold product is a service we demand an immediate payment. Our accountant "
"only handles bank statements at the end of week, so we have to mark this "
"invoice as paid immediately in order to indicate that we can start rendering"
" services to our customer."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:39
msgid ""
"Our customer send us a payment confirmation. We can thus register a payment "
"and mark the invoice as paid."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:45
msgid ""
"By clicking on **register payment,** we are telling Odoo that our customer "
"has paid the Invoice. We thus have to specify the amount and the payment "
"method."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:52
msgid ""
"Now we can always find the payment details in the Invoice by clicking on the"
" :menuselection:`Info --> Open Payment`."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:58
msgid ""
"The invoice has been paid and **the reconciliation has been done "
"automatically.**"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:62
msgid "Case 2: Bank statements reconciliations"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:64
msgid ""
"We start at our issued Invoice of 3000 euros for Smith & Co. Let's also "
"assume that other Invoices are open for different customers."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:70
msgid ""
"We receive our bank statement and find that not only the invoice issued to "
"Smith & Co has been paid, but the one to Buzz of 92 euros as well."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:73
msgid ""
"**Import** or **Create** the bank statements. Please refer to the documents "
"from the Bank Feeds section."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:79
msgid "On the dashboard, click on **Reconcile # Items**"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:84
msgid ""
"If everything was right (correct partner name, right amount) odoo will do "
"the reconciliations **automatically**."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:90
msgid "If some issues are found, you will need to take **manual actions**."
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:92
msgid ""
"For example, if the partner is missing from your bank statement, just fill "
"it in :"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:98
msgid ""
"If the payment is done with a down payment, just check if it is all right "
"and validate all related payments :"
msgstr ""

#: ../../accounting/bank/reconciliation/use_cases.rst:105
msgid "Hit CTRL-Enter to reconcile all the balanced items in the sheet."
msgstr ""

#: ../../accounting/bank/setup.rst:3
msgid "Setup"
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:3
msgid "How to setup a new bank account?"
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:5
msgid ""
"In Odoo, you can manage multiple bank accounts. In this page, you will be "
"guided in the creation, modification or deletion of a bank or a credit card "
"account."
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:10
msgid "Edit a bank account"
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:12
msgid ""
"To ease the process, a bank account is already there. We suggest you to edit"
" it first before filling your own bank information."
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:15
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Bank Accounts` and "
"click on the **Bank** item. Edit it."
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:23
msgid ""
"Odoo will detect the bank account type (e.g. IBAN) to allow some payment "
"method like SEPA"
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:28
msgid "Create a bank account"
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:30
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Bank Accounts`. Click"
" on **create** and fill in the form. You can decide to show the bank account"
" number in you intend to send documents like sales orders or invoices. "
"Select the payments methods you support with this bank account."
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:41
msgid ""
"If you are working in a multi-company environnement, you'll have to switch "
"the company on your user preferences in order to add, edit or delete bank "
"accounts from another company."
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:54
msgid ""
"The initial balance of a bank statement will be set to the closing balance "
"of the previous one within the same journal automatically."
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:57
msgid "Delete a bank account or credit card account"
msgstr ""

#: ../../accounting/bank/setup/create_bank_account.rst:59
msgid ""
"From the list of bank accounts, select items to delete and delete them from "
"the action menu or go to the form and delete a single item from the action "
"menu"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:3
msgid "How to manage a bank in a foreign currency?"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:5
msgid ""
"In Odoo, every transaction is recorded in the default currency of the "
"company. Reports are all based on the currency of the company. But for "
"transactions occurring in another currency, Odoo stores both the value in "
"the currency of the company and the value in the currency of the "
"transaction."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:11
msgid ""
"When you have a bank account in a foreign currencies, for every transaction,"
" Odoo stores two values:"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:14
msgid "The debit/credit in the currency of the company"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:16
msgid "The debit/credit in the currency of the bank account"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:18
msgid ""
"Currency rates are updated automatically using yahoo.com, or the European "
"Central bank web-services."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:25
msgid "Activate the multi-currency feature"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:27
msgid ""
"In order to allow your company to work with multiple currencies, you should "
"activate the multi-currency mode. In the accounting application, go into "
":menuselection:`Configuration --> Settings --> Accounting & Finance "
"Features` make sure the **Allow Multi-currencies** box is ticked. Provide a "
"**Currency Exchange Gain / Loss** account, then click on **Apply**."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:34
msgid "Configure currencies"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:36
msgid ""
"Once the Odoo is configured to support multiple currencies, you should "
"activate the currencies you plan to work with. To do that, go to the menu "
":menuselection:`Configuration --> Currencies`. All the currencies are "
"created by default, but you should activate the ones you plan to support (to"
" activate a currency, check its \"Active\" field)."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:42
msgid ""
"After having activated the currencies, you can configure the parameters to "
"automate the currency rate update. These options are also in the settings of"
" the Accounting application, in the bottom of the page:"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:49
msgid "Click on the **Update Now** link to update the currency rates now."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:52
msgid "Create a new bank account"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:54
msgid ""
"In the accounting application, we first go to :menuselection:`Configuration "
"--> Accounting / Bank account`, and we create a new one."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:60
msgid ""
"Once you save this bank account, Odoo will create all the documents for you:"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:63
msgid "An account in the trial balance"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:65
msgid "A journal in your dashboard"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:67
msgid ""
"Information about the bank account in the footer of your invoices if checked"
" the box **Show in Invoices Footer**"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:71
msgid "Example: A vendor bill in a foreign currency"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:73
msgid ""
"Based on the above example, let's assume we receive the following bill from "
"a supplier in China."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:76
msgid ""
"In the :menuselection:`Purchase --> Vendor Bills` , this is what you could "
"see:"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:81
msgid ""
"Once you are ready to pay this bill, click on register payment on the bill "
"to record a payment."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:87
msgid ""
"That's all you have to do. Odoo will automatically post the foreign exchange"
" gain or loss at the reconciliation of the payment with the invoice, "
"depending if the currency rate increased or decreased between the invoice "
"and the payment date."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:92
msgid ""
"Note that you can pay a foreign bill with another currency. In such a case, "
"Odoo will automatically convert between the two currencies."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:96
msgid "Customers Statements"
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:98
msgid ""
"Customers and vendor statements are managed in the currency of the invoice. "
"So, the amount due by your customer (to your vendor) is always expressed in "
"the currency of the invoice."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:102
msgid ""
"If you have several invoices with different currencies for the same "
"customer, Odoo will split the customer statement by currency, as shown in "
"the report below."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:109
msgid ""
"In the above report, the account receivable associated to Camptocamp is not "
"managed in a secondary currency, which means that it keeps every transaction"
" in its own currency. If you prefer, you can set the account receivable for "
"this customer in a secondary currency and all its debts will automatically "
"be converted to this currency."
msgstr ""

#: ../../accounting/bank/setup/foreign_currency.rst:115
msgid ""
"In such a case, the customer statement always has only one currency. In "
"general, this is not what the customer expect as he prefers to see the "
"amounts in the currency of the invoices he received;"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:3
msgid "How to manage a cash register?"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:5
msgid ""
"The cash register is a journal to register receivings and payments "
"transactions. It calculates the total money in and out, computing the total "
"balance."
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:14
msgid ""
"Configure the Cash journal in :menuselection:`Accounting --> Configuration "
"--> Journals`."
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:17
msgid ""
"In the tab Journal Entries, the Default Debit and Credit Account can be "
"configured as well as the currency of the journal"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:21
msgid "Usage"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:24
msgid "How to register cash payments?"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:26
msgid ""
"To register a cash payment specific to another customer, you should follow "
"these steps:"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:29
msgid ""
"Go to :menuselection:`Accounting --> Dashboard --> Cash --> Register "
"Transactions`"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:32
msgid "Fill in the start and ending balance"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:34
msgid ""
"Register the transactions, specifying the customers linked to the "
"transaction"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:37
msgid "Put money in"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:39
msgid ""
"Put money in is used to placed your cash manually before starting your "
"transactions. From the Register Transactions window, go to "
":menuselection:`More --> Put money in`"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:47
msgid "Take money out"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:49
msgid ""
"Take money out is used to collect/get yor your cash manually after ending "
"all your transactions. From the Register Transaction windows, go to "
":menuselection:`More --> Take money out`"
msgstr ""

#: ../../accounting/bank/setup/manage_cash_register.rst:56
msgid ""
"The transactions will be added to the current cash payment registration."
msgstr ""

#: ../../accounting/fiscality.rst:3
msgid "Fiscality"
msgstr ""

#: ../../accounting/fiscality/fiscal_year.rst:3
msgid "Fiscal Year"
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:3
msgid "How to do a year end in Odoo? (close a fiscal year)"
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:5
msgid ""
"Before going ahead with closing a fiscal year, there are a few steps one "
"should typically take to ensure that your accounting is correct, up to date,"
" and accurate:"
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:9
msgid ""
"Make sure you have fully reconciled your **bank account(s)** up to year end "
"and confirm that your ending book balances agree with your bank statement "
"balances."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:13
msgid "Verify that all **customer invoices** have been entered and approved."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:15
msgid "Confirm that you have entered and agreed all **vendor bills**."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:17
msgid "Validate all **expenses**, ensuring their accuracy."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:19
msgid ""
"Corroborate that all **received payments** have been entered and recorded "
"accurately."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:23
msgid "Year-end checklist"
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:25
msgid "Run a **Tax report**, and verify that your tax information is correct."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:27
msgid "Reconcile all accounts on your **Balance Sheet**:"
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:29
msgid ""
"Agree your bank balances in Odoo against your actual bank balances on your "
"statements. Utilize the **Bank Reconciliation** report to assist with this."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:33
msgid ""
"Reconcile all transactions in your cash and bank accounts by running your "
"**Aged Receivables** and **Aged Payables** reports."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:36
msgid ""
"Audit your accounts, being sure to fully understand the transactions "
"affecting them and the nature of the transactions, making sure to include "
"loans and fixed assets."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:40
msgid ""
"Run the optional **Payments Matching** feature, under the **More** dropdown "
"on the dashboard, validating any open **Vendor Bills** and **Customer "
"Invoices** with their payments. This step is optional, however it may assist"
" the year-end process if all outstanding payments and invoices are "
"reconciled, and could lead finding errors or mistakes in the system."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:47
msgid ""
"Your accountant/bookkeeper will likely verify your balance sheet items and "
"book entries for:"
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:50
msgid ""
"Year-end manual adjustments, using the **Adviser Journal Entries** menu (For"
" example, the **Current Year Earnings** and **Retained Earnings** reports)."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:54
msgid "**Work in Progress**."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:56
msgid "**Depreciation Journal Entries**."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:58
msgid "**Loans**."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:60
msgid "**Tax adjustments**."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:62
msgid ""
"If your accountant/bookkeeper is going through end of the year auditing, "
"they may want to have paper copies of all balance sheet items (such as "
"loans, bank accounts, prepayments, sales tax statements, etc...) to agree "
"these against your Odoo balances."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:67
msgid ""
"During this process, it is good practice to set the **Lock date for Non-"
"Advisers** to the last day of the preceding financial year, which is set "
"under the accounting configuration. This way, the accountant can be "
"confident that nobody is changing the previous year transactions while "
"auditing the books."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:77
msgid "Closing the fiscal year"
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:79
msgid ""
"In Odoo there is no need to do a specific year end closing entry in order to"
" close out income statement accounts. The reports are created in real-time, "
"meaning that the **Income statement** corresponds directly with the year-end"
" date you specify in Odoo. Therefore, any time you generate the **Income "
"Statement**, the beginning date will correspond with the beginning of the "
"**Fiscal Year** and the account balances will all be 0."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:86
msgid ""
"Once the accountant/bookkeeper has created the journal entry to allocate the"
" **Current Year Earnings**, you should set the **Lock Date** to the last day"
" of the fiscal year. Making sure that before doing so, you confirm whether "
"or not the current year earnings in the **Balance Sheet** is correctly "
"reporting a 0 balance."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/close_fiscal_year.rst:93
msgid ":doc:`fiscal_year`"
msgstr ""

#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:3
msgid "Manage Fiscal Years"
msgstr ""

#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:5
msgid ""
"In most cases, the fiscal years last 12 months. If it is your case, you just"
" have to define what is the last day of your fiscal year in the accounting "
"settings. By default, it is set on the 31st December."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:12
msgid ""
"However, there might be some exceptions. For example, if it is the first "
"fiscal year of your business, it could last more or less than 12 months. In "
"this case, some additional configuration is required."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:16
msgid ""
"Go in :menuselection:`accounting --> configuration --> settings` and "
"activate the fiscal years."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:22
msgid ""
"You can then configure your fiscal years in :menuselection:`accounting --> "
"configuration --> fiscal years`."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:29
msgid ""
"You only have to create fiscal years if they last more or less than 12 "
"months."
msgstr ""

#: ../../accounting/fiscality/fiscal_year/fiscal_year.rst:34
msgid ":doc:`close_fiscal_year`"
msgstr ""

#: ../../accounting/fiscality/taxes.rst:3
#: ../../accounting/localizations/argentina.rst:135
#: ../../accounting/localizations/colombia.rst:115
#: ../../accounting/overview/process_overview/customer_invoice.rst:111
msgid "Taxes"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:3
msgid "How to manage prices for B2B (tax excluded) and B2C (tax included)?"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:5
msgid ""
"When working with consumers, prices are usually expressed with taxes "
"included in the price (e.g., in most eCommerce). But, when you work in a B2B"
" environment, companies usually negotiate prices with taxes excluded."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:9
msgid ""
"Odoo manages both use cases easily, as long as you register your prices on "
"the product with taxes excluded or included, but not both together. If you "
"manage all your prices with tax included (or excluded) only, you can still "
"easily do sales order with a price having taxes excluded (or included): "
"that's easy."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:15
msgid ""
"This documentation is only for the specific use case where you need to have "
"two references for the price (tax included or excluded), for the same "
"product. The reason of the complexity is that there is not a symmetrical "
"relationship with prices included and prices excluded, as shown in this use "
"case, in belgium with a tax of 21%:"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:21
msgid "Your eCommerce has a product at **10€ (taxes included)**"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:23
msgid "This would do **8.26€ (taxes excluded)** and a **tax of 1.74€**"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:25
msgid ""
"But for the same use case, if you register the price without taxes on the "
"product form (8.26€), you get a price with tax included at 9.99€, because:"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:29
msgid "**8.26€ \\* 1.21 = 9.99€**"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:31
msgid ""
"So, depending on how you register your prices on the product form, you will "
"have different results for the price including taxes and the price excluding"
" taxes:"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:35
msgid "Taxes Excluded: **8.26€ & 10.00€**"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:37
msgid "Taxes Included: **8.26€ & 9.99€**"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:40
msgid ""
"If you buy 100 pieces at 10€ taxes included, it gets even more tricky. You "
"will get: **1000€ (taxes included) = 826.45€ (price) + 173.55€ (taxes)** "
"Which is very different from a price per piece at 8.26€ tax excluded."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:45
msgid ""
"This documentation explains how to handle the very specific use case where "
"you need to handle the two prices (tax excluded and included) on the product"
" form within the same company."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:50
msgid ""
"In terms of finance, you have no more revenues selling your product at 10€ "
"instead of 9.99€ (for a 21% tax), because your revenue will be exactly the "
"same at 9.99€, only the tax is 0.01€ higher. So, if you run an eCommerce in "
"Belgium, make your customer a favor and set your price at 9.99€ instead of "
"10€. Please note that this does not apply to 20€ or 30€, or other tax rates,"
" or a quantity >1. You will also make you a favor since you can manage "
"everything tax excluded, which is less error prone and easier for your "
"salespeople."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:63
#: ../../accounting/localizations/argentina.rst:6
#: ../../accounting/localizations/colombia.rst:6
#: ../../accounting/localizations/mexico.rst:15
msgid "Introduction"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:65
msgid ""
"The best way to avoid this complexity is to choose only one way of managing "
"your prices and stick to it: price without taxes or price with taxes "
"included. Define which one is the default stored on the product form (on the"
" default tax related to the product), and let Odoo compute the other one "
"automatically, based on the pricelist and fiscal position. Negotiate your "
"contracts with customers accordingly. This perfectly works out-of-the-box "
"and you have no specific configuration to do."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:73
msgid ""
"If you can not do that and if you really negotiate some prices with tax "
"excluded and, for other customers, others prices with tax included, you "
"must:"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:77
msgid ""
"always store the default price TAX EXCLUDED on the product form, and apply a"
" tax (price included on the product form)"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:80
msgid "create a pricelist with prices in TAX INCLUDED, for specific customers"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:83
msgid ""
"create a fiscal position that switches the tax excluded to a tax included"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:86
msgid ""
"assign both the pricelist and the fiscal position to customers who want to "
"benefit to this pricelist and fiscal position"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:89
msgid "For the purpose of this documentation, we will use the above use case:"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:91
msgid "your product default sale price is 8.26€ tax excluded"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:93
msgid ""
"but we want to sell it at 10€, tax included, in our shops or eCommerce "
"website"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:97
msgid "Setting your products"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:99
msgid ""
"Your company must be configured with tax excluded by default. This is "
"usually the default configuration, but you can check your **Default Sale "
"Tax** from the menu :menuselection:`Configuration --> Settings` of the "
"Accounting application."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:107
msgid ""
"Once done, you can create a **B2C** pricelist. You can activate the "
"pricelist feature per customer from the menu: :menuselection:`Configuration "
"--> Settings` of the Sale application. Choose the option **different prices "
"per customer segment**."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:112
msgid ""
"Once done, create a B2C pricelist from the menu "
":menuselection:`Configuration --> Pricelists`. It's also good to rename the "
"default pricelist into B2B to avoid confusion."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:116
msgid ""
"Then, create a product at 8.26€, with a tax of 21% (defined as tax not "
"included in price) and set a price on this product for B2C customers at 10€,"
" from the :menuselection:`Sales --> Products` menu of the Sales application:"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:125
msgid "Setting the B2C fiscal position"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:127
msgid ""
"From the accounting application, create a B2C fiscal position from this "
"menu: :menuselection:`Configuration --> Fiscal Positions`. This fiscal "
"position should map the VAT 21% (tax excluded of price) with a VAT 21% (tax "
"included in price)"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:136
msgid "Test by creating a quotation"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:138
msgid ""
"Create a quotation from the Sale application, using the "
":menuselection:`Sales --> Quotations` menu. You should have the following "
"result: 8.26€ + 1.73€ = 9.99€."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:145
msgid ""
"Then, create a quotation but **change the pricelist to B2C and the fiscal "
"position to B2C** on the quotation, before adding your product. You should "
"have the expected result, which is a total price of 10€ for the customer: "
"8.26€ + 1.74€ = 10.00€."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:153
msgid "This is the expected behavior for a customer of your shop."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:156
msgid "Avoid changing every sale order"
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:158
msgid ""
"If you negotiate a contract with a customer, whether you negotiate tax "
"included or tax excluded, you can set the pricelist and the fiscal position "
"on the customer form so that it will be applied automatically at every sale "
"of this customer."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:163
msgid ""
"The pricelist is in the **Sales & Purchases** tab of the customer form, and "
"the fiscal position is in the accounting tab."
msgstr ""

#: ../../accounting/fiscality/taxes/B2B_B2C.rst:166
msgid ""
"Note that this is error prone: if you set a fiscal position with tax "
"included in prices but use a pricelist that is not included, you might have "
"wrong prices calculated for you. That's why we usually recommend companies "
"to only work with one price reference."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:3
msgid "How to adapt taxes to my customer status or localization"
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:5
msgid ""
"Most often sales tax rates depend on your customer status or localization. "
"To map taxes, Odoo brings the so-called *Fiscal Positions*."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:9
msgid "Create tax mapping"
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:11
msgid ""
"A fiscal position is just a set of rules that maps default taxes (as defined"
" on product form) into other taxes. In the screenshot below, foreign "
"customers get a 0% tax instead of the default 15%, for both sales and "
"purchases."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:18
msgid ""
"The main fiscal positions are automatically created according to your "
"localization. But you may have to create fiscal positions for specific use "
"cases. To define fiscal positions, go to "
":menuselection:`Invoicing/Accounting --> Configuration --> Fiscal "
"Positions`."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:24
msgid ""
"If you use Odoo Accounting, you can also map the Income/Expense accounts "
"according to the fiscal position. For example, in some countries, revenues "
"from sales are not posted in the same account than revenues from sales in "
"foreign countries."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:29
msgid "Adapt taxes to your customer status"
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:31
msgid ""
"If a customer falls into a specific taxation rule, you need to apply a tax-"
"mapping. To do so, create a fiscal position and assign it to your customers."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:37
msgid ""
"Odoo will use this specific fiscal position for any order/invoice recorded "
"for the customer."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:40
msgid ""
"If you set the fiscal position in the sales order or invoice manually, it "
"will only apply to this document and not to future orders/invoices of the "
"same customer."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:44
msgid "Adapt taxes to your customer address (destination-based)"
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:46
msgid ""
"Depending on your localization, sales taxes may be origin-based or "
"destination-based. Most states or countries require you to collect taxes at "
"the rate of the destination (i.e. your buyer’s address) while some others "
"require to collect them at the rate effective at the point of origin (i.e. "
"your office or warehouse)."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:51
msgid ""
"If you are under the destination-based rule, create one fiscal position per "
"tax-mapping to apply."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:53
msgid "Check the box *Detect Automatically*."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:54
msgid ""
"Select a country group, country, state or city to trigger the tax-mapping."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:59
msgid ""
"This way if no fiscal position is set on the customer, Odoo will choose the "
"fiscal position matching the shipping address on creating an order."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:63
msgid ""
"For eCommerce orders, the tax of the visitor's cart will automatically "
"update and apply the new tax after the visitor has logged in or filled in "
"his shipping address."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:68
msgid "Specific use cases"
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:70
msgid ""
"If, for some fiscal positions, you want to remove a tax, instead of "
"replacing by another, just keep the *Tax to Apply* field empty."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:76
msgid ""
"If, for some fiscal positions, you want to replace a tax by two other taxes,"
" just create two lines having the same *Tax on Product*."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:80
msgid "The fiscal positions are not applied on assets and deferred revenues."
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:84
#: ../../accounting/fiscality/taxes/default_taxes.rst:27
#: ../../accounting/fiscality/taxes/retention.rst:70
msgid ":doc:`create`"
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:85
#: ../../accounting/fiscality/taxes/default_taxes.rst:29
msgid ":doc:`taxcloud`"
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:86
#: ../../accounting/fiscality/taxes/create.rst:70
#: ../../accounting/fiscality/taxes/default_taxes.rst:31
msgid ":doc:`tax_included`"
msgstr ""

#: ../../accounting/fiscality/taxes/application.rst:87
#: ../../accounting/fiscality/taxes/default_taxes.rst:30
msgid ":doc:`B2B_B2C`"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:3
msgid "How to manage cash basis taxes"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:5
msgid ""
"The cash basis taxes are due when the payment has been done and not at the "
"validation of the invoice (as it is the case with standard taxes). Reporting"
" your income and expenses to the administration based on the cash basis "
"method is legal in some countries and under some conditions."
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:10
msgid ""
"Example : You sell a product in the 1st quarter of your fiscal year and "
"receive the payment the 2nd quarter of your fiscal year. Based on the cash "
"basis method, the tax you have to pay to the administration is due for the "
"2nd quarter."
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:16
msgid "How to configure cash basis taxes ?"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:18
msgid ""
"You first have to activate the setting in :menuselection:`Accounting --> "
"Configuration --> Settings --> Allow Tax Cash Basis`. You will be asked to "
"define the Tax Cash Basis Journal."
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:27
msgid ""
"Once this is done, you can configure your taxes in "
":menuselection:`Accounting --> Configuration --> Taxes`. At first set the "
"proper transitional accounts to post taxes until you register the payment."
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:35
msgid ""
"In the *Advanced Options* tab you will turn *Tax Due* to *Based on Payment*."
" You will then have to define the *Tax Received* account in which to post "
"the tax amount when the payment is received and the *Base Tax Received "
"Account* to post the base tax amount for an accurate tax report."
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:45
msgid "What is the impact of cash basis taxes in my accounting ?"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:47
msgid ""
"Let’s take an example. You make a sale of $100 with a 15% cash basis tax. "
"When you validate the customer invoice, the following entry is created in "
"your accounting:"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:52
msgid "Customer Invoices Journal"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:54
#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:68
#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:80
#: ../../accounting/others/analytic/usage.rst:64
#: ../../accounting/others/analytic/usage.rst:157
#: ../../accounting/overview/process_overview/customer_invoice.rst:107
#: ../../accounting/overview/process_overview/customer_invoice.rst:128
msgid "**Debit**"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:54
#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:68
#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:80
#: ../../accounting/others/analytic/usage.rst:64
#: ../../accounting/others/analytic/usage.rst:157
#: ../../accounting/overview/process_overview/customer_invoice.rst:107
#: ../../accounting/overview/process_overview/customer_invoice.rst:128
msgid "**Credit**"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:56
#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:72
msgid "Receivables $115"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:58
#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:82
msgid "Temporary Tax Account $15"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:60
#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:86
#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:88
msgid "Income Account $100"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:63
msgid "A few days later, you receive the payment:"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:66
msgid "Bank Journal"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:70
msgid "Bank $115"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:75
msgid ""
"When you reconcile the invoice and the payment, this entry is generated:"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:78
msgid "Tax Cash Basis Journal"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:84
msgid "Tax Received Account $15"
msgstr ""

#: ../../accounting/fiscality/taxes/cash_basis_taxes.rst:92
msgid ""
"The last two journal items are neutral but they are needed to insure correct"
" tax reports in Odoo with accurate base tax amounts. We advise to use a "
"default revenue account. The balance of this account will then always be at "
"zero."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:3
msgid "How to create new taxes"
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:5
msgid ""
"Odoo's tax engine is very flexible and support many different type of taxes:"
" value added taxes (VAT), eco-taxes, federal/states/city taxes, retention, "
"withholding taxes, etc. For most countries, your system is pre-configured "
"with the right taxes."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:10
msgid ""
"This section details how you can define new taxes for specific use cases."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:12
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Taxes`. From this "
"menu, you get all the taxes you can use: sales taxes and purchase taxes."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:18
msgid "Choose a scope: Sales, Purchase or None (e.g. deprecated tax)."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:20
msgid "Select a computation method:"
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:22
msgid "**Fixed**: eco-taxes, etc."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:24
msgid "**Percentage of Price**: most common (e.g. 15% sales tax)"
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:26
msgid "**Percentage of Price Tax Included**: used in Brazil, etc."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:28
msgid "**Group of taxes**: allows to have a compound tax"
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:34
msgid ""
"If you use Odoo Accounting, set a tax account (i.e. where the tax journal "
"item will be posted). This field is optional, if you keep it empty, Odoo "
"posts the tax journal item in the income account."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:39
msgid ""
"If you want to avoid using a tax, you can not delete it because the tax is "
"probably used in several invoices. So, in order to avoid users to continue "
"using this tax, you should set the field *Tax Scope* to *None*."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:44
msgid ""
"If you need more advanced tax mechanism, you can install the module "
"**account_tax_python** and you will be able to define new taxes with Python "
"code."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:49
msgid "Advanced configuration"
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:51
msgid ""
"**Label on Invoices**: a short text on how you want this tax to be printed "
"on invoice line. For example, a tax named \"15% on Services\" can have the "
"following label on invoice \"15%\"."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:55
msgid ""
"**Tax Group**: defines where this tax is summed in the invoice footer. All "
"the tax belonging to the same tax group will be grouped on the invoice "
"footer. Examples of tax group: VAT, Retention."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:59
msgid ""
"**Include in Analytic Cost**: the tax is counted as a cost and, thus, "
"generate an analytic entry if your invoice uses analytic accounts."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:63
msgid ""
"**Tags**: are used for custom reports. Usually, you can keep this field "
"empty."
msgstr ""

#: ../../accounting/fiscality/taxes/create.rst:69
#: ../../accounting/fiscality/taxes/default_taxes.rst:28
#: ../../accounting/fiscality/taxes/taxcloud.rst:93
msgid ":doc:`application`"
msgstr ""

#: ../../accounting/fiscality/taxes/default_taxes.rst:3
msgid "How to set default taxes"
msgstr ""

#: ../../accounting/fiscality/taxes/default_taxes.rst:5
msgid ""
"Taxes applied in your country are installed automatically for most "
"localizations."
msgstr ""

#: ../../accounting/fiscality/taxes/default_taxes.rst:7
msgid ""
"Default taxes set in orders and invoices come from each product's Invoicing "
"tab. Such taxes are used when you sell to companies that are in the same "
"country/state than you."
msgstr ""

#: ../../accounting/fiscality/taxes/default_taxes.rst:13
msgid ""
"To change the default taxes set for any new product created go to "
":menuselection:`Invoicing/Accounting --> Configuration --> Settings`."
msgstr ""

#: ../../accounting/fiscality/taxes/default_taxes.rst:20
msgid ""
"If you work in a multi-companies environment, the sales and purchase taxes "
"may have a different value according to the company you work for. You can "
"login into two different companies and change this field for each company."
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:3
msgid "How to manage withholding taxes?"
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:5
msgid ""
"A withholding tax, also called a retention tax, is a government requirement "
"for the payer of a customer invoice to withhold or deduct tax from the "
"payment, and pay that tax to the government. In most jurisdictions, "
"withholding tax applies to employment income."
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:10
msgid ""
"With normal taxes, the tax is added to the subtotal to give you the total to"
" pay. As opposed to normal taxes, withholding taxes are deducted from the "
"amount to pay, as the tax will be paid by the customer."
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:14
msgid "As, an example, in Colombia you may have the following invoice:"
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:19
msgid ""
"In this example, the **company** who sent the invoice owes $20 of taxes to "
"the **government** and the **customer** owes $10 of taxes to the "
"**government**."
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:25
msgid ""
"In Odoo, a withholding tax is defined by creating a negative tax. For a "
"retention of 10%, you would configure the following tax (accessible through "
":menuselection:`Configuration --> Taxes`):"
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:32
msgid ""
"In order to make it appear as a retention on the invoice, you should set a "
"specific tax group **Retention** on your tax, in the **Advanced Options** "
"tab."
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:39
msgid ""
"Once the tax is defined, you can use it in your products, sales order or "
"invoices."
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:43
msgid ""
"If the retention is a percentage of a regular tax, create a Tax with a **Tax"
" Computation** as a **Tax Group** and set the two taxes in this group "
"(normal tax and retention)."
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:48
msgid "Applying retention taxes on invoices"
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:50
msgid ""
"Once your tax is created, you can use it on customer forms, sales order or "
"customer invoices. You can apply several taxes on a single customer invoice "
"line."
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:58
msgid ""
"When you see the customer invoice on the screen, you get only a **Taxes "
"line** summarizing all the taxes (normal taxes & retentions). But when you "
"print or send the invoice, Odoo does the correct grouping amongst all the "
"taxes."
msgstr ""

#: ../../accounting/fiscality/taxes/retention.rst:63
msgid "The printed invoice will show the different amounts in each tax group."
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:3
msgid "How to set tax-included prices"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:5
msgid ""
"In most countries, B2C prices are tax-included. To do that in Odoo, check "
"*Included in Price* for each of your sales taxes in "
":menuselection:`Accounting --> Configuration --> Accounting --> Taxes`."
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:12
msgid ""
"This way the price set on the product form includes the tax. As an example, "
"let's say you have a product with a sales tax of 10%. The sales price on the"
" product form is $100."
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:16
msgid "If the tax is not included in the price, you will get:"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:18
msgid "Price without tax: $100"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:20
msgid "Taxes: $10"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:22
msgid "Total to pay: $110"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:24
msgid "If the tax is included in the price"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:26
msgid "Price without tax: 90.91"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:28
msgid "Taxes: $9.09"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:30
msgid "Total to pay: $100"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:32
msgid ""
"You can rely on following documentation if you need both tax-included (B2C) "
"and tax-excluded prices (B2B): :doc:`B2B_B2C`."
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:36
msgid "Show tax-included prices in eCommerce catalog"
msgstr ""

#: ../../accounting/fiscality/taxes/tax_included.rst:38
msgid ""
"By default prices displayed in your eCommerce catalog are tax-excluded. To "
"display it in tax-included, check *Show line subtotals with taxes included "
"(B2C)* in :menuselection:`Sales --> Configuration --> Settings` (Tax "
"Display)."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:3
msgid "How to get correct tax rates in the United States using TaxCloud"
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:5
msgid ""
"The **TaxCloud** integration allows you to correctly calculate the sales tax"
" for every address in the United States and keeps track of which products "
"are exempt from sales tax and in which states each exemption applies. "
"TaxCloud calculates sales tax in real-time for every state, city, and "
"special jurisdiction in the United States."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:15
msgid "In TaxCloud"
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:16
msgid ""
"Create a free account on `TaxCloud <https://taxcloud.com/#register>`__ "
"website."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:18
msgid ""
"Register your Odoo website on TaxCloud to get an *API ID* and an *API Key*."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:23
msgid ""
"In Settings on TaxCloud, click *Locations* to enter the location of your "
"Office(s) & Warehouse(s)."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:24
msgid ""
"In Settings on TaxCloud, click *Manage Tax States* to verify the states "
"where you collect sales tax."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:27
msgid "In Odoo"
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:28
msgid ""
"Go to :menuselection:`Invoicing / Accounting --> Configuration --> Settings`"
" and check *TaxCloud - Compute tax rates based on U.S. ZIP codes* (note: "
"actually uses complete street address)."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:30
msgid "Enter your TaxCloud credentials."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:31
msgid "Click SAVE to store your credentials."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:36
msgid ""
"Click the Refresh Icon next to *Default Category* to import the TIC product "
"categories from TaxCloud (Taxability Information Codes). Some categories may"
" imply specific rates or attract product/service type exemptions."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:38
msgid ""
"Select your default *TIC Code*. This will apply to any new product created."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:40
msgid ""
"Set a specific TaxCloud TIC Category on the *General Information* tab of the"
" Product, or on the Product Category."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:42
msgid ""
"Make sure your company address is complete (including the state and the zip "
"code). Go to :menuselection:`Settings --> Users & Companies --> Companies` "
"to open and edit your Company record."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:47
msgid "How it works"
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:49
msgid ""
"Salestax is calculated in Odoo based on fiscal positions (see "
":doc:`application`). A Fiscal Position for the United States is created when"
" installing *TaxCloud*. Everything works out-of-the-box."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:54
msgid ""
"You can configure Odoo to automtically detect which Customers should use "
"this fiscal position.  Go to :menuselection:`Accounting --> Configuration "
"--> Fiscal Positions` to open and edit the record."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:61
msgid ""
"Now, this fiscal position is automatically set on any sales order, web "
"order, or invoice when the customer country is *United States*. This "
"triggers the automated tax computation."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:68
msgid ""
"Add your product(s). You have two options to get Sales Tax on the Order.  "
"You can confirm it, or you can save it and from the *Action* Menu choose "
"**Update Taxes with TaxCloud**."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:73
msgid "Coupons & Promotions"
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:75
msgid ""
"If you use the Coupon or Promotion Programs, the integration with Taxcloud "
"might seem a bit odd."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:77
msgid ""
"The problem lies with the fact that Taxcloud does not accept lines with "
"negative amounts as part of the tax computation. This means that the amount "
"of the lines added by the promotion program must be deduced from the total "
"of the lines it impacts. This means, amongst other complications, that "
"orders that use coupons or promotions with a Taxcloud fiscal position "
"**must** be invoiced completely - you cannot create invoices for partial "
"deliveries, etc."
msgstr ""

#: ../../accounting/fiscality/taxes/taxcloud.rst:83
msgid ""
"Another specific oddity is possible in the UI: imagine that you sell a "
"product from the Taxcloud category *[20110] Computers* and that you have a "
"promotion program in place that provides a 50% discount on this product. If "
"the tax rate for this particular product is 7%, the tax rate that will be "
"computed from the Taxcloud integration will display 3.5%. This happens "
"because the discount is included in the price that is sent to Taxcloud, but "
"in Odoo this discount is in another line entirely. At the end of the day, "
"your tax computation will be correct (since a 3.5% tax on the full price is "
"the equivalent of a 7% tax on half the price), but this might be surprising "
"from a user point of view."
msgstr ""

#: ../../accounting/localizations.rst:3
msgid "Localizations"
msgstr ""

#: ../../accounting/localizations/argentina.rst:3
msgid "Argentina"
msgstr ""

#: ../../accounting/localizations/argentina.rst:8
msgid ""
"The Argentinean localization has been improved and extended in Odoo v13, in "
"this version the next modules are available:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:11
msgid ""
"**l10n_ar**: This module add accounting features for the Argentinian "
"localization, which represent the minimal configuration needed for a company"
"  to operate in Argentina and under the AFIP (Administración Federal de "
"Ingresos Públicos) regulations and guidelines."
msgstr ""

#: ../../accounting/localizations/argentina.rst:15
msgid ""
"**l10n_ar_reports**: Add VAT Book report which is a legal requirement in "
"Argentine and that holds the VAT detail info of sales or purchases recorded "
"on the journal entries. This module includes as well the VAT summary report "
"that is used to analyze the invoice"
msgstr ""

#: ../../accounting/localizations/argentina.rst:19
msgid ""
"**l10n_ar_edi**: This module includes all technical and functional "
"requirements to generate Electronic Invoice via web service, based on the "
"AFIP regulations."
msgstr ""

#: ../../accounting/localizations/argentina.rst:27
msgid "Install the Argentinean localization modules"
msgstr ""

#: ../../accounting/localizations/argentina.rst:29
msgid ""
"For this, go to *Apps* and search for Argentina. Then click *Install* for "
"the first two modules."
msgstr ""

#: ../../accounting/localizations/argentina.rst:35
msgid "Configure your company"
msgstr ""

#: ../../accounting/localizations/argentina.rst:37
msgid ""
"Once that the modules are installed, the first step is to set up your "
"company data. Additional to the basic information, a key field to fill in "
"the AFIP Responsibility Type, that represent the fiscal obligation and "
"structure of the company:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:46
msgid "Chart of Account"
msgstr ""

#: ../../accounting/localizations/argentina.rst:48
msgid ""
"In Accounting settings there are three available packages of Chart of "
"accounts, which are related to the AFIP responsibility type of the Company, "
"considering that if the base companies don't require as many accounts as the"
" companies that gave more complex fiscal requirements:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:52
msgid "Monotributista  (149 accounts)."
msgstr ""

#: ../../accounting/localizations/argentina.rst:53
msgid "IVA Exempto   (159 accounts)."
msgstr ""

#: ../../accounting/localizations/argentina.rst:54
msgid "Responsables Inscriptos  (166 Accounts)."
msgstr ""

#: ../../accounting/localizations/argentina.rst:60
msgid "Configure Master data"
msgstr ""

#: ../../accounting/localizations/argentina.rst:63
msgid "Electronic Invoice Credentials"
msgstr ""

#: ../../accounting/localizations/argentina.rst:66
msgid "Environment"
msgstr ""

#: ../../accounting/localizations/argentina.rst:68
msgid ""
"The AFIP infrastructure is replicated in two separate environments, Testing "
"and Production."
msgstr ""

#: ../../accounting/localizations/argentina.rst:70
msgid ""
"Testing is provided so that the Companies can test their developments until "
"they are ready to move into the Production environment. As these two "
"environments are completely isolated from each other, the digital "
"certificates of one instance are not valid in the other one."
msgstr ""

#: ../../accounting/localizations/argentina.rst:74
msgid ""
"Go to :menuselection:`Accounting --> Settings --> Argentinian Localization` "
"to select the environment:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:81
msgid "AFIP Certificates"
msgstr ""

#: ../../accounting/localizations/argentina.rst:82
msgid ""
"The electronic invoice and other afip services work with WebServices (WS) "
"provided by the AFIP."
msgstr ""

#: ../../accounting/localizations/argentina.rst:84
msgid ""
"In order to enable communication with the AFIP, the first step is to request"
" a Digital Certificate if you don’t have one already."
msgstr ""

#: ../../accounting/localizations/argentina.rst:87
msgid ""
"Generate certificate Sign Request (Odoo). When this option is selected a "
"file with extension ``.csr`` (certificate signing request) is generated to "
"be used the AFIP portal to request the certificate."
msgstr ""

#: ../../accounting/localizations/argentina.rst:93
msgid ""
"Generate Certificate (AFIP). Access the AFIP portal and follow the "
"instructions described in the next document in order to get a certificate. "
"`Get AFIP Certificate "
"<http://www.afip.gob.ar/ws/WSAA/wsaa_obtener_certificado_produccion.pdf>`_."
msgstr ""

#: ../../accounting/localizations/argentina.rst:97
msgid ""
"Upload Certificate and Private Key (Odoo). Once the certificate has been "
"generated, it needs to be uploaded in Odoo, using the pencil next in the "
"field “Certificado” and selecting the corresponding file."
msgstr ""

#: ../../accounting/localizations/argentina.rst:104
msgid ""
"In case you need to configure the Homologation Certificate, please refer to "
"the AFIP official documentation: `Homologation Certificate "
"<http://www.afip.gob.ar/ws/documentacion/certificados.asp>`_."
msgstr ""

#: ../../accounting/localizations/argentina.rst:109
#: ../../accounting/localizations/colombia.rst:79
msgid "Partner"
msgstr ""

#: ../../accounting/localizations/argentina.rst:112
msgid "Identification Type and VAT"
msgstr ""

#: ../../accounting/localizations/argentina.rst:114
msgid ""
"As part of the Argentinean localization, the document types defined by the "
"AFIP are now available on the Partner form, this information is essential "
"for most transactions. There are six identification types available by "
"default:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:122
msgid ""
"The complete list of Identification types defined by the AFIP is included in"
" Odoo but only the common ones are active."
msgstr ""

#: ../../accounting/localizations/argentina.rst:126
msgid "AFIP Responsibility Type"
msgstr ""

#: ../../accounting/localizations/argentina.rst:128
msgid ""
"In Argentina the document type associated with customers and vendors "
"transactions is defined based on the AFIP Responsibility type, this field "
"should be defined in the partner form:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:137
msgid ""
"As part of the localization module,  the taxes are created automatically "
"with their related financial account and configuration."
msgstr ""

#: ../../accounting/localizations/argentina.rst:144
msgid "Taxes Types"
msgstr ""

#: ../../accounting/localizations/argentina.rst:146
msgid "Argentina has several tax types, the most common ones are:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:148
msgid "VAT. Is the regular VAT and it can have several percentages."
msgstr ""

#: ../../accounting/localizations/argentina.rst:149
msgid "Perception. Advance payment of a tax that is applied on Invoices."
msgstr ""

#: ../../accounting/localizations/argentina.rst:150
msgid "Retention. Advance payment of a tax that is applied on payments"
msgstr ""

#: ../../accounting/localizations/argentina.rst:151
msgid "Otros."
msgstr ""

#: ../../accounting/localizations/argentina.rst:154
msgid "Special Taxes"
msgstr ""

#: ../../accounting/localizations/argentina.rst:156
msgid ""
"Some argentine taxes are not commonly used  for all companies, these type of"
" taxes are included as inactive by default, it's important that before "
"creating a new tax you confirm if they are not already included in the "
"Inactive taxes:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:164
msgid "Document Types"
msgstr ""

#: ../../accounting/localizations/argentina.rst:166
msgid ""
"In some Latin America countries, including Argentina, some accounting "
"transactions like invoices and vendor bills are classified by  document "
"types defined by the government fiscal authorities (In Argentina case: "
"AFIP)."
msgstr ""

#: ../../accounting/localizations/argentina.rst:170
msgid ""
"The document type is an essential information that needs to be displayed in "
"the printed reports and that needs to be easily identified, within the set "
"of invoices as well of account moves."
msgstr ""

#: ../../accounting/localizations/argentina.rst:173
msgid ""
"Each document type can have a unique sequence per journal where it is "
"assigned. As part of the localization, the Document Type include the country"
" on which the document is applicable and the data is created automatically "
"when the localization module is installed."
msgstr ""

#: ../../accounting/localizations/argentina.rst:177
msgid ""
"The information required for the document types is included by default so "
"the user doesn't need to fill anything on this view:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:184
msgid ""
"There are several document types that are inactive by default but can be "
"activated if needed."
msgstr ""

#: ../../accounting/localizations/argentina.rst:187
msgid "Letters"
msgstr ""

#: ../../accounting/localizations/argentina.rst:189
msgid ""
"For Argentina, the document types include a letter that helps that indicates"
" the transaction/operation, example:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:192
msgid ""
"When an invoice is related to a B2B transaction, a document type \"A\" must "
"be used."
msgstr ""

#: ../../accounting/localizations/argentina.rst:193
msgid ""
"When an invoice is related to a B2C transaction, a document type \"B\" must "
"be used."
msgstr ""

#: ../../accounting/localizations/argentina.rst:194
msgid ""
"When an invoice is related to exportation transaction, a document type \"E\""
" must be used."
msgstr ""

#: ../../accounting/localizations/argentina.rst:196
msgid ""
"The documents included in the localization have the proper letter "
"associated, the user doesn't need to configure anything additional."
msgstr ""

#: ../../accounting/localizations/argentina.rst:203
msgid "Use on Invoices"
msgstr ""

#: ../../accounting/localizations/argentina.rst:205
msgid "The document type on each transaction will be determined by:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:207
msgid ""
"The Journal related to the Invoice, identifying if the journal use "
"documents."
msgstr ""

#: ../../accounting/localizations/argentina.rst:208
msgid ""
"Condition applied based on the type of Issues and Receiver (ex. Type of "
"fiscal regimen of the buyer and type of fiscal regimen of the vendor)"
msgstr ""

#: ../../accounting/localizations/argentina.rst:212
#: ../../accounting/localizations/colombia.rst:133
msgid "Journals"
msgstr ""

#: ../../accounting/localizations/argentina.rst:214
msgid ""
"In the Argentinean localization the Journal can have a different approach "
"depending on its usage and internal type, to configure you journals go to "
":menuselection:`Accounting --> Configuration --> Journals`:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:218
msgid ""
"For Sales and Purchase Journals it’s possible to enable the option *Use "
"Documents*, this indicates the Journal enables a list of document types that"
" can be related to the Invoices and vendor Bills, for more detail of the "
"invoices, please refer to the section 2.3 Document Types."
msgstr ""

#: ../../accounting/localizations/argentina.rst:222
msgid ""
"If the Sales/Purchase journal are used without the option *Use Documents* it"
" because they won’t be used to generate fiscal invoices, but mostly for "
"account moves related to internal control process."
msgstr ""

#: ../../accounting/localizations/argentina.rst:226
msgid "AFIP Information (also known as AFIP Point of Sale)"
msgstr ""

#: ../../accounting/localizations/argentina.rst:231
msgid ""
"**AFIP POS System**: This field is only visible for the Sales journals and "
"defined the type of AFIP POS that will be used to manage the transactions "
"for which the journal is created. The AFIP POS defines as well:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:235
msgid "The sequences of document types related to the Web service."
msgstr ""

#: ../../accounting/localizations/argentina.rst:236
msgid "The structure and data of the electronic invoice file."
msgstr ""

#: ../../accounting/localizations/argentina.rst:239
msgid "Web Services"
msgstr ""

#: ../../accounting/localizations/argentina.rst:240
msgid ""
"``wsfev1: Electronic Invoice.`` This is the most common service, is used to "
"generated invoices for document types A, B, C, M  with no detail per item."
msgstr ""

#: ../../accounting/localizations/argentina.rst:242
msgid ""
"``wsbfev1: Electronic Fiscal Bond.``  For those who invoice capital goods "
"and wish to access the benefit of the Electronic Tax Bonds granted by the "
"Ministry of Economy. For more detail you can refer to the next link: `Fiscal"
" Bond <https://www.argentina.gob.ar/acceder-un-bono-por-fabricar-bienes-de-"
"capital>`_."
msgstr ""

#: ../../accounting/localizations/argentina.rst:246
msgid ""
"``wsfexv1: Electronic Exportation Invoice.`` Used to generate invoices for "
"international customers and transactions that involve exportation process, "
"the document type related is type “E”."
msgstr ""

#: ../../accounting/localizations/argentina.rst:252
msgid ""
"**AFIP POS Number**: This is the number configured in the AFIP to identify "
"the operations related to this AFIP POS."
msgstr ""

#: ../../accounting/localizations/argentina.rst:255
msgid ""
"**AFIP POS Address**: This field is related to commercial address registered"
" for the POS, which is usually the same address than the Company. For "
"example: has multiple stores (fiscal locations) then AFIP will require that "
"you have one AFIP POS per location: this location will be printed in the "
"invoice report."
msgstr ""

#: ../../accounting/localizations/argentina.rst:260
msgid ""
"**Unified Book**: When AFIP POS System is Preimpresa the document types "
"(applicable to the journal) with the same letter will share the same "
"sequence.  For example:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:263
msgid "Invoice: FA-A 0001-00000002."
msgstr ""

#: ../../accounting/localizations/argentina.rst:264
msgid "Credit Note: NC-A 0001-00000003."
msgstr ""

#: ../../accounting/localizations/argentina.rst:265
msgid "Debit Note: ND-A 0001-00000004."
msgstr ""

#: ../../accounting/localizations/argentina.rst:268
msgid "Sequences"
msgstr ""

#: ../../accounting/localizations/argentina.rst:269
msgid ""
"In case that you want to synchronize the next number in the sequence in Odoo"
" based on the next number in the AFIP POS, the next button that is visible "
"under :doc:`developer mode <../../general/developer_mode/activate>` can be "
"used:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:277
msgid ""
"When creating the Purchase journals, it's possible to define if they can be "
"related to document types or not.  In case that the option to use documents "
"is selected, there is no need to manually associate the document type "
"sequences as the document number is provided by the vendor."
msgstr ""

#: ../../accounting/localizations/argentina.rst:283
#: ../../accounting/localizations/colombia.rst:163
#: ../../accounting/localizations/mexico.rst:204
msgid "Usage and testing"
msgstr ""

#: ../../accounting/localizations/argentina.rst:286
#: ../../accounting/localizations/colombia.rst:166
msgid "Invoice"
msgstr ""

#: ../../accounting/localizations/argentina.rst:288
msgid ""
"After the partners and journals are created and configured, when the "
"invoices are created the will have the next behaviour:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:292
msgid "Document type assignation"
msgstr ""

#: ../../accounting/localizations/argentina.rst:294
msgid ""
"Once the partner is selected the document type will filled automatically, "
"based on the AFIP document type:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:297
msgid "**Invoice for a customer IVA Responsable Inscripto, prefix A**."
msgstr ""

#: ../../accounting/localizations/argentina.rst:302
msgid "**Invoice for an end customer, prefix B**."
msgstr ""

#: ../../accounting/localizations/argentina.rst:307
msgid "**Exportation Invoice, prefix E**."
msgstr ""

#: ../../accounting/localizations/argentina.rst:312
msgid ""
"As it is shown in the invoices, all of them use the same journal but the "
"prefix and sequence is given by the document type."
msgstr ""

#: ../../accounting/localizations/argentina.rst:315
msgid ""
"The most common document type will be defined automatically for the "
"different combinations of AFIP responsibility type but it can be updated "
"manually by the user."
msgstr ""

#: ../../accounting/localizations/argentina.rst:320
msgid "Electronic Invoice elements"
msgstr ""

#: ../../accounting/localizations/argentina.rst:321
msgid ""
"When using electronic invoice, if all the information is correct the Invoice"
" is posted in the standard way, in case that something needs to be addressed"
" (check the section common errors for more detail), an error message is "
"raised indicating the issue/proposed solution and the invoice remains in "
"draft until the related data is corrected."
msgstr ""

#: ../../accounting/localizations/argentina.rst:326
msgid ""
"Once the invoice is posted, the information related to the AFIP validation "
"and status is displayed in the AFIP Tab, including:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:329
msgid "AFIP Autorisation:  CAE number."
msgstr ""

#: ../../accounting/localizations/argentina.rst:330
msgid ""
"Expiration date: Deadline to deliver the invoice to the customers. Normally "
"10 days after the CAE is generated."
msgstr ""

#: ../../accounting/localizations/argentina.rst:332
msgid "Result:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:334
msgid "Aceptado en AFIP."
msgstr ""

#: ../../accounting/localizations/argentina.rst:335
msgid "Aceptado con Observaciones."
msgstr ""

#: ../../accounting/localizations/argentina.rst:341
msgid "Invoice Taxes"
msgstr ""

#: ../../accounting/localizations/argentina.rst:343
msgid ""
"Based on the  AFIP Responsibility type,  the VAT tax can have a different "
"behavior on the pdf report:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:346
msgid ""
"**A. Tax excluded:** In this case the taxed amount needs to be clearly "
"identified in the report. This condition applies when the customer has the "
"following AFIP Responsibility type:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:349
msgid "Responsable Inscripto."
msgstr ""

#: ../../accounting/localizations/argentina.rst:354
msgid ""
"**B. Tax amount included:** This means that the taxed amount is included as "
"part of the product price, subtotal and totals. This condition applies when "
"the customer has the following AFIP Responsibility types:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:358
msgid "IVA Sujeto Exento."
msgstr ""

#: ../../accounting/localizations/argentina.rst:359
msgid "Consumidor Final."
msgstr ""

#: ../../accounting/localizations/argentina.rst:360
msgid "Responsable Monotributo."
msgstr ""

#: ../../accounting/localizations/argentina.rst:361
msgid "IVA liberado."
msgstr ""

#: ../../accounting/localizations/argentina.rst:368
msgid "Special Use Cases"
msgstr ""

#: ../../accounting/localizations/argentina.rst:371
msgid "Invoices for Services"
msgstr ""

#: ../../accounting/localizations/argentina.rst:372
msgid ""
"For electronic invoices that include Services, the AFIP requires to report "
"the  service starting and ending date, this information can be filled in the"
" tab “Other Info”:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:378
msgid ""
"If  the dates are not selected manually before the invoice is validated, the"
" values will be filled automatically considering the beginning and day of "
"the invoice month:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:386
msgid "Exportation Invoices"
msgstr ""

#: ../../accounting/localizations/argentina.rst:387
msgid ""
"The invoices related to Exportation transactions required a Journal that "
"used the AFIP POS System “Expo Voucher - Web Service” so the proper document"
" type be associated:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:393
msgid ""
"When the customer selected in the Invoice has set the AFIP responsibility "
"type as “Cliente / Proveedor del Exterior” or “IVA Liberado – Ley Nº "
"19.640”, Odoo automatically assigned:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:396
msgid "Journal related to the exportation Web Service."
msgstr ""

#: ../../accounting/localizations/argentina.rst:397
msgid "Exportation document type ."
msgstr ""

#: ../../accounting/localizations/argentina.rst:398
msgid "Fiscal position: Compras/Ventas al exterior."
msgstr ""

#: ../../accounting/localizations/argentina.rst:399
msgid "Concepto AFIP:  Products / Definitive export of goods."
msgstr ""

#: ../../accounting/localizations/argentina.rst:400
msgid "Exempt Taxes."
msgstr ""

#: ../../accounting/localizations/argentina.rst:406
msgid ""
"The Exportation Documents required the Incoterm in :menuselection:`Other "
"Info --> Accounting`:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:413
msgid "Fiscal Bond"
msgstr ""

#: ../../accounting/localizations/argentina.rst:414
msgid ""
"The Electronic Fiscal bond is used for those who invoice capital goods and "
"wish to access the benefit of the Electronic Tax Bonds granted by the "
"Ministry of Economy."
msgstr ""

#: ../../accounting/localizations/argentina.rst:417
#: ../../accounting/localizations/argentina.rst:442
msgid ""
"For these transactions it’s important to have into consideration the next "
"requirements:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:419
msgid "Currency (according to parameter table) and invoice quotation."
msgstr ""

#: ../../accounting/localizations/argentina.rst:420
msgid "Taxes."
msgstr ""

#: ../../accounting/localizations/argentina.rst:421
msgid "Zone."
msgstr ""

#: ../../accounting/localizations/argentina.rst:422
msgid "Detail each item."
msgstr ""

#: ../../accounting/localizations/argentina.rst:424
msgid "Code according to the Common Nomenclator of Mercosur (NCM)."
msgstr ""

#: ../../accounting/localizations/argentina.rst:425
msgid "Complete description."
msgstr ""

#: ../../accounting/localizations/argentina.rst:426
msgid "Unit Net Price."
msgstr ""

#: ../../accounting/localizations/argentina.rst:427
msgid "Quantity."
msgstr ""

#: ../../accounting/localizations/argentina.rst:428
msgid "Unit of measurement."
msgstr ""

#: ../../accounting/localizations/argentina.rst:429
msgid "Bonus."
msgstr ""

#: ../../accounting/localizations/argentina.rst:430
msgid "VAT rate."
msgstr ""

#: ../../accounting/localizations/argentina.rst:434
msgid "Electronic Credit Invoice MiPyme (FCE)"
msgstr ""

#: ../../accounting/localizations/argentina.rst:436
msgid ""
"**Invoices:** There are several document types classified as Mipyme also "
"known as Electronic Credit Invoice (FCE in spanish), which is used to "
"impulse the SME, its purpose is to develop a mechanism that improves the "
"financing conditions of these companies and allows them to increase their "
"productivity, through the early collection of credits and receivables issued"
" to their clients and / or vendors."
msgstr ""

#: ../../accounting/localizations/argentina.rst:444
msgid "Specific document types (201, 202, 206, etc)."
msgstr ""

#: ../../accounting/localizations/argentina.rst:445
msgid "The emisor should be eligible by the AFIP to MiPyme transactions."
msgstr ""

#: ../../accounting/localizations/argentina.rst:446
msgid "The amount should be bigger than 100,000 ARS."
msgstr ""

#: ../../accounting/localizations/argentina.rst:447
msgid ""
"A bank account type CBU must be related to the emisor, otherwise the invoice"
" can’t be validated, having these errors messages for example:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:453
msgid ""
"**Credit& Debit Notes:** When creating a Credit/Debit note related to a FCE "
"document, it is important take the next points into consideration:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:456
msgid ""
"Use the Credit and Debit Note buttons, so the correct reference of the "
"originator document passed to the note."
msgstr ""

#: ../../accounting/localizations/argentina.rst:462
msgid ""
"The document letter should be the same than the originator document (either "
"A or B)."
msgstr ""

#: ../../accounting/localizations/argentina.rst:463
msgid ""
"The same currency as the source document must be used.  When using a "
"secondary currency there is an exchange difference  if the currency rate is "
"different between the emission day and the payment date, it’s possible to "
"create a credit/debit note to decrease/increase the amount to pay in ARS."
msgstr ""

#: ../../accounting/localizations/argentina.rst:468
msgid "In the workflow we can have two scenarios:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:470
msgid ""
"The FCE is rejected so the Credit Note should have the field “FCE, is "
"Cancellation?” as True."
msgstr ""

#: ../../accounting/localizations/argentina.rst:471
msgid ""
"The Credit Note, is created with the negative amount to annulate the FCE "
"document, in this case the field “FCE, is Cancellation?” must be empty "
"(false)."
msgstr ""

#: ../../accounting/localizations/argentina.rst:478
msgid "Invoice printed report"
msgstr ""

#: ../../accounting/localizations/argentina.rst:479
msgid ""
"The PDF report related to electronic invoices that have been validated by "
"the AFIP includes a barcode at the bottom of the format which represent the "
"CAE number, the Expiration Date is also displayed as it’s legal requirement:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:488
msgid "Troubleshooting and Auditing"
msgstr ""

#: ../../accounting/localizations/argentina.rst:489
msgid ""
"For auditing and troubleshooting purposes you can get the detailed "
"information of an invoice number that has been  previously sent to the AFIP,"
msgstr ""

#: ../../accounting/localizations/argentina.rst:499
msgid ""
"You can also get the last number used in AFIP for a specific Document Type "
"and POS Number as support for any possible  issues on the sequence "
"synchronization between Odoo and AFIP."
msgstr ""

#: ../../accounting/localizations/argentina.rst:507
#: ../../accounting/others/multicurrencies/invoices_payments.rst:64
#: ../../accounting/payables/supplier_bills.rst:3
msgid "Vendor Bills"
msgstr ""

#: ../../accounting/localizations/argentina.rst:509
msgid ""
"Based on the purchase journal selected for the vendor bill, the document "
"type is now a required field. This value is auto populated based on the AFIP"
" Responsibility type of Issuer and Customer, but the value can be switched "
"if necessary."
msgstr ""

#: ../../accounting/localizations/argentina.rst:516
msgid ""
"The document number needs to be registered manually and the format is "
"validated automatically, in case that the format is invalid a user error "
"will be displayed indicating the correct format that is expected."
msgstr ""

#: ../../accounting/localizations/argentina.rst:523
msgid ""
"The vendor bill number is structured in the same way that the invoices with "
"the difference that the document sequence is input by the user: “Document "
"Prefix - Letter -  Document number\"."
msgstr ""

#: ../../accounting/localizations/argentina.rst:528
msgid "Validate Vendor Bill number in AFIP"
msgstr ""

#: ../../accounting/localizations/argentina.rst:529
msgid ""
"As most companies have internal controls to verify that the vendor bill is "
"related to an AFIP valid document,  an automatic validation can be set in "
":menuselection:`Accounting --> Settings --> Argentinian Localization --> "
"Validate document in the AFIP`, considering the following levels:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:533
msgid ""
"**Not available:** The verification is not done (this is the default value)."
msgstr ""

#: ../../accounting/localizations/argentina.rst:534
msgid ""
"**Available:**  The verification  is done, in case the number is not valid "
"it only raises a warning but it allows you to post the vendor bill."
msgstr ""

#: ../../accounting/localizations/argentina.rst:536
msgid ""
"**Required:** The verification  is done and it doesn't allow the user to "
"post the vendor bill if the document number is not valid."
msgstr ""

#: ../../accounting/localizations/argentina.rst:543
msgid "How to use it in Odoo"
msgstr ""

#: ../../accounting/localizations/argentina.rst:544
msgid ""
"This tool incorporates in the vendor bill a new \"Verify on AFIP\" button "
"located next to the AFIP Authorization code."
msgstr ""

#: ../../accounting/localizations/argentina.rst:550
msgid ""
"In case it’s not a valid AFIP authorization the value “Rejected” will be "
"displayed and the details of the validation will be added to the chatter."
msgstr ""

#: ../../accounting/localizations/argentina.rst:558
msgid "Special Use cases"
msgstr ""

#: ../../accounting/localizations/argentina.rst:560
msgid "Untaxed Concepts"
msgstr ""

#: ../../accounting/localizations/argentina.rst:561
msgid ""
"There are some transactions that include items that are not part of the VAT "
"base amount, this is commonly used in fuel and gasoline invoices."
msgstr ""

#: ../../accounting/localizations/argentina.rst:564
msgid ""
"The vendor bill will be registered using 1 item for each product that is "
"part of the VAT base amount and an additional item to register the amount of"
"  the Exempt concept:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:571
msgid "Perception Taxes"
msgstr ""

#: ../../accounting/localizations/argentina.rst:572
msgid ""
"The vendor bill will be registered using 1 item for each product that is "
"part of the VAT base amount, the perception tax can be added in any of the "
"product lines, as result we will have one tax group for the VAT and one for "
"the perception, the perception default value is always 1.00."
msgstr ""

#: ../../accounting/localizations/argentina.rst:580
msgid ""
"You should use the pencil that is the next to the Perception amount to edit "
"it and set the correct amount."
msgstr ""

#: ../../accounting/localizations/argentina.rst:586
msgid "After this is done the invoice can be validated."
msgstr ""

#: ../../accounting/localizations/argentina.rst:590
msgid "Reports"
msgstr ""

#: ../../accounting/localizations/argentina.rst:592
msgid "As part of the localization the next Financial reports were added:"
msgstr ""

#: ../../accounting/localizations/argentina.rst:598
msgid "VAT Reports"
msgstr ""

#: ../../accounting/localizations/argentina.rst:601
msgid "Libro de IVA Ventas"
msgstr ""

#: ../../accounting/localizations/argentina.rst:607
msgid "Libro de IVA Compras"
msgstr ""

#: ../../accounting/localizations/argentina.rst:613
msgid "Resumen de IVA"
msgstr ""

#: ../../accounting/localizations/argentina.rst:619
msgid "IIBB - Reports"
msgstr ""

#: ../../accounting/localizations/argentina.rst:622
msgid "IIBB - Ventas por Jurisdicción"
msgstr ""

#: ../../accounting/localizations/argentina.rst:628
msgid "IIBB - Compras  por Jurisdicción"
msgstr ""

#: ../../accounting/localizations/colombia.rst:3
msgid "Colombia"
msgstr ""

#: ../../accounting/localizations/colombia.rst:8
msgid ""
"Electronic invoicing for Colombia is available from Odoo 12 and requires the"
" next modules:"
msgstr ""

#: ../../accounting/localizations/colombia.rst:11
msgid ""
"**l10n_co**: All the basic data to manage the accounting module, contains "
"the default setup for: chart of accounts, taxes, retentions, identification "
"document types"
msgstr ""

#: ../../accounting/localizations/colombia.rst:14
msgid ""
"**l10n_co_edi**: This module includes all the extra fields that are required"
" for the Integration with Carvajal T&S and generate the electronic invoice, "
"based on the DIAN legal requirements."
msgstr ""

#: ../../accounting/localizations/colombia.rst:20
msgid "Workflow"
msgstr ""

#: ../../accounting/localizations/colombia.rst:30
msgid "Install the Colombian localization modules"
msgstr ""

#: ../../accounting/localizations/colombia.rst:32
msgid ""
"For this, go in Apps and search for Colombia. Then click Install for the "
"first two modules."
msgstr ""

#: ../../accounting/localizations/colombia.rst:40
msgid "Configure credentials for Carvajal T&S web service"
msgstr ""

#: ../../accounting/localizations/colombia.rst:42
msgid ""
"Once that the modules are installed, in order to be able to connect with "
"Carvajal T&S Web Service, it's necessary to configure the user and "
"credentials, this information will be provided by Carvajal T&S."
msgstr ""

#: ../../accounting/localizations/colombia.rst:46
#: ../../accounting/localizations/colombia.rst:68
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Settings` and look "
"for the *Colombian Electronic Invoice* section."
msgstr ""

#: ../../accounting/localizations/colombia.rst:52
msgid ""
"Using the Testing mode it is possible to connect with a Carvajal T&S testing"
" environment. This allows users to test the complete workflow and "
"integration with the CEN Financiero portal, which is accessible here: "
"https://cenfinancierolab.cen.biz"
msgstr ""

#: ../../accounting/localizations/colombia.rst:57
msgid ""
"Once that Odoo and Carvajal T&S is fully configured and ready for production"
" the testing environment can be disabled."
msgstr ""

#: ../../accounting/localizations/colombia.rst:62
msgid "Configure your report data"
msgstr ""

#: ../../accounting/localizations/colombia.rst:64
msgid ""
"As part of the configurable information that is sent in the XML, you can "
"define the data for the fiscal section and the bank information in the PDF."
msgstr ""

#: ../../accounting/localizations/colombia.rst:76
msgid "Configure data required in the XML"
msgstr ""

#: ../../accounting/localizations/colombia.rst:82
msgid "Identification"
msgstr ""

#: ../../accounting/localizations/colombia.rst:84
msgid ""
"As part of the Colombian Localization, the document types defined by the "
"DIAN are now available on the Partner form. Colombian partners have to have "
"their identification number and document type set:"
msgstr ""

#: ../../accounting/localizations/colombia.rst:91
msgid ""
"When the document type is RUT the identification number needs to be "
"configured in Odoo including the verification digit, Odoo will split this "
"number when the data to the third party vendor is sent."
msgstr ""

#: ../../accounting/localizations/colombia.rst:98
msgid "Fiscal structure (RUT)"
msgstr ""

#: ../../accounting/localizations/colombia.rst:100
msgid ""
"The partner's responsibility codes (section 53 in the RUT document) are "
"included as part of the electronic invoice module given that is part of the "
"information required by the DIAN ."
msgstr ""

#: ../../accounting/localizations/colombia.rst:104
msgid ""
"These fields can be found in :menuselection:`Partner --> Sales & Purchase "
"Tab --> Fiscal Information`"
msgstr ""

#: ../../accounting/localizations/colombia.rst:110
msgid ""
"Additionally two booleans fields were added in order to specify the fiscal "
"regimen of the partner."
msgstr ""

#: ../../accounting/localizations/colombia.rst:117
msgid ""
"If your sales transactions include products with taxes, it's important to "
"consider that an extra field *Value Type* needs to be configured per tax. "
"This option is located in the Advanced Options tab."
msgstr ""

#: ../../accounting/localizations/colombia.rst:124
msgid ""
"Retention tax types (ICA, IVA, Fuente) are also included in the options to "
"configure your taxes. This configuration is used in order to correctly "
"display taxes in the invoice PDF."
msgstr ""

#: ../../accounting/localizations/colombia.rst:135
msgid ""
"Once the DIAN has assigned the official sequence and prefix for the "
"electronic invoice resolution, the Sales journals related to your invoice "
"documents need to be updated in Odoo.  The sequence can be accessed using "
"the :doc:`Developer mode <../../general/developer_mode/activate>`: "
":menuselection:`Accounting --> Settings --> Configuration Setting --> "
"Journals`."
msgstr ""

#: ../../accounting/localizations/colombia.rst:144
msgid ""
"Once that the sequence is opened, the Prefix and Next Number fields should "
"be configured and synchronized with the CEN Financiero."
msgstr ""

#: ../../accounting/localizations/colombia.rst:152
msgid "Users"
msgstr ""

#: ../../accounting/localizations/colombia.rst:154
msgid ""
"The default template that is used by Odoo on the invoice PDF includes the "
"job position of the salesperson, so these fields should be configured:"
msgstr ""

#: ../../accounting/localizations/colombia.rst:168
msgid ""
"When all your master data and credentials has been configured, it's possible"
" to start testing the electronic invoice workflow."
msgstr ""

#: ../../accounting/localizations/colombia.rst:173
#: ../../accounting/overview/process_overview/customer_invoice.rst:30
msgid "Invoice creation"
msgstr ""

#: ../../accounting/localizations/colombia.rst:175
msgid ""
"The functional workflow that takes place before an invoice validation "
"doesn't change. The main changes that are introduced with the electronic "
"invoice are the next fields:"
msgstr ""

#: ../../accounting/localizations/colombia.rst:182
msgid "There are three types of documents:"
msgstr ""

#: ../../accounting/localizations/colombia.rst:184
msgid ""
"**Factura Electronica**: This is the regular type of document and its "
"applicable for Invoices, Credit Notes and Debit Notes."
msgstr ""

#: ../../accounting/localizations/colombia.rst:186
msgid ""
"**Factura de Importación**: This should be selected for importation "
"transactions."
msgstr ""

#: ../../accounting/localizations/colombia.rst:188
msgid ""
"**Factura de contingencia**: This is an exceptional type that is used as a "
"manual backup in case that the company is not able to use the ERP and it's "
"necessary to generate the invoice manually, when this invoice is added to "
"the ERP, this invoice type should be selected."
msgstr ""

#: ../../accounting/localizations/colombia.rst:196
msgid "Invoice validation"
msgstr ""

#: ../../accounting/localizations/colombia.rst:198
msgid ""
"After the invoice is validated an XML file is created and sent automatically"
" to Carvajal, this file is displayed in the chatter."
msgstr ""

#: ../../accounting/localizations/colombia.rst:204
msgid ""
"An extra field is now displayed in \"Other Info\" tab with the name of the "
"XML file. Additionally there is a second extra field that is displayed with "
"the Electronic Invoice status, with the initial value \"In progress\":"
msgstr ""

#: ../../accounting/localizations/colombia.rst:214
msgid "Reception of legal XML and PDF"
msgstr ""

#: ../../accounting/localizations/colombia.rst:216
msgid ""
"The electronic invoice vendor receives the XML file and proceeds to validate"
" the structure and the information in it, if everything is correct the "
"invoice status changes to \"Validated\" after using the \"Check Carvajal "
"Status\" button in the Action dropdown. They then proceed to generate a "
"Legal XML which includes a digital signature and a unique code (CUFE), a PDF"
" invoice that includes a QR code and the CUFE is also generated."
msgstr ""

#: ../../accounting/localizations/colombia.rst:224
msgid "After this:"
msgstr ""

#: ../../accounting/localizations/colombia.rst:226
msgid ""
"A ZIP containing the legal XML and the PDF is downloaded and displayed in "
"the invoice chatter:"
msgstr ""

#: ../../accounting/localizations/colombia.rst:233
msgid "The Electronic Invoice status changes to \"Accepted\""
msgstr ""

#: ../../accounting/localizations/colombia.rst:237
msgid "Common errors"
msgstr ""

#: ../../accounting/localizations/colombia.rst:239
msgid ""
"During the XML validation the most common errors are usually related to "
"missing master data. In such cases, error messages are shown in the chatter "
"after updating the electronic invoice status."
msgstr ""

#: ../../accounting/localizations/colombia.rst:246
msgid ""
"After the master data is corrected, it's possible to reprocess the XML with "
"the new data and send the updated version, using the following button:"
msgstr ""

#: ../../accounting/localizations/colombia.rst:258
msgid "Additional use cases"
msgstr ""

#: ../../accounting/localizations/colombia.rst:260
msgid ""
"The process for credit and debit notes is exactly the same as the invoice, "
"the functional workflow remains the same as well."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:3
msgid "Colombia (ES)"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:6
msgid "Introducción"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:8
msgid ""
"La Facturación Electrónica para Colombia está disponible en Odoo 12 y "
"requiere los siguientes Módulos:"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:11
msgid ""
"**l10n_co**: Contiene los datos básicos para manejar el módulo de "
"contabilidad, incluyendo la configuración por defecto de los siguientes "
"puntos:"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:15
msgid "Plan Contable"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:16
#: ../../accounting/localizations/colombia_ES.rst:124
msgid "Impuestos"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:17
msgid "Retenciones"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:18
msgid "Tipos de Documentos de Identificación"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:20
msgid ""
"**l10n_co_edi**: Este módulo incluye todos los campos adicionales que son "
"requeridos para la Integración entre Carvajal T&S y la generación de la "
"Factura Electrónica, basado en los requisitos legales de la DIAN."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:26
msgid "Flujo General"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:33
msgid "Configuración"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:36
msgid "Instalación de los módulos de Localización Colombiana"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:38
msgid ""
"Para esto ve a las aplicaciones y busca “Colombia”, luego da click en "
"Instalar a los primeros dos módulos:"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:46
msgid "Configuración de las credenciales del Servicio Web de Carvajal T&S"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:50
msgid ""
"Una vez que los módulos están instalados, para poderte conectar con el "
"Servicio Web de Carvajal T&S, es necesario configurar el Usuario y las "
"Credenciales. Esta información será provista por Carvajal T&S."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:52
msgid ""
"Ve a :menuselection:`Facturación --> Configuración --> Configuración` y "
"busca la sección **Facturación Electrónica Colombiana**"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:57
msgid ""
"La funcionalidad de pruebas le permite conectarse e interactuar con el "
"ambiente piloto de Carvajal T&S, esto permite a los usuarios probar el flujo"
" completo y la integración con el Portal Financiero CEN, al cual se accede a"
" través de la siguiente liga: `Cenfinanciero "
"<https://cenfinancierolab.cen.biz>`_."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:62
msgid ""
"Una vez que el ambiente de producción está listo en Odoo y en Carvajal T&S "
"el ambiente de pruebas debe ser deshabilitado para poder enviar la "
"información al ambiente de producción de Carvajal, para el cual es utilizada"
" la siguiente URL: `Cenfinanciero <https://cenfinancierolab.cen.biz>`_."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:69
msgid "Configuración de Información para PDF"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:73
msgid ""
"Como parte de la información configurable que es enviada en el XML, puedes "
"definir los datos de la sección fiscal del PDF, así como de la información "
"Bancaria."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:75
msgid ""
"Ve a :menuselection:`Contabilidad --> Configuración --> Ajustes` y busca la "
"sección **Facturación Electrónica Colombiana**."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:82
msgid "Configuración de los Datos Principales Requeridos en el XML"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:85
msgid "Contacto (Tercero)"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:88
msgid "Identificación"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:90
msgid ""
"Como parte de la Localización Colombiana, los tipos de documentos definidos "
"por la DIAN ahora están disponibles en el formulario de Contactos, por lo "
"cual ya es posible asignarles su número de identificación asociado al tipo "
"de documento correspondiente."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:98
msgid ""
"Nota: Cuando el tipo de documento es RUT la identificación necesita ser "
"ingresada en Odoo incluyendo el Dígito de Verificación. Odoo separará este "
"número cuando la información sea enviada a los proveedores terceros."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:105
msgid "Estructura Fiscal (RUT)"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:107
msgid ""
"Los Códigos de tipo de Obligación aplicables a los terceros (sección 53 en "
"el documento de RUT), son incluidos como parte del módulo de Facturación "
"Electrónica, dado que es información requerida por la DIAN."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:111
msgid ""
"Estos campos se encuentran en :menuselection:`Contactos --> Pestaña de "
"Ventas y Compras --> Información Fiscal`"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:117
msgid ""
"Adicionalmente dos últimos campos fueron agregados para especificar el "
"régimen fiscal del contacto. Cabe aclarar que para envío de Factura "
"electrónica de Carvajal, únicamente se hace distinción de entre Grandes "
"Contribuyentes y Régimen simplificado, por lo se muestran solo estas dos "
"opciones."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:126
msgid ""
"Si tus transacciones de ventas incluyen productos con impuestos, es "
"importante considerar que un campo adicional llamado *Tipo de Valor* "
"necesita ser configurado en la siguiente ruta: :menuselection:`Contabilidad "
"--> Configuración --> Impuestos: --> Opciones Avanzadas --> Tipo de Valor`"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:134
msgid ""
"Los impuestos para Retenciones (ICA, IVA y Fuente) también están incluidos "
"en las opciones para configurar tus impuestos, esta configuración es "
"considerada para desplegar correctamente los impuestos en la representación "
"gráfica de la Factura. (PDF)"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:144
msgid "Diarios"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:146
msgid ""
"Una vez que la DIAN ha asignado la secuencia y prefijo oficiales para la "
"resolución de la Facturación Electrónica, los Diarios de Ventas relacionados"
" con tus documentos de facturación necesitan ser actualizados en Odoo."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:151
msgid ""
"La secuencia es configurada usando el modo de desarrollador en la siguiente "
"ruta: :menuselection:`Contabilidad --> Configuración --> Diarios --> Liga de"
" Secuencia`"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:158
msgid ""
"Una vez que la secuencia es abierta, los campos de Prefijo y Siguiente "
"Número deben ser configurados y sincronizados con el CEN Financiero."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:166
msgid "Usuarios"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:168
msgid ""
"La plantilla por defecto que es usada por Odoo en la representación gráfica "
"incluye el nombre del Vendedor, así que estos campos deben ser considerados:"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:177
msgid "Uso y Pruebas"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:180
msgid "Facturas"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:182
msgid ""
"Una vez que toda la información principal y las credenciales han sido "
"configuradas, es posible empezar a probar el flujo de la Facturación "
"Electrónica siguiendo las instrucciones que se detallan a continuación:"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:188
msgid "Invoice Creation"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:190
msgid ""
"El flujo de trabajo funcional que lleva lugar antes de la validación de una "
"factura continua siendo igual con Facturación Electrónica, "
"independientemente de si es creada desde una Orden de Venta o si es creado "
"manualmente."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:195
msgid ""
"Los cambios principales que son introducidos con la Facturación Electrónica "
"son los siguientes:"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:198
msgid "Hay tres tipos de documentos"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:200
msgid ""
"**Factura electrónica**. Este es el documento normal y aplica para Facturas,"
" Notas de Crédito y Notas de Débito."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:203
msgid ""
"**Factura de Importación**. Debe ser seleccionada para transacciones de "
"importación."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:206
msgid ""
"**Factura de Contingencia**. Esta es un caso excepcional y es utilizada como"
" un respaldo manual en caso que la compañía no pueda usar el ERP y hay "
"necesidad de crear la factura manualmente. Al ingresar esta factura en el "
"ERP, se debe seleccionar este tipo."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:216
msgid "Invoice Validation"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:218
msgid ""
"Después que la factura fue validada, un archivo XML es creado y enviado "
"automáticamente al proveedor de la factura electrónica. Este archivo es "
"desplegado en el historial."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:225
msgid ""
"Un campo adicional es ahora desplegado en la pestaña de “Otra Información” "
"con el nombre del archivo XML. Adicionalmente hay un segundo campo adicional"
" que es desplegado con el estatus de la Factura Electrónica, con el valor "
"inicial **En Proceso**."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:235
msgid "Recepción del XML y PDF Legal"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:242
msgid ""
"El proveedor de la Factura Electrónica recibe el archivo XML y procede a "
"validar la información y la estructura contenida. Si todo es correcto, el "
"estatus de la Factura cambia a “Validado”. Como parte de este proceso se "
"generar el XML Legal, el cual incluye una firma digital y un código único "
"(CUFE) y generan el PDF de la Factura (el cual incluye un código QR) y el "
"CUFE."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:246
msgid ""
"Odoo envía una petición de actualización automáticamente para verificar que "
"el XML fue creado. Si este es el caso, las siguientes acciones son hechas "
"automáticamente:"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:248
msgid ""
"El XML Legal y el PDF son incluidos en un archivo ZIP y desplegados en el "
"historial de la Factura."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:253
msgid "El estatus de la Factura Electrónica es cambiado a “Aceptado”."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:258
msgid ""
"En caso que el PDF y el XML sean requeridos inmediatamente, es posible "
"mandar manualmente la petición del estatus usando el siguiente botón:"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:267
msgid "Errores Frecuentes"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:269
msgid ""
"Durante la validación del XML los errores más comunes usualmente están "
"relacionados con información principal faltante. En estos casos, los "
"detalles del error son recuperados en la petición de actualización y "
"desplegados en el historial."
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:277
msgid ""
"Si la información principal es corregida, es posible re procesar el XML con "
"la nueva información y mandar la versión actualizada usando el siguiente "
"botón:"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:289
msgid "Casos de Uso adicionales"
msgstr ""

#: ../../accounting/localizations/colombia_ES.rst:291
msgid ""
"El proceso para las Notas de Crédito y Débito (Proveedores) es exactamente "
"el mismo que en las Facturas. Su flujo de trabajo funcional se mantiene "
"igual."
msgstr ""

#: ../../accounting/localizations/france.rst:3
msgid "France"
msgstr ""

#: ../../accounting/localizations/france.rst:6
msgid "FEC"
msgstr ""

#: ../../accounting/localizations/france.rst:8
msgid ""
"If you have installed the French Accounting, you will be able to download "
"the FEC. For this, go in :menuselection:`Accounting --> Reporting --> France"
" --> FEC`."
msgstr ""

#: ../../accounting/localizations/france.rst:12
msgid ""
"If you do not see the submenu **FEC**, go in **Apps** and search for the "
"module called **France-FEC** and verify if it is well installed."
msgstr ""

#: ../../accounting/localizations/france.rst:16
msgid "French Accounting Reports"
msgstr ""

#: ../../accounting/localizations/france.rst:18
msgid ""
"If you have installed the French Accounting, you will have access to some "
"accounting reports specific to France:"
msgstr ""

#: ../../accounting/localizations/france.rst:20
msgid "Bilan comptable"
msgstr ""

#: ../../accounting/localizations/france.rst:21
msgid "Compte de résultats"
msgstr ""

#: ../../accounting/localizations/france.rst:22
msgid "Plan de Taxes France"
msgstr ""

#: ../../accounting/localizations/france.rst:25
msgid "Get the VAT anti-fraud certification with Odoo"
msgstr ""

#: ../../accounting/localizations/france.rst:27
msgid ""
"As of January 1st 2018, a new anti-fraud legislation comes into effect in "
"France and DOM-TOM. This new legislation stipulates certain criteria "
"concerning the inalterability, security, storage and archiving of sales "
"data. These legal requirements are implemented in Odoo, version 9 onward, "
"through a module and a certificate of conformity to download."
msgstr ""

#: ../../accounting/localizations/france.rst:34
msgid "Is my company required to use an anti-fraud software?"
msgstr ""

#: ../../accounting/localizations/france.rst:36
msgid ""
"Your company is required to use an anti-fraud cash register software like "
"Odoo (CGI art. 286, I. 3° bis) if:"
msgstr ""

#: ../../accounting/localizations/france.rst:39
msgid "You are taxable (not VAT exempt) in France or any DOM-TOM,"
msgstr ""

#: ../../accounting/localizations/france.rst:40
msgid "Some of your customers are private individuals (B2C)."
msgstr ""

#: ../../accounting/localizations/france.rst:42
msgid ""
"This rule applies to any company size. Auto-entrepreneurs are exempted from "
"VAT and therefore are not affected."
msgstr ""

#: ../../accounting/localizations/france.rst:46
msgid "Get certified with Odoo"
msgstr ""

#: ../../accounting/localizations/france.rst:48
msgid "Getting compliant with Odoo is very easy."
msgstr ""

#: ../../accounting/localizations/france.rst:50
msgid ""
"Your company is requested by the tax administration to deliver a certificate"
" of conformity testifying that your software complies with the anti-fraud "
"legislation. This certificate is granted by Odoo SA to Odoo Enterprise users"
" `here <https://www.odoo.com/my/contract/french-certification/>`_. If you "
"use Odoo Community, you should `upgrade to Odoo Enterprise "
"<https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_ or contact"
" your Odoo service provider."
msgstr ""

#: ../../accounting/localizations/france.rst:58
msgid "In case of non-conformity, your company risks a fine of €7,500."
msgstr ""

#: ../../accounting/localizations/france.rst:60
msgid "To get the certification just follow the following steps:"
msgstr ""

#: ../../accounting/localizations/france.rst:62
msgid ""
"Install the anti-fraud module fitting your Odoo environment from the *Apps* "
"menu:"
msgstr ""

#: ../../accounting/localizations/france.rst:65
msgid ""
"if you use Odoo Point of Sale: *l10n_fr_pos_cert*: France - VAT Anti-Fraud "
"Certification for Point of Sale (CGI 286 I-3 bis)"
msgstr ""

#: ../../accounting/localizations/france.rst:66
msgid ""
"in any other case: *l10n_fr_certification*: France - VAT Anti-Fraud "
"Certification (CGI 286 I-3 bis)"
msgstr ""

#: ../../accounting/localizations/france.rst:68
msgid ""
"Make sure a country is set on your company, otherwise your entries won’t be "
"encrypted for the inalterability check. To edit your company’s data, go to "
":menuselection:`Settings --> Users & Companies --> Companies`. Select a "
"country from the list; Do not create a new country."
msgstr ""

#: ../../accounting/localizations/france.rst:72
msgid ""
"Download the mandatory certificate of conformity delivered by Odoo SA `here "
"<https://www.odoo.com/my/contract/french-certification/>`__."
msgstr ""

#: ../../accounting/localizations/france.rst:75
msgid ""
"To install the module in any system created before December 18th 2017, you "
"should update the modules list. To do so, activate the :doc:`Developer mode "
"<../../general/developer_mode/activate>`. Then go to the *Apps* menu and "
"press *Update Modules List* in the top-menu."
msgstr ""

#: ../../accounting/localizations/france.rst:79
msgid ""
"In case you run Odoo on-premise, you need to update your installation and "
"restart your server beforehand."
msgstr ""

#: ../../accounting/localizations/france.rst:81
msgid ""
"If you have installed the initial version of the anti-fraud module (prior to"
" December 18th 2017), you need to update it. The module's name was *France -"
" Accounting - Certified CGI 286 I-3 bis*. After an update of the modules "
"list, search for the updated module in *Apps*, select it and click "
"*Upgrade*. Finally, make sure the following module *l10n_fr_sale_closing* is"
" installed."
msgstr ""

#: ../../accounting/localizations/france.rst:90
msgid "Anti-fraud features"
msgstr ""

#: ../../accounting/localizations/france.rst:92
msgid "The anti-fraud module introduces the following features:"
msgstr ""

#: ../../accounting/localizations/france.rst:94
msgid ""
"**Inalterability**: deactivation of all the ways to cancel or modify key "
"data of POS orders, invoices and journal entries;"
msgstr ""

#: ../../accounting/localizations/france.rst:96
msgid "**Security**: chaining algorithm to verify the inalterability;"
msgstr ""

#: ../../accounting/localizations/france.rst:97
msgid ""
"**Storage**: automatic sales closings with computation of both period and "
"cumulative totals (daily, monthly, annually)."
msgstr ""

#: ../../accounting/localizations/france.rst:101
msgid "Inalterability"
msgstr ""

#: ../../accounting/localizations/france.rst:103
msgid ""
"All the possible ways to cancel and modify key data of paid POS orders, "
"confirmed invoices and journal entries are deactivated, if the company is "
"located in France or in any DOM-TOM."
msgstr ""

#: ../../accounting/localizations/france.rst:107
msgid ""
"If you run a multi-companies environment, only the documents of such "
"companies are impacted."
msgstr ""

#: ../../accounting/localizations/france.rst:111
msgid "Security"
msgstr ""

#: ../../accounting/localizations/france.rst:113
msgid ""
"To ensure the inalterability, every order or journal entry is encrypted upon"
" validation. This number (or hash) is calculated from the key data of the "
"document as well as from the hash of the precedent documents."
msgstr ""

#: ../../accounting/localizations/france.rst:118
msgid ""
"The module introduces an interface to test the data inalterability. If any "
"information is modified on a document after its validation, the test will "
"fail. The algorithm recomputes all the hashes and compares them against the "
"initial ones. In case of failure, the system points out the first corrupted "
"document recorded in the system."
msgstr ""

#: ../../accounting/localizations/france.rst:124
msgid ""
"Users with *Manager* access rights can launch the inalterability check. For "
"POS orders, go to :menuselection:`Point of Sales --> Reporting --> French "
"Statements`. For invoices or journal entries, go to "
":menuselection:`Invoicing/Accounting --> Reporting --> French Statements`."
msgstr ""

#: ../../accounting/localizations/france.rst:131
msgid "Storage"
msgstr ""

#: ../../accounting/localizations/france.rst:133
msgid ""
"The system also processes automatic sales closings on a daily, monthly and "
"annual basis. Such closings distinctly compute the sales total of the period"
" as well as the cumulative grand totals from the very first sales entry "
"recorded in the system."
msgstr ""

#: ../../accounting/localizations/france.rst:139
msgid ""
"Closings can be found in the *French Statements* menu of Point of Sale, "
"Invoicing and Accounting apps."
msgstr ""

#: ../../accounting/localizations/france.rst:143
msgid ""
"Closings compute the totals for journal entries of sales journals (Journal "
"Type = Sales)."
msgstr ""

#: ../../accounting/localizations/france.rst:145
msgid ""
"For multi-companies environments, such closings are performed by company."
msgstr ""

#: ../../accounting/localizations/france.rst:147
msgid ""
"POS orders are posted as journal entries at the closing of the POS session. "
"Closing a POS session can be done anytime. To prompt users to do it on a "
"daily basis, the module prevents from resuming a session opened more than 24"
" hours ago. Such a session must be closed before selling again."
msgstr ""

#: ../../accounting/localizations/france.rst:153
msgid ""
"A period’s total is computed from all the journal entries posted after the "
"previous closing of the same type, regardless of their posting date. If you "
"record a new sales transaction for a period already closed, it will be "
"counted in the very next closing."
msgstr ""

#: ../../accounting/localizations/france.rst:158
msgid ""
"For test & audit purposes such closings can be manually generated in the "
":doc:`Developer mode <../../general/developer_mode/activate>`. Then go to "
":menuselection:`Settings --> Technical --> Automation --> Scheduled "
"Actions`."
msgstr ""

#: ../../accounting/localizations/france.rst:164
msgid "Responsibilities"
msgstr ""

#: ../../accounting/localizations/france.rst:166
msgid ""
"Do not uninstall the module! If you do so, the hashes will be reset and none"
" of your past data will be longer guaranteed as being inalterable."
msgstr ""

#: ../../accounting/localizations/france.rst:169
msgid ""
"Users remain responsible for their Odoo instance and must use it with due "
"diligence. It is not permitted to modify the source code which guarantees "
"the inalterability of data."
msgstr ""

#: ../../accounting/localizations/france.rst:173
msgid ""
"Odoo absolves itself of all and any responsibility in case of changes in the"
" module’s functions caused by 3rd party applications not certified by Odoo."
msgstr ""

#: ../../accounting/localizations/france.rst:178
msgid "More Information"
msgstr ""

#: ../../accounting/localizations/france.rst:180
msgid ""
"You will find more information about this legislation in the official "
"documents:"
msgstr ""

#: ../../accounting/localizations/france.rst:182
msgid ""
"`Frequently Asked Questions "
"<https://www.economie.gouv.fr/files/files/directions_services/dgfip/controle_fiscal/actualites_reponses/logiciels_de_caisse.pdf>`_"
msgstr ""

#: ../../accounting/localizations/france.rst:183
msgid ""
"`Official Statement "
"<http://bofip.impots.gouv.fr/bofip/10691-PGP.html?identifiant=BOI-TVA-"
"DECLA-30-10-30-20160803>`_"
msgstr ""

#: ../../accounting/localizations/france.rst:184
msgid ""
"`Item 88 of Finance Law 2016 "
"<https://www.legifrance.gouv.fr/affichTexteArticle.do?idArticle=JORFARTI000031732968&categorieLien=id&cidTexte=JORFTEXT000031732865>`_"
msgstr ""

#: ../../accounting/localizations/germany.rst:3
msgid "Germany"
msgstr ""

#: ../../accounting/localizations/germany.rst:6
msgid "German Chart of Accounts"
msgstr ""

#: ../../accounting/localizations/germany.rst:8
msgid ""
"The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can "
"choose the one you want by going in :menuselection:`Accounting --> "
"Configuration` then choose the package you want in the Fiscal Localization "
"section."
msgstr ""

#: ../../accounting/localizations/germany.rst:12
#: ../../accounting/localizations/spain.rst:17
msgid ""
"Be careful, you can only change the accounting package as long as you have "
"not created any accounting entry."
msgstr ""

#: ../../accounting/localizations/germany.rst:16
msgid ""
"When you create a new SaaS database, the SKR03 is installed by default."
msgstr ""

#: ../../accounting/localizations/germany.rst:19
msgid "German Accounting Reports"
msgstr ""

#: ../../accounting/localizations/germany.rst:21
msgid ""
"Here is the list of German-specific reports available on Odoo Enterprise:"
msgstr ""

#: ../../accounting/localizations/germany.rst:23
#: ../../accounting/localizations/spain.rst:27
#: ../../accounting/others/reporting/main_reports.rst:30
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:65
msgid "Balance Sheet"
msgstr ""

#: ../../accounting/localizations/germany.rst:24
#: ../../accounting/localizations/netherlands.rst:19
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:17
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:89
msgid "Profit & Loss"
msgstr ""

#: ../../accounting/localizations/germany.rst:25
msgid "Tax Report (Umsatzsteuervoranmeldung)"
msgstr ""

#: ../../accounting/localizations/germany.rst:26
msgid "Partner VAT Intra"
msgstr ""

#: ../../accounting/localizations/germany.rst:29
msgid "Export from Odoo to Datev"
msgstr ""

#: ../../accounting/localizations/germany.rst:31
msgid ""
"It is possible to export your accounting entries from Odoo to Datev. To be "
"able to use this feature, the german accounting localization needs to be "
"installed on your Odoo Enterprise database. Then you can go in "
":menuselection:`Accounting --> Reporting --> General Ledger` then click on "
"the **Export Datev (csv)** button."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:3
msgid "Italy (IT)"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:5
msgid ""
"Questa guida spiegherà come utilizzare la fattura elettronica in Odoo e come"
" configurare correttamente i dati aziendali, i contatti e la contabilità. "
"Per testare la fattura elettronica i dati devono essere reali e non "
"inventati, altrimenti il sistema dell’agenzia delle entrate non riconoscerà "
"l’interscambio di informazioni."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:13
msgid "Configurare le informazioni sulla tua Azienda"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:15
msgid ""
"Il passo successivo è la configurazione delle informazioni necessarie al "
"funzionamento della fatturazione elettronica. Si può accedere alla schermata"
" dall’applicazione Impostazioni: selezionare “Utenti e aziende” e scegliere "
"Aziende. Accedere quindi alle informazioni sulla Azienda per cui si desidera"
" configurare la fatturazione elettronica."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:21
msgid ""
"I dati necessari al funzionamento dello strumento di fatturazione "
"elettronica sono i seguenti:"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:24
msgid ""
"Server PEC. Le informazioni sul server utilizzato dal tuo indirizzo di posta"
" elettronica certificata sono fornite dal tuo fornitore o dal Ministero. Lo "
"stesso server deve essere configurato come server che gestisce tutta la "
"corrispondenza mail in Odoo, per saperne di più si puo’ consultare la "
"relativa :doc:`guida <../../discuss/email_servers>`."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:30
msgid ""
"Indirizzo PEC dell’ Azienda, tale indirizzo deve essere lo stesso registrato"
" presso l’Agenzia delle Entrate per l’utilizzo dei servizi di fatturazione "
"elettronica."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:34
msgid ""
"Indirizzo PEC dell’Agenzia delle Entrate. La mail sarà fornito al momento "
"della registrazione della tua PEC presso l’Agenzia delle Entrate, ricorda "
"che l’Agenzia delle Entrate potrebbe cambiare questo indirizzo in seguito, "
"previa comunicazione."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:39
msgid ""
"Partita IVA e Codice Fiscale. Per far si che la Fatturazione Elettronica "
"funzioni correttamente, questi cambi devono essere compilati correttamente."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:43
msgid ""
"Regime Fiscale. Il regime fiscale a cui è sottoposta l’Azienda deve essere "
"selezionato scegliendo dalla lista precompilata fornita da Odoo. Chiedi al "
"commercialista qual’è il corretto regime fiscale!"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:47
msgid "Numero di Iscrizione nel registro delle Imprese."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:54
msgid "Configurare le impostazioni per la Fatturazione Elettronica"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:56
msgid ""
"Numero di iscrizione nel registro Imprese tenuto presso la Camera di "
"Commercio."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:59
msgid ""
"Rappresentate Fiscale. Questa opzione è dedicata ad aziende con sede al di "
"fuori del territorio nazionale ma conducenti attività commerciali in Italia "
"rilevanti ai fini dell’IVA. È possibile indicare in questo campo se "
"l’Azienda si avvale di un Rappresentate Fiscale in Italia."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:70
msgid "Configurare il profilo dei clienti"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:72
msgid ""
"Per un corretto utilizzo dell’applicazione, il profilo di clienti e "
"fornitori, nell’applicazione contatti, deve essere configurato con le "
"necessarie informazioni legali."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:76
msgid ""
"Selezionando il nome del cliente e accedendo quindi ai suoi dati, si trovano"
" i seguenti campi che devono essere compilati: Indirizzo PEC, Codice Fiscale"
" e Indice PA *che deve contere i 6-7 caratteri contenuti nell’indice PA e "
"necessari per la comunicazione tramite fattura elettronica*."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:87
msgid "Il processo di fatturazione"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:89
msgid ""
"Si può procedere ad emettere una fattura seguendo le indicazioni "
"dell’applicazione. Il momento che determina il formale invio della fattura è"
" il momento in cui viene selezionata l’opzione “Valida”. La fattura viene "
"quindi inviata: lo stato della sua consegna verrà notificato all’utente "
"tramite pop-up sulla parte iniziale della schermata della fattura."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:102
msgid "I messaggi che possono apparire sono i seguenti:"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:104
msgid "Fattura invitata. In attesa di accettazione"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:106
msgid "Invio fallito. Puoi modificare la fattura ed inviarla di nuovo"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:108
msgid ""
"La fattura è stata correttamente inviata ed accettata dal destinatario."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:111
msgid ""
"I vari stadi di spedizione e recezione della fattura sono visibili anche "
"dall’elenco delle Fatture nella forma di icone, accanto alla colonna “Stato”"
" dall’applicazione contabilità."
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:115
msgid "*Icona Rossa*: Invio fallito"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:117
msgid "*Icona Gialla*: Fattura invitata. In attesa di accettazione"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:119
msgid "*Icona Verde*: Fattura inviata e accettata dal destinatario"
msgstr ""

#: ../../accounting/localizations/italy_IT.rst:121
msgid ""
"Per inviare la fattura tramite PEC e generare il file XML, basterà cliccare "
"su invia. Il documento verrà poi mostrato tra gli allegati."
msgstr ""

#: ../../accounting/localizations/mexico.rst:3
msgid "Mexico"
msgstr ""

#: ../../accounting/localizations/mexico.rst:6
msgid ""
"This documentation is written assuming that you follow and know the official"
" documentation regarding Invoicing, Sales and Accounting and that you have "
"experience working with odoo on such areas, we are not intended to put here "
"procedures that are already explained on those documents, just the "
"information necessary to allow you use odoo in a Company with the country "
"\"Mexico\" set."
msgstr ""

#: ../../accounting/localizations/mexico.rst:17
msgid "The mexican localization is a group of 3 modules:"
msgstr ""

#: ../../accounting/localizations/mexico.rst:19
msgid ""
"**l10n_mx:** All basic data to manage the accounting, taxes and the chart of"
" account, this proposed chart of account installed is a intended copy of the"
" list of group codes offered by the `SAT`_."
msgstr ""

#: ../../accounting/localizations/mexico.rst:22
msgid ""
"**l10n_mx_edi**: All regarding to electronic transactions, CFDI 3.2 and 3.3,"
" payment complement, invoice addendum."
msgstr ""

#: ../../accounting/localizations/mexico.rst:24
msgid ""
"**l10n_mx_reports**: All mandatory electronic reports for electronic "
"accounting are here (Accounting app required)."
msgstr ""

#: ../../accounting/localizations/mexico.rst:27
msgid ""
"With the Mexican localization in Odoo you will be able not just to comply "
"with the required features by law in México but to use it as your accounting"
" and invoicing system due to all the set of normal requirements for this "
"market, becoming your Odoo in the perfect solution to administer your "
"company in Mexico."
msgstr ""

#: ../../accounting/localizations/mexico.rst:38
msgid ""
"After the configuration we will give you the process to test everything, try"
" to follow step by step in order to allow you to avoid expend time on fix "
"debugging problems. In any step you can recall the step and try again."
msgstr ""

#: ../../accounting/localizations/mexico.rst:44
msgid "Install the Mexican Accounting Localization"
msgstr ""

#: ../../accounting/localizations/mexico.rst:46
msgid "For this, go in Apps and search for Mexico. Then click on *Install*."
msgstr ""

#: ../../accounting/localizations/mexico.rst:52
msgid ""
"When creating a database from www.odoo.com, if you choose Mexico as country "
"when creating your account, the mexican localization will be automatically "
"installed."
msgstr ""

#: ../../accounting/localizations/mexico.rst:58
msgid "Electronic Invoices (CDFI 3.2 and 3.3 format)"
msgstr ""

#: ../../accounting/localizations/mexico.rst:60
msgid ""
"To enable this requirement in Mexico go to configuration in accounting Go in"
" :menuselection:`Accounting --> Settings` and enable the option on the image"
" with this you will be able to generate the signed invoice (CFDI 3.2 and "
"3.3) and generate the payment complement signed as well (3.3 only) all fully"
" integrate with the normal invoicing flow in Odoo."
msgstr ""

#: ../../accounting/localizations/mexico.rst:73
msgid "Set you legal information in the company"
msgstr ""

#: ../../accounting/localizations/mexico.rst:75
msgid ""
"First, make sure that your company is configured with the correct data. Go "
"in :menuselection:`Settings --> Users --> Companies` and enter a valid "
"address and VAT for your company. Don’t forget to define a mexican fiscal "
"position on your company’s contact."
msgstr ""

#: ../../accounting/localizations/mexico.rst:82
msgid ""
"If you want use the Mexican localization on test mode, you can put any known"
" address inside Mexico with all fields for the company address and set the "
"vat to **TCM970625MB1**."
msgstr ""

#: ../../accounting/localizations/mexico.rst:91
msgid ""
"Set the proper \"Fiscal Position\" on the partner that represent the company"
msgstr ""

#: ../../accounting/localizations/mexico.rst:93
msgid ""
"Go In the same form where you are editing the company save the record in "
"order to set this form as a readonly and on readonly view click on the "
"partner link, then edit it and set in the *Invoicing* tab the proper Fiscal "
"Information (for the **Test Environment** this must be *601 - General de Ley"
" Personas Morales*, just search it as a normal Odoo field if you can't see "
"the option)."
msgstr ""

#: ../../accounting/localizations/mexico.rst:101
msgid "Enabling CFDI Version 3.3"
msgstr ""

#: ../../accounting/localizations/mexico.rst:104
msgid ""
"This steps are only necessary when you will enable the CFDI 3.3 (only "
"available for V11.0 and above) if you do not have Version 11.0 or above on "
"your SaaS instance please ask for an upgrade by submitting a ticket to "
"support in https://www.odoo.com/help."
msgstr ""

#: ../../accounting/localizations/mexico.rst:109
msgid ""
"Enable the :doc:`Developer mode <../../general/developer_mode/activate>`."
msgstr ""

#: ../../accounting/localizations/mexico.rst:111
msgid ""
"Go and look the following technical parameter, on :menuselection:`Settings "
"--> Technical --> Parameters --> System Parameters` and set the parameter "
"called *l10n_mx_edi_cfdi_version* to 3.3 (Create it if the entry with this "
"name does not exist)."
msgstr ""

#: ../../accounting/localizations/mexico.rst:117
msgid ""
"The CFDI 3.2 will be legally possible until November 30th 2017 enable the "
"3.3 version will be a mandatory step to comply with the new `SAT "
"resolution`_ in any new database created since v11.0 released CFDI 3.3 is "
"the default behavior."
msgstr ""

#: ../../accounting/localizations/mexico.rst:127
msgid "Important considerations when yo enable the CFDI 3.3"
msgstr ""

#: ../../accounting/localizations/mexico.rst:129
#: ../../accounting/localizations/mexico.rst:680
msgid ""
"Your tax which represent the VAT 16% and 0% must have the \"Factor Type\" "
"field set to \"Tasa\"."
msgstr ""

#: ../../accounting/localizations/mexico.rst:137
msgid ""
"You must go to the Fiscal Position configuration and set the proper code (it"
" is the first 3 numbers in the name) for example for the test one you should"
" set 601, it will look like the image."
msgstr ""

#: ../../accounting/localizations/mexico.rst:144
msgid ""
"All products must have for CFDI 3.3 the \"SAT code\" and the field "
"\"Reference\" properly set, you can export them and re import them to do it "
"faster."
msgstr ""

#: ../../accounting/localizations/mexico.rst:152
msgid "Configure the PAC in order to sign properly the invoices"
msgstr ""

#: ../../accounting/localizations/mexico.rst:154
msgid ""
"To configure the EDI with the **PACs**, you can go in "
":menuselection:`Accounting --> Settings --> Electronic Invoicing (MX)`. You "
"can choose a PAC within the **List of supported PACs** on the *PAC field* "
"and then enter your PAC username and PAC password."
msgstr ""

#: ../../accounting/localizations/mexico.rst:160
msgid ""
"Remember you must sign up in the refereed PAC before hand, that process can "
"be done with the PAC itself on this case we will have two (2) availables "
"`Finkok`_ and `Solución Factible`_."
msgstr ""

#: ../../accounting/localizations/mexico.rst:164
msgid ""
"You must process your **Private Key (CSD)** with the SAT institution before "
"follow this steps, if you do not have such information please try all the "
"\"Steps for Test\" and come back to this process when you finish the process"
" proposed for the SAT in order to set this information for your production "
"environment with real transactions."
msgstr ""

#: ../../accounting/localizations/mexico.rst:174
msgid ""
"If you ticked the box *MX PAC test environment* there is no need to enter a "
"PAC username or password."
msgstr ""

#: ../../accounting/localizations/mexico.rst:181
msgid ""
"Here is a SAT certificate you can use if you want to use the *Test "
"Environment* for the Mexican Accounting Localization."
msgstr ""

#: ../../accounting/localizations/mexico.rst:184
msgid "`Certificate`_"
msgstr ""

#: ../../accounting/localizations/mexico.rst:185
msgid "`Certificate Key`_"
msgstr ""

#: ../../accounting/localizations/mexico.rst:186
msgid "**Password:** 12345678a"
msgstr ""

#: ../../accounting/localizations/mexico.rst:190
msgid "Configure the tag in sales taxes"
msgstr ""

#: ../../accounting/localizations/mexico.rst:192
msgid ""
"This tag is used to set the tax type code, transferred or withhold, "
"applicable to the concept in the CFDI. So, if the tax is a sale tax the "
"\"Tag\" field should be \"IVA\", \"ISR\" or \"IEPS\"."
msgstr ""

#: ../../accounting/localizations/mexico.rst:199
msgid ""
"Note that the default taxes already has a tag assigned, but when you create "
"a new tax you should choose a tag."
msgstr ""

#: ../../accounting/localizations/mexico.rst:207
msgid "Invoicing"
msgstr ""

#: ../../accounting/localizations/mexico.rst:209
msgid ""
"To use the mexican invoicing you just need to do a normal invoice following "
"the normal Odoo's behaviour."
msgstr ""

#: ../../accounting/localizations/mexico.rst:212
msgid ""
"Once you validate your first invoice a correctly signed invoice should look "
"like this:"
msgstr ""

#: ../../accounting/localizations/mexico.rst:219
msgid ""
"You can generate the PDF just clicking on the Print button on the invoice or"
" sending it by email following the normal process on odoo to send your "
"invoice by email."
msgstr ""

#: ../../accounting/localizations/mexico.rst:226
msgid ""
"Once you send the electronic invoice by email this is the way it should "
"looks like."
msgstr ""

#: ../../accounting/localizations/mexico.rst:234
msgid "Cancelling invoices"
msgstr ""

#: ../../accounting/localizations/mexico.rst:236
msgid ""
"The cancellation process is completely linked to the normal cancellation in "
"Odoo."
msgstr ""

#: ../../accounting/localizations/mexico.rst:238
msgid "If the invoice is not paid."
msgstr ""

#: ../../accounting/localizations/mexico.rst:240
msgid "Go to to the customer invoice journal where the invoice belong to."
msgstr ""

#: ../../accounting/localizations/mexico.rst:246
msgid "Check the \"Allow cancelling entries\" field."
msgstr ""

#: ../../accounting/localizations/mexico.rst:250
msgid "Go back to your invoice and click on the button \"Cancel Invoice\"."
msgstr ""

#: ../../accounting/localizations/mexico.rst:254
msgid ""
"For security reasons it is recommendable return the check on the to allow "
"cancelling to false again, then go to the journal and un check such field."
msgstr ""

#: ../../accounting/localizations/mexico.rst:257
msgid "**Legal considerations**"
msgstr ""

#: ../../accounting/localizations/mexico.rst:259
msgid "A cancelled invoice will automatically cancelled on the SAT."
msgstr ""

#: ../../accounting/localizations/mexico.rst:260
msgid ""
"If you retry to use the same invoice after cancelled, you will have as much "
"cancelled CFDI as you tried, then all those xml are important to maintain a "
"good control of the cancellation reasons."
msgstr ""

#: ../../accounting/localizations/mexico.rst:263
msgid ""
"You must unlink all related payment done to an invoice on odoo before cancel"
" such document, this payments must be cancelled to following the same "
"approach but setting the \"Allow Cancel Entries\" in the payment itself."
msgstr ""

#: ../../accounting/localizations/mexico.rst:269
msgid "Payments (Just available for CFDI 3.3)"
msgstr ""

#: ../../accounting/localizations/mexico.rst:271
msgid ""
"To generate the payment complement you only need to follow the normal "
"payment process in Odoo, this considerations to understand the behavior are "
"important."
msgstr ""

#: ../../accounting/localizations/mexico.rst:274
msgid ""
"To generate payment complement the payment term in the invoice must be PPD, "
"because It is the expected behavior legally required for \"Cash payment\"."
msgstr ""

#: ../../accounting/localizations/mexico.rst:278
msgid "**1.1. How can I generate an invoice with payment term `PUE`?**"
msgstr ""

#: ../../accounting/localizations/mexico.rst:280
msgid ""
"`According to the SAT documentation`_ a payment is classified as ``PUE`` if "
"the invoice was agreed to be fully payed before the 17th of the next "
"calendar month (the next month of the CFDI date), any other condition will "
"generate a ``PPD`` invoice."
msgstr ""

#: ../../accounting/localizations/mexico.rst:285
msgid "**1.2. How can I get this with Odoo?**"
msgstr ""

#: ../../accounting/localizations/mexico.rst:287
msgid ""
"In order to set the appropriate CFDI payment term (PPD or PUE), you can "
"easily set it by using the ``Payment Terms`` defined in the invoice."
msgstr ""

#: ../../accounting/localizations/mexico.rst:290
msgid ""
"If an invoice is generated without ``Payment Term`` the attribute "
"``MetodoPago`` will be ``PUE``."
msgstr ""

#: ../../accounting/localizations/mexico.rst:293
msgid ""
"Today, if is the first day of the month and is generated an invoice with "
"``Payment Term`` ``30 Net Days`` the ``Due Date`` calculated is going to be "
"the first day of the following month, this means its before the 17th of the "
"next month, then the attribute ``MetodoPago`` will be ``PUE``."
msgstr ""

#: ../../accounting/localizations/mexico.rst:298
msgid ""
"Today, if an invoice is generated with ``Payment Term`` ``30 Net Days`` and "
"the ``Due Date`` is higher than the day 17 of the next month the "
"``MetodoPago`` will be ``PPD``."
msgstr ""

#: ../../accounting/localizations/mexico.rst:302
msgid ""
"If having a ``Payment Term`` with 2 lines or more, for example ``30% Advance"
" End of Following Month``, this is an installments term, then the attribute "
"``MetodoPago`` will be ``PPD``."
msgstr ""

#: ../../accounting/localizations/mexico.rst:306
msgid ""
"To test a normal signed payment just create an invoice with payment term "
"``30% Advance End of Following Month`` and then register a payment to it."
msgstr ""

#: ../../accounting/localizations/mexico.rst:308
msgid "You must print the payment in order to retrieve the PDF properly."
msgstr ""

#: ../../accounting/localizations/mexico.rst:309
msgid ""
"Regarding the \"Payments in Advance\" you must create a proper invoice with "
"the payment in advance itself as a product line setting the proper SAT code "
"following the procedure on the official documentation `given by the SAT`_ in"
" the section **Apéndice 2 Procedimiento para la emisión de los CFDI en el "
"caso de anticipos recibidos**."
msgstr ""

#: ../../accounting/localizations/mexico.rst:314
msgid ""
"Related to topic 4 it is blocked the possibility to create a Customer "
"Payment without a proper invoice."
msgstr ""

#: ../../accounting/localizations/mexico.rst:320
msgid "The accounting for Mexico in odoo is composed by 3 reports:"
msgstr ""

#: ../../accounting/localizations/mexico.rst:322
msgid "Chart of Account (Called and shown as COA)."
msgstr ""

#: ../../accounting/localizations/mexico.rst:323
msgid "Electronic Trial Balance."
msgstr ""

#: ../../accounting/localizations/mexico.rst:324
msgid "DIOT report."
msgstr ""

#: ../../accounting/localizations/mexico.rst:326
msgid ""
"1. and 2. are considered as the electronic accounting, and the DIOT is a "
"report only available on the context of the accounting."
msgstr ""

#: ../../accounting/localizations/mexico.rst:329
msgid ""
"You can find all those reports in the original report menu on Accounting "
"app."
msgstr ""

#: ../../accounting/localizations/mexico.rst:336
msgid "Electronic Accounting (Requires Accounting App)"
msgstr ""

#: ../../accounting/localizations/mexico.rst:339
msgid "Electronic Chart of account CoA"
msgstr ""

#: ../../accounting/localizations/mexico.rst:341
msgid ""
"The electronic accounting never has been easier, just go to "
":menuselection:`Accounting --> Reporting --> Mexico --> COA` and click on "
"the button **Export for SAT (XML)**"
msgstr ""

#: ../../accounting/localizations/mexico.rst:349
msgid "How to add new accounts ?"
msgstr ""

#: ../../accounting/localizations/mexico.rst:351
msgid ""
"If you add an account with the coding convention NNN.YY.ZZ where NNN.YY is a"
" SAT coding group then your account will be automatically configured."
msgstr ""

#: ../../accounting/localizations/mexico.rst:354
msgid ""
"Example to add an Account for a new Bank account go to "
":menuselection:`Accounting --> Settings --> Chart of Account` and then "
"create a new account on the button \"Create\" and try to create an account "
"with the number 102.01.99 once you change to set the name you will see a tag"
" automatically set, the tags set are the one picked to be used in the COA on"
" xml."
msgstr ""

#: ../../accounting/localizations/mexico.rst:365
msgid "What is the meaning of the tag ?"
msgstr ""

#: ../../accounting/localizations/mexico.rst:367
msgid ""
"To know all possible tags you can read the `Anexo 24`_ in the SAT website on"
" the section called **Código agrupador de cuentas del SAT**."
msgstr ""

#: ../../accounting/localizations/mexico.rst:371
msgid ""
"When you install the module l10n_mx and yous Chart of Account rely on it "
"(this happen automatically when you install setting Mexico as country on "
"your database) then you will have the more common tags if the tag you need "
"is not created you can create one on the fly."
msgstr ""

#: ../../accounting/localizations/mexico.rst:378
msgid "Electronic Trial Balance"
msgstr ""

#: ../../accounting/localizations/mexico.rst:380
msgid ""
"Exactly as the COA but with Initial balance debit and credit, once you have "
"your coa properly set you can go to :menuselection:`Accounting --> Reports "
"--> Mexico --> Trial Balance` this is automatically generated, and can be "
"exported to XML using the button in the top  **Export for SAT (XML)** with "
"the previous selection of the period you want to export."
msgstr ""

#: ../../accounting/localizations/mexico.rst:389
msgid ""
"All the normal auditory and analysis features are available here also as any"
" regular Odoo Report."
msgstr ""

#: ../../accounting/localizations/mexico.rst:394
msgid "DIOT Report (Requires Accounting App)"
msgstr ""

#: ../../accounting/localizations/mexico.rst:397
msgid "What is the DIOT and the importance of presenting it SAT"
msgstr ""

#: ../../accounting/localizations/mexico.rst:399
msgid ""
"When it comes to procedures with the SAT Administration Service we know that"
" we should not neglect what we present. So that things should not happen in "
"Odoo."
msgstr ""

#: ../../accounting/localizations/mexico.rst:402
msgid ""
"The DIOT is the Informational Statement of Operations with Third Parties "
"(DIOT), which is an an additional obligation with the VAT, where we must "
"give the status of our operations to third parties, or what is considered "
"the same, with our providers."
msgstr ""

#: ../../accounting/localizations/mexico.rst:407
msgid ""
"This applies both to individuals and to the moral as well, so if we have VAT"
" for submitting to the SAT and also dealing with suppliers it is necessary "
"to. submit the DIOT:"
msgstr ""

#: ../../accounting/localizations/mexico.rst:412
msgid "When to file the DIOT and in what format ?"
msgstr ""

#: ../../accounting/localizations/mexico.rst:414
msgid ""
"It is simple to present the DIOT, since like all format this you can obtain "
"it in the page of the SAT, it is the electronic format A-29 that you can "
"find in the SAT website."
msgstr ""

#: ../../accounting/localizations/mexico.rst:418
msgid ""
"Every month if you have operations with third parties it is necessary to "
"present the DIOT, just as we do with VAT, so that if in January we have "
"deals with suppliers, by February we must present the information pertinent "
"to said data."
msgstr ""

#: ../../accounting/localizations/mexico.rst:424
msgid "Where the DIOT is presented ?"
msgstr ""

#: ../../accounting/localizations/mexico.rst:426
msgid ""
"You can present DIOT in different ways, it is up to you which one you will "
"choose and which will be more comfortable for you than you will present "
"every month or every time you have dealings with suppliers."
msgstr ""

#: ../../accounting/localizations/mexico.rst:430
msgid ""
"The A-29 format is electronic so you can present it on the SAT page, but "
"this after having made up to 500 records."
msgstr ""

#: ../../accounting/localizations/mexico.rst:433
msgid ""
"Once these 500 records are entered in the SAT, you must present them to the "
"Local Taxpayer Services Administration (ALSC) with correspondence to your "
"tax address, these records can be presented in a digital storage medium such"
" as a CD or USB, which once validated you will be returned, so do not doubt "
"that you will still have these records and of course, your CD or USB."
msgstr ""

#: ../../accounting/localizations/mexico.rst:440
msgid "One more fact to know: the Batch load ?"
msgstr ""

#: ../../accounting/localizations/mexico.rst:442
msgid ""
"When reviewing the official SAT documents on DIOT, you will find the Batch "
"load, and of course the first thing we think is what is that ?, and "
"according to the SAT site is:"
msgstr ""

#: ../../accounting/localizations/mexico.rst:446
msgid ""
"The \"batch upload\" is the conversion of records databases of transactions "
"with suppliers made by taxpayers in text files (.txt). These files have the "
"necessary structure for their application and importation into the system of"
" the Informative Declaration of Operations with third parties, avoiding the "
"direct capture and consequently, optimizing the time invested in its "
"integration for the presentation in time and form to the SAT."
msgstr ""

#: ../../accounting/localizations/mexico.rst:453
msgid ""
"You can use it to present the DIOT, since it is allowed, which will make "
"this operation easier for you, so that it does not exist to avoid being in "
"line with the SAT in regard to the Information Statement of Operations with "
"Third Parties."
msgstr ""

#: ../../accounting/localizations/mexico.rst:458
msgid "You can find the `official information here`_."
msgstr ""

#: ../../accounting/localizations/mexico.rst:461
msgid "How Generate this report in Odoo ?"
msgstr ""

#: ../../accounting/localizations/mexico.rst:463
msgid ""
"Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions "
"with third partied (DIOT)`."
msgstr ""

#: ../../accounting/localizations/mexico.rst:467
msgid ""
"A report view is shown, select last month to report the immediate before "
"month you are or left the current month if it suits to you."
msgstr ""

#: ../../accounting/localizations/mexico.rst:472
msgid "Click on \"Export (TXT)."
msgstr ""

#: ../../accounting/localizations/mexico.rst:476
msgid ""
"Save in a secure place the downloaded file and go to SAT website and follow "
"the necessary steps to declare it."
msgstr ""

#: ../../accounting/localizations/mexico.rst:481
msgid ""
"Important considerations on your Supplier and Invoice data for the DIOT"
msgstr ""

#: ../../accounting/localizations/mexico.rst:483
msgid ""
"All suppliers must have set the fields on the accounting tab called \"DIOT "
"Information\", the *L10N Mx Nationality* field is filled with just select "
"the proper country in the address, you do not need to do anything else "
"there, but the *L10N Mx Type Of Operation* must be filled by you in all your"
" suppliers."
msgstr ""

#: ../../accounting/localizations/mexico.rst:490
msgid ""
"There are 3 options of VAT for this report, 16%, 0% and exempt, an invoice "
"line in odoo is considered exempt if no tax on it, the other 2 taxes are "
"properly configured already."
msgstr ""

#: ../../accounting/localizations/mexico.rst:493
msgid ""
"Remember to pay an invoice which represent a payment in advance you must ask"
" for the invoice first and then pay it and reconcile properly the payment "
"following standard odoo procedure."
msgstr ""

#: ../../accounting/localizations/mexico.rst:496
msgid ""
"You do not need all you data on partners filled to try to generate the "
"supplier invoice, you can fix this information when you generate the report "
"itself."
msgstr ""

#: ../../accounting/localizations/mexico.rst:499
msgid ""
"Remember this report only shows the Supplier Invoices that were actually "
"paid."
msgstr ""

#: ../../accounting/localizations/mexico.rst:501
msgid ""
"If some of this considerations are not taken into account a message like "
"this will appear when generate the DIOT on TXT with all the partners you "
"need to check on this particular report, this is the reason we recommend use"
" this report not just to export your legal obligation but to generate it "
"before the end of the month and use it as your auditory process to see all "
"your partners are correctly set."
msgstr ""

#: ../../accounting/localizations/mexico.rst:513
msgid "Extra Recommended features"
msgstr ""

#: ../../accounting/localizations/mexico.rst:516
msgid "Contact Module (Free)"
msgstr ""

#: ../../accounting/localizations/mexico.rst:518
msgid ""
"If you want to administer properly your customers, suppliers and addresses "
"this module even if it is not a technical need, it is highly recommended to "
"install."
msgstr ""

#: ../../accounting/localizations/mexico.rst:524
msgid "Multi currency (Requires Accounting App)"
msgstr ""

#: ../../accounting/localizations/mexico.rst:526
msgid ""
"In Mexico almost all companies send and receive payments in different "
"currencies if you want to manage such capability you should enable the multi"
" currency feature and you should enable the synchronization with "
"**Banxico**, such feature allow you retrieve the proper exchange rate "
"automatically retrieved from SAT and not being worried of put such "
"information daily in the system manually."
msgstr ""

#: ../../accounting/localizations/mexico.rst:533
msgid "Go to settings and enable the multi currency feature."
msgstr ""

#: ../../accounting/localizations/mexico.rst:540
msgid ""
"Enabling Explicit errors on the CFDI using the XSD local validator (CFDI "
"3.3)"
msgstr ""

#: ../../accounting/localizations/mexico.rst:542
msgid ""
"Frequently you want receive explicit errors from the fields incorrectly set "
"on the xml, those errors are better informed to the user if the check is "
"enable, to enable the Check with xsd feature follow the next steps (with the"
" :doc:`Developer mode <../../general/developer_mode/activate>` enabled)."
msgstr ""

#: ../../accounting/localizations/mexico.rst:547
msgid ""
"Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`"
msgstr ""

#: ../../accounting/localizations/mexico.rst:548
msgid "Look for the Action called \"Download XSD files to CFDI\""
msgstr ""

#: ../../accounting/localizations/mexico.rst:549
msgid "Click on button \"Create Contextual Action\""
msgstr ""

#: ../../accounting/localizations/mexico.rst:550
msgid ""
"Go to the company form :menuselection:`Settings --> Users&Companies --> "
"Companies`"
msgstr ""

#: ../../accounting/localizations/mexico.rst:551
msgid "Open any company you have."
msgstr ""

#: ../../accounting/localizations/mexico.rst:552
#: ../../accounting/localizations/mexico.rst:575
msgid "Click on \"Action\" and then on \"Download XSD file to CFDI\"."
msgstr ""

#: ../../accounting/localizations/mexico.rst:557
msgid ""
"Now you can make an invoice with any error (for example a product without "
"code which is pretty common) and an explicit error will be shown instead a "
"generic one with no explanation."
msgstr ""

#: ../../accounting/localizations/mexico.rst:562
msgid "If you see an error like this:"
msgstr ""

#: ../../accounting/localizations/mexico.rst:564
msgid "The cfdi generated is not valid"
msgstr ""

#: ../../accounting/localizations/mexico.rst:566
msgid ""
"attribute decl. 'TipoRelacion', attribute 'type': The QName value "
"'{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_TipoRelacion' does "
"not resolve to a(n) simple type definition., line 36"
msgstr ""

#: ../../accounting/localizations/mexico.rst:570
msgid ""
"This can be caused by a database backup restored in anothe server, or when "
"the XSD files are not correctly downloaded. Follow the same steps as above "
"but:"
msgstr ""

#: ../../accounting/localizations/mexico.rst:574
msgid "Go to the company in which the error occurs."
msgstr ""

#: ../../accounting/localizations/mexico.rst:581
msgid "**Error messages** (Only applicable on CFDI 3.3):"
msgstr ""

#: ../../accounting/localizations/mexico.rst:583
msgid ""
"9:0:ERROR:SCHEMASV:SCHEMAV_CVC_MINLENGTH_VALID: Element "
"'{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': "
"[facet 'minLength'] The value '' has a length of '0'; this underruns the "
"allowed minimum length of '1'."
msgstr ""

#: ../../accounting/localizations/mexico.rst:588
msgid ""
"9:0:ERROR:SCHEMASV:SCHEMAV_CVC_PATTERN_VALID: Element "
"'{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': "
"[facet 'pattern'] The value '' is not accepted by the pattern '[^|]{1,100}'."
msgstr ""

#: ../../accounting/localizations/mexico.rst:592
msgid ""
"**Solution**: You forgot to set the proper \"Reference\" field in the "
"product, please go to the product form and set your internal reference "
"properly."
msgstr ""

#: ../../accounting/localizations/mexico.rst:596
#: ../../accounting/localizations/mexico.rst:636
#: ../../accounting/localizations/mexico.rst:667
msgid "**Error messages**:"
msgstr ""

#: ../../accounting/localizations/mexico.rst:598
msgid ""
"6:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element "
"'{http://www.sat.gob.mx/cfd/3}RegimenFiscal': The attribute 'Regimen' is "
"required but missing."
msgstr ""

#: ../../accounting/localizations/mexico.rst:602
msgid ""
"5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element "
"'{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'RegimenFiscal' is "
"required but missing."
msgstr ""

#: ../../accounting/localizations/mexico.rst:605
msgid ""
"**Solution**: You forget to set the proper \"Fiscal Position\" on the "
"partner of the company, go to customers, remove the customer filter and look"
" for the partner called as your company and set the proper fiscal position "
"which is the kind of business you company does related to SAT list of "
"possible values, antoher option can be that you forgot follow the "
"considerations about fiscal positions."
msgstr ""

#: ../../accounting/localizations/mexico.rst:613
msgid ""
"Yo must go to the Fiscal Position configuration and set the proper code (it "
"is the first 3 numbers in the name) for example for the test one you should "
"set 601, it will look like the image."
msgstr ""

#: ../../accounting/localizations/mexico.rst:620
msgid ""
"For testing purposes this value must be set to ``601 - General de Ley "
"Personas Morales`` which is the one required for the demo VAT."
msgstr ""

#: ../../accounting/localizations/mexico.rst:623
#: ../../accounting/localizations/mexico.rst:654
msgid "**Error message**:"
msgstr ""

#: ../../accounting/localizations/mexico.rst:625
msgid ""
"2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element "
"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'FormaPago': [facet "
"'enumeration'] The value '' is not an element of the set {'01', '02', '03', "
"'04', '05', '06', '08', '12', '13', '14', '15', '17', '23', '24', '25', "
"'26', '27', '28', '29', '30', '99'}"
msgstr ""

#: ../../accounting/localizations/mexico.rst:631
msgid "**Solution**: The payment method is required on your invoice."
msgstr ""

#: ../../accounting/localizations/mexico.rst:638
msgid ""
"2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element "
"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': "
"[facet 'enumeration'] The value '' is not an element of the set {'00"
msgstr ""

#: ../../accounting/localizations/mexico.rst:641
#: ../../accounting/localizations/mexico.rst:656
msgid ""
"2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element "
"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' "
"is not a valid value of the atomic type "
"'{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'."
msgstr ""

#: ../../accounting/localizations/mexico.rst:644
msgid ""
"5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element "
"'{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'Rfc' is required but "
"missing."
msgstr ""

#: ../../accounting/localizations/mexico.rst:647
msgid ""
"**Solution**: You must set the address on your company properly, this is a "
"mandatory group of fields, you can go to your company configuration on "
":menuselection:`Settings --> Users & Companies --> Companies` and fill all "
"the required fields for your address following the step :ref:`mx-legal-"
"info`."
msgstr ""

#: ../../accounting/localizations/mexico.rst:661
msgid ""
"**Solution**: The postal code on your company address is not a valid one for"
" Mexico, fix it."
msgstr ""

#: ../../accounting/localizations/mexico.rst:669
msgid ""
"18:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element "
"'{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is "
"required but missing."
msgstr ""

#: ../../accounting/localizations/mexico.rst:672
msgid ""
"34:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element "
"'{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is "
"required but missing.\", '')"
msgstr ""

#: ../../accounting/localizations/mexico.rst:676
msgid ""
"**Solution**: Set the mexican name for the tax 0% and 16% in your system and"
" used on the invoice."
msgstr ""

#: ../../accounting/localizations/netherlands.rst:2
msgid "Netherlands"
msgstr ""

#: ../../accounting/localizations/netherlands.rst:5
msgid "XAF Export"
msgstr ""

#: ../../accounting/localizations/netherlands.rst:7
msgid ""
"With the Dutch accounting localization installed, you will be able to export"
" all your accounting entries in XAF format. For this, you have to go in "
":menuselection:`Accounting --> Reporting --> General Ledger`, you define the"
" entries you want to export using the filters (period, journals, ...) and "
"then you click on the button **EXPORT (XAF)**."
msgstr ""

#: ../../accounting/localizations/netherlands.rst:14
msgid "Dutch Accounting Reports"
msgstr ""

#: ../../accounting/localizations/netherlands.rst:16
msgid ""
"If you install the Dutch accounting localization, you will have access to "
"some reports that are specific to the Netherlands such as :"
msgstr ""

#: ../../accounting/localizations/netherlands.rst:21
msgid "Tax Report (Aangifte omzetbelasting)"
msgstr ""

#: ../../accounting/localizations/netherlands.rst:23
msgid "Intrastat Report (ICP)"
msgstr ""

#: ../../accounting/localizations/spain.rst:3
msgid "Spain"
msgstr ""

#: ../../accounting/localizations/spain.rst:6
msgid "Spanish Chart of Accounts"
msgstr ""

#: ../../accounting/localizations/spain.rst:8
msgid ""
"In Odoo, there are several Spanish Chart of Accounts that are available by "
"default:"
msgstr ""

#: ../../accounting/localizations/spain.rst:10
msgid "PGCE PYMEs 2008"
msgstr ""

#: ../../accounting/localizations/spain.rst:11
msgid "PGCE Completo 2008"
msgstr ""

#: ../../accounting/localizations/spain.rst:12
msgid "PGCE Entitades"
msgstr ""

#: ../../accounting/localizations/spain.rst:14
msgid ""
"You can choose the one you want by going in :menuselection:`Accounting --> "
"Configuration` then choose the package you want in the **Fiscal "
"Localization** section."
msgstr ""

#: ../../accounting/localizations/spain.rst:20
msgid ""
"When you create a new SaaS database, the PGCE PYMEs 2008 is installed by "
"default."
msgstr ""

#: ../../accounting/localizations/spain.rst:23
msgid "Spanish Accounting Reports"
msgstr ""

#: ../../accounting/localizations/spain.rst:25
msgid ""
"If the Spanish Accounting Localization is installed, you will have access to"
" accounting reports specific to Spain:"
msgstr ""

#: ../../accounting/localizations/spain.rst:28
msgid "Tax Report (Modelo 111)"
msgstr ""

#: ../../accounting/localizations/spain.rst:29
msgid "Tax Report (Modelo 115)"
msgstr ""

#: ../../accounting/localizations/spain.rst:30
msgid "Tax Report (Modelo 303)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:3
msgid "Switzerland"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:6
msgid "ISR (In-payment Slip with Reference number)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:8
msgid ""
"The ISRs are payment slips used in Switzerland. You can print them directly "
"from Odoo. On the customer invoices, there is a new button called *Print "
"ISR*."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:16
msgid ""
"The button *Print ISR* only appears there is well a bank account defined on "
"the invoice. You can use CH6309000000250097798 as bank account number and "
"010391391 as CHF ISR reference."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:23
msgid "Then you open a pdf with the ISR."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:28
msgid ""
"There exists two layouts for ISR: one with, and one without the bank "
"coordinates. To choose which one to use, there is an option to print the "
"bank information on the ISR. To activate it, go in "
":menuselection:`Accounting --> Configuration --> Settings --> Accounting "
"Reports` and tick this box :"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:38
msgid "Currency Rate Live Update"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:40
msgid ""
"You can update automatically your currencies rates based on the Federal Tax "
"Administration from Switzerland. For this, go in :menuselection:`Accounting "
"--> Settings`, activate the multi-currencies setting and choose the service "
"you want."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:49
msgid "Updated VAT for January 2018"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:51
msgid ""
"Starting from the 1st January 2018, new reduced VAT rates will be applied in"
" Switzerland. The normal 8.0% rate will switch to 7.7% and the specific rate"
" for the hotel sector will switch from 3.8% to 3.7%."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:56
msgid "How to update your taxes in Odoo Enterprise (SaaS or On Premise)?"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:58
msgid ""
"If you have the V11.1 version, all the work is already been done, you don't "
"have to do anything."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:61
msgid ""
"If you have started on an earlier version, you first have to update the "
"module \"Switzerland - Accounting Reports\". For this, you go in "
":menuselection:`Apps --> remove the filter \"Apps\" --> search for "
"\"Switzerland - Accounting Reports\" --> open the module --> click on "
"\"upgrade\"`."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:68
msgid ""
"Once it has been done, you can work on creating new taxes for the updated "
"rates."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:72
msgid ""
"**Do not suppress or modify the existing taxes** (8.0% and 3.8%). You want "
"to keep them since you may have to use both rates for a short period of "
"time. Instead, remember to archive them once you have encoded all your 2017 "
"transactions."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:77
msgid "The creation of such taxes should be done in the following manner:"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:79
msgid ""
"**Purchase taxes**: copy the origin tax, change its name, label on invoice, "
"rate and tax group (effective from v10 only)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:82
msgid ""
"**Sale taxes**: copy the origin tax, change its name, label on invoice, rate"
" and tax group (effective from v10 only). Since the vat report now shows the"
" details for old and new rates, you should also set the tags accordingly to"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:87
msgid ""
"For 7.7% taxes: Switzerland VAT Form: grid 302 base, Switzerland VAT Form: "
"grid 302 tax"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:90
msgid ""
"For 3.7% taxes: Switzerland VAT Form: grid 342 base, Switzerland VAT Form: "
"grid 342 tax"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:93
msgid ""
"You'll find below, as examples, the correct configuration for all taxes "
"included in Odoo by default"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:97
msgid "**Tax Name**"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:97
msgid "**Rate**"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:97
msgid "**Label on Invoice**"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:97
msgid "**Tax Group (effective from V10)**"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:97
msgid "**Tax Scope**"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:97
msgid "**Tag**"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:99
msgid "TVA 7.7% sur achat B&S (TN)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:99
#: ../../accounting/localizations/switzerland.rst:101
#: ../../accounting/localizations/switzerland.rst:103
#: ../../accounting/localizations/switzerland.rst:105
#: ../../accounting/localizations/switzerland.rst:115
#: ../../accounting/localizations/switzerland.rst:115
#: ../../accounting/localizations/switzerland.rst:117
msgid "7.7%"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:99
msgid "7.7% achat"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:99
#: ../../accounting/localizations/switzerland.rst:101
#: ../../accounting/localizations/switzerland.rst:103
#: ../../accounting/localizations/switzerland.rst:105
#: ../../accounting/localizations/switzerland.rst:115
#: ../../accounting/localizations/switzerland.rst:117
msgid "TVA 7.7%"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:99
#: ../../accounting/localizations/switzerland.rst:101
#: ../../accounting/localizations/switzerland.rst:103
#: ../../accounting/localizations/switzerland.rst:105
#: ../../accounting/localizations/switzerland.rst:107
#: ../../accounting/localizations/switzerland.rst:109
#: ../../accounting/localizations/switzerland.rst:111
#: ../../accounting/localizations/switzerland.rst:113
msgid "Purchases"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:99
#: ../../accounting/localizations/switzerland.rst:101
#: ../../accounting/localizations/switzerland.rst:107
#: ../../accounting/localizations/switzerland.rst:109
msgid "Switzerland VAT Form: grid 400"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:101
msgid "TVA 7.7% sur achat B&S (Incl. TN)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:101
msgid "7.7% achat Incl."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:103
msgid "TVA 7.7% sur invest. et autres ch. (TN)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:103
msgid "7.7% invest."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:103
#: ../../accounting/localizations/switzerland.rst:105
#: ../../accounting/localizations/switzerland.rst:111
#: ../../accounting/localizations/switzerland.rst:113
msgid "Switzerland VAT Form: grid 405"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:105
msgid "TVA 7.7% sur invest. et autres ch. (Incl. TN)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:105
msgid "7.7% invest. Incl."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:107
msgid "TVA 3.7% sur achat B&S (TS)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:107
#: ../../accounting/localizations/switzerland.rst:109
#: ../../accounting/localizations/switzerland.rst:111
#: ../../accounting/localizations/switzerland.rst:113
#: ../../accounting/localizations/switzerland.rst:119
#: ../../accounting/localizations/switzerland.rst:119
#: ../../accounting/localizations/switzerland.rst:121
msgid "3.7%"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:107
msgid "3.7% achat"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:107
#: ../../accounting/localizations/switzerland.rst:109
#: ../../accounting/localizations/switzerland.rst:111
#: ../../accounting/localizations/switzerland.rst:113
#: ../../accounting/localizations/switzerland.rst:119
#: ../../accounting/localizations/switzerland.rst:121
msgid "TVA 3.7%"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:109
msgid "TVA 3.7% sur achat B&S (Incl. TS)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:109
msgid "3.7% achat Incl."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:111
msgid "TVA 3.7% sur invest. et autres ch. (TS)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:111
msgid "3.7% invest"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:113
msgid "TVA 3.7% sur invest. et autres ch. (Incl. TS)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:113
msgid "3.7% invest Incl."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:115
msgid "TVA due a 7.7% (TN)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:115
#: ../../accounting/localizations/switzerland.rst:117
#: ../../accounting/localizations/switzerland.rst:119
#: ../../accounting/localizations/switzerland.rst:121
#: ../../accounting/overview/process_overview/customer_invoice.rst:113
#: ../../accounting/receivables/customer_invoices/overview.rst:16
msgid "Sales"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:115
#: ../../accounting/localizations/switzerland.rst:117
msgid ""
"Switzerland VAT Form: grid 302 base, Switzerland VAT Form: grid 302 tax"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:117
msgid "TVA due à 7.7% (Incl. TN)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:117
msgid "7.7% Incl."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:119
msgid "TVA due à 3.7% (TS)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:119
#: ../../accounting/localizations/switzerland.rst:121
msgid ""
"Switzerland VAT Form: grid 342 base, Switzerland VAT Form: grid 342 tax"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:121
msgid "TVA due a 3.7% (Incl. TS)"
msgstr ""

#: ../../accounting/localizations/switzerland.rst:121
msgid "3.7% Incl."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:124
msgid ""
"If you have questions or remarks, please contact our support using "
"odoo.com/help."
msgstr ""

#: ../../accounting/localizations/switzerland.rst:128
msgid ""
"Don't forget to update your fiscal positions. If you have a version 11.1 (or"
" higher), there is nothing to do. Otherwise, you will also have to update "
"your fiscal positions accordingly."
msgstr ""

#: ../../accounting/others.rst:3
#: ../../accounting/receivables/customer_invoices/overview.rst:109
msgid "Others"
msgstr ""

#: ../../accounting/others/adviser.rst:3
msgid "Adviser"
msgstr ""

#: ../../accounting/others/adviser/budget.rst:3
msgid "How to manage a financial budget?"
msgstr ""

#: ../../accounting/others/adviser/budget.rst:8
msgid ""
"Managing budgets is an essential part of running a business. Budgets help "
"people become more intentional with the way money is spent and direct people"
" to organize and prioritize their work to meet financial goals. They allows "
"you to plan your desired financial outcome and then measure your actual "
"performance against the plan. Odoo manages budgets using both General and "
"Analytic Accounts."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:15
msgid ""
"We will use the following example to illustrate. We just started a project "
"with Smith&Co and we would like to budget the incomes and expenses of that "
"project. We plan to have a revenue of 1000 and we don't want to spend more "
"than 700."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:23
msgid ""
"First we need to install the relevant apps to use budgeting. The main module"
" is the accounting app. Go in the app module and install the **Accounting "
"and Finance** app."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:30
msgid ""
"Further configuration is as well necessary. Go to :menuselection:`Accounting"
" module --> Configuration --> Settings` and enable the **Budget management**"
" feature"
msgstr ""

#: ../../accounting/others/adviser/budget.rst:38
msgid "Budgetary Positions"
msgstr ""

#: ../../accounting/others/adviser/budget.rst:40
msgid ""
"Budgetary positions are lists of accounts for which you want to keep budgets"
" (typically expense or income accounts). They need to be defined so Odoo can"
" know it which accounts he needs to go get the budget information."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:45
msgid ""
"The budgetary positions act as a type of restriction on what can be recorded"
" in the 'practical amount' column in a budget."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:48
msgid ""
"Each budgetary position can have any number of accounts from the general "
"ledger (the main chart of accounts) assigned to it, though it must have at "
"least one."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:51
msgid ""
"If you record a transaction that has an analytic account assigned to it that"
" *is* included in a budget line but one of the general ledger accounts *is "
"not* included in the budgetary position for that same budget line, it will "
"not appear within the 'practical amount' column of that budget line."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:56
msgid ""
"Some budgetary positions might be already installed with your chart of "
"accounts."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:59
msgid ""
"To define the positions enter the :menuselection:`Accounting module --> "
"Configuration --> Budgetary Positions`."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:62
msgid ""
"For our example we need to define what accounts relates to our project's "
"expenses. Create a position and add items to select the accounts."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:68
msgid ""
"In this case we select the three relevant accounts used wherein we will book"
" our expenses."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:74
msgid "Click on *Select*."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:79
msgid "Save the changes to confirm your Budgetary position."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:81
msgid ""
"Repeat this steps to create a revenue budgetary position. Only in this case "
"select the relevant income accounts."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:85
msgid "Analytical account"
msgstr ""

#: ../../accounting/others/adviser/budget.rst:87
msgid ""
"Odoo needs to know which costs or expenses are relevant to a specified "
"budget. To do so we need to link our invoices and expenses to a defined "
"analytical account. Create an analytical account by entering the Accounting "
"module and clicking :menuselection:`Advisers --> Analytic Accounts --> Open "
"Charts`. Create a new Account called Smith&Co project and select the related"
" partner."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:98
msgid "Set a budget"
msgstr ""

#: ../../accounting/others/adviser/budget.rst:100
msgid ""
"Let's now set our targets for our budget. We specified that we expect to "
"gain 1000 with this project and we would like not to spend more than 700."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:104
msgid ""
"To set those targets, enter the accounting app, select "
":menuselection:`Advisers --> Budgets` and create a new Budget."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:107
msgid ""
"We have to give a name to the budget. In this case we'll call it \"Smith "
"Project\". Select the period wherein the budget will be applicable. Next add"
" an item to specify your targets in the Budget Line."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:114
msgid ""
"Select the Budgetary Position related to the Budget Line. In other words, "
"select the position that points to the accounts you want to budget. In this "
"case we will start with our 700 maximum charge target. Select the \"Cost\" "
"Budgetary Position and specify the Planned Amount. As we are recording a "
"cost, we need to specify a **negative amount**. Finally, select the "
"corresponding analytic account."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:124
msgid ""
"Click on **Save & new** to input the revenue budget. The Budgetary Position "
"is Revenue and the Planned Amount is 1000. Save and close"
msgstr ""

#: ../../accounting/others/adviser/budget.rst:127
msgid "You'll need to **Confirm** and **Approve** the budget."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:130
msgid "Check your budget"
msgstr ""

#: ../../accounting/others/adviser/budget.rst:132
msgid ""
"You can check your budget at any time. To see the evolution, let's book some"
" Invoices and Vendors Bills."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:136
msgid ""
"If you use analytical accounts remember that you need to specify the account"
" in the invoice and/or purchase line."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:140
msgid ""
"For more information about booking invoices and purchase orders see "
":doc:`../../receivables/customer_invoices/overview`"
msgstr ""

#: ../../accounting/others/adviser/budget.rst:143
msgid "Go back in the budget list and find the Smith Project."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:145
msgid ""
"Via the analytical account, Odoo can account the invoice lines and purchase "
"lines booked in the accounts and will display them in the **Practical "
"Amount** column."
msgstr ""

#: ../../accounting/others/adviser/budget.rst:153
msgid ""
"The theoretical amount represents the amount of money you theoretically "
"could have spend / should have received in function of the date. When your "
"budget is 1200 for 12 months (january to december), and today is 31 of "
"january, the theoretical amount will be 1000, since this is the actual "
"amount that could have been realised."
msgstr ""

#: ../../accounting/others/adviser/reverse_entry.rst:3
msgid "Reverse an accounting entry automatically"
msgstr ""

#: ../../accounting/others/adviser/reverse_entry.rst:5
msgid ""
"You may want to automatically reverse an accounting entry at a specific "
"date."
msgstr ""

#: ../../accounting/others/adviser/reverse_entry.rst:8
msgid ""
"This is, for example, used when you make a provision (e.g. provision for bad"
" debt). When making the accounting entry for the provision, the amount you "
"entered is only an estimated amount. You will only be sure of the amount at "
"the end of the fiscal year. That's why, at that point, you want the "
"accounting entry to be reversed to be able to enter the real loss that "
"occurred."
msgstr ""

#: ../../accounting/others/adviser/reverse_entry.rst:15
msgid ""
"For this, you just have to tick the box \"Reverse Automatically\" on the "
"journal entry and to define a reversal date. The accounting entry will be "
"reversed at that date."
msgstr ""

#: ../../accounting/others/analytic.rst:3
msgid "Analytic"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:3
msgid "How to track costs of purchases, expenses, subcontracting?"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:8
msgid ""
"Thanks to analytical accounting we can track costs of purchases, expenses "
"and subcontracting in the accounting module."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:11
msgid ""
"We'll take the following example. We sold a consulting package for a "
"customer. The package is all inclusive meaning no extra cost can be added. "
"We would however like to follow which cost were attached to this transaction"
" as we need to pay for purchases, expenses, and subcontracting costs related"
" to the project."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:20
msgid ""
"The following modules needs to be installed to track cost. Enter the app "
"module and install the following apps:"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:28
msgid ""
"Please note that the applications provided by these apps only allows us to "
"**track** the costs. We won't be able to automatically re invoice those "
"costs to our customers. To track and **re invoice costs** you should install"
" the Sales management app as well."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:37
msgid "Enable Analytical accounting"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:39
msgid ""
"Next step is to activate the analytical accounting. In the accounting app, "
"select :menuselection:`Configuration --> Settings` and thick the Analytic "
"accounting box."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:46
msgid ""
"Moreover, scroll down and tick the **Analytic accounting for purchases** "
"box."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:52
msgid "Don't forget to save your changes."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:55
msgid "Create an Analytical account."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:57
msgid ""
"First of all you should create an Analytical account on which you can point "
"all your expenses. Enter the accounting app, select "
":menuselection:`Configuration --> Analytic Accounts`. Create a new one. In "
"this case we will call it \"consulting pack\" for our customer Smith&Co."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:65
msgid "We will point all our costs to this account to keep track of them."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:68
msgid "Record an expense"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:70
msgid ""
"We start by booking an expense. Our IT technician had to take a train to go "
"see our customer. He paid for his ticket himself."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:75
msgid "Create an expense product"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:77
msgid ""
"We first need to create an expense product. Enter the **Expense** module, "
"Click on :menuselection:`Configuration --> Expense Products`. Create a new "
"product called Train ticket and set the cost price to 15.50 euros. Make sure"
" the **Can be expensed** box is ticked."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:86
msgid "Book the expense"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:88
msgid ""
"Enter the Expense module, click on :menuselection:`My expenses --> Create`. "
"Select the Train ticket product and link it to the analytical account "
"discussed above."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:95
msgid ""
"Submit to manager and wait for the manager to approve and post the journal "
"entries."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:99
msgid "Create a Purchase Order linked to the analytical account"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:102
msgid "Purchase Product"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:104
msgid ""
"We also need to buy a software for our customers. In the purchase app create"
" a purchase order for the software product. Within the line we can link the "
"product's cost with the analytical account. Specify the order line and "
"select the correct analytical account. Confirm the sale."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:113
msgid ""
"Accept the delivery and enter the invoice. Once the invoice is entered the "
"cost price (**Vendor Price** field) will be booked in the analytical "
"account."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:117
msgid "Subcontracting"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:119
msgid ""
"The purchase module can be used in the same way as seen previously to handle"
" subcontracting. if we purchase a service from another company we can re "
"invoice this cost by linking the purchase order line to the correct "
"analytical account. We simply need to create the correct vendors product."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:126
msgid "You can also track cost with timesheets, see: :doc:`timesheets`"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:129
msgid "Track costs in accounting"
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:131
msgid ""
"Now that everything is booked and points to the analytical account. Simply "
"open it to check the costs related to that account."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:134
msgid ""
"Enter the accounting module, click on :menuselection:`Advisers --> Analytic "
"Accounts --> Open Charts`."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:137
msgid ""
"Select \"consulting pack - Smith\" and click on the cost and revenue button "
"to have an overview of all cost linked to the account."
msgstr ""

#: ../../accounting/others/analytic/purchases_expenses.rst:144
msgid ""
"If you would like to have the revenue as well you should invoice the "
"Consulting Pack in the Invoice menu and link the invoice line to this same "
"analytical account."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:3
msgid "How to track costs of human resources with timesheets?"
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:5
msgid ""
"Human resource of course has a cost. It is interesting to see how much a "
"particular contract costs the company in term of human power in relation to "
"the invoiced amounts."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:9
msgid ""
"We will take the following example: Our two employees **Harry Potter** and "
"**Cedric Digory** both work on a **Consultancy pack** for our customer "
"**Smith&Co**. Harry is paid 18€ p.h. and Cedric's salary is 12€ p.h. We "
"would like to track their timesheet costs within the accounting app, and "
"compare them with the revenue of the consultancy service."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:18
msgid ""
"First, install the three applications necessary to use this functionality, "
"namely **Accounting**, **Sales** and **Timesheet**. Enter the apps module "
"name and install them."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:31
msgid ""
"Next you will need to enable analytical accounting. To do so enter the "
"**Accounting app**. Select :menuselection:`Configuration --> Settings` and "
"tick the **Analytic accounting** option (see picture below)"
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:38
msgid "Apply your changes."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:41
msgid "Create an employee"
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:43
msgid ""
"In order to check the revenue of an employee you need to have one. To create"
" an employee enter the **Employee** app. Select **Employees** and create a "
"new employee, fill in the name and the basic information."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:47
msgid ""
"On the employee sheet enter the **HR settings** tab. Here you are able to "
"specify the **Timesheet Cost** of your employee. In this case Harry has a "
"cost of 18 euros / hours. We will thus fill in 18 in this field."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:55
msgid ""
"If you want the employee to be able to enter timesheets he needs to be "
"related to a User."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:58
msgid ""
"Repeat the operation to create the Cedric Digory employee. Don't forget to "
"specify its related user and **Timesheet Costs**."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:62
msgid "Issue a Sales Order"
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:64
msgid ""
"We created two employees called Harry Potter and Cedric Diggory in the "
"**Employee** app. Both of them will work on a consultancy contract for our "
"customer Smith&Co where they will point their hours on a timesheet."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:68
msgid ""
"We thus need to create a **sales order** with a **service** product invoiced"
" **based on time and material** and tracked by timesheets with **hours** as "
"unit of measures."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:75
msgid ""
"For more information on how to create a sales order based on time and "
"material please see :doc:`../../../sales/invoicing/time_materials`."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:78
msgid ""
"We save a Sales Order with the service product **External Consulting**. An "
"analytical account will automatically be generated once the **Sales Order** "
"is confirmed. Our employees will have to point to that account (in this case"
" **SO002-Smith&Co**) in order to be able to invoice their hours (see picture"
" below)."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:88
msgid "Fill in timesheet"
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:90
msgid ""
"As an employee linked to a user, Harry can enter the **Timesheet** app and "
"specify his timesheets for the contract. Logged on Harry's account we enter "
"the **Timesheet** app and enter a detailed line pointing to the **Analytical"
" Account** discussed above."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:95
msgid "Harry worked three hours on a SWOT analysis for Smith&Co."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:100
msgid ""
"In the meantime, Cedric discussed businesses needs with the customer for 1 "
"hour and specified it as well in his personal timesheet, pointing as well on"
" the **Analytic Account**."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:104
msgid ""
"In the **Sales Order** we notice that the delivered amounts of hours is "
"automatically computed (see picture below)."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:111
msgid "Analytic accounting"
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:113
msgid ""
"Thanks to analytic accounts we are able to have an overview of HR cost and "
"revenues. All the revenues and cost of this transactions have been "
"registered in the **SO002-Smith&Co** account."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:117
msgid "We can use two methods to analyze this situation."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:120
msgid "Without filters"
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:122
msgid ""
"If we pointed all our costs and revenues of the project on the correct "
"analytical account we can easily retrieve the cost and revenues related to "
"this analytical account. Enter the *Accounting* app, select "
":menuselection:`Adviser --> Analytic Accounts --> Open Charts`."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:127
msgid ""
"Note : you can specify a period for **Analysis**. If you want to open the "
"current situation you should keep the fields empty. We can already note the "
"credit and debit balance of the account."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:134
msgid ""
"If we click on the account a special button is provided to have the details "
"of cost and revenues (see picture below)."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:140
msgid ""
"Click the button **Cost/Revenue** to have an overview of cost and revenues "
"with the corresponding description."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:144
msgid "With filters"
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:146
msgid "We can thus filter this information from the **Analytic Entries**."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:148
msgid ""
"Enter the **Accounting** app, and click on :menuselection:`Adviser --> "
"Analytic Entries`. In this menu we have several options to analyse the human"
" resource cost."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:151
msgid ""
"We filter on the **Analytic account** so we can see the cost and revenues of"
" the project. Add a custom **Filter** where the **Analytic Account** "
"contains the **Sales Order** number."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:158
msgid ""
"In the results we see timesheets activities and invoiced lines with the "
"corresponding costs and revenues."
msgstr ""

#: ../../accounting/others/analytic/timesheets.rst:164
msgid ""
"We can group the different analytical accounts together and check their "
"respective revenues. Simply group by **Analytic account** and select the "
"**Graph view** to have a clear overview."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:3
msgid "Analytic account use cases"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:5
msgid "The analytic accounting can be used for several purposes:"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:7
msgid "analyse costs of a company"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:9
msgid "reinvoice time to a customer"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:11
msgid "analyse performance of a service or a project"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:13
msgid ""
"To manage analytic accounting, you have to activate it in "
":menuselection:`Configuration --> Settings`:"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:19
msgid ""
"To illustrate analytic accounts clearly, you will follow three use cases, "
"each in one of three different types of company:"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:22
msgid "Industrial company: Costs Analyse"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:24
msgid "Law Firm: reinvoice spent hours"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:26
msgid "IT/Services Company: performance analysis"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:29
msgid "Case 1: Industrial company: Costs Analyse"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:31
msgid ""
"In industry, you will often find analytic charts of accounts structured into"
" departments and products the company itself is built on."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:34
msgid ""
"The objective is to examine the costs, sales and margins by "
"department/resources and by product. The first level of the structure "
"comprises the different departments, and the lower levels represent the "
"product ranges the company makes and sells."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:39
msgid ""
"**Analytic Chart of Accounts for an Industrial Manufacturing Company**:"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:41
msgid "Marketing Department"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:43
msgid "Commercial Department"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:45
msgid "Administration Department"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:47
#: ../../accounting/others/analytic/usage.rst:66
#: ../../accounting/others/analytic/usage.rst:70
#: ../../accounting/others/analytic/usage.rst:72
#: ../../accounting/others/analytic/usage.rst:80
msgid "Production Range 1"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:49
#: ../../accounting/others/analytic/usage.rst:68
#: ../../accounting/others/analytic/usage.rst:82
msgid "Production Range 2"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:51
msgid ""
"In daily use, it is useful to mark the analytic account on each purchase "
"invoice. When the invoice is approved, it will automatically generate the "
"entries for both the general and the corresponding analytic accounts. For "
"each entry on the general accounts, there is at least one analytic entry "
"that allocates costs to the department which incurred them."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:58
msgid ""
"Here is a possible breakdown of some general accounting entries for the "
"example above, allocated to various analytic accounts:"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:62
msgid "**General accounts**"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:62
msgid "**Analytic accounts**"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:64
#: ../../accounting/others/analytic/usage.rst:157
msgid "**Title**"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:64
#: ../../accounting/others/analytic/usage.rst:64
#: ../../accounting/others/analytic/usage.rst:157
#: ../../accounting/overview/process_overview/customer_invoice.rst:107
#: ../../accounting/overview/process_overview/customer_invoice.rst:128
msgid "**Account**"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:64
msgid "**Value**"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:66
msgid "Purchase of Raw Material"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:66
#: ../../accounting/others/analytic/usage.rst:68
#: ../../accounting/others/analytic/usage.rst:70
#: ../../accounting/others/analytic/usage.rst:72
#: ../../accounting/others/analytic/usage.rst:84
msgid "2122"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:66
msgid "1500"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:66
msgid "-1 500"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:68
msgid "Subcontractors"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:68
#: ../../accounting/others/analytic/usage.rst:72
#: ../../accounting/others/analytic/usage.rst:84
msgid "450"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:68
#: ../../accounting/others/analytic/usage.rst:72
msgid "-450"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:70
msgid "Credit Note for defective materials"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:70
#: ../../accounting/others/analytic/usage.rst:70
msgid "200"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:72
msgid "Transport charges"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:74
msgid "Staff costs"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:74
msgid "2121"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:74
msgid "10000"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:74
#: ../../accounting/others/analytic/usage.rst:84
msgid "Marketing"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:74
#: ../../accounting/others/analytic/usage.rst:80
#: ../../accounting/others/analytic/usage.rst:82
msgid "-2 000"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:76
msgid "Commercial"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:76
msgid "-3 000"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:78
#: ../../accounting/others/analytic/usage.rst:167
msgid "Administrative"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:78
msgid "-1 000"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:84
msgid "PR"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:84
msgid "-400"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:87
msgid ""
"The analytic representation by department enables you to investigate the "
"costs allocated to each department in the company. The analytic chart of "
"accounts shows the distribution of the company's costs using the example "
"above:"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:94
msgid ""
"In this example of a hierarchical structure in Odoo, you can analyse not "
"only the costs of each product range, but also the costs of the whole "
"production. A report that relates both general accounts and analytic "
"accounts enables you to get a breakdown of costs within a given department."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:103
msgid ""
"The examples above are based on a breakdown of the costs of the company. "
"Analytic allocations can be just as effective for sales. That gives you the "
"profitability (sales - costs) of different departments."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:107
msgid ""
"This analytic representation by department is generally used by trading "
"companies and industries."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:110
msgid ""
"A variantion of this, is not to break it down by sales and marketing "
"departments, but to assign each cost to its corresponding product range. "
"This will give you an analysis of the profitability of each product range."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:115
msgid ""
"Choosing one over the other depends on how you look at your marketing "
"effort. Is it a global cost allocated in some general way, or is each "
"product range responsible for its own marketing costs?"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:120
msgid "Case 2: Law Firm: costs of human resources?"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:122
msgid ""
"Law firms generally adopt management by case, where each case represents a "
"current client file. All of the expenses and products are then attached to a"
" given file/analytic account."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:126
msgid ""
"A principal preoccupation of law firms is the invoicing of hours worked, and"
" the profitability by case and by employee."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:129
msgid ""
"Mechanisms used for encoding the hours worked will be covered in detail in "
"timesheet documentation. Like most system processes, hours worked are "
"integrated into the analytic accounting. In the employee form, specify the "
"cost of the employee. The hourly charge is a function of the employee's "
"cost."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:135
msgid ""
"So a law firm will opt for an analytic representation which reflects the "
"management of the time that employees work on the different customer cases."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:139
msgid ""
"Billing for the different cases is a bit unusual. The cases do not match any"
" entry in the general account nor do they come from purchase or sales "
"invoices. They are represented by the various analytic operations and do not"
" have exact counterparts in the general accounts. They are calculated on the"
" basis of the hourly cost per employee."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:145
msgid ""
"At the end of the month when you pay salaries and benefits, you integrate "
"them into the general accounts but not in the analytic accounts, because "
"they have already been accounted for in billing each account. A report that "
"relates data from the analytic and general accounts then lets you compare "
"the totals, so you can readjust your estimates of hourly cost per employee "
"depending on the time actually worked."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:153
msgid ""
"The following table shows an example of different analytic entries that you "
"can find for your analytic account:"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:157
msgid "**Amount**"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:157
msgid "**General Account**"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:159
msgid "Study the file (1 h)"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:159
#: ../../accounting/others/analytic/usage.rst:161
#: ../../accounting/others/analytic/usage.rst:165
#: ../../accounting/others/analytic/usage.rst:169
msgid "Case 1.1"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:159
msgid "-15"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:161
msgid "Search for information (3 h)"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:161
msgid "-45"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:163
msgid "Consultation (4 h)"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:163
msgid "Case 2.1"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:163
msgid "-60"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:165
msgid "Service charges"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:165
#: ../../accounting/others/analytic/usage.rst:165
msgid "280"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:165
msgid "705 – Billing services"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:167
msgid "Stationery purchase"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:167
msgid "-42"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:167
msgid "601 – Furniture purchase"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:167
msgid "42"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:169
msgid "Fuel Cost -Client trip"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:169
msgid "-35"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:169
msgid "613 – Transports"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:169
msgid "35"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:171
msgid "Staff salaries"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:171
msgid "6201 – Salaries"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:171
msgid "3 000"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:174
msgid ""
"Such a structure allows you to make a detailed study of the profitability of"
" various transactions."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:177
msgid ""
"For more details about profitablity, please read the following document: "
":doc:`timesheets`"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:180
msgid ""
"But analytical accounting is not limited to a simple analysis of the "
"profitability of different customer. The same data can be used for automatic"
" recharging of the services to the customer at the end of the month. To "
"invoice customers, just link the analytic account to a sale order and sell "
"products that manage timesheet or expenses ."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:187
msgid "Case 3: IT Services Company: perfomance analysis"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:189
msgid "Most IT service companies face the following problems:"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:191
msgid "project planning,"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:193
msgid "invoicing, profitability and financial follow-up of projects,"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:195
msgid "managing support contracts."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:197
msgid ""
"To deal with these problems, you would use an analytic chart of accounts "
"structured by project and by sale order."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:200
msgid ""
"The management of services, expenditures and sales is similar to that "
"presented above for lawyers. Invoicing and the study of profitability are "
"also similar."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:204
msgid ""
"But now look at support contracts. These contracts are usually limited to a "
"prepaid number of hours. Each service posted in the analytic accounts shows "
"the remaining hours of support. To manage support contracts, you would "
"create a product configured to invoice on order and link the sale order to "
"an analytic account"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:210
msgid ""
"In Odoo, each analytic line lists the number of units sold or used, as well "
"as what you would usually find there – the amount in currency units (USD or "
"GBP, or whatever other choice you make). So you can sum the quantities sold "
"and used on each sale order to determine whether any hours of the support "
"contract remain."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:217
msgid "Conclusion"
msgstr ""

#: ../../accounting/others/analytic/usage.rst:219
msgid ""
"Analytic accounting helps you to analyse costs and revenues whatever the use"
" case. You can sell or purchase services, track time or analyse the "
"production performance."
msgstr ""

#: ../../accounting/others/analytic/usage.rst:223
msgid ""
"Analytic accounting is flexible and easy to use through all Odoo "
"applications (sales, purchase, timesheet, production, invoice, …)."
msgstr ""

#: ../../accounting/others/inventory.rst:3
msgid "Inventory"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:3
msgid "Impact on the average price valuation when returning goods"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:5
msgid ""
"As stated in the `*inventory valuation page* "
"<https://www.odoo.com/documentation/functional/valuation.html>`__, one of "
"the possible costing method you can use in perpetual stock valuation, is the"
" average cost."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:10
msgid ""
"This document answers to one recurrent question for companies using that "
"method to make their stock valuation: how does a shipping returned to its "
"supplier impact the average cost and the accounting entries? This document "
"is **only** for the specific use case of a perpetual valuation (as opposed "
"to the periodic one) and in average price costing method (as opposed to "
"standard of FIFO)."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:18
msgid "Definition of average cost"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:20
msgid ""
"The average cost method calculates the cost of ending inventory and cost of "
"goods sold on the basis of weighted average cost per unit of inventory."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:24
msgid ""
"The weighted average cost per unit is calculated using the following "
"formula:"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:27
msgid ""
"When new products arrive in a warehouse, the new average cost is recomputed "
"as:"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:33
msgid ""
"When products leave the warehouse: the average cost **does not** change"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:36
msgid "Defining the purchase price"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:38
msgid ""
"The purchase price is estimated at the reception of the products (you might "
"not have received the vendor bill yet) and reevaluated at the reception of "
"the vendor bill. The purchase price includes the cost you pay for the "
"products, but it may also includes additional costs, like landed costs."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:45
msgid "Average cost example"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:48
#: ../../accounting/others/inventory/avg_price_valuation.rst:82
#: ../../accounting/others/inventory/avg_price_valuation.rst:101
#: ../../accounting/others/inventory/avg_price_valuation.rst:117
#: ../../accounting/others/inventory/avg_price_valuation.rst:144
msgid "Operation"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:48
#: ../../accounting/others/inventory/avg_price_valuation.rst:82
#: ../../accounting/others/inventory/avg_price_valuation.rst:101
#: ../../accounting/others/inventory/avg_price_valuation.rst:117
msgid "Delta Value"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:48
#: ../../accounting/others/inventory/avg_price_valuation.rst:82
#: ../../accounting/others/inventory/avg_price_valuation.rst:101
#: ../../accounting/others/inventory/avg_price_valuation.rst:117
#: ../../accounting/others/inventory/avg_price_valuation.rst:144
msgid "Inventory Value"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:48
#: ../../accounting/others/inventory/avg_price_valuation.rst:82
#: ../../accounting/others/inventory/avg_price_valuation.rst:101
#: ../../accounting/others/inventory/avg_price_valuation.rst:117
#: ../../accounting/others/inventory/avg_price_valuation.rst:144
msgid "Qty On Hand"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:48
#: ../../accounting/others/inventory/avg_price_valuation.rst:82
#: ../../accounting/others/inventory/avg_price_valuation.rst:101
#: ../../accounting/others/inventory/avg_price_valuation.rst:117
#: ../../accounting/others/inventory/avg_price_valuation.rst:144
msgid "Avg Cost"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:50
#: ../../accounting/others/inventory/avg_price_valuation.rst:50
#: ../../accounting/others/inventory/avg_price_valuation.rst:146
#: ../../accounting/others/inventory/avg_price_valuation.rst:146
#: ../../accounting/others/inventory/avg_price_valuation.rst:150
#: ../../accounting/others/inventory/avg_price_valuation.rst:154
#: ../../accounting/others/inventory/avg_price_valuation.rst:156
#: ../../accounting/others/inventory/avg_price_valuation.rst:160
msgid "$0"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:50
#: ../../accounting/others/inventory/avg_price_valuation.rst:146
msgid "0"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:52
#: ../../accounting/others/inventory/avg_price_valuation.rst:148
msgid "Receive 8 Products at $10"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:52
msgid "+8\\*$10"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:52
#: ../../accounting/others/inventory/avg_price_valuation.rst:148
#: ../../accounting/others/inventory/avg_price_valuation.rst:150
msgid "$80"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:52
#: ../../accounting/others/inventory/avg_price_valuation.rst:148
#: ../../accounting/others/inventory/avg_price_valuation.rst:150
msgid "8"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:52
#: ../../accounting/others/inventory/avg_price_valuation.rst:148
#: ../../accounting/others/inventory/avg_price_valuation.rst:150
msgid "$10"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:54
#: ../../accounting/others/inventory/avg_price_valuation.rst:152
msgid "Receive 4 Products at $16"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:54
msgid "+4\\*$16"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:54
#: ../../accounting/others/inventory/avg_price_valuation.rst:152
#: ../../accounting/others/inventory/avg_price_valuation.rst:154
msgid "$144"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:54
#: ../../accounting/others/inventory/avg_price_valuation.rst:152
#: ../../accounting/others/inventory/avg_price_valuation.rst:154
msgid "12"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:54
#: ../../accounting/others/inventory/avg_price_valuation.rst:56
#: ../../accounting/others/inventory/avg_price_valuation.rst:84
#: ../../accounting/others/inventory/avg_price_valuation.rst:86
#: ../../accounting/others/inventory/avg_price_valuation.rst:86
#: ../../accounting/others/inventory/avg_price_valuation.rst:103
#: ../../accounting/others/inventory/avg_price_valuation.rst:105
#: ../../accounting/others/inventory/avg_price_valuation.rst:105
#: ../../accounting/others/inventory/avg_price_valuation.rst:107
#: ../../accounting/others/inventory/avg_price_valuation.rst:119
#: ../../accounting/others/inventory/avg_price_valuation.rst:121
#: ../../accounting/others/inventory/avg_price_valuation.rst:121
#: ../../accounting/others/inventory/avg_price_valuation.rst:123
#: ../../accounting/others/inventory/avg_price_valuation.rst:152
#: ../../accounting/others/inventory/avg_price_valuation.rst:154
#: ../../accounting/others/inventory/avg_price_valuation.rst:156
#: ../../accounting/others/inventory/avg_price_valuation.rst:158
#: ../../accounting/others/inventory/avg_price_valuation.rst:160
#: ../../accounting/others/inventory/avg_price_valuation.rst:160
msgid "$12"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:56
#: ../../accounting/others/inventory/avg_price_valuation.rst:156
msgid "Deliver 10 Products"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:56
msgid "-10\\*$12"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:56
#: ../../accounting/others/inventory/avg_price_valuation.rst:84
#: ../../accounting/others/inventory/avg_price_valuation.rst:103
#: ../../accounting/others/inventory/avg_price_valuation.rst:119
#: ../../accounting/others/inventory/avg_price_valuation.rst:156
msgid "$24"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:56
#: ../../accounting/others/inventory/avg_price_valuation.rst:84
#: ../../accounting/others/inventory/avg_price_valuation.rst:103
#: ../../accounting/others/inventory/avg_price_valuation.rst:119
#: ../../accounting/others/inventory/avg_price_valuation.rst:156
msgid "2"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:60
msgid ""
"At the beginning, the Avg Cost is set to 0 set as there is no product in the"
" inventory. When the first reception is made, the average cost becomes "
"logically the purchase price."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:64
msgid ""
"At the second reception, the average cost is updated because the total "
"inventory value is now ``$80 + 4*$16 = $144``. As we have 12 units on hand, "
"the average price per unit is ``$144 / 12 = $12``."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:68
msgid ""
"By definition, the delivery of 10 products does not change the average cost."
" Indeed, the inventory value is now $24 as we have only 2 units remaining of"
" each ``$24 / 2 = $12``."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:73
msgid "Purchase return use case"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:75
msgid ""
"In case of a product returned to its supplier after reception, the inventory"
" value is reduced using the average cost formulae (not at the initial price "
"of these products!)."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:79
msgid "Which means that the above table will be updated as follow:"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:86
#: ../../accounting/others/inventory/avg_price_valuation.rst:107
#: ../../accounting/others/inventory/avg_price_valuation.rst:123
#: ../../accounting/others/inventory/avg_price_valuation.rst:158
msgid "Return of 1 Product initially bought at $10"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:86
#: ../../accounting/others/inventory/avg_price_valuation.rst:105
#: ../../accounting/others/inventory/avg_price_valuation.rst:121
#: ../../accounting/others/inventory/avg_price_valuation.rst:123
msgid "-1\\*$12"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:86
#: ../../accounting/others/inventory/avg_price_valuation.rst:105
#: ../../accounting/others/inventory/avg_price_valuation.rst:121
#: ../../accounting/others/inventory/avg_price_valuation.rst:158
#: ../../accounting/others/inventory/avg_price_valuation.rst:160
msgid "1"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:90
msgid "Explanation: counter example"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:92
msgid ""
"Remember the definition of **Average Cost**, saying that we do not update "
"the average cost of a product leaving the inventory. If you break this rule,"
" you may lead to inconsistencies in your inventory."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:96
msgid ""
"As an example, here is the scenario when you deliver one piece to the "
"customer and return the other one to your supplier (at the cost you "
"purchased it). Here is the operation:"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:105
#: ../../accounting/others/inventory/avg_price_valuation.rst:121
msgid "Customer Shipping 1 product"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:107
msgid "-1\\*$10"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:107
#: ../../accounting/others/inventory/avg_price_valuation.rst:158
msgid "**$2**"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:107
#: ../../accounting/others/inventory/avg_price_valuation.rst:123
msgid "**0**"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:110
msgid ""
"As you can see in this example, this is not correct: an inventory valuation "
"of $2 for 0 pieces in the warehouse."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:113
msgid ""
"The correct scenario should be to return the goods at the current average "
"cost:"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:123
msgid "**$0**"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:126
msgid ""
"On the other hand, using the average cost to value the return ensure a "
"correct inventory value at all times."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:130
msgid "Further thoughts on anglo saxon mode"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:132
msgid ""
"For people in using the **anglo saxon accounting** principles, there is "
"another concept to take into account: the stock input account of the "
"product, which is intended to hold at any time the value of vendor bills to "
"receive. So the stock input account will increase on reception of incoming "
"shipments and will decrease when receiving the related vendor bills."
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:139
msgid ""
"Back to our example, we see that when the return is valued at the average "
"price, the amount booked in the stock input account is the original purchase"
" price:"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:144
msgid "stock input"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:144
msgid "price diff"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:148
msgid "($80)"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:150
msgid "Receive vendor bill $80"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:152
msgid "($64)"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:154
msgid "Receive vendor bill $64"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:158
msgid "**$10**"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:158
msgid "**$12**"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:160
msgid "Receive vendor refund $10"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:160
msgid "$2"
msgstr ""

#: ../../accounting/others/inventory/avg_price_valuation.rst:163
msgid ""
"This is because the vendor refund will be made using the original purchase "
"price, so to zero out the effect of the return in the stock input in last "
"operation, we need to reuse the original price. The price difference account"
" located on the product category is used to book the difference between the "
"average cost and the original purchase price."
msgstr ""

#: ../../accounting/others/multicurrencies.rst:3
msgid "Multicurrency"
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:3
msgid "Record exchange rates at payments"
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:8
msgid ""
"Any company doing international trade faces the case where the payments are "
"in a different currency."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:11
msgid ""
"After receiving their payments, you have the option to convert the amount "
"into your company currency. Multi currency payment implies rates "
"fluctuations. The rate differences are automatically recorded by Odoo."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:19
msgid "Enable multi-currencies"
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:21
msgid ""
"In the accounting module, Go to :menuselection:`Configuration --> Settings` "
"and flag **Allow multi currencies**, then click on **apply**."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:27
msgid ""
"Configure the currency rates in :menuselection:`Configuration --> "
"Currencies`. Write down the rate and make sure the currency is active."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:33
msgid ""
"In this document, the base currency is **Euro** and we will record payments "
"in **Dollars**."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:40
msgid ""
"You can automatically fetch the currency rates from the **European Central "
"Bank** or from **Yahoo**. Please read the document : :doc:`how_it_works`."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:45
#: ../../accounting/others/multicurrencies/invoices_payments.rst:31
msgid "Configure your journal"
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:47
msgid ""
"In order to register payments in other currencies, you have to **remove the "
"currency constraint** on the journal. Go to the accounting application, "
"Click on **More** on the journal and **Settings**."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:54
msgid ""
"Check if the **Currency** field is empty or in the foreign currency in which"
" you will register the payments. If a currency is filled in, it means that "
"you can register payments only in this currency."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:62
msgid "Record a payment in a different currency"
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:64
msgid ""
"In the **Accounting** application, go to :menuselection:`Sales --> "
"Payments`. Register the payment and indicate that it was done in the foreign"
" currency. Then click on **confirm**."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:71
#: ../../accounting/others/multicurrencies/invoices_payments.rst:83
msgid "The journal entry has been posted but not allocated."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:73
#: ../../accounting/others/multicurrencies/invoices_payments.rst:85
msgid ""
"Go back to your invoice (:menuselection:`Sales --> Customer Invoices`) and "
"click on **Add** to allocate the payment."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:80
msgid "Record a bank statement in a different currency"
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:82
msgid ""
"Create or import the bank statement of your payment. The **Amount** is in "
"the company currency. There are two complementary fields, the **Amount "
"currency**, which is the amount that was actually paid and the **Currency** "
"in which it was paid."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:89
msgid ""
"When reconciling it, Odoo will directly match the payment with the right "
"**Invoice**. You will get the invoice price in the invoice currency and the "
"amount in your company currency."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:97
msgid "Check the exchange rate differences"
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:99
msgid ""
"Go to :menuselection:`Adviser --> Journal Entries` and look for the "
"**Exchange difference** journal entries. All the exchange rates differences "
"are recorded in it."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:106
msgid ""
"The Exchange difference journal can be changed in your accounting settings."
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:109
#: ../../accounting/payables/pay/multiple.rst:147
#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:68
msgid ":doc:`../../bank/reconciliation/configure`"
msgstr ""

#: ../../accounting/others/multicurrencies/exchange.rst:110
#: ../../accounting/payables/pay/multiple.rst:100
#: ../../accounting/payables/pay/sepa.rst:131
msgid ":doc:`../../bank/reconciliation/use_cases`"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:3
#: ../../accounting/others/multicurrencies/how_it_works.rst:110
msgid "How is Odoo's multi-currency working?"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:8
msgid ""
"Choosing to use the multi-currency option in Odoo will allow you to send "
"sales invoices, quotes and purchase orders or receive bills and payments in "
"currencies other than your own. With multi-currency, you can also set up "
"bank accounts in other currencies and run reports on your foreign currency "
"activities."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:18
msgid "Turn on multi-currency"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:20
msgid ""
"In the accounting module, Go to :menuselection:`Configuration --> Settings` "
"and flag **Allow multi currencies**, then click on **Apply**."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:27
#: ../../accounting/others/multicurrencies/how_it_works.rst:159
#: ../../accounting/others/multicurrencies/invoices_payments.rst:109
msgid "Exchange Rate Journal"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:29
msgid ""
"The **Rate Difference Journal** records the differences between the payment "
"registration and the expected amount. For example, if a payment is paid 1 "
"month after the invoice was issued, the exchange rate has probably changed. "
"The fluctuation implies some loss or profit that are recorded by Odoo."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:35
msgid "You can change it in the settings:"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:41
msgid "View or edit rate being used"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:43
msgid ""
"You can manually configure the currency rates in "
":menuselection:`Configuration --> Currencies`. Open the currencies you want "
"to use in Odoo and edit it. Make sure the currency is active."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:50
msgid "Click on **View Rates** to edit it and to see the history :"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:55
msgid ""
"Click on **Create** to add the rate. Fill in the date and the rate. Click on"
" **Save** when you are done."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:62
msgid "Live Currency Rate"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:64
msgid ""
"By default, the currencies need to be updated manually. But you can "
"synchronize it with `Yahoo <https://finance.yahoo.com/currency-"
"converter/>`__ or the `European Central Bank <http://www.ecb.europa.eu>`__. "
"In :menuselection:`Configuration --> Settings`, go to the **Live Currency "
"Rate** section."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:69
msgid ""
"Choose the interval : Manually, Daily, Weekly or Monthly. You can always "
"force the update by clicking on **Update Now**. Select the provider, and you"
" are set !"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:77
msgid "Only the **active** currencies are updated"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:80
msgid "Configure your charts of account"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:82
msgid ""
"In the accounting application, go to :menuselection:`Adviser --> Charts of "
"Accounts`. On each account, you can set a currency. It will force all moves "
"for this account to have the account currency."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:86
msgid ""
"If you leave it empty, it means that it can handle all currencies that are "
"Active."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:93
msgid "Configure your journals"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:95
msgid ""
"In order to register payments in other currencies, you have to remove the "
"currency constraint on the journal. Go to the accounting application, Click "
"on **More** on the journal and **Settings**."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:102
#: ../../accounting/others/multicurrencies/invoices_payments.rst:40
msgid ""
"Check if the currency field is empty or in the foreign currency in which you"
" will register the payments. If a currency is filled in, it means that you "
"can register payments only in this currency."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:112
#: ../../accounting/others/multicurrencies/invoices_payments.rst:50
msgid ""
"Now that you are working in a multi-currency environment, all accountable "
"items will be linked to a currency, domestic or foreign."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:116
msgid "Sales Orders and Invoices"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:118
#: ../../accounting/others/multicurrencies/invoices_payments.rst:56
msgid ""
"You are now able to set a different currency than the company one on your "
"sale orders and on your invoices. The currency is set for the whole "
"document."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:126
msgid "Purchases orders and Vendor Bills"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:128
#: ../../accounting/others/multicurrencies/invoices_payments.rst:66
msgid ""
"You are now able to set a different currency than the company one on your "
"purchase orders and on your vendor bills. The currency is set for the whole "
"document."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:136
msgid "Payment Registrations"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:138
msgid ""
"In the accounting application, go to :menuselection:`Sales --> Payments`. "
"Register the payment and set the currency."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:147
#: ../../accounting/others/multicurrencies/invoices_payments.rst:94
msgid ""
"When creating or importing bank statements, the amount is in the company "
"currency. But there are now two complementary fields, the amount that was "
"actually paid and the currency in which it was paid."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:154
msgid ""
"When reconciling it, Odoo will directly match the payment with the right "
"Invoice. You will get the invoice price in the invoice currency and the "
"amount in your company currency."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:161
msgid ""
"Go to :menuselection:`Adviser --> Journal Entries` and look for the Exchange"
" difference journal entries. All the exchange rates differences are recorded"
" in it."
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:168
msgid ":doc:`invoices_payments`"
msgstr ""

#: ../../accounting/others/multicurrencies/how_it_works.rst:169
#: ../../accounting/others/multicurrencies/invoices_payments.rst:119
msgid ":doc:`exchange`"
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:3
msgid "How to manage invoices & payment in multiple currencies?"
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:8
msgid ""
"Odoo provides multi-currency support with automatic currency gross or loss "
"entry adjustment. There are a few things Odoo has been to ease the user's "
"life."
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:12
msgid ""
"All the account transactions will be done using the company currency. "
"However you can see two extra fields with the journal entry where secondary "
"currency and amount will visible. You can create multi-currency journals of "
"force a specific currency."
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:17
msgid ""
"When creating an invoice, the currency can be changed very easily; however "
"Odoo takes the company currency as a default assignment. It will convert all"
" the amounts automatically using that currency."
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:25
msgid "Enable Multi-Currency"
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:27
msgid ""
"For information about enabling Multi-Currency, please read the document: "
":doc:`how_it_works`"
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:33
msgid ""
"In order to register payments in other currencies, you have to remove the "
"currency constraint on the journal. Go to the accounting application, on the"
" journal, click on :menuselection:`More --> Settings`."
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:48
msgid "Multi-currency invoices & Vendor Bills"
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:54
msgid "Invoices"
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:74
msgid "Multi-currency Payments"
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:76
msgid ""
"In the accounting application, go to :menuselection:`Sales --> Payments`. "
"Register the payment and indicate that it was done in the foreign currency. "
"Then click on **Confirm**."
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:92
msgid "Multi- Currency Bank Statements"
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:101
msgid ""
"When reconciling it, Odoo will directly match the payment with the right "
"invoice. You will get the invoice price in the invoice currency and the "
"amount in your company currency."
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:111
msgid ""
"Go to :menuselection:`Adviser --> Journal Entries` and look for the "
"**Exchange Difference** journal entries. All the exchange rates differences "
"are recorded in it."
msgstr ""

#: ../../accounting/others/multicurrencies/invoices_payments.rst:118
msgid ":doc:`how_it_works`"
msgstr ""

#: ../../accounting/others/reporting.rst:3
#: ../../accounting/overview/process_overview/supplier_bill.rst:124
msgid "Reporting"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:3
msgid "How to create a customized reports with your own formulas?"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:8
msgid ""
"Odoo 13 comes with a powerful and easy-to-use reporting framework. Creating "
"new reports (such as a tax report or a balance sheet or income statement "
"with specific groupings and layout ) to suit your needs is now easier than "
"ever."
msgstr ""

#: ../../accounting/others/reporting/customize.rst:14
msgid "Activate the developer mode"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:16
msgid ""
"In order to have access to the financial report creation interface, the "
":doc:`Developer mode <../../../general/developer_mode/activate>` needs to be"
" activated."
msgstr ""

#: ../../accounting/others/reporting/customize.rst:20
msgid "Create your financial report"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:22
msgid ""
"First, you need to create your financial report. To do that, go to "
":menuselection:`Accounting --> Configuration --> Financial Reports`"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:28
msgid ""
"Once the name is entered, there are two other parameters that need to be "
"configured:"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:31
msgid "**Show Credit and Debit Columns**"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:33
msgid "**Analysis Period** :"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:35
msgid "Based on date ranges (e.g. Profit and Loss)"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:37
msgid "Based on a single date (e.g. Balance Sheet)"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:39
msgid ""
"Based on date ranges with 'older' and 'total' columns and last 3 months "
"(e.g. Aged Partner Balances)"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:42
msgid "Bases on date ranges and cash basis method (e.g. Cash Flow Statement)"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:46
msgid "Add lines in your custom reports"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:48
msgid ""
"After you've created the report, you need to fill it with lines. They all "
"need a **name**, a **code** (that is used to refer to the line), a "
"**sequence number** and a **level** (Used for the line rendering)."
msgstr ""

#: ../../accounting/others/reporting/customize.rst:55
msgid ""
"In the **formulas** field you can add one or more formulas to assign a value"
" to the balance column (and debit and credit column if applicable – "
"separated by ;)"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:59
msgid "You have several objects available in the formula :"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:61
msgid ""
"``Ndays`` : The number of days in the selected period (for reports with a "
"date range)."
msgstr ""

#: ../../accounting/others/reporting/customize.rst:64
msgid ""
"Another report, referenced by its code. Use ``.balance`` to get its balance "
"value (also available are ``.credit``, ``.debit`` and ``.amount_residual``)"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:68
msgid ""
"A line can also be based on the sum of account move lines on a selected "
"domain. In which case you need to fill the domain field with an Odoo domain "
"on the account move line object. Then an extra object is available in the "
"formulas field, namely ``sum``, the sum of the account move lines in the "
"domain. You can also use the group by field to group the account move lines "
"by one of their columns."
msgstr ""

#: ../../accounting/others/reporting/customize.rst:75
msgid "Other useful fields :"
msgstr ""

#: ../../accounting/others/reporting/customize.rst:77
msgid "**Type** : Type of the result of the formula."
msgstr ""

#: ../../accounting/others/reporting/customize.rst:79
msgid ""
"**Is growth good when positive** : Used when computing the comparison "
"column. Check if growth is good (displayed in green) or not."
msgstr ""

#: ../../accounting/others/reporting/customize.rst:82
msgid ""
"**Special date changer** : If a specific line in a report should not use the"
" same dates as the rest of the report."
msgstr ""

#: ../../accounting/others/reporting/customize.rst:85
msgid ""
"**Show domain** : How the domain of a line is displayed. Can be foldable "
"(``default``, hidden at the start but can be unfolded), ``always`` (always "
"displayed) or ``never`` (never shown)."
msgstr ""

#: ../../accounting/others/reporting/customize.rst:90
msgid ":doc:`main_reports`"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:3
msgid "What are the main reports available?"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:5
msgid ""
"Besides the reports created specifically in each localisation module, a few "
"very useful **generic** and **dynamic reports** are available for all "
"countries :"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:9
msgid "**Balance Sheet**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:10
msgid "**Profit and Loss**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:11
msgid "**Chart of Account**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:12
msgid "**Executive Summary**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:13
msgid "**General Ledger**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:14
msgid "**Aged Payable**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:15
msgid "**Aged Receivable**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:16
msgid "**Cash Flow Statement**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:17
msgid "**Tax Report**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:18
msgid "**Bank Reconciliation**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:20
msgid ""
"You can annotate every reports to print them and report to your adviser. "
"Export to xls to manage extra analysis. Drill down in the reports to see "
"more details (payments, invoices, journal items, etc.)."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:24
msgid ""
"You can also compare values with another period. Choose how many periods you"
" want to compare the chosen time period with. You can choose up to 12 "
"periods back from the date of the report if you don't want to use the "
"default **Previous 1 Period** option."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:32
msgid ""
"The **Balance Sheet** shows a snapshot of the assets, liabilities and equity"
" of your organisation as at a particular date."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:39
msgid "Profit and Loss"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:41
msgid ""
"The **Profit and Loss** report (or **Income Statement**) shows your "
"organisation's net income, by deducting expenses from revenue for the report"
" period."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:49
msgid "Chart of account"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:51
msgid "A listing of all your accounts grouped by class."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:57
msgid "Executive Summary"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:59
msgid ""
"The **Executive Summary** allows for a quick look at all the important "
"figures you need to run your company."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:62
msgid ""
"In very basic terms, this is what each of the items in this section is "
"reporting :"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:77
msgid "**Performance:**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:68
msgid "**Gross profit margin:**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:67
msgid ""
"The contribution each individual sale made by your business less any direct "
"costs needed to make those sales (things like labour, materials, etc)."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:74
msgid "**Net profit margin:**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:71
msgid ""
"The contribution each individual sale made by your business less any direct "
"costs needed to make those sales, as well as any fixed overheads your "
"company has (things like rent, electricity, taxes you need to pay as a "
"result of those sales)."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:77
msgid "**Return on investment (p.a.):**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:77
msgid ""
"The ratio of net profit made, to the amount of assets the company used to "
"make those profits."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:97
msgid "**Position:**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:81
msgid "**Average debtor days:**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:81
msgid ""
"The average number of days it takes your customers to pay you (fully), "
"across all your customer invoices."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:84
msgid "**Average creditor days:**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:84
msgid ""
"The average number of days it takes you to pay your suppliers (fully) across"
" all your bills."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:89
msgid "**Short term cash forecast:**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:87
msgid ""
"How much cash is expected in or out of your organisation in the next month "
"i.e. balance of your **Sales account** for the month less the balance of "
"your **Purchases account** for the month."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:97
msgid "**Current assets to liabilities:**"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:92
msgid ""
"Also referred to as **current ratio**, this is the ratio of current assets "
"(assets that could be turned into cash within a year) to the current "
"liabilities (liabilities which will be due in the next year). This is "
"typically used as as a measure of a company's ability to service its debt."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:103
msgid "General Ledger"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:105
msgid ""
"The **General Ledger Report** shows all transactions from all accounts for a"
" chosen date range. The initial summary report shows the totals for each "
"account and from there you can view a detailed transaction report or any "
"exceptions. This report is useful for checking every transaction that "
"occurred during a certain period of time."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:115
msgid "Aged Payable"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:117
msgid ""
"Run the **Aged Payable Details** report to display information on individual"
" bills, credit notes and overpayments owed by you, and how long these have "
"gone unpaid."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:125
msgid "Aged Receivable"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:127
msgid ""
"The **Aged Receivables** report shows the sales invoices that were awaiting "
"payment during a selected month and several months prior."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:134
msgid "Cash Flow Statement"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:136
msgid ""
"The **Cash Flow Statement** shows how changes in balance sheet accounts and "
"income affect cash and cash equivalents, and breaks the analysis down to "
"operating, investing and financing activities."
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:144
msgid "Tax Report"
msgstr ""

#: ../../accounting/others/reporting/main_reports.rst:146
msgid ""
"This report allows you to see the **net** and **tax amounts** for all the "
"taxes grouped by type (sale/purchase)."
msgstr ""

#: ../../accounting/overview/getting_started.rst:3
msgid "Getting Started"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:3
#: ../../accounting/overview/main_concepts/memento.rst:67
msgid "Chart of Accounts"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:5
msgid ""
"The **Chart of Accounts (COA)** is the list of all the accounts used to "
"record financial transactions in the general ledger of an organization."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:8
msgid ""
"The accounts are usually listed in the order of appearance in the financial "
"reports. Most of the time, they are listed as follows :"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:11
msgid "Balance Sheet accounts"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:13
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:65
msgid "Assets"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:14
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:77
msgid "Liabilities"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:15
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:85
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:85
msgid "Equity"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:19
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:89
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:89
msgid "Income"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:20
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:93
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:93
msgid "Expense"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:22
msgid ""
"When browsing your Chart of Accounts, you can filter the accounts by number,"
" in the left column, and also group them by Account Type."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:30
msgid "Configuration of an Account"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:32
msgid ""
"The country you select at the creation of your database (or additional "
"company on your database) determines which **Fiscal Localization Package** "
"is installed by default. This package includes a standard Chart of Accounts "
"already configured according to the country's regulations. You can use it "
"directly or set it according to your company's needs."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:38
msgid ""
"It is not possible to modify the **Fiscal Localization** of a company once a"
" Journal Entry has been posted."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:41
msgid ""
"To create a new account, go to :menuselection:`Accounting --> Configuration "
"--> Chart of Accounts`, click on *Create*, and fill out the form."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:45
msgid "Code and Name"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:47
msgid ""
"Each account is identified by its **Code** and **Name**, which also "
"indicates the account's purpose."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:50
msgid "Type"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:52
msgid ""
"Configuring correctly the **Account Type** is critical as it serves multiple"
" purposes:"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:54
msgid "Information on the account's purpose and behavior"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:55
msgid "Generate country-specific legal and financial reports"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:56
msgid "Set the rules to close a fiscal year"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:57
msgid "Generate opening entries"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:59
msgid ""
"To configure an account type, open the **Type** field's drop-down selector "
"and select the right type among the following list:"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:63
msgid "Report"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:63
msgid "Category"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:63
msgid "Account Types"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:65
msgid "Receivable"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:67
msgid "Bank and Cash"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:69
msgid "Current Assets"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:71
msgid "Non-current Assets"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:73
msgid "Prepayments"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:75
msgid "Fixed Assets"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:77
msgid "Payable"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:79
msgid "Credit Card"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:81
msgid "Current Liabilities"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:83
msgid "Non-current Liabilities"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:87
msgid "Current Year Earnings"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:91
msgid "Other Income"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:95
msgid "Depreciation"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:97
msgid "Cost of Revenue"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:99
#: ../../accounting/overview/getting_started/chart_of_accounts.rst:99
msgid "Other"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:99
msgid "Off-Balance Sheet"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:103
msgid "Assets, Deferred Expenses, and Deferred Revenues Automation"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:105
msgid ""
"Some Account Types display a new field **to automate** the creation of "
":ref:`Assets <assets-automation>` entries, :ref:`Deferred Expenses "
"<deferred-expenses-automation>` entries, and :ref:`Deferred Revenues "
"<deferred-revenues-automation>` entries."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:109
msgid "You have three choices for the **Automation** field:"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:111
#: ../../accounting/payables/supplier_bills/assets.rst:238
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:177
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:177
msgid "**No:** this is the default value. Nothing happens."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:112
msgid ""
"**Create in draft:** whenever a transaction is posted on the account, a "
"draft entry is created, but not validated. You must first fill out the "
"corresponding form."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:114
msgid ""
"**Create and validate:** you must also select a Model. Whenever a "
"transaction is posted on the account, an entry is created and immediately "
"validated."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:118
msgid "Please refer to the related documentation for more information."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:121
msgid "Default Taxes"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:123
msgid ""
"Select a **default tax** that will be applied when this account is chosen "
"for a product sale or purchase."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:127
msgid "Tags"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:129
msgid ""
"Some accounting reports require **tags** to be set on the relevant accounts."
" By default, you can choose among the tags that are used by the *Cash Flow "
"Statement*."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:133
msgid "Account Groups"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:135
msgid ""
"**Account Groups** are useful to list multiple accounts as *sub-accounts* of"
" a bigger account and thus consolidate reports such as the **Trial "
"Balance**."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:138
msgid ""
"To create a new Account Group, open the account you want to configure as "
"sub-account, click on the *Group* drop-down selector, select *Create and "
"Edit...*, fill out the form, and save. Next, set all the sub-accounts with "
"the right Account Group."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:142
msgid ""
"To display your **Trial Balance** report with your Account Groups, go to "
":menuselection:`Accounting --> Reporting --> Trial Balance`, then open the "
"*Options* menu and select **Hierarchy and Subtotals**."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:151
msgid "Allow Reconciliation"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:153
msgid ""
"Some accounts, such as accounts made to record the transactions of a payment"
" method, can be used for the reconciliation of journal entries."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:156
msgid ""
"For example, an invoice paid with a credit card can be *marked as paid* if "
"reconciled with the payment. Therefore, the account used to record credit "
"card payments needs to be configured as *allowing reconciliation*."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:160
msgid "To do so, check the **Allow Reconciliation** box and save."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:163
msgid "Deprecated"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:165
msgid ""
"It is not possible to delete an account once a transaction has been recorded"
" on it. You can make them unusable by using the **Deprecated** feature."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:168
msgid "To do so, check the **Deprecated** box and save."
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:171
msgid ":doc:`../../payables/supplier_bills/assets`"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:172
msgid ":doc:`../../payables/supplier_bills/deferred_expenses`"
msgstr ""

#: ../../accounting/overview/getting_started/chart_of_accounts.rst:173
msgid ":doc:`../../receivables/customer_invoices/deferred_revenues`"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:3
msgid "How to setup Odoo Accounting?"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:5
msgid ""
"The Odoo Accounting application has an implementation guide that you should "
"follow to configure it. It's a step-by-step wizard with links to the "
"different screens you will need."
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:9
msgid ""
"Once you have `installed the Accounting application "
"<https://www.odoo.com/apps/modules/online/account_accountant/>`__, you "
"should click on the top-right progressbar to get access to the "
"implementation guide."
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:17
msgid "The implementation guide will help you through the following steps:"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:19
msgid "Completing your company settings"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:20
msgid "Entering in your bank accounts"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:21
msgid "Selecting your chart of accounts"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:22
msgid "Confirming your usual tax rates"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:23
msgid "Setting up any foreign currencies"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:24
msgid "Importing your customers"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:25
msgid "Importing your suppliers"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:26
msgid "Importing your products"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:27
msgid "Importing your outstanding transactions"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:28
msgid "Importing your starting balances"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:29
msgid "Define the users for accounting"
msgstr ""

#: ../../accounting/overview/getting_started/setup.rst:34
msgid ""
"Once a step is done, you can click on the \"Mark as Done\" button, in the "
"bottom of the screen. That way, you can track the progress of your overall "
"configuration of Odoo."
msgstr ""

#: ../../accounting/overview/main_concepts.rst:3
msgid "Main Concepts"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:3
msgid "The Accounting behind Odoo"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:5
msgid ""
"This page summarises the way Odoo deals with typical accounts and "
"transactions."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:9
msgid "Double-entry bookkeeping"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:11
msgid ""
"Odoo automatically creates all the behind-the-scenes journal entries for "
"each of your accounting transactions: customer invoices, point of sale "
"order, expenses, inventory moves, etc."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:15
msgid ""
"Odoo uses the rules of double-entry bookkeeping system: all journal entries "
"are automatically balanced (sum of debits = sum of credits)."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:19
msgid ""
"`Understand Odoo's accounting transactions per document "
"<https://odoo.com/documentation/functional/accounting.html>`_"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:23
msgid "Accrual and Cash Basis Methods"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:25
msgid ""
"Odoo supports both accrual and cash basis reporting. This allows you to "
"report income / expense at the time transactions occur (i.e., accrual "
"basis), or when payment is made or received (i.e., cash basis)."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:30
msgid "Multi-companies"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:32
msgid ""
"Odoo allows one to manage several companies within the same database. Each "
"company has its own chart of accounts and rules. You can get consolidation "
"reports following your consolidation rules."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:36
msgid ""
"Users can access several companies but always work in one company at a time."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:40
msgid "Multi-currencies"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:42
msgid ""
"Every transaction is recorded in the default currency of the company. For "
"transactions occurring in another currency, Odoo stores both the value in "
"the currency of the company and the value in the currency of the "
"transaction. Odoo can generate currencies gains and losses after the "
"reconciliation of the journal items."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:48
msgid ""
"Currency rates are updated once a day using a yahoo.com online web-service."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:52
msgid "International Standards"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:54
msgid ""
"Odoo accounting supports more than 50 countries. The Odoo core accounting "
"implements accounting standards that are common to all countries. Specific "
"modules exist per country for the specificities of the country like the "
"chart of accounts, taxes, or bank interfaces."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:60
msgid "In particular, Odoo's core accounting engine supports:"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:62
msgid ""
"Anglo-Saxon Accounting (U.S., U.K.,, and other English-speaking countries "
"including Ireland, Canada, Australia, and New Zealand) where costs of good "
"sold are reported when products are sold/delivered."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:66
msgid "European accounting where expenses are accounted at the supplier bill."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:69
msgid "Odoo also have modules to comply with IFRS rules."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:72
msgid "Accounts Receivable & Payable"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:74
msgid ""
"By default, Odoo uses a single account for all account receivable entries "
"and one for all accounts payable entries. You can create separate accounts "
"per customers/suppliers, but you don't need to."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:79
msgid ""
"As transactions are associated to customers or suppliers, you get reports to"
" perform analysis per customer/supplier such as the customer statement, "
"revenues per customers, aged receivable/payables, ..."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:84
msgid "Wide range of financial reports"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:86
msgid ""
"In Odoo, you can generate financial reports in real time. Odoo's reports "
"range from basic accounting reports to advanced management reports. Odoo's "
"reports include:"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:90
msgid "Performance reports (such as Profit and Loss, Budget Variance)"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:91
msgid ""
"Position reports (such as Balance Sheet, Aged Payables, Aged Receivables)"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:93
msgid "Cash reports (such as Bank Summary)"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:94
msgid "Detail reports (such as Trial Balance and General Ledger)"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:95
msgid "Management reports (such as Budgets, Executive Summary)"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:97
msgid ""
"Odoo's report engine allows you to customize your own report based on your "
"own formulae."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:101
msgid "Import bank feeds automatically"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:103
msgid ""
"Bank reconciliation is a process that matches your bank statement lines, as "
"supplied by the bank, to your accounting transactions in the general ledger."
" Odoo makes bank reconciliation easy by frequently importing bank statement "
"lines from your bank directly into your Odoo account. This means you can "
"have a daily view of your cashflow without having to log into your online "
"banking or wait for your paper bank statements."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:111
msgid ""
"Odoo speeds up bank reconciliation by matching most of your imported bank "
"statement lines to your accounting transactions. Odoo also remembers how "
"you've treated other bank statement lines and provides suggested general "
"ledger transactions."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:117
msgid "Calculate the tax you owe your tax authority"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:119
msgid ""
"Odoo totals all your accounting transactions for your tax period and uses "
"these totals to calculate your tax obligation. You can then check your sales"
" tax by running Odoo's Tax Report."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:124
msgid "Inventory Valuation"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:126
msgid ""
"Odoo support both periodic (manual) and perpetual (automated) inventory "
"valuations. The available methods are standard price, average price, LIFO "
"(for countries allowing it) and FIFO."
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:131
msgid ""
"`View impact of the valuation method on your transactions "
"<https://odoo.com/documentation/functional/valuation.html>`_"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:135
msgid "Easy retained earnings"
msgstr ""

#: ../../accounting/overview/main_concepts/in_odoo.rst:137
msgid ""
"Retained earnings are the portion of income retained by your business. Odoo "
"automatically calculates your current year earnings in real time so no year-"
"end journal or rollover is required.  This is calculated by reporting the "
"profit and loss balance to your balance sheet report automatically."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:5
msgid "Accounting Memento For Entrepreneurs (US GAAP)"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:11
msgid ""
"The **Profit and Loss** (P&L) report shows the performance of the company "
"over a specific period (usually the current year)."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:16
msgid ""
"The **Gross Profit** equals the revenues from sales minus the cost of goods "
"sold."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:21
msgid ""
"**Operating Expenses** (OPEX) include administration, sales and R&D salaries"
" as well as rent and utilities, miscellaneous costs, insurances, … anything "
"beyond the costs of products sold."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:27
msgid ""
"The **Balance Sheet** is a snapshot of the company's finances at a specific "
"date (as opposed to the Profit and Loss which is an analysis over a period)"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:32
msgid ""
"**Assets** represent the company's wealth, things it owns. Fixed assets "
"includes building and offices, current assets include bank accounts and "
"cash. A client owing money is an asset. An employee is not an asset."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:38
msgid ""
"**Liabilities** are obligations from past events that the company will have "
"to pay in the future (utility bills, debts, unpaid suppliers)."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:43
msgid ""
"**Equity** is the amount of the funds contributed by the owners (founders or"
" shareholders) plus previously retained earnings (or losses)."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:48
msgid "Each year, net profits (or losses) are reported to retained earnings."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:54
msgid ""
"What is owned (an asset) has been financed through debts to reimburse "
"(liabilities) or equity (profits, capital)."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:57
msgid ""
"A difference is made between buying an assets (e.g. a building) and expenses"
" (e.g. fuel). Assets have an intrinsic value over time, versus expenses "
"having value in them being consumed for the company to \"work\"."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:64
msgid "Assets = Liabilities + Equity"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:69
msgid ""
"The **chart of accounts** lists all the accounts, whether they are balance "
"sheet accounts or P&L accounts. Every financial transaction (e.g. a payment,"
" an invoice) impacts accounts by moving value from one account (credit) to "
"an other account (debit)."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:76
msgid "Balance = Debit - Credit"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:84
#: ../../accounting/receivables/customer_invoices/credit_notes.rst:83
#: ../../accounting/receivables/customer_invoices/payment_terms.rst:76
msgid "Journal Entries"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:86
msgid ""
"Every financial document of the company (e.g. an invoice, a bank statement, "
"a pay slip, a capital increase contract) is recorded as a journal entry, "
"impacting several accounts."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:90
msgid ""
"For a journal entry to be *balanced*, the sum of all its debits must be "
"equal to the sum of all its credits."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:95
msgid "examples of accounting entries for various transactions. Example:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:97
msgid "Example 1: Customer Invoice:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:99
#: ../../accounting/overview/main_concepts/memento.rst:117
msgid "Explanation:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:101
msgid "You generate a revenue of $1,000"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:102
msgid "You have a tax to pay of $90"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:103
msgid "The customer owes $1,090"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:105
#: ../../accounting/overview/main_concepts/memento.rst:122
msgid "Configuration:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:107
msgid "Income: defined on the product, or the product category"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:108
#: ../../accounting/overview/main_concepts/memento.rst:125
msgid "Account Receivable: defined on the customer"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:109
msgid "Tax: defined on the tax set on the invoice line"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:111
msgid ""
"The fiscal position used on the invoice may have a rule that replaces the "
"Income Account or the tax defined on the product by another one."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:115
msgid "Example 2: Customer Payment:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:119
msgid "Your customer owes $1,090 less"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:120
msgid "Your receive $1,090 on your bank account"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:124
msgid "Bank Account: defined on the related bank journal"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:130
#: ../../accounting/overview/main_concepts/memento.rst:216
#: ../../accounting/overview/main_concepts/memento.rst:226
#: ../../accounting/overview/main_concepts/memento.rst:242
msgid "Reconciliation"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:132
msgid ""
"Reconciliation is the process of linking journal items of a specific "
"account, matching credits and debits."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:135
msgid ""
"Its primary purpose is to link payments to their related invoices in order "
"to mark invoices that are paid and clear the customer statement. This is "
"done by doing a reconciliation on the *Accounts Receivable* account."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:139
msgid ""
"An invoice is marked as paid when its Accounts Receivable journal items are "
"reconciled with the related payment journal items."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:142
msgid "Reconciliation is performed automatically by the system when:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:144
msgid "the payment is registered directly on the invoice"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:145
msgid ""
"the links between the payments and the invoices are detected at the bank "
"matching process"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:0
msgid "Customer Statement Example"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:156
#: ../../accounting/overview/process_overview/customer_invoice.rst:109
#: ../../accounting/overview/process_overview/customer_invoice.rst:132
msgid "Accounts Receivable"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:156
#: ../../accounting/overview/main_concepts/memento.rst:216
#: ../../accounting/overview/main_concepts/memento.rst:226
#: ../../accounting/overview/main_concepts/memento.rst:242
#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96
#: ../../accounting/receivables/customer_payments/check.rst:68
#: ../../accounting/receivables/customer_payments/check.rst:81
#: ../../accounting/receivables/customer_payments/check.rst:131
#: ../../accounting/receivables/customer_payments/credit_cards.rst:77
#: ../../accounting/receivables/customer_payments/credit_cards.rst:91
#: ../../accounting/receivables/customer_payments/credit_cards.rst:140
msgid "Debit"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:156
#: ../../accounting/overview/main_concepts/memento.rst:216
#: ../../accounting/overview/main_concepts/memento.rst:226
#: ../../accounting/overview/main_concepts/memento.rst:242
#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96
#: ../../accounting/receivables/customer_payments/check.rst:68
#: ../../accounting/receivables/customer_payments/check.rst:81
#: ../../accounting/receivables/customer_payments/check.rst:131
#: ../../accounting/receivables/customer_payments/credit_cards.rst:77
#: ../../accounting/receivables/customer_payments/credit_cards.rst:91
#: ../../accounting/receivables/customer_payments/credit_cards.rst:140
msgid "Credit"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:158
msgid "Invoice 1"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:158
#: ../../accounting/overview/main_concepts/memento.rst:218
#: ../../accounting/overview/main_concepts/memento.rst:220
#: ../../accounting/overview/main_concepts/memento.rst:228
#: ../../accounting/overview/main_concepts/memento.rst:230
#: ../../accounting/overview/main_concepts/memento.rst:244
#: ../../accounting/overview/main_concepts/memento.rst:246
#: ../../accounting/overview/process_overview/customer_invoice.rst:113
msgid "100"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:160
msgid "Payment 1.1"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:160
msgid "70"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:162
msgid "Invoice 2"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:162
#: ../../accounting/overview/main_concepts/memento.rst:166
msgid "65"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:164
msgid "Payment 1.2"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:164
msgid "30"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:166
msgid "Payment 2"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:168
msgid "Invoice 3"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:168
#: ../../accounting/overview/main_concepts/memento.rst:172
msgid "50"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:172
msgid "Total To Pay"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:179
msgid ""
"Bank reconciliation is the matching of bank statement lines (provided by "
"your bank) with transactions recorded internally (payments to suppliers or "
"from customers). For each line in a bank statement, it can be:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:184
msgid "matched with a previously recorded payment:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:184
msgid ""
"a payment is registered when a check is received from a customer, then "
"matched when checking the bank statement"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:188
msgid "recorded as a new payment:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:187
msgid ""
"the payment's journal entry is created and :ref:`reconciled "
"<accounting/reconciliation>` with the related invoice when processing the "
"bank statement"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:191
msgid "recorded as another transaction:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:191
msgid "bank transfer, direct charge, etc."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:193
msgid ""
"Odoo should automatically reconcile most transactions, only a few of them "
"should need manual review. When the bank reconciliation process is finished,"
" the balance on the bank account in Odoo should match the bank statement's "
"balance."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:201
msgid "Checks Handling"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:203
msgid "There are two approaches to manage checks and internal wire transfer:"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:205
msgid "Two journal entries and a reconciliation"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:206
msgid "One journal entry and a bank reconciliation"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:210
msgid ""
"The first journal entry is created by registering the payment on the "
"invoice. The second one is created when registering the bank statement."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:216
#: ../../accounting/overview/main_concepts/memento.rst:226
#: ../../accounting/overview/main_concepts/memento.rst:242
#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96
#: ../../accounting/receivables/customer_payments/check.rst:68
#: ../../accounting/receivables/customer_payments/check.rst:81
#: ../../accounting/receivables/customer_payments/check.rst:131
#: ../../accounting/receivables/customer_payments/credit_cards.rst:77
#: ../../accounting/receivables/customer_payments/credit_cards.rst:91
#: ../../accounting/receivables/customer_payments/credit_cards.rst:140
msgid "Account"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:218
#: ../../accounting/overview/main_concepts/memento.rst:244
#: ../../accounting/receivables/customer_invoices/payment_terms.rst:98
#: ../../accounting/receivables/customer_invoices/payment_terms.rst:100
#: ../../accounting/receivables/customer_payments/check.rst:70
#: ../../accounting/receivables/customer_payments/check.rst:133
#: ../../accounting/receivables/customer_payments/credit_cards.rst:79
#: ../../accounting/receivables/customer_payments/credit_cards.rst:142
msgid "Account Receivable"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:218
#: ../../accounting/overview/main_concepts/memento.rst:244
msgid "Invoice ABC"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:220
#: ../../accounting/overview/main_concepts/memento.rst:228
msgid "Undeposited funds"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:220
#: ../../accounting/overview/main_concepts/memento.rst:228
msgid "Check 0123"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:230
#: ../../accounting/overview/main_concepts/memento.rst:246
#: ../../accounting/overview/process_overview/customer_invoice.rst:130
#: ../../accounting/receivables/customer_payments/check.rst:85
#: ../../accounting/receivables/customer_payments/check.rst:135
#: ../../accounting/receivables/customer_payments/credit_cards.rst:95
#: ../../accounting/receivables/customer_payments/credit_cards.rst:144
msgid "Bank"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:235
msgid ""
"A journal entry is created by registering the payment on the invoice. When "
"reconciling the bank statement, the statement line is linked to the existing"
" journal entry."
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:242
msgid "Bank Statement"
msgstr ""

#: ../../accounting/overview/main_concepts/memento.rst:246
msgid "Statement XYZ"
msgstr ""

#: ../../accounting/overview/process_overview.rst:3
msgid "Process overview"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:3
msgid "From Customer Invoice to Payments Collection"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:5
msgid ""
"Odoo supports multiple invoicing and payment workflows, so you can choose "
"and use the ones that match your business needs. Whether you want to accept "
"a single payment for a single invoice, or process a payment spanning "
"multiple invoices and taking discounts for early payments, you can do so "
"efficiently and accurately."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:12
msgid "From Draft Invoice to Profit and Loss"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:14
msgid ""
"If we pick up at the end of a typical 'order to cash' scenario, after the "
"goods have been shipped, you will: issue an invoice; receive payment; "
"deposit that payment at the bank; make sure the Customer Invoice is closed; "
"follow up if Customers are late; and finally present your Income on the "
"Profit and Loss report and show the decrease in Assets on the Balance Sheet "
"report."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:21
msgid ""
"Invoicing in most countries occurs when a contractual obligation is met. If "
"you ship a box to a customer, you have met the terms of the contract and can"
" bill them. If your supplier sends you a shipment, they have met the terms "
"of that contract and can bill you. Therefore, the terms of the contract is "
"fulfilled when the box moves to or from the truck. At this point, Odoo "
"supports the creation of what is called a Draft Invoice by Warehouse staff."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:32
msgid ""
"Draft invoices can be manually generated from other documents such as Sales "
"Orders, Purchase Orders,etc. Although you can create a draft invoice "
"directly if you would like."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:36
msgid ""
"An invoice must be provided to the customer with the necessary information "
"in order for them to pay for the goods and services ordered and delivered. "
"It must also include other information needed to pay the invoice in a timely"
" and precise manner."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:42
msgid "Draft invoices"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:44
msgid ""
"The system generates invoice which are initially set to the Draft state. "
"While these invoices"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:47
msgid ""
"remain unvalidated, they have no accounting impact within the system. There "
"is nothing to stop users from creating their own draft invoices."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:50
msgid "Let's create a customer invoice with following information:"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:52
msgid "Customer: Agrolait"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:53
msgid "Product: iMac"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:54
msgid "Quantity: 1"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:55
msgid "Unit Price: 100"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:56
msgid "Taxes: Tax 15%"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:64
msgid "The document is composed of three parts:"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:66
msgid "the top of the invoice, with customer information,"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:67
msgid "the main body of the invoice, with detailed invoice lines,"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:68
msgid "the bottom of the page, with detail about the taxes, and the totals."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:71
msgid "Open or Pro-forma invoices"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:73
msgid ""
"An invoice will usually include the quantity and the price of goods and/or "
"services, the date, any parties involved, the unique invoice number, and any"
" tax information."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:77
msgid ""
"\"Validate\" the invoice when you are ready to approve it. The invoice then "
"moves from the Draft state to the Open state."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:80
msgid ""
"When you have validated an invoice, Odoo gives it a unique number from a "
"defined, and modifiable, sequence."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:86
msgid ""
"Accounting entries corresponding to this invoice are automatically generated"
" when you validate the invoice. You can see the details by clicking on the "
"entry in the Journal Entry field in the \"Other Info\" tab."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:95
msgid "Send the invoice to customer"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:97
msgid ""
"After validating the customer invoice, you can directly send it to the "
"customer via the 'Send by email' functionality."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:103
msgid ""
"A typical journal entry generated from a validated invoice will look like as"
" follows:"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:107
#: ../../accounting/overview/process_overview/customer_invoice.rst:128
msgid "**Partner**"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:107
#: ../../accounting/overview/process_overview/customer_invoice.rst:128
msgid "**Due date**"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:109
#: ../../accounting/overview/process_overview/customer_invoice.rst:111
#: ../../accounting/overview/process_overview/customer_invoice.rst:130
#: ../../accounting/overview/process_overview/customer_invoice.rst:132
msgid "Agrolait"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:109
msgid "01/07/2015"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:109
#: ../../accounting/overview/process_overview/customer_invoice.rst:130
#: ../../accounting/overview/process_overview/customer_invoice.rst:132
msgid "115"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:111
msgid "15"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:117
msgid "Payment"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:119
msgid ""
"In Odoo, an invoice is considered to be paid when the associated accounting "
"entry has been reconciled with the payment entries. If there has not been a "
"reconciliation, the invoice will remain in the Open state until you have "
"entered the payment."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:124
msgid ""
"A typical journal entry generated from a payment will look like as follows:"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:136
msgid "Receive a partial payment through the bank statement"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:138
msgid ""
"You can manually enter your bank statements in Odoo, or you can import them "
"in from a csv file or from several other predefined formats according to "
"your accounting localisation."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:142
msgid ""
"Create a bank statement from the accounting dashboard with the related "
"journal and enter an amount of $100 ."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:149
msgid "Reconcile"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:151
msgid "Now let's reconcile!"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:156
msgid ""
"You can now go through every transaction and reconcile them or you can mass "
"reconcile with instructions at the bottom."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:158
msgid ""
"After reconciling the items in the sheet, the related invoice will now "
"display \"You have outstanding payments for this customer. You can reconcile"
" them to pay this invoice. \""
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:168
msgid ""
"Apply the payment. Below, you can see that the payment has been added to the"
" invoice."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:175
msgid "Payment Followup"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:177
msgid ""
"There's a growing trend of customers paying bills later and later. "
"Therefore, collectors must make every effort to collect money and collect it"
" faster."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:181
msgid ""
"Odoo will help you define your follow-up strategy. To remind customers to "
"pay their outstanding invoices, you can define different actions depending "
"on how severely overdue the customer is. These actions are bundled into "
"follow-up levels that are triggered when the due date of an invoice has "
"passed a certain number of days. If there are other overdue invoices for the"
" same customer, the actions of the most overdue invoice will be executed."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:189
msgid ""
"By going to the customer record and diving into the \"Overdue Payments\" you"
" will see the follow-up message and all overdue invoices."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:199
msgid "Customer aging report:"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:201
msgid ""
"The customer aging report will be an additional key tool for the collector "
"to understand the customer credit issues, and to prioritize their work."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:205
msgid ""
"Use the aging report to determine which customers are overdue and begin your"
" collection efforts."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:212
msgid "Profit and loss"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:214
msgid ""
"The Profit and Loss statement displays your revenue and expense details. "
"Ultimately, this gives you a clear image of your Net Profit and Loss. It is "
"sometimes referred to as the \"Income Statement\" or \"Statement of Revenues"
" and Expenses.\""
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:223
msgid "Balance sheet"
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:225
msgid ""
"The balance sheet summarizes your company's liabilities, assets and equity "
"at a specific moment in time."
msgstr ""

#: ../../accounting/overview/process_overview/customer_invoice.rst:234
msgid ""
"For example, if you manage your inventory using the perpetual accounting "
"method, you should expect a decrease in account \"Current Assets\" once the "
"material has been shipped to the customer."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:3
#: ../../accounting/overview/process_overview/supplier_bill.rst:15
msgid "From Vendor Bill to Payment"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:5
msgid ""
"Once vendor bills are registered in Odoo, you can easily pay vendors for the"
" correct amount and at the right time (not too late, not too early; "
"depending on your vendor policy). Odoo also offers reports to track your "
"aged payable balances."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:10
msgid ""
"If you want to control vendor bills received from your vendors, you can use "
"the Odoo Purchase application that allows you to control and pre-complete "
"them automatically based on past purchase orders."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:18
msgid "Record a new vendor bill"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:20
msgid ""
"When a vendor bill is received, you can record it from "
":menuselection:`Purchases --> Vendor Bills` in the Accounting application. "
"As a shortcut, you can also use the **New Bill** feature on the accounting "
"dashboard."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:27
msgid ""
"To register a new vendor bill, start by selecting a vendor and inputting "
"their invoice as the **Vendor Reference**, then add and confirm the product "
"lines, making sure to have the right product quantities, taxes and prices."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:35
msgid ""
"Save the invoice to update the pre tax and tax amounts at the bottom of the "
"screen. You will most likely need to configure the prices of your products "
"without taxes as Odoo will compute the tax for you."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:40
msgid ""
"On the bottom left corner, Odoo shows a summary table of all taxes on the "
"vendor bill. In several countries, different methods are accepted to round "
"the totals (round per line, or round globally). The default rounding method "
"in Odoo is to round the final prices per line (as you may have different "
"taxes per product. E.g. Alcohol and cigarettes). However if your vendor has "
"a different tax amount on their bill, you can change the amount in the "
"bottom left table to adjust and match."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:48
msgid "Validate The Vendor Bill"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:50
msgid ""
"Once the vendor bill is validated, a journal entry will be generated based "
"on the configuration on the invoice. This journal entry may differ depending"
" on the the accounting package you choose to use."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:54
msgid ""
"For most European countries, the journal entry will use the following "
"accounts:"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:57
#: ../../accounting/overview/process_overview/supplier_bill.rst:66
msgid "**Accounts Payable:** defined on the vendor form"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:59
#: ../../accounting/overview/process_overview/supplier_bill.rst:68
msgid "**Taxes:** defined on the products and per line"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:61
msgid "**Expenses:** defined on the line item product used"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:63
msgid ""
"For Anglo-Saxon (US) accounting, the journal entry will use the following "
"accounts:"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:70
msgid "**Goods Received:** defined on the product form"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:72
msgid ""
"You can check your Profit & Loss or the Balance Sheet reports after having "
"validated a couple of vendor bills to see the impact on your general ledger."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:77
msgid "Pay a bill"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:79
msgid ""
"To create a payment for an open vendor bill directly, you can click on "
"**Register a Payment** at the top of the form."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:82
msgid ""
"From there, you select the payment method (i.e. Checking account, credit "
"card, check, etc…) and the amount you wish to pay. By default, Odoo will "
"propose the entire remaining balance on the bill for payment. In the memo "
"field, we recommend you set the vendor invoice number as a reference (Odoo "
"will auto fill this field from the from the vendor bill if set it "
"correctly)."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:94
msgid ""
"You can also register a payment to a vendor directly without applying it to "
"a vendor bill. To do that, :menuselection:`Purchases --> Payments`. Then, "
"from the vendor bill you will be able to reconcile this payment with "
"directly."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:99
msgid "Printing vendor Checks"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:101
msgid ""
"If you choose to pay your vendor bills by check, Odoo offers a method to do "
"so directly from your vendor payments within Odoo. Whether you do so on a "
"daily basis or prefer to do so at the end of the week, you can print in "
"checks in batches."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:106
msgid ""
"If you have checks to print, Odoo's accounting dashboard acts as a to do "
"list and reminds you of how many checks you have left to be printed."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:112
msgid ""
"By selecting the amount of checks to be printed, you can dive right into a "
"list of all payments that are ready to be processed."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:115
msgid ""
"Select all the checks you wish to print (use the first checkbox to select "
"them all) and set the action to **Print Checks**. Odoo will ask you to set "
"the next check number in the sequence and will then print all the checks at "
"once."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:127
msgid "Aged payable balance"
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:129
msgid ""
"In order to get a list of open vendor bills and their related due dates, you"
" can use the **Aged Payable** report, under the reporting menu, (in "
":menuselection:`Reporting --> Business Statement --> Aged payable`) to get a"
" visual of all of your outstanding bills."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:137
msgid ""
"From here, you can click directly on a vendors name to open up the details "
"of all outstanding bills and the amounts due, or you can annotate any line "
"for managements information. At any point in time while you're looking "
"through the report, you can print directly to Excel or PDF and get exactly "
"what you see on the screen."
msgstr ""

#: ../../accounting/overview/process_overview/supplier_bill.rst:144
msgid ":doc:`customer_invoice`"
msgstr ""

#: ../../accounting/payables.rst:3
msgid "Account Payables"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:3
msgid "How to keep track of employee expenses?"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:5
msgid ""
"Employee expenses are charges incurred on behalf of the company. The company"
" then reimburses these expenses to the employee. The receipts encountered "
"most frequently are:"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:9
msgid "car travel, reimbursed per unit of distance (mile or kilometer),"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:11
msgid "subsistence expenses, reimbursed based on the bill,"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:13
msgid ""
"other purchases, such as stationery and books, destined for the company but "
"carried out by the employee."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:19
msgid ""
"To manage expenses, you need to install the **Expense Tracker** application "
"from the Apps module."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:22
msgid ""
"You will also need to install the **Sales Management** module in order to "
"re-invoice your expenses to your customers."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:25
msgid ""
"Once these applications are installed you can configure the different "
"products that represent the types of expenses. To create the firsts "
"products, go to the menu :menuselection:`Configuration --> Expenses "
"Products` in the **Expenses** application."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:30
msgid "Some examples of products can be:"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:32
msgid "**Travel (car)**"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:34
#: ../../accounting/payables/misc/employee_expense.rst:50
msgid "Product Type: Service"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:36
#: ../../accounting/payables/misc/employee_expense.rst:52
msgid "Invoicing Policy: Invoice based on time and material"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:38
msgid "Expense Invoice Policy: At sales price"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:40
msgid "Sale Price: 0.32"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:42
msgid ""
"Unit of Measure: Km or mile (you will need to enable the **Multiple Unit of "
"Measures** option from :menuselection:`Sales module --> Configuration`)"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:48
msgid "**Hotel**"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:54
msgid "Expense Invoice Policy: At cost"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:56
msgid "Unit of Measure: Unit"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:58
msgid ""
"In these examples, the first product will be an expense we reimburse to the "
"employee based on the number of km he did with his own car (e.g. to visit a "
"customer): 0.32€ / km. The hotel is reimbursed based on the real cost of the"
" hotel."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:63
msgid ""
"Be sure that all these products have the checkbox **Can be expensed** "
"checked and the invoicing policy set to **Invoice Based on time and "
"material**. This invoicing policy means that, if the expense is related to a"
" customer project/sale order, Odoo will re-invoice this expense to the "
"customer."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:69
msgid "Odoo support two types of expenses:"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:71
msgid "expenses paid by employee with their own money"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:73
msgid "expenses paid with a company credit card"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:76
msgid "The expenses workflow"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:79
msgid "Record a new expense"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:81
msgid ""
"Every employee of the company can register their expenses from "
":menuselection:`Expenses application --> My Expenses`. The workflow for "
"personal expenses work that way:"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:85
msgid "an employee record his expense, and submit it to the manager"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:87
msgid "the manager approve or refuse the expense"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:89
msgid "the accountant post journal entries"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:91
msgid ""
"the company reimburse the employee expense (the employee is like a vendor, "
"with a payable account)"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:94
msgid ""
"if the expense is linked to an analytic account, the company can reinvoice "
"the customer"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:97
msgid "For every expense, the employee should record at least:"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:99
msgid "a description: that should include the reference of the ticket / bill"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:101
msgid "a product: the expense type"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:103
msgid ""
"a price (e.g. hotel) or a quantity (e.g. reimburse km if travel with his own"
" car)"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:106
msgid ""
"Depending of the policy of the company, he might have to attach a scan or a "
"photo of the expense. To do that, just a write a message in the bottom of "
"the expense with the scan of the bill/ticket in attachment."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:113
msgid ""
"If the expense is linked to a customer project, you should not forget to set"
" an analytic account, related to the customer project or sale order (you "
"might have to activate analytic accounts in the accounting settings to get "
"this feature)."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:118
msgid ""
"Once the expense is fully recorded, the employee has to click the button "
"**Submit to Manager**. In some companies, employees should submit their "
"expenses grouped at the end of the month, or at the end of a business trip."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:123
msgid ""
"An employee can submit all his expenses in batch, using the Submit Expenses "
"action from the list view of expenses, or the small icons in the list view."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:128
msgid "Validation by the manager"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:130
msgid ""
"Managers should receive an email for every expense to be approved (the "
"manager of an employee is defined on the employee form). They can use the "
"menu **To Approve** to check all expenses that are waiting for validation."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:135
msgid "The manager can:"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:137
msgid ""
"discuss on an expense to ask for more information (e.g., if a scan of the "
"bill is missing);"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:140
msgid "reject an expense;"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:142
msgid "approve an expense."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:145
msgid "Control by the accountant"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:147
msgid ""
"Then, all expenses that have been validated by the manager should be posted "
"by the accountant. When an expense is posted, the related journal entry is "
"created and posted in your accounting."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:151
msgid ""
"If the accountant wants to create only one journal entry for a batch of "
"expenses, he can post expenses in batch from the list view of all expenses."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:156
msgid "Reinvoice expenses to customers"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:158
msgid ""
"If the expense was linked to an analytic account related to a sale order, "
"the sale order has a new line related to the expense. This line is not "
"invoiced to the customer yet and will be included in the next invoice that "
"will be send to the customer (charge travel and accommodations on a customer"
" project)"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:164
msgid ""
"To invoice the customer, just click on the invoice button on his sale order."
" (or it will be done automatically at the end of the week/month if you "
"invoice all your orders in batch)"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:170
#: ../../accounting/receivables/customer_invoices/overview.rst:95
msgid ":doc:`../../../sales/invoicing/expense`"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:173
msgid "Reimburse the employee"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:175
msgid ""
"If the expense was paid with the employee's own money, the company should "
"reimburse the employee. In such a case, the employee will appear in the aged"
" payable balance until the company reimburse him his expenses."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:180
msgid ""
"All you have to do is to create a payment to this employee for the amount "
"due."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:187
msgid "Expenses that are not reinvoiced to customers"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:189
msgid ""
"If some expenses should not be reinvoiced to customers, you have two "
"options:"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:192
msgid ""
"if the decision to invoice or not is related to the product, change the "
"invoicing policy on the product:"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:195
msgid "**based on time and material**: reinvoice the customer"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:197
msgid "**based on sale orders**: do not reinvoice the customer"
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:199
msgid ""
"if you have to make an exception for one invoice that should not be "
"reinvoiced to the customer, do not set the related analytic account for this"
" invoice."
msgstr ""

#: ../../accounting/payables/misc/employee_expense.rst:204
msgid ":doc:`forecast`"
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:3
msgid "How to forecast future bills to pay?"
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:5
msgid ""
"When you get hundreds of vendor bills per month with each of them having "
"different payment terms, it could be complex to follow what you have to pay "
"and when. Paying your vendors too early can decrease your cash "
"availabilities and paying too late can lead to extra charges."
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:10
msgid ""
"Fortunately, Odoo provides you the right tools to manage payment orders to "
"vendors efficiently."
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:14
msgid "Configuration: payment terms"
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:16
msgid ""
"In order to track the vendor conditions, we use payment terms in Odoo. "
"Payment terms allow to keep track of the conditions to compute the due date "
"on an invoice. As an example, a payment term can be:"
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:20
msgid "50% within 30 days"
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:22
msgid "50% within 45 days"
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:24
msgid ""
"To create your most common payment terms, use the menu: "
":menuselection:`Configuration --> Management --> Payment Terms` in the "
"**Accounting** application. The following example show a payment term of 30%"
" directly and the balance after 30 days."
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:32
msgid ""
"Once payment terms are defined, you can assign them to your vendor by "
"default. Set the Vendor Payment Term field on the Accounting tab of a vendor"
" form. That way, every time you will purchase to this vendor, Odoo will "
"propose you automatically the right payment term."
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:42
msgid ""
"If you do not set a specific payment term on a vendor, you will still be "
"able to set a specific payment term on the vendor bill."
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:46
msgid "Forecast bills to pay with the Aged Payables report"
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:48
msgid ""
"In order to track amounts to be paid to the vendors, use the Aged Payable "
"report. You can get it from the Reports menu of the Accounting application. "
"This report gives you a summary per vendor of the amounts to pay, compared "
"to their due date (the due date being computed on each bill using the "
"payment term)."
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:57
msgid ""
"This reports tells you how much you will have to pay within the next months."
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:61
msgid "Select bills to pay"
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:63
msgid ""
"Using the menu :menuselection:`Purchases --> Vendor Bills`, you can get a "
"list of vendor bills. Using the advanced filters, you can list all the bills"
" that you should pay or the bills that are overdue (you are late on the "
"payment)."
msgstr ""

#: ../../accounting/payables/misc/forecast.rst:70
msgid ""
"From this screen, you can also switch to the pivot table or the graph view "
"to get statistics on the amount due over the next month, using the group by "
"\"Due Date\" feature."
msgstr ""

#: ../../accounting/payables/pay.rst:3
msgid "Vendor Payments"
msgstr ""

#: ../../accounting/payables/pay/check.rst:3
msgid "Pay by Checks"
msgstr ""

#: ../../accounting/payables/pay/check.rst:5
msgid ""
"Once you decide to pay a supplier bill, you can select to pay by check. "
"Then, at the end of the day, the manager can print all checks by batch. "
"Finally, the bank reconciliation process will match the checks you sent to "
"suppliers with actual bank statements."
msgstr ""

#: ../../accounting/payables/pay/check.rst:14
#: ../../accounting/payables/pay/sepa.rst:29
msgid "Install the required module"
msgstr ""

#: ../../accounting/payables/pay/check.rst:16
msgid ""
"To record supplier payments by checks, you must install the **Check "
"Writing** module. This module handle the process of recording checks in "
"Odoo. Others modules are necessary to print checks, according to the "
"country. As an example, the **U.S. Check Printing** module is required to "
"print U.S. checks."
msgstr ""

#: ../../accounting/payables/pay/check.rst:23
msgid ""
"According to your country and the chart of account you use, those modules "
"may be installed by default. (example: United States users have nothing to "
"install, it's configured by default)."
msgstr ""

#: ../../accounting/payables/pay/check.rst:28
msgid "Activate checks payment methods"
msgstr ""

#: ../../accounting/payables/pay/check.rst:30
msgid ""
"In order to allow payments by checks, you must activate the payment method "
"on related bank journals. From the accounting dashboard (the screen you get "
"when you enter the accounting application), click on your bank account on "
":menuselection:`More --> Settings` option. On the **Payment Method** field, "
"set **Check**."
msgstr ""

#: ../../accounting/payables/pay/check.rst:40
msgid "Compatible check stationery for printing checks"
msgstr ""

#: ../../accounting/payables/pay/check.rst:43
msgid "United States"
msgstr ""

#: ../../accounting/payables/pay/check.rst:45
msgid "For the United States, Odoo supports by default the check formats of:"
msgstr ""

#: ../../accounting/payables/pay/check.rst:47
msgid "**Quickbooks & Quicken**: check on top, stubs in the middle and bottom"
msgstr ""

#: ../../accounting/payables/pay/check.rst:48
msgid "**Peachtree**: check in the middle, stubs on top and bottom"
msgstr ""

#: ../../accounting/payables/pay/check.rst:49
msgid "**ADP**: check in the bottom, and stubs on the top."
msgstr ""

#: ../../accounting/payables/pay/check.rst:51
msgid ""
"It is also possible to customize your own check format through "
"customizations."
msgstr ""

#: ../../accounting/payables/pay/check.rst:54
msgid "Pay a supplier bill with a check"
msgstr ""

#: ../../accounting/payables/pay/check.rst:56
msgid "Paying a supplier with a check is done in three steps:"
msgstr ""

#: ../../accounting/payables/pay/check.rst:58
msgid "registering a payment you'd like to do on the bill"
msgstr ""

#: ../../accounting/payables/pay/check.rst:59
msgid "printing checks in batch for all registered payments"
msgstr ""

#: ../../accounting/payables/pay/check.rst:60
msgid "reconcile bank statements"
msgstr ""

#: ../../accounting/payables/pay/check.rst:63
msgid "Register a payment by check"
msgstr ""

#: ../../accounting/payables/pay/check.rst:65
msgid ""
"To register a payment on a bill, open any supplier bill from the menu "
":menuselection:`Purchases --> Vendor Bills`. Once the supplier bill is "
"validated, you can register a payment. Set the **Payment Method** to "
"**Check** and validate the payment dialog."
msgstr ""

#: ../../accounting/payables/pay/check.rst:74
msgid "Print checks"
msgstr ""

#: ../../accounting/payables/pay/check.rst:76
msgid ""
"From the accounting dashboard, on your bank account, you should see a link "
"\"X checks to print\". Click on this link and you will get the list of all "
"checks that are not printed yet. From this screen, you can print all checks "
"in batch or review them one by one."
msgstr ""

#: ../../accounting/payables/pay/check.rst:81
msgid ""
"If you want to review every payment one by one before printing the check, "
"open on the payment and click on **Print Check** if you accept it. A dialog "
"will ask you the number of the check. It automatically proposes you the next"
" number, but you can change it if it does not match your next check number."
msgstr ""

#: ../../accounting/payables/pay/check.rst:87
msgid ""
"To print all checks in batch, select all payments from the list view and "
"Print Check from the top \"print\" menu."
msgstr ""

#: ../../accounting/payables/pay/check.rst:94
msgid "Reconcile bank statements"
msgstr ""

#: ../../accounting/payables/pay/check.rst:96
msgid ""
"Once you process your bank statement, when the check is credited from your "
"bank account, Odoo will propose you automatically to match it with the "
"payment. This will mark the payment as **Reconciled**."
msgstr ""

#: ../../accounting/payables/pay/check.rst:101
msgid ""
"To review checks that have not been credited, open the list of payments and "
"filter on the Sent state. Review those payments that have a date more than 2"
" weeks ago."
msgstr ""

#: ../../accounting/payables/pay/check.rst:106
msgid "Pay anything with a check"
msgstr ""

#: ../../accounting/payables/pay/check.rst:108
msgid ""
"You can register a payment that is not related to a supplier bill. To do so,"
" use the top menu :menuselection:`Purchases --> Payments`. Register your "
"payment and select a payment method by check."
msgstr ""

#: ../../accounting/payables/pay/check.rst:112
msgid ""
"If you pay a specific supplier bill, put the reference of the bill in the "
"**Memo** field."
msgstr ""

#: ../../accounting/payables/pay/check.rst:118
msgid ""
"Once your payment by check is registered, don't forget to **Confirm** it. "
"Once confirmed, you can use **Print Check** directly or follow the preceding"
" flow to print checks in batch:"
msgstr ""

#: ../../accounting/payables/pay/check.rst:122
msgid "`Print checks`_"
msgstr ""

#: ../../accounting/payables/pay/check.rst:123
msgid "`Reconcile bank statements`_"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:3
msgid "How to pay several bills at once?"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:5
msgid ""
"Odoo provides a simple and effective way to handle several bills at once, "
"with various quick or complex options. With one single process, anyone is "
"able to handle bills and payment in just a few clicks."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:10
msgid "Pay multiple bills with one payment"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:13
msgid "Record several payments"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:15
msgid ""
"In the following example, we will generate some bills. You can control the "
"whole process from your accounting dashboard (first screen you get when you "
"open the accounting application)."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:22
msgid ""
"To create a bill, open the Dashboard menu and click on **Vendor Bills**. In "
"the Vendor Bills window, click on **Create**."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:28
msgid ""
"Choose the vendor from which you wish to purchase the product, and click on "
"Add an item to add one (or more) product(s). Click on **Save** and then "
"**Validate**."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:33
msgid "Pay supplier bills, one after the other"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:38
msgid ""
"We will now record a payment for one bill only. Open the bill, then click on"
" **Register Payment**. Insert the Payment Method, Date and Amount, and click"
" on **Validate**."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:45
msgid ""
"Once you have validated the payment, the system will automatically reconcile"
" the payment with the bill, and set the bill as **Paid**. The system will "
"also generate a move from the payment account and reconcile it with the "
"expense transaction."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:51
msgid "Pay several bills altogether"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:53
msgid ""
"In order to illustrate the process thoroughly, create at least 2 more bills "
"following the above standing guide. **Make sure all bills come from the same"
" vendor.**"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:60
msgid ""
"In the Vendors Bills, select the new bills you have just created by checking"
" the box next to each of them. In the Action menu located in the middle of "
"the page, click on **Register Payment**."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:67
msgid ""
"Insert the details of the payment. The system calculated the total amount "
"for both bills, but you can modify it freely. Click on **Validate**."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:71
msgid "Record the payment, reconcile afterwards"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:73
msgid ""
"You can also reconcile a payment with bills after the payment has been "
"recorded."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:76
msgid "First, we need to create a payment"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:78
msgid ""
"This will handle from :menuselection:`Dashboard --> Bank journal --> More "
"Option --> Send Money`"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:84
msgid ""
"Creating payment order with check payment method. Selecting related Vendor "
"and amount which remain to pay. After filling all details, we will confirm "
"the payment order which will generate payment transaction with the system."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:92
msgid ""
"As you can see, bill payment status show what is posted and what is "
"remaining to reconcile."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:95
msgid ""
"After receiving bank statement from the bank with payment detail, you can "
"reconcile the transaction from the Dashboard. It will automatically map the "
"transaction amount."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:103
msgid "Partial payments of several supplier bills"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:106
msgid "How to pay several supplier bills having cash discounts at once?"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:108
msgid ""
"You already learned how to pay bills in various way but what about partial "
"payment? We are taking another example where we will do partial payment for "
"various bills."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:112
msgid ""
"We are creating multiple bills and partially pay them through bank "
"statements."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:115
msgid ""
"We are adding payment terms which allow some cash discount where vendor "
"offer us early payment discount."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:121
msgid ""
"We are creating the following bills with the assignment of the above payment"
" term."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:127
msgid "We have created the following bills:"
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:132
msgid ""
"We will pay the invoices by creating bank statement where we will adjust the"
" cash discount our vendor provided under payment terms."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:138
msgid ""
"Before reconciling this bank statement, we need to create one statement "
"model for cash discount."
msgstr ""

#: ../../accounting/payables/pay/multiple.rst:144
msgid "Now we are going back to bank statement and opening reconcile view."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:3
#: ../../accounting/payables/pay/sepa.rst:65
msgid "Pay with SEPA"
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:5
msgid ""
"SEPA, the Single Euro Payments Area, is a payment-integration initiative of "
"the European union for simplification of bank transfers denominated in EURO."
" SEPA allows you to send payment orders to your bank to automate bank wire "
"transfer."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:10
msgid ""
"SEPA is supported by the banks of the 28 EU member states as well as "
"Iceland, Norway, Switzerland, Andorra, Monaco and San Marino."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:13
msgid ""
"With Odoo, once you decide to pay a vendor, you can select to pay the bill "
"with SEPA. Then, at the end of the day, the manager can generate the SEPA "
"file containing all bank wire transfers and send it to the bank. The file "
"follows the SEPA Credit Transfer 'PAIN.001.001.03' specifications. This is a"
" well-defined standard that makes consensus among banks."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:20
msgid ""
"Once the payments are processed by your bank, you can directly import the "
"account statement inside Odoo. The bank reconciliation process will "
"seamlessly match the SEPA orders you sent to your bank with actual bank "
"statements."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:31
msgid ""
"To pay suppliers with SEPA, you must install the **SEPA Credit Transfer** "
"module. This module handle the process of generating SEPA files based on "
"Odoo payments."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:36
msgid ""
"According to your country and the chart of account you use, this module may "
"be installed by default."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:40
msgid "Activate SEPA payment methods on banks"
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:42
msgid ""
"In order to allow payments by SEPA, you must activate the payment method on "
"related bank journals. From the accounting dashboard (the screen you get "
"when you enter the accounting application), click on \"More\" on your bank "
"account and select the \"Settings\" option."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:47
msgid ""
"To activate SEPA, click the **Advanced Settings** tab and, in the **Payment "
"Methods** part of the **Miscellaneous** section, check the box **Sepa Credit"
" Transfer**."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:51
msgid ""
"Make sure to specify the IBAN account number (domestic account number won't "
"work with SEPA) and the BIC (bank identifier code) on your bank journal."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:56
msgid ""
"By default, the payments you send using SEPA will use your company name as "
"initiating party name. This is what appears on the recipient's bank "
"statement in the **payment from** field. You can customize it in your "
"company settings, in the tab **Configuration**, under the **SEPA** section."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:68
msgid "Register your payments"
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:70
msgid ""
"You can register a payment that is not related to a supplier bill. To do so,"
" use the top menu :menuselection:`Purchases --> Payments`. Register your "
"payment and select a payment method by Sepa Credit Transfer."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:74
msgid ""
"If it's the first time you pay this vendor, you will have to fill in the "
"Recipient Bank Account field with, at least, the bank name, IBAN and BIC "
"(Bank Identifier Code). Odoo will automatically verify the IBAN format."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:78
msgid ""
"For future payments to this vendor, Odoo will propose you automatically the "
"bank accounts but you will be able to select another one or create a new "
"one."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:82
msgid ""
"If you pay a specific supplier bill, put the reference of the bill in the "
"**memo** field."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:88
msgid ""
"Once your payment is registered, don't forget to Confirm it. You can also "
"pay vendor bills from the bill directly using the Register Payment button on"
" top of a vendor bill. The form is the same, but the payment is directly "
"linked to the bill and will be automatically reconciled to it."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:94
msgid "Generate SEPA files"
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:96
msgid ""
"From your accounting dashboard, you should see if there are SEPA files to "
"generate for every bank account."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:102
msgid ""
"Click on the link to check all the payments that are ready to transfer via "
"SEPA. Then, select all the payments you want to send (or check the top box "
"to select all payment at once) and click on :menuselection:`More --> "
"Download SEPA Payments`."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:114
msgid "The bank refuses my SEPA file"
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:116
msgid ""
"Ask your bank if they support **PAIN.001.001.03 SEPA Credit Transfers**. If "
"they don't, or cannot provide relevant informations, please forward the "
"error message to your Odoo partner."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:121
msgid "There is no Bank Identifier Code recorded for bank account ..."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:123
msgid ""
"In order to send a SEPA payment, the recipient must be identified by a valid"
" IBAN and BIC. If this message appear, you probably encoded an IBAN account "
"for the partner you are paying but forgot to fill in the BIC field."
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:129
#: ../../accounting/receivables/customer_payments/credit_cards.rst:166
#: ../../accounting/receivables/customer_payments/recording.rst:126
msgid ":doc:`check`"
msgstr ""

#: ../../accounting/payables/pay/sepa.rst:130
#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:64
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:121
msgid ":doc:`../../bank/setup/create_bank_account`"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:3
msgid "Non-current Assets and Fixed Assets"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:5
msgid ""
"**Non-current Assets**, also known as **long-term assets**, are investments "
"that are expected to be realized after one year. They are capitalized rather"
" than being expensed and appear on the company's balance sheet. Depending on"
" their nature, they may undergo **depreciation**."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:9
msgid ""
"**Fixed Assets** are a type of Non-current Assets and include the properties"
" bought for their productive aspects, such as buildings, vehicles, "
"equipment, land, and software."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:12
msgid ""
"For example, let's say we buy a car for $ 27,000. We plan to amortize it "
"over five years, and we will sell it for $ 7,000 afterward. Using the "
"linear, or straight-line, depreciation method, $ 4,000 are expensed each "
"year as **depreciation expenses**. After five years, the **Accumulated "
"Depreciation** amount reported on the balance sheet equals $ 20,000, leaving"
" us with $ 7,000 of **Not Depreciable Value**, or Salvage value."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:18
msgid ""
"Odoo Accounting handles depreciation by creating all depreciation entries "
"automatically in *draft mode*. They are then posted periodically."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:21
msgid "Odoo supports the following **Depreciation Methods**:"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:23
msgid "Linear"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:24
msgid "Degressive"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:25
msgid "Accelerated Degressive"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:28
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:25
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:24
msgid ""
"The server checks once a day if an entry must be posted. It might then take "
"up to 24 hours before you see a change from *draft* to *posted*."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:32
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:29
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:28
msgid "Prerequisites"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:34
msgid ""
"Such transactions must be posted on an **Assets Account** rather than on the"
" default expense account."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:38
msgid "Configure an Assets Account"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:40
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:37
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:36
msgid ""
"To configure your account in the **Chart of Accounts**, go to "
":menuselection:`Accounting --> Configuration --> Chart of Accounts`, click "
"on *Create*, and fill out the form."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:48
msgid ""
"This account's type must be either *Fixed Assets* or *Non-current Assets*."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:51
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:48
msgid "Post an expense to the right account"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:54
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:51
msgid "Select the account on a draft bill"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:56
msgid ""
"On a draft bill, select the right account for all the assets you are buying."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:65
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:61
msgid "Choose a different Expense Account for specific products"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:67
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:63
msgid ""
"Start editing the product, go to the *Accounting* tab, select the right "
"**Expense Account**, and save."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:75
msgid ""
"It is possible to :ref:`automate the creation of assets entries <assets-"
"automation>` for these products."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:81
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:75
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:74
msgid "Change the account of a posted journal item"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:83
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:77
msgid ""
"To do so, open your Purchases Journal by going to :menuselection:`Accounting"
" --> Accounting --> Purchases`, select the journal item you want to modify, "
"click on the account, and select the right one."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:92
msgid "Assets entries"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:97
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:89
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:88
msgid "Create a new entry"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:99
msgid ""
"An **Asset entry** automatically generates all journal entries in *draft "
"mode*. They are then posted one by one at the right time."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:102
msgid ""
"To create a new entry, go to :menuselection:`Accounting --> Accounting --> "
"Assets`, click on *Create*, and fill out the form."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:105
msgid ""
"Click on **select related purchases** to link an existing journal item to "
"this new entry. Some fields are then automatically filled out, and the "
"journal item is now listed under the **Related Purchase** tab."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:113
msgid ""
"Once done, you can click on *Compute Depreciation* (next to the *Confirm* "
"button) to generate all the values of the **Depreciation Board**. This board"
" shows you all the entries that Odoo will post to depreciate your asset, and"
" at which date."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:122
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:114
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:113
msgid "What does \"Prorata Temporis\" mean?"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:124
msgid ""
"The **Prorata Temporis** feature is useful to depreciate your assets the "
"most accurately possible."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:126
msgid ""
"With this feature, the first entry on the Depreciation Board is computed "
"based on the time left between the *Prorata Date* and the *First "
"Depreciation Date* rather than the default amount of time between "
"depreciations."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:130
msgid ""
"For example, the Depreciation Board above has its first depreciation with an"
" amount of $ 241.10 rather than $ 4,000.00. Consequently, the last entry is "
"also lower and has an amount of $ 3758.90."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:134
msgid "What are the different Depreciation Methods"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:136
msgid ""
"The **Linear Depreciation Method** divides the initial Depreciable Value by "
"the number of depreciations planned. All depreciation entries have the same "
"amount."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:139
msgid ""
"The **Degressive Depreciation Method** multiplies the Depreciable Value by "
"the **Degressive Factor** for each entry. Each depreciation entry has a "
"lower amount than the previous entry."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:142
msgid ""
"The **Accelerated Degressive Depreciation Method** uses the Degressive "
"Method, but with a minimum Depreciation equal to the Linear Method. This "
"method ensures a fast depreciation at the beginning, followed by a constant "
"one afterward."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:147
msgid "Assets from the Purchases Journal"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:149
msgid ""
"You can create an asset entry from a specific journal item in your "
"**Purchases Journal**."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:151
msgid ""
"To do so, open your Purchases Journal by going to :menuselection:`Accounting"
" --> Accounting --> Purchases`, and select the journal item you want to "
"record as an asset. Make sure that it is posted in the right account (see: "
":ref:`journal-assets-account`)."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:155
msgid ""
"Then, click on *Action*, select **Create Asset**, and fill out the form the "
"same way you would do to :ref:`create a new entry <create-assets-entry>`."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:163
msgid "Modification of an Asset"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:165
msgid ""
"You can modify the values of an asset to increase or decrease its value."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:167
msgid ""
"To do so, open the asset you want to modify, and click on *Modify "
"Depreciation*. Then, fill out the form with the new depreciation values and "
"click on *Modify*."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:170
msgid ""
"A **decrease in value** posts a new Journal Entry for the **Value Decrease**"
" and modifies all the future *unposted* Journal Entries listed in the "
"Depreciation Board."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:173
msgid ""
"An **increase in value** requires you to fill out additional fields related "
"to the account movements and creates a new Asset entry with the **Value "
"Increase**. The Gross Increase Asset Entry can be accessed with a Smart "
"Button."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:182
msgid "Disposal of Fixed Assets"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:184
msgid ""
"To **sell** an asset or **dispose** of it implies that it must be removed "
"from the Balance Sheet."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:186
msgid ""
"To do so, open the asset you want to dispose of, click on *Sell or Dispose*,"
" and fill out the form."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:192
msgid ""
"Odoo Accounting then generates all the journal entries necessary to dispose "
"of the asset, including the gain or loss on sale, which is based on the "
"difference between the asset's book value at the time of the sale and the "
"amount it is sold for."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:197
msgid ""
"To record the sale of an asset, you must first post the related Customer "
"Invoice so you can link the sale of the asset with it."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:201
msgid "Assets Models"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:203
msgid ""
"You can create **Assets Models** to create your Asset entries faster. It is "
"particularly useful if you recurrently buy the same kind of assets."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:206
msgid ""
"To create a model, go to :menuselection:`Accounting --> Configuration --> "
"Assets Models`, click on *Create*, and fill out the form the same way you "
"would do to create a new entry."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:210
msgid ""
"You can also convert a *confirmed Asset entry* into a model by opening it "
"from :menuselection:`Accounting --> Accounting --> Assets` and then, by "
"clicking on the button *Save Model*."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:215
msgid "Apply an Asset Model to a new entry"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:217
msgid ""
"When you create a new Asset entry,  fill out the **Fixed Asset Account** "
"with the right asset account."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:220
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:160
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:160
msgid ""
"New buttons with all the models linked to that account appear at the top of "
"the form. Clicking on a model button fills out the form according to that "
"model."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:230
msgid "Automate the Assets"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:232
msgid ""
"When you create or edit an account of which the type is either *Non-current "
"Assets* or *Fixed Assets*, you can configure it to create assets for the "
"expenses that are credited on it automatically."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:236
msgid "You have three choices for the **Automate Assets** field:"
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:239
msgid ""
"**Create in draft:** whenever a transaction is posted on the account, a "
"draft *Assets entry* is created, but not validated. You must first fill out "
"the form in :menuselection:`Accounting --> Accounting --> Assets`."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:242
msgid ""
"**Create and validate:** you must also select an Asset Model (see: `Assets "
"Models`_). Whenever a transaction is posted on the account, an *Assets "
"entry* is created and immediately validated."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:250
msgid ""
"You can, for example, select this account as the default **Expense Account**"
" of a product to fully automate its purchase. (see: :ref:`product-assets-"
"account`)."
msgstr ""

#: ../../accounting/payables/supplier_bills/assets.rst:254
#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:195
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:194
msgid ":doc:`../../overview/getting_started/chart_of_accounts`"
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:3
msgid "When should I use supplier bills or purchase receipts?"
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:5
msgid ""
"Purchase receipts are different than vendor bills. Vendor bills are requests"
" for payment. If I issue a Purchase Order my vendor will in most business "
"cases send me a Vendor Bill. Depending on his invoice policy I then have a "
"defined amount of time to pay the Bill. A Purchase receipts are "
"confirmations of received payments. They are my day-to-day ticket receipts."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:12
msgid ""
"From an accounting point of view this makes a difference as a Vendor Bill "
"will first credit a debt account before reconciling with the bank account. "
"On the other hand we usually immediately pay the purchase receipts, which "
"means no debt account is necessary."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:17
msgid ""
"Moreover purchase receipts can have a different tax amount per product line,"
" as vendors bills apply one tax amount over the entire bill."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:20
msgid ""
"If my company's bank account is used to pay for goods where only a purchase "
"receipt are issued I should use the purchase receipts function in Odoo to "
"handle them in accounting."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:24
msgid ""
"Let's take the following example: we need to buy tea for our customers from "
"a local tea store that doesn't issue bills. We go every week buy 50 euros "
"worth of tea and a teapot worth 20 euros. We pay with the company's bank "
"account."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:32
msgid ""
"To handle purchase receipts in Odoo one module and one app has to be "
"installed. Go into the app module and install the accounting app."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:38
msgid ""
"Then, go in the search bar, delete the default module search, and search for"
" \"purchase\". Install the **Sale & Purchase Vouchers** module."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:45
msgid "Register a receipt"
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:47
msgid ""
"By installing the **Sale & Purchase Vouchers** I've made the new **Purchase "
"Receipts** drop down menu visible in the accounting app."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:50
msgid ""
"To import our 50 euros worth of tea purchase receipt, enter the accounting "
"app, select :menuselection:`Purchases --> Purchase Receipts`."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:53
msgid ""
"Create a new Purchase Receipt and fill in all the necessary information. "
"Note that you have the choice in the Payment field between **Pay Later** or "
"**Pay Now**. It's a significant difference as Pay Later will generate a debt"
" accounting entry whereas Pay Now will immediately credit the Bank account."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:59
msgid ""
"In most cases you immediately pay, we will thus select the Pay Directly "
"option. Add the products, the related account and the appropriate taxe. For "
"the example we suppose the tea is a 12% taxe and the Tea Pott 21%."
msgstr ""

#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:66
msgid ""
"Validate the Purchase Receipt to post it. Don't forget you need to "
":doc:`reconcile payments <../../bank/reconciliation/use_cases>` in order to "
"completely close the transaction in your accounting."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:3
msgid "Deferred Expenses and Prepayments"
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:5
msgid ""
"**Deferred expenses** and **prepayments** (also known as **prepaid "
"expense**), are both costs that have already occurred for unconsumed "
"products or services yet to receive."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:8
msgid ""
"Such costs are **assets** for the company that pays them since it already "
"paid for products and services still to receive or that are yet to be used. "
"The company cannot report them on the current **Profit and Loss statement**,"
" or *Income Statement*, since the payments will be effectively expensed in "
"the future."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:13
msgid ""
"These future expenses must be deferred on the company's balance sheet until "
"the moment in time they can be **recognized**, at once or over a defined "
"period, on the Profit and Loss statement."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:16
msgid ""
"For example, let's say we pay $ 1200 at once for one year of insurance. We "
"already pay the cost now but haven't used the service yet. Therefore, we "
"post this new expense in a *prepayment account* and decide to recognize it "
"on a monthly basis. Each month, for the next 12 months, $ 100 will be "
"recognized as an expense."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:21
msgid ""
"Odoo Accounting handles deferred expenses and prepayments by spreading them "
"in multiple entries that are automatically created in *draft mode* and then "
"posted periodically."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:31
msgid ""
"Such transactions must be posted on a **Deferred Expense Account** rather "
"than on the default expense account."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:35
msgid "Configure a Deferred Expense Account"
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:45
msgid "This account's type must be either *Current Assets* or *Prepayments*"
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:53
msgid ""
"On a draft bill, select the right account for all the products of which the "
"expenses must be deferred."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:71
msgid ""
"It is possible to automate the creation of expense entries for these "
"products (see: `Automate the Deferred Expenses`_)."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:86
msgid "Deferred Expenses entries"
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:91
msgid ""
"A **Deferred Expense entry** automatically generates all journal entries in "
"*draft mode*. They are then posted one by one at the right time until the "
"full amount of the expense is recognized."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:94
msgid ""
"To create a new entry, go to :menuselection:`Accounting --> Accounting --> "
"Deferred Expense`, click on *Create*, and fill out the form."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:97
msgid ""
"Click on **select related purchases** to link an existing journal item to "
"this new entry. Some fields are then automatically filled out, and the "
"journal item is now listed under the **Related Expenses** tab."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:105
msgid ""
"Once done, you can click on *Compute Deferral* (next to the *Confirm* "
"button) to generate all the values of the **Expense Board**. This board "
"shows you all the entries that Odoo will post to recognize your expense, and"
" at which date."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:116
msgid ""
"The **Prorata Temporis** feature is useful to recognize your expense the "
"most accurately possible."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:118
msgid ""
"With this feature, the first entry on the Expense Board is computed based on"
" the time left between the *Prorata Date* and the *First Recognition Date* "
"rather than the default amount of time between recognitions."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:122
msgid ""
"For example, the Expense Board above has its first expense with an amount of"
" $ 70.97 rather than $ 100.00. Consequently, the last entry is also lower "
"and has an amount of $ 29.03."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:126
msgid "Deferred Entry from the Purchases Journal"
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:128
msgid ""
"You can create a deferred entry from a specific journal item in your "
"**Purchases Journal**."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:130
msgid ""
"To do so, open your Purchases Journal by going to :menuselection:`Accounting"
" --> Accounting --> Purchases`, and select the journal item you want to "
"defer. Make sure that it is posted in the right account (see: `Change the "
"account of a posted journal item`_)."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:134
#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:134
msgid ""
"Then, click on *Action*, select **Create Deferred Entry**, and fill out the "
"form the same way you would do to `create a new entry`_."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:142
msgid "Deferred Expense Models"
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:144
msgid ""
"You can create **Deferred Expense Models** to create your Deferred Expense "
"entries faster."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:146
msgid ""
"To create a model, go to :menuselection:`Accounting --> Configuration --> "
"Deferred Expense Models`, click on *Create*, and fill out the form the same "
"way you would do to create a new entry."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:150
msgid ""
"You can also convert a *confirmed Deferred Expense entry* into a model by "
"opening it from :menuselection:`Accounting --> Accounting --> Deferred "
"Expenses` and then, by clicking on the button *Save Model*."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:155
msgid "Apply a Deferred Expense Model to a new entry"
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:157
msgid ""
"When you create a new Deferred Expense entry,  fill out the **Deferred "
"Expense Account** with the right recognition account."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:170
msgid "Automate the Deferred Expenses"
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:172
msgid ""
"When you create or edit an account of which the type is either *Current "
"Assets* or *Prepayments*, you can configure it to defer the expenses that "
"are credited on it automatically."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:175
msgid "You have three choices for the **Automate Deferred Expense** field:"
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:178
msgid ""
"**Create in draft:** whenever a transaction is posted on the account, a "
"draft *Deferred Expenses entry* is created, but not validated. You must "
"first fill out the form in :menuselection:`Accounting --> Accounting --> "
"Deferred Expenses`."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:181
msgid ""
"**Create and validate:** you must also select a Deferred Expense Model (see:"
" `Deferred Expense Models`_). Whenever a transaction is posted on the "
"account, a *Deferred Expenses entry* is created and immediately validated."
msgstr ""

#: ../../accounting/payables/supplier_bills/deferred_expenses.rst:190
msgid ""
"You can, for example, select this account as the default **Expense Account**"
" of a product to fully automate its purchase. (see: `Choose a different "
"Expense Account for specific products`_)."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:3
msgid "How to manage vendor Bills?"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:5
msgid ""
"The **Purchase** application allows you to manage your purchase orders, "
"incoming products, and vendor bills all seamlessly in one place."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:8
msgid ""
"If you want to set up a vendor bill control process, the first thing you "
"need to do is to have purchase data in Odoo. Knowing what has been purchased"
" and received is the first step towards understanding your purchase "
"management processes."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:13
msgid "Here is the standard work flow in Odoo:"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:15
msgid ""
"You begin with a **Request for Quotation (RFQ)** to send out to your "
"vendor(s)."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:18
msgid ""
"Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase "
"Order (PO)**."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:21
msgid ""
"Confirming the PO generates an **Incoming Shipment** if you purchased any "
"stockable products."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:24
msgid ""
"Upon receiving a **Vendor Bill** from your Vendor, validate the bill with "
"products received in the previous step to ensure accuracy."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:27
msgid ""
"This process may be done by three different people within the company, or "
"only one."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:34
msgid "Installing the Purchase and Inventory applications"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:36
msgid ""
"From the **Apps** application, search for the **Purchase** module and "
"install it. Due to certain dependencies, installing Purchase will "
"automatically install the **Inventory** and **Accounting** applications."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:41
msgid "Creating products"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:43
msgid ""
"Creating products in Odoo is essential for quick and efficient purchasing "
"within Odoo. Simply navigate to the Products submenu under Purchase and "
"click create."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:50
msgid ""
"When creating the product, pay attention to the **Product Type** field, "
"since it is important:"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:53
msgid ""
"Products that are set as **Stockable or Consumable** will allow you to keep "
"track of their inventory levels. These options imply stock management and "
"will allow for receiving these kinds of products."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:58
msgid ""
"Conversely, products that are set as a **Service or Digital Product** will "
"not imply stock management, simply due to the fact that there is no "
"inventory to manage. You will not be able to receive products under either "
"of these designations."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:64
msgid ""
"It is recommended that you create a **Miscellaneous** product for all "
"purchases that occur infrequently and do not require inventory valuation or "
"management. If you create such a product, it is recommended to set the "
"product type to **Service**."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:69
msgid "Managing your Vendor Bills"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:72
msgid "Purchasing products or services"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:74
msgid ""
"From the purchase application, you can create a purchase order with as many "
"products as you need. If the vendor sends you a confirmation or quotation "
"for an order, you may record the order reference number in the **Vendor "
"Reference** field. This will enable you to easily match the PO with the the "
"vendor bill later (as the vendor bill will probably include the Vendor "
"Reference)"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:84
msgid ""
"Validate the purchase order and receive the products from the Inventory "
"application."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:88
msgid "Receiving Products"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:90
msgid ""
"If you purchased any stockable products that you manage the inventory of, "
"you will need to receive the products from the Inventory application after "
"you confirm a purchase order. From the **Inventory dashboard**, you should "
"see a button linking you directly to the transfer of products. This button "
"is outlined in red below:"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:99
msgid ""
"Navigating this route will take you to a list of all orders waiting to be "
"received."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:105
msgid ""
"If you have a lot of awaiting orders, apply a filter using the search bar in"
" the upper right. With this search bar, you may filter based on the vendor "
"(partner), the product, or the source document (also known as the reference "
"of your purchase order). You can also group the orders by different criteria"
" under **Group By**. Selecting an item from this list will open the "
"following screen where you then will receive the products."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:116
msgid "Purchasing service products does not trigger a delivery order."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:119
msgid "Managing Vendor Bills"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:121
msgid ""
"When you receive a vendor bill for a previous purchase, be sure to record it"
" in the Purchases application under the **Control Menu**. You need to create"
" a new vendor bill even if you already registered a purchase order."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:129
msgid ""
"The first thing you will need to do upon creating a vendor bill is to select"
" the appropriate vendor, since doing so will also pull up any associated "
"accounting or pricelist information. From there, you can choose to specify "
"one or multiple Purchase Orders to populate the Vendor Bill with. When you "
"select a Purchase Order from the list, Odoo will pull any uninvoiced "
"products associated to that Purchase Order and automatically populate that "
"information below. If you are having a hard time finding the appropriate "
"vendor bill, you may search through the list by inputting the vendor "
"reference number or your internal purchase order number."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:143
msgid ""
"While the invoice is in a draft state, you can make any modifications you "
"need (i.e. remove or add product lines, modify quantities, and change "
"prices)."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:148
msgid "Your vendor may send you several bills for the same Purchase Order if:"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:150
msgid ""
"Your vendor is in back-order and is sending you invoices as they ship the "
"products."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:151
msgid "Your vendor is sending you a partial bill or asking for a deposit."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:153
msgid ""
"Every time you record a new vendor bill, Odoo will automatically populate "
"the product quantities based on what has been received from the vendor. If "
"this value is showing a zero, this means that you have not yet received this"
" product and simply serves as a reminder that the product is not in hand and"
" you may need to inquire further into this. At any point in time, before you"
" validate the Vendor Bill, you may override this zero quantity."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:162
msgid "Vendor Bill Matching"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:165
msgid "What to do if your vendor bill does not match what you received"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:167
msgid ""
"If the bill you receive from the vendor has quantities that do not match the"
" quantities automatically populated by Odoo, this could be due to several "
"reasons:"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:171
msgid ""
"The vendor is incorrectly charging you for products and/or services that you"
" have not ordered."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:174
msgid ""
"The vendor is billing you for products that you might not have received yet,"
" as the invoicing control may be based on ordered or received quantities."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:178
msgid "The vendor did not bill you for previously purchased products."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:180
msgid ""
"In these instances it is recommended that you verify that the bill, and any "
"associated purchase order to the vendor, are accurate and that you "
"understand what you have ordered and what you have already received."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:184
msgid ""
"If you are unable to find a purchase order related to a vendor bill, this "
"could be due to one of a few reasons:"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:187
msgid ""
"The vendor has already invoiced you for this purchase order; therefore it is"
" not going to appear anywhere in the selection."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:190
msgid ""
"Someone in the company forgot to record a purchase order for this vendor."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:193
msgid "The vendor is charging you for something you did not order."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:198
msgid "How product quantities are managed"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:200
msgid ""
"By default, services are managed based on ordered quantities, while "
"stockables and consumables are managed based on received quantities."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:203
msgid ""
"If you need to manage products based on ordered quantities over received "
"quantities, you will need to belong to the group **Purchase Manager**. Ask "
"your system administrator to enable these access on :menuselection:`Settings"
" --> Users --> Users --> Access Rights`. Once you belong to the correct "
"group, select the product(s) you wish to modify, and you should see a new "
"field appear, labeled **Control Purchase Bills**."
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:213
msgid ""
"You can then change the default management method for the selected product "
"to be based on either:"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:216
msgid "Ordered quantities"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:218
msgid "or Received quantities"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:221
msgid "Batch Billing"
msgstr ""

#: ../../accounting/payables/supplier_bills/manage.rst:223
msgid ""
"When creating a vendor bill and selecting the appropriate purchase order, "
"you may continue to select additional purchase orders. Odoo will add the "
"additional line items from the purchase orders you select. If you have not "
"deleted the previous line items from the first purchase order, the bill will"
" be linked to all the appropriate purchase orders."
msgstr ""

#: ../../accounting/receivables.rst:3
msgid "Account Receivables"
msgstr ""

#: ../../accounting/receivables/customer_invoices.rst:3
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:77
msgid "Customer Invoices"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:3
msgid "Offer cash discounts"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:5
msgid ""
"Cash discounts are incentives you can offer to customers to motivate them to"
" pay within a specific time frame. For instance, you offer a 2% discount if "
"the customer pays you within the first 5 days of the invoice, when it is due"
" in 30 days. This approach can greatly improve your average collection "
"period."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:12
msgid "Set up a cash discount"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:14
msgid ""
"To set up a cash discount, go to :menuselection:`Accounting --> "
"Configuration --> Management --> Payment Terms` and click on *Create*. Add a"
" *Percent* type of term with a corresponding value (e.g. 98% of the total "
"price for a 2% discount) and the number of days during which the offer is "
"valid. You can also change the default balance term if needed."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:25
msgid "Start offering the cash discount"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:27
msgid ""
"Now, you can create a customer invoice and select the cash discount payment "
"term you added. Once the invoice is validated, Odoo will automatically split"
" the account receivables part of the journal entry into two installments "
"having different due dates. Since the discounted price is already "
"calculated, your payment controls will be simplified."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:37
msgid "Grant the cash discount"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:39
msgid ""
"The customer fulfilled the payment terms and therefore benefits from the "
"cash discount. When you process the bank statement, match the payment with "
"the related journal entry. Then, select the remaining cash discount and "
"click on *Create Write-off* to reconcile it."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:48
msgid ""
"You can also create a dedicated reconciliation model to make the process "
"easier. In this case, you should add a tax to the model based on the taxes "
"applied to your invoices. This means that if you handle multiple tax rates, "
"you need to create several reconciliation models. Note that depending on "
"your localisation, you might already have a Cash Discount model available by"
" default."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:56
msgid "Register the full payment"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:58
msgid ""
"In this case, the customer has not fulfilled the payment term and cannot "
"benefit from the cash discount. When you process the bank statement, match "
"the payment with the two related journal entries."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:67
msgid ":doc:`../../receivables/customer_invoices/payment_terms`"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:3
msgid "Cash Rounding"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:4
msgid ""
"**Cash rounding** is required when the lowest physical denomination of "
"currency, or the smallest coin, is higher than the minimum unit of account."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:8
msgid ""
"For example, some countries require their companies to round up or down the "
"total amount of an invoice to the nearest five cents, when the payment is "
"made in cash."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:14
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Settings` and enable "
"*Cash Rounding*, then click on *Save*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:20
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Cash Roundings`, and "
"click on *Create*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:23
msgid ""
"Define here your *Rounding Precision*, *Rounding Strategy*, and *Rounding "
"Method*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:26
msgid "Odoo supports two **rounding strategies**:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:28
msgid ""
"**Add a rounding line**: a *rounding* line is added on the invoice. You have"
" to define which account records the cash roundings."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:31
msgid "**Modify tax amount**: the rounding is applied in the taxes section."
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:34
msgid "Apply roundings"
msgstr ""

#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:35
msgid ""
"When editing a draft invoice, open the *Other Info* tab, go to the "
"*Accounting Information* section, and select the appropriate *Cash Rounding "
"Method*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:3
msgid "Credit Notes and Refunds"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:4
msgid ""
"A **credit note**, or **credit memo**, is a document issued to a customer "
"that notifies them that they have been credited a certain amount."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:11
msgid "There are several reasons that can lead to a credit note, such as:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:9
msgid "a mistake in the invoice"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:10
msgid "a return of the goods, or a rejection of the services"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:11
msgid "the goods delivered are damaged"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:14
msgid ""
"Issuing a credit note is the only legal way to cancel, refund or modify a "
"validated invoice. Don’t forget to *register the payment* afterward if you "
"need to send money back to your customer."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:20
msgid "Issue a Credit Note"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:21
msgid ""
"You can create a credit note from scratch by going to "
":menuselection:`Accounting --> Customers --> Credit Notes`, and by clicking "
"on *Create*. Filling the Credit Note’s form works the same way as the "
"Invoice’s form."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:26
msgid ""
"However, most of the time, credit notes are generated directly from the "
"invoices they are related to."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:29
msgid "To do so, open the *Customer Invoice*, and click on *Add Credit Note*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:37
msgid "You can choose between three options:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:35
#: ../../accounting/receivables/customer_invoices/credit_notes.rst:44
msgid "Partial Refund"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:36
#: ../../accounting/receivables/customer_invoices/credit_notes.rst:55
msgid "Full Refund"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:37
#: ../../accounting/receivables/customer_invoices/credit_notes.rst:66
msgid "Full refund and new draft invoice"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:40
msgid ""
"Credit Notes’ numbers start with “R” and are followed by the number of the "
"document they are related to (e.g., RINV/2019/0004)."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:45
msgid ""
"Odoo creates a draft credit note already prefilled with all the necessary "
"information from the original invoice."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:48
msgid ""
"This is the option to choose to do a partial refund, or if you want to "
"modify any detail on the credit note."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:52
msgid ""
"This is the only option available for invoices that are already marked as "
"*Paid*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:56
msgid ""
"Odoo creates a credit note, automatically validates it, and reconciles the "
"original invoice with it."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:62
msgid ""
"This is the option to choose to do a full refund or cancel a validated "
"invoice."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:67
msgid ""
"Odoo creates a credit note, automatically validates it, reconciles the "
"original invoice with it, and open a new draft invoice prefilled with the "
"same details from the original invoice."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:71
msgid ""
"This is the option to choose to modify the content of a validated invoice."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:74
msgid "Record a Vendor Refund"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:75
msgid ""
"**Vendor Refunds** are recorded the same way you would do with invoices’ "
"credit notes:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:77
msgid ""
"You can either create a credit note from scratch by going to "
":menuselection:`Accounting --> Vendors --> Refund`, and by clicking on "
"*Create*, or by opening the validated *Vendor Bill*, and clicking on *Add "
"Credit Note*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:84
msgid ""
"Issuing a credit note from an invoice creates a **reverse entry** that "
"zeroes out the journal items generated by the original invoice."
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:87
msgid "Here is an example of an invoice’s journal entry:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/credit_notes.rst:92
msgid ""
"And here is the credit note’s journal entry generated to reverse the "
"original invoice above:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:3
msgid "Deferred Revenues"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:5
msgid ""
"**Deferred revenues**, or **unearned revenue**, are payments made in advance"
" by customers for products yet to deliver or services yet to render."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:8
msgid ""
"Such payments are a **liability** for the company that receives them since "
"it still owes its customers these products or services. The company cannot "
"report them on the current **Profit and Loss statement**, or *Income "
"Statement*, since the payments will be effectively earned in the future."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:12
msgid ""
"These future revenues must be deferred on the company's balance sheet until "
"the moment in time they can be **recognized**, at once or over a defined "
"period, on the Profit and Loss statement."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:15
msgid ""
"For example, let's say we sell a five-year extended warranty for $ 350. We "
"already receive the money now but haven't earned it yet. Therefore, we post "
"this new income in a deferred revenue account and decide to recognize it on "
"a yearly basis. Each year, for the next 5 years, $ 70 will be recognized as "
"revenue."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:20
msgid ""
"Odoo Accounting handles deferred revenues by spreading them in multiple "
"entries that are automatically created in *draft mode* and then posted "
"periodically."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:30
msgid ""
"Such transactions must be posted on a **Deferred Revenue Account** rather "
"than on the default income account."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:34
msgid "Configure a Deferred Revenue Account"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:44
msgid ""
"This account's type must be either *Current Liabilities* or *Non-current "
"Liabilities*"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:47
msgid "Post an income to the right account"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:50
msgid "Select the account on a draft invoice"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:52
msgid ""
"On a draft invoice, select the right account for all the products of which "
"the incomes must be deferred."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:60
msgid "Choose a different Income Account for specific products"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:62
msgid ""
"Start editing the product, go to the *Accounting* tab, select the right "
"**Income Account**, and save."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:70
msgid ""
"It is possible to automate the creation of revenue entries for these "
"products (see: `Automate the Deferred Revenues`_)."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:76
msgid ""
"To do so, open your Sales Journal by going to :menuselection:`Accounting -->"
" Accounting --> Sales`, select the journal item you want to modify, click on"
" the account, and select the right one."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:85
msgid "Deferred Revenues entries"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:90
msgid ""
"A **Deferred Revenues entry** automatically generates all journal entries in"
" *draft mode*. They are then posted one by one at the right time until the "
"full amount of the income is recognized."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:93
msgid ""
"To create a new entry, go to :menuselection:`Accounting --> Accounting --> "
"Deferred Revenues`, click on *Create*, and fill out the form."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:96
msgid ""
"Click on **select related purchases** to link an existing journal item to "
"this new entry. Some fields are then automatically filled out, and the "
"journal item is now listed under the **Related Sales** tab."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:104
msgid ""
"Once done, you can click on *Compute Revenue* (next to the *Confirm* button)"
" to generate all the values of the **Revenue Board**. This board shows you "
"all the entries that Odoo will post to recognize your revenue, and at which "
"date."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:115
msgid ""
"The **Prorata Temporis** feature is useful to recognize your revenue the "
"most accurately possible."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:117
msgid ""
"With this feature, the first entry on the Revenue Board is computed based on"
" the time left between the *Prorata Date* and the *First Recognition Date* "
"rather than the default amount of time between recognitions."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:121
msgid ""
"For example, the Revenue Board above has its first revenue with an amount of"
" $ 4.22 rather than $ 70.00. Consequently, the last entry is also lower and "
"has an amount of $ 65.78."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:125
msgid "Deferred Entry from the Sales Journal"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:127
msgid ""
"You can create a deferred entry from a specific journal item in your **Sales"
" Journal**."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:129
msgid ""
"To do so, open your Sales Journal by going to :menuselection:`Accounting -->"
" Accounting --> Sales`, and select the journal item you want to defer. Make "
"sure that it is posted in the right account (see: `Change the account of a "
"posted journal item`_)."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:142
msgid "Deferred Revenue Models"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:144
msgid ""
"You can create **Deferred Revenue Models** to create your Deferred Revenue "
"entries faster."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:146
msgid ""
"To create a model, go to :menuselection:`Accounting --> Configuration --> "
"Deferred Revenue Models`, click on *Create*, and fill out the form the same "
"way you would do to create a new entry."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:150
msgid ""
"You can also convert a *confirmed Deferred Revenue entry* into a model by "
"opening it from :menuselection:`Accounting --> Accounting --> Deferred "
"Revenues` and then, by clicking on the button *Save Model*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:155
msgid "Apply a Deferred Revenue Model to a new entry"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:157
msgid ""
"When you create a new Deferred Revenue entry,  fill out the **Deferred "
"Revenue Account** with the right recognition account."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:170
msgid "Automate the Deferred Revenues"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:172
msgid ""
"When you create or edit an account of which the type is either *Current "
"Liabilities* or *Non-current Liabilities*, you can configure it to defer the"
" revenues that are credited on it automatically."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:175
msgid "You have three choices for the **Automate Deferred Revenue** field:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:178
msgid ""
"**Create in draft:** whenever a transaction is posted on the account, a "
"draft *Deferred Revenues entry* is created, but not validated. You must "
"first fill out the form in :menuselection:`Accounting --> Accounting --> "
"Deferred Revenues`."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:181
msgid ""
"**Create and validate:** you must also select a Deferred Revenue Model (see:"
" `Deferred Revenue Models`_). Whenever a transaction is posted on the "
"account, a *Deferred Revenues entry* is created and immediately validated."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:190
msgid ""
"You can, for example, select this account as the default **Income Account** "
"of a product to fully automate its sale. (see: `Choose a different Income "
"Account for specific products`_)."
msgstr ""

#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:195
msgid ""
"`Odoo Academy: Deferred Revenues (Recognition) "
"<https://www.odoo.com/r/EWO>`_"
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:3
msgid "Add EPC QR Codes to invoices"
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:4
msgid ""
"European Payments Council Quick Response Code, or **EPC QR Code**, are two-"
"dimensional barcodes that customers can scan with their **mobile banking "
"applications** to initiate a **SEPA Credit Transfer (SCT)**, and pay their "
"invoices instantly."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:10
msgid ""
"In addition to bringing ease of use and speed, it greatly reduces typing "
"errors that would potentially make for payment issues."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:15
msgid ""
"This feature is only available in several European countries such as "
"Austria, Belgium, Finland, Germany, and The Netherlands."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:21
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Settings` and "
"activate the **SEPA QR Code** feature."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:28
msgid "Configure your Bank Account’s journal"
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:29
msgid ""
"Make sure that your *Bank Account* is correctly configured on Odoo with your"
" IBAN and BIC."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:32
msgid ""
"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, "
"open your *bank journal*, then fill out the *Bank Account* and *Bank* under "
"the *Bank Account* tab."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:40
msgid "Issue Invoices with EPC QR Codes"
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:41
msgid ""
"EPC QR Codes are added automatically to your invoices, as long as you issue "
"them to customers that are located in a country where this feature is "
"available."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:45
msgid ""
"Go to :menuselection:`Accounting --> Customers --> Invoices`, and create a "
"new invoice."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:48
msgid ""
"Before posting it, open the *Other Info* tab. Odoo automatically fills out "
"the *Bank Account* field with your IBAN."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:51
msgid ""
"Make sure that the account indicated is the one you want to use to receive "
"your customer’s payment as Odoo uses this field to generate the EPC QR Code."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:59
msgid ""
"If you want to issue an invoice without an EPC QR Code, remove the IBAN "
"indicated in the *Bank Account* field, under the *Other Info* tab of the "
"invoice."
msgstr ""

#: ../../accounting/receivables/customer_invoices/epc_qr_code.rst:65
msgid ""
"`Odoo Academy: QR Code on Invoices for European Customers "
"<https://www.odoo.com/r/VuU>`_"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:3
msgid "Overview of the invoicing process"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:5
msgid ""
"Depending on your business and the application you use, there are different "
"ways to automate the customer invoice creation in Odoo. Usually, draft "
"invoices are created by the system (with information coming from other "
"documents like sales order or contracts) and accountant just have to "
"validate draft invoices and send the invoices in batch (by regular mail or "
"email)."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:12
msgid ""
"Depending on your business, you may opt for one of the following way to "
"create draft invoices:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:19
msgid "Sales Order ‣ Invoice"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:21
msgid ""
"In most companies, salespeople create quotations that become sales order "
"once they are validated. Then, draft invoices are created based on the sales"
" order. You have different options like:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:25
msgid ""
"Invoice manually: use a button on the sale order to trigger the draft "
"invoice"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:28
msgid ""
"Invoice before delivery: invoice the full order before triggering the "
"delivery order"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:31
msgid "Invoice based on delivery order: see next section"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:33
msgid ""
"Invoice before delivery is usually used by the eCommerce application when "
"the customer pays at the order and we deliver afterwards. (pre-paid)"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:37
msgid ""
"For most other use cases, it's recommended to invoice manually. It allows "
"the salesperson to trigger the invoice on demand with options: invoice the "
"whole order, invoice a percentage (advance), invoice some lines, invoice a "
"fixed advance."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:42
msgid "This process is good for both services and physical products."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:45
msgid ":doc:`../../../sales/invoicing/proforma`"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:48
msgid "Sales Order ‣ Delivery Order ‣ Invoice"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:50
msgid ""
"Retailers and eCommerce usually invoice based on delivery orders, instead of"
" sales order. This approach is suitable for businesses where the quantities "
"you deliver may differs from the ordered quantities: foods (invoice based on"
" actual Kg)."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:55
msgid ""
"This way, if you deliver a partial order, you only invoice for what you "
"really delivered. If you do back orders (deliver partially and the rest "
"later), the customer will receive two invoices, one for each delivery order."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:61
msgid ":doc:`../../../sales/invoicing/invoicing_policy`"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:64
msgid "eCommerce Order ‣ Invoice"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:66
msgid ""
"An eCommerce order will also trigger the creation of the order when it is "
"fully paid. If you allow paying orders by check or wire transfer, Odoo only "
"creates an order and the invoice will be triggered once the payment is "
"received."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:72
msgid "Contracts"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:75
msgid "Regular Contracts ‣ Invoices"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:77
msgid ""
"If you use contracts, you can trigger invoice based on time and material "
"spent, expenses or fixed lines of services/products. Every month, the "
"salesperson will trigger invoice based on activities on the contract."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:81
msgid "Activities can be:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:83
msgid ""
"fixed products/services, coming from a sale order linked to this contract"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:84
msgid "materials purchased (that you will re-invoice)"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:85
msgid "time and material based on timesheets or purchases (subcontracting)"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:86
msgid ""
"expenses like travel and accommodation that you re-invoice to the customer"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:88
msgid ""
"You can invoice at the end of the contract or trigger intermediate invoices."
" This approach is used by services companies that invoice mostly based on "
"time and material. For services companies that invoice on fix price, they "
"use a regular sales order."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:94
msgid ":doc:`../../../sales/invoicing/time_materials`"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:96
msgid ":doc:`../../../sales/invoicing/milestone`"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:99
msgid "Recurring Contracts ‣ Invoices"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:101
msgid ""
"For subscriptions, an invoice is triggered periodically, automatically. The "
"frequency of the invoicing and the services/products invoiced are defined on"
" the contract."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:106
msgid ":doc:`../../../sales/invoicing/subscriptions`"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:112
msgid "Creating an invoice manually"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:114
msgid ""
"Users can also create invoices manually without using contracts or a sales "
"order. It's a recommended approach if you do not need to manage the sales "
"process (quotations), or the delivery of the products or services."
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:119
msgid ""
"Even if you generate the invoice from a sales order, you may need to create "
"invoices manually in exceptional use cases:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:122
msgid "if you need to create a refund"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:124
msgid "If you need to give a discount"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:126
msgid "if you need to change an invoice created from a sales order"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:128
msgid "if you need to invoice something not related to your core business"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:131
msgid "Specific modules"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:133
msgid "Some specific modules are also able to generate draft invoices:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:135
msgid "**membership**: invoice your members every year"
msgstr ""

#: ../../accounting/receivables/customer_invoices/overview.rst:137
msgid "**repairs**: invoice your after-sale services"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:3
msgid "Payment Terms and Installment Plans"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:5
msgid ""
"**Payment Terms** regroup all the conditions under which a sale is completed"
" and paid. They can be applied to sales orders, customer invoices, and "
"supplier bills, mostly to ensure that they will be correctly paid, and on "
"time. These conditions cover:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:9
msgid "The due date"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:10
msgid "Some discounts"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:11
msgid "Any other condition on the payment"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:13
msgid ""
"Defining Payment Terms automates the computation of payments due dates, both"
" for invoices and bills. This is particularly helpful in managing "
"installment plans."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:16
msgid ""
"An **installment plan** allows the customers to pay an invoice in parts, "
"with the amounts and payment dates defined beforehand by the seller."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:19
msgid "**Examples of Payment Terms:**"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "**Immediate Payment**"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "The full payment is due on the day of the invoice's issuance."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "**15 Days** (or **Net 15**)"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "The full payment is due 15 days after the invoice date."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "**21 MFI**"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid ""
"The full payment is due by the 21st of the month following the invoice date."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "**2% 10, Net 30 EOM**"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid ""
"2% :doc:`cash discount <cash_discounts>` if the payment is received within "
"ten days. Otherwise, the full payment is due at the end of the month "
"following the invoice date."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:32
msgid ""
"Payment terms are not to be confused with payment in several parts. If, for "
"a specific order, you invoice the customer in two parts, that is nor a "
"payment term nor an installment plan, but an invoicing policy."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:39
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Payment Terms` and "
"click on *Create*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:41
msgid ""
"The **Description on the Invoice** is the displayed text on a sale order, "
"invoice, or bill."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:43
msgid ""
"In the **Terms** section, you can add a set of rules, that we call *terms*, "
"to define what needs to be paid, and by which due date."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:46
msgid ""
"To add a term, click on *Add a line*, and define its *Type*, *Value*, and "
"*Due Date Computation*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:49
msgid "Terms are computed in the order they are set up."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:50
msgid "The **balance** should always be used for the last line."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:52
msgid ""
"In the following example, 30% of the invoice is due on the day of issuance "
"of the invoice, and the balance is due at the end of the following month."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:60
msgid "Using Payment Terms"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:62
msgid "Payment Terms can be defined with the **Payment Terms** field on:"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "**Contacts**"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid ""
"To set specific payment terms automatically on new sales orders, invoices, "
"and bills of a contact. This can be modified in the contact’s *Form View*, "
"under the *Sales & Purchase* tab."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "**Quotations**"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid ""
"To set specific payment terms automatically on all invoices generated from a"
" quotation."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "**Customer Invoices**"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "To set specific payment terms on an invoice."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid "**Vendor Bills**"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:0
msgid ""
"To set specific payment terms on a bill. This is mostly useful when you need"
" to manage vendor terms with several installments. Otherwise, setting the "
"*Due Date* is enough."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:77
msgid ""
"Invoices with specific Payment Terms generate different *Journal Entries*, "
"with one *Journal Item* for each different *Due Date* computed."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:80
msgid ""
"This makes for easier *Follow-ups* and *Reconciliation* since Odoo takes "
"each due date into account, rather than just the balance due date."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:83
msgid ""
"In the following example, an invoice of $1000 has been issued with the "
"following payment terms: 30% of the invoice is due on the day of issuance of"
" the invoice, and the balance is due at the end of the following month."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:92
msgid ""
"The $1000 debited on the Account Receivable is split into two distinct "
"*Journal Items*. Both of them have their own **Due Date**."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96
msgid "Due date"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:98
msgid "February 21"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:98
msgid "300"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:100
msgid "March 31"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:100
msgid "700"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:102
msgid "Product Sales"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:102
msgid "1000"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:105
msgid ""
"This allows for easier reconciliation and to accurately follow up late "
"payments."
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:108
msgid ":doc:`cash_discounts`"
msgstr ""

#: ../../accounting/receivables/customer_invoices/payment_terms.rst:109
msgid ""
"`Odoo Learn: Terms and Conditions (T&C) and Payment Terms "
"<https://www.odoo.com/r/fpv>`_"
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:3
msgid "Send your Invoices by Post (Snailmail)"
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:5
msgid ""
"Direct mail is a great way to capture individuals’ attention at a time where"
" inboxes are always full. Odoo allows you to send invoices and follow-up "
"reports by post, worldwide, directly from your database."
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:10
msgid "Set up Snailmail"
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:12
msgid ""
"Go to :menuselection:`Accounting --> Settings --> Snailmail` and activate "
"the feature."
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:14
msgid ""
"If you would like this option to be a default feature, enable *Send by Post*"
" under *Default Sending Options*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:21
msgid "Send your invoices by post"
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:23
msgid ""
"Open your Invoice, click on the *Send & Print* button and select *Send by "
"Post*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:30
msgid ""
"Make sure to have your customer’s address set correctly, and that it "
"includes a country, before sending the letter."
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:34
msgid "Pricing"
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:37
msgid ""
"*Snailmail* is an *In-App Purchase (IAP)* service which requires prepaid "
"stamps (=credits) to work. Sending one document consumes one stamp."
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:40
msgid ""
"To buy stamps, go to :menuselection:`Accounting --> Configuration --> "
"Settings --> Snailmail` and click on *Buy credits*, or go to "
":menuselection:`Settings --> Odoo IAP` and click on *View my Services*."
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:43
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""

#: ../../accounting/receivables/customer_invoices/snailmail.rst:45
msgid ""
"Click `here <https://iap.odoo.com/privacy#header_4>`_ to know about our "
"*Privacy Policy*."
msgstr ""

#: ../../accounting/receivables/customer_payments.rst:3
msgid "Customer Payments"
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:3
msgid "Batch Payments: SEPA Direct Debit (SDD)"
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:4
msgid ""
"SEPA, the Single Euro Payments Area, is a payment-integration initiative of "
"the European Union for simplification of bank transfers denominated in EURO."
" With **SEPA Direct Debit**, your customers can sign a **mandate** that "
"authorizes you to collect future payments from their bank accounts "
"automatically."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:10
msgid ""
"You can record your customer mandates in Odoo, and generate XML files "
"containing pending payments made with an SDD mandate."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:0
msgid ""
"SDD is supported by all SEPA countries, which includes the 28 member states "
"of the European Union as well as additional countries."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:0
#: ../../accounting/receivables/customer_payments/batch_sdd.rst:123
msgid ""
"`List of all SEPA countries <https://www.europeanpaymentscouncil.eu"
"/document-library/other/epc-list-sepa-scheme-countries>`_."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:19
msgid ""
"Go to :menuselection:`Accounting --> Configuration --> Settings` nd activate"
" the **SEPA Direct Debit (SDD)** feature. Enter the **Creditor Identifier** "
"of your company. This number is provided by your bank, or the authority "
"responsible for delivering them."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:28
msgid "SEPA Direct Debit Mandates"
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:30
msgid "Create a mandate"
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:31
msgid ""
"The SEPA Direct Debit Mandate is the document that your customers sign to "
"authorize you to collect money directly from their bank accounts."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:34
msgid ""
"To create a new one, go to :menuselection:`Accounting --> Customers --> "
"Direct Debit Mandates`, click on *Create*, and fill out the new mandate’s "
"form."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:41
msgid ""
"First, export the PDF file by clicking on *Print*. It is then up to your "
"customer to sign this document. Once done, upload the signed file in the "
"**Original Document** field, and click on *Validate* to start running the "
"mandate."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:47
msgid ""
"First, make sure, that the **IBAN bank accounts details** are correctly "
"recorded on the debtor’s contact form, under the *Accounting* tab, and in "
"your own *Bank Account* settings."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:52
msgid "Close or revoke a mandate"
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:53
msgid ""
"Direct Debit mandates are closed automatically after their *End Date*. If "
"this field is left blank, then the mandate keeps being *Active* until it is "
"*Closed* or *Revoked*."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:60
msgid ""
"Clicking on **Close** updates the mandate’s end day to the current day. This"
" means that invoices made after the present day won’t be processed "
"automatically with an SDD payment."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:64
msgid ""
"Clicking on **Revoke** disables the mandate immediately. No SDD payment can "
"be registered anymore, regardless of the invoice’s date. However, payments "
"that have already been registered will still be included to the next SDD XML"
" file."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:70
msgid ""
"Once a mandate has been *closed* or *revoked*, it cannot be reactivated. If "
"a customer requires to pay with SDD payments again, you will have to create "
"a new mandate from scratch."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:75
msgid "Get paid with SDD Batch Payments"
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:78
msgid ""
"All new posted invoice issued to customers with an active mandate will "
"automatically register payment and have their status marked as *Paid*."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:82
msgid ""
"If you have unpaid invoices that could be paid with a new mandate, it is "
"still possible to do it. Go on the invoice, click on *Register Payment* and "
"choose *SEPA Direct Debit* as payment method."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:87
msgid "Generate SEPA Direct Debit XML files to submit payments"
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:88
msgid ""
"To submit your SDD payments to your bank, you will first generate an **XML "
"file** that can be uploaded directly to your bank interface."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:91
msgid ""
"The files generated by Odoo follow the SEPA Direct Debit **PAIN.008.001.02**"
" specifications as required by the SEPA customer-to-bank Implementation "
"Guidelines, which ensures compatibility with the banks."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:95
msgid ""
"To generate your XML file for the pending SDD payments, go to the related "
"*bank journal* on your *Accounting dashboard*, then click on *Direct Debit "
"Payments to Collect*."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:102
msgid ""
"Select all the payments in the list that you want to include in your SDD XML"
" file, then click on *Action* and select *Create Batch Payment*."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:108
msgid ""
"Odoo then takes you to your *Batch Payment*’s form. Click on *Validate* and "
"then download the SDD XML file."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:114
msgid "Finally, upload this file to your bank to process the payments."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:117
msgid ""
"You can retrieve all the generated SDD XML files by going to "
":menuselection:`Accounting --> Configuration --> Customers --> Batch "
"Payments`."
msgstr ""

#: ../../accounting/receivables/customer_payments/batch_sdd.rst:122
msgid ""
"`Odoo Academy: SEPA Direct Debit Mandates (SDD) "
"<https://www.odoo.com/r/Zxs>`_"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:3
msgid "How to register customer payments by checks?"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:5
msgid ""
"There are two ways to handle payments received by checks. Odoo support both "
"approaches so that you can use the one that better fits your habits."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:9
msgid ""
"**Undeposited Funds:** once you receive the check, you record a payment by "
"check on the invoice. (using a Check journal and posted on the Undeposited "
"Fund account) Then, once the check arrives in your bank account, move money "
"from Undeposited Funds to your bank account."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:16
msgid ""
"**One journal entry only:** once your receive the check, you record a "
"payment on your bank, paid by check, without going through the **Undeposited"
" Funds**. Once you process your bank statement, you do the matching with "
"your bank feed and the check payment, without creating a dedicated journal "
"entry."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:23
msgid ""
"We recommend the first approach as it is more accurate (your bank account "
"balance is accurate, taking into accounts checks that have not been cashed "
"yet). Both approaches require the same effort."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:27
msgid ""
"Even if the first method is cleaner, Odoo support the second approach "
"because some accountants are used to it (quickbooks and peachtree users)."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:32
msgid ""
"You may have a look at the *Deposit Ticket feature* if you deposit several "
"checks to your bank accounts in batch."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:36
#: ../../accounting/receivables/customer_payments/credit_cards.rst:37
msgid "Option 1: Undeposited Funds"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:41
msgid "Create a journal **Checks**"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:43
msgid "Set **Undeposited Checks** as a defaut credit/debit account"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:45
msgid ""
"Set the bank account related to this journal as **Allow Reconciliation**"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:48
#: ../../accounting/receivables/customer_payments/check.rst:109
msgid "From check payments to bank statements"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:50
msgid ""
"The first way to handle checks is to create a check journal. Thus, checks "
"become a payment method in itself and you will record two transactions."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:54
#: ../../accounting/receivables/customer_payments/check.rst:111
msgid ""
"Once you receive a customer check, go to the related invoice and click on "
"**Register Payment**. Fill in the information about the payment:"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:57
msgid ""
"Payment method: Check Journal (that you configured with the debit and credit"
" default accounts as **Undeposited Funds**)"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:60
msgid "Memo: write the Check number"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:65
#: ../../accounting/receivables/customer_payments/credit_cards.rst:74
msgid "This operation will produce the following journal entry:"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:68
#: ../../accounting/receivables/customer_payments/check.rst:81
#: ../../accounting/receivables/customer_payments/check.rst:131
#: ../../accounting/receivables/customer_payments/credit_cards.rst:77
#: ../../accounting/receivables/customer_payments/credit_cards.rst:91
#: ../../accounting/receivables/customer_payments/credit_cards.rst:140
msgid "Statement Match"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:70
#: ../../accounting/receivables/customer_payments/check.rst:72
#: ../../accounting/receivables/customer_payments/check.rst:83
#: ../../accounting/receivables/customer_payments/check.rst:85
#: ../../accounting/receivables/customer_payments/check.rst:133
#: ../../accounting/receivables/customer_payments/check.rst:135
#: ../../accounting/receivables/customer_payments/credit_cards.rst:79
#: ../../accounting/receivables/customer_payments/credit_cards.rst:81
#: ../../accounting/receivables/customer_payments/credit_cards.rst:93
#: ../../accounting/receivables/customer_payments/credit_cards.rst:95
#: ../../accounting/receivables/customer_payments/credit_cards.rst:142
#: ../../accounting/receivables/customer_payments/credit_cards.rst:144
msgid "100.00"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:72
#: ../../accounting/receivables/customer_payments/check.rst:83
msgid "Undeposited Funds"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:75
#: ../../accounting/receivables/customer_payments/check.rst:121
msgid "The invoice is marked as paid as soon as you record the check."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:77
msgid ""
"Then, once you get the bank statements, you will match this statement with "
"the check that is in Undeposited Funds."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:83
#: ../../accounting/receivables/customer_payments/check.rst:133
#: ../../accounting/receivables/customer_payments/credit_cards.rst:93
#: ../../accounting/receivables/customer_payments/credit_cards.rst:142
msgid "X"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:89
msgid ""
"If you use this approach to manage received checks, you get the list of "
"checks that have not been cashed in the **Undeposit Funds** account "
"(accessible, for example, from the general ledger)."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:94
msgid ""
"Both methods will produce the same data in your accounting at the end of the"
" process. But, if you have checks that have not been cashed, this one is "
"cleaner because those checks have not been reported yet on your bank "
"account."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:100
#: ../../accounting/receivables/customer_payments/credit_cards.rst:109
msgid "Option 2: One journal entry only"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:105
msgid ""
"These is nothing to configure if you plan to manage your checks using this "
"method."
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:114
msgid "**Payment method:** the bank that will be used for the deposit"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:116
msgid "Memo: write the check number"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:123
msgid ""
"Once you will receive the bank statements, you will do the matching with the"
" statement and this actual payment. (technically: point this payment and "
"relate it to the statement line)"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:127
#: ../../accounting/receivables/customer_payments/credit_cards.rst:136
msgid ""
"With this approach, you will get the following journal entry in your books:"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:139
msgid ""
"You may also record the payment directly without going on the customer "
"invoice, using the menu :menuselection:`Sales --> Payments`. This method may"
" be more convenient if you have a lot of checks to record in a batch but you"
" will have to reconcile entries afterwards (matching payments with invoices)"
msgstr ""

#: ../../accounting/receivables/customer_payments/check.rst:145
msgid ""
"If you use this approach to manage received checks, you can use the report "
"**Bank Reconciliation Report** to verify which checks have been received or "
"paid by the bank. (this report is available from the **More** option from "
"the Accounting dashboard on the related bank account)."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:3
msgid "How to register credit card payments on invoices?"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:5
msgid ""
"There are two ways to handle payments received by credit cards. Odoo support"
" both approaches so that you can use the one that better fits your habits."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:9
msgid ""
"**Undeposited Funds** (mostly used in european countries): once you receive "
"the credit card payment authorization, you record a payment by credit card "
"on the invoice (using a Credit card journal and posted on the Undeposited "
"Fund account). Then, once the credit card payments arrives in your bank "
"account, move money from Undeposited Funds to your bank account."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:16
msgid ""
"**One journal entry only** (mostly used in the U.S.): once your receive the "
"credit card payment, you record a payment on your bank, paid by credit card,"
" without going through the Undeposited Funds. Once you process your bank "
"statement, you do the matching with your bank feed and the credit card "
"payment, without creating a dedicated journal entry ."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:23
msgid ""
"We recommend the first approach as it is more accurate (your bank account "
"balance is accurate, taking into accounts credit cards that have not been "
"cashed yet). Both approaches require the same effort."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:27
msgid ""
"If you use eCommerce and an automated payment gateway, you will only need to"
" take care of the bank reconciliation part as paid invoice will be "
"automatically recorded in the right journal. You will use the second "
"approach."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:32
msgid ""
"Even if the first method is cleaner, Odoo support the second approach "
"because some accountants are used to it (*QuickBooks* and *Peachtree* "
"users)."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:42
msgid ""
"On the Accounting module, go to :menuselection:`Configuration --> Journals "
"--> Create`"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:44
msgid ""
"Create a Journal called 'Credit card payments' with the following data:"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:46
msgid "**Journal Name**: Credit card"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:47
msgid "**Default debit account**: Credit cards"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:48
msgid "**Default credit account**: Credit cards"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:50
msgid ""
"The account type should be \"Credit Card\". Once it's done, don't forget to "
"set the \"Credit cards\" account as \"Allow Reconciliation\"."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:57
#: ../../accounting/receivables/customer_payments/credit_cards.rst:118
msgid "From credit card payments to bank statements"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:59
msgid ""
"The first way to handle credit cards is to create a credit card journal. "
"Thus, credit cards become a payment method in itself and you will record two"
" transactions."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:63
#: ../../accounting/receivables/customer_payments/credit_cards.rst:120
msgid ""
"Once you receive a customer credit card payment, go to the related invoice "
"and click on Register Payment. Fill in the information about the payment:"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:67
msgid "**Payment method**: Credit card"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:69
msgid "**Memo**: write the invoice reference"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:81
msgid "Credit Cards"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:84
msgid ""
"The invoice is marked as paid as soon as you record the credit card payment."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:87
msgid ""
"Then, once you get the bank statements, you will match this statement with "
"the credit card that is in the 'Credit card' account."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:93
msgid "Credit cards"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:98
msgid ""
"If you use this approach to manage credit cards payments, you get the list "
"of credit cards payments that have not been cashed in the \"Credit card\" "
"account (accessible, for example, from the general ledger)."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:103
msgid ""
"Both methods will produce the same data in your accounting at the end of the"
" process. But, if you have credit cards that have not been cashed, this one "
"is cleaner because those credit cards have not been reported yet on your "
"bank account."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:114
msgid ""
"There is nothing to configure if you plan to manage your credit cards using "
"this method."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:124
msgid "**Payment method**: the bank that will be used for the deposit"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:126
msgid "**Memo**: write the credit card transaction number"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:131
msgid ""
"The invoice is marked as paid as soon as the credit card payment has been "
"recorded. Once you receive the bank statements, you will do the matching "
"with the statement and this actual payment (technically: point this payment "
"and relate it to the statement line)."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:148
msgid ""
"You may also record the payment directly without going on the customer "
"invoice, using the top menu :menuselection:`Sales --> Payments`. This method"
" may be more convenient if you have a lot of credit cards to record in a "
"batch but you will have to reconcile entries afterwards (matching payments "
"with invoices)."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:153
msgid ""
"If you use this approach to manage received credit cards, you can use the "
"report \"Bank Reconciliation Report\" to verify which credit cards have been"
" received or paid by the bank (this report is available from the \"More\" "
"option from the Accounting dashboard on the related bank account)."
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:164
msgid ":doc:`recording`"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:165
#: ../../accounting/receivables/customer_payments/recording.rst:125
msgid ":doc:`../../bank/feeds/paypal`"
msgstr ""

#: ../../accounting/receivables/customer_payments/credit_cards.rst:167
#: ../../accounting/receivables/customer_payments/recording.rst:127
msgid ":doc:`followup`"
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:3
msgid "Follow-up on invoices and get paid faster"
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:5
msgid ""
"It is essential for your business to collect payments when they are overdue."
" Odoo will help you identify payments that are late and will allow you to "
"send the appropriate reminders."
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:10
msgid "Manage your follow-ups"
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:13
msgid ""
"We recommend that you reconcile your bank statements before launching your "
"follow-up process. It will avoid you the trouble of sending a statement to a"
" customer that has already paid you."
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:17
msgid ""
"The overdue invoices you need to follow-up on are available by default in "
":menuselection:`Accounting --> Sales --> Follow-up Reports`. There, you can "
"easily send a reminder by email or print it as a letter. Then, you can click"
" on the *Done* button to view the next follow-up that needs your attention."
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:23
msgid ""
"Otherwise, if now is not the time for a reminder, click on *Remind me "
"later*. You will get the next report according to the *Next Reminder Date* "
"set on the statement."
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:28
msgid ""
"To avoid sending too many reminders in a short period of time, change the "
"number of days calculated between each report by going to "
":menuselection:`Accounting --> Configuration --> Settings --> Payment "
"Follow-up`."
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:33
msgid ""
"You can also set a trust level for your customers by marking them as bad, "
"normal or good debtors on the follow-up reports."
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:40
msgid "Send reminders in batch"
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:42
msgid ""
"To get your follow-up process easier, you can send reminder emails in batch "
"from your follow-up reports page. Select all the reports you would like to "
"process, click on *Action* and then on *Process Follow-ups*. A pdf document "
"containing all of the follow-up letters for you to print will also be "
"automatically generated."
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:52
msgid "Plan a follow-up process"
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:54
msgid ""
"To plan a follow-up process, go to :menuselection:`Accounting --> "
"Configuration --> Settings` and activate the *Follow-up Levels* feature "
"under the *Customer Payments* section. Then, click on the new *Follow-up "
"Levels* button that has appeared on your settings page."
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:59
msgid ""
"A follow-up plan with several actions is available by default in Odoo, but "
"you can customize it any way you want. Depending on a specific number of "
"overdue days, plan to send an email, a letter or to undertake a manual "
"action. You can also edit the template used for the statement according to "
"the stage of the process."
msgstr ""

#: ../../accounting/receivables/customer_payments/followup.rst:69
msgid ""
"If you would like to get a reminder before the actual due date, set a "
"negative number of due days."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:3
msgid "What are the different ways to record a payment?"
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:5
msgid ""
"In Odoo, a payment can either be linked directly to an invoice or be a stand"
" alone record for use on a later date:"
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:8
msgid ""
"If a payment is linked to an invoice, it reduces the amount due of the "
"invoice. You can have multiple payments linked to the same invoice."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:12
msgid ""
"If a payment is not linked to an invoice, the customer has an outstanding "
"credit with your company, or your company as an outstanding balance with a "
"vendor. You can use this outstanding credit/debit to pay future invoices or "
"bills."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:18
msgid "Paying an invoice"
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:20
msgid ""
"If you register a payment on a customer invoice or a vendor bill, the "
"payment is automatically reconciled with the invoice reducing the amount "
"due."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:27
msgid ""
"The green icon near the payment line will display more information about the"
" payment. From there you can choose to open the journal entry or reconcile "
"the payment."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:32
msgid ""
"If you unreconcile a payment, it is still registered in your books but not "
"linked to the specific invoice any longer. If you unreconcile a payment in a"
" different currency, Odoo will create a journal entry to reverse the "
"Currency Exchange Loss/Gain posted at the time of reconciliation."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:38
msgid "Payments not tied to an invoice"
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:41
msgid "Registering a payment"
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:43
msgid ""
"In the Accounting application, you can create a new payment from the Sales "
"menu (register a customer payment) or the Purchases menu (pay a vendor). If "
"you use these menus, the payment is not linked to an invoice, but can easily"
" be reconciled on an invoice later on."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:51
msgid ""
"When registering a new payment, you must select a customer or vendor, the "
"payment method, and the amount of the payment. The currency of the "
"transaction is defined by the payment method. If the payment refers to a "
"document (sale order, purchase order or invoice), set the reference of this "
"document in the memo field."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:57
msgid ""
"Once confirmed, a journal entry will be posted reflecting the transaction "
"just made in the accounting application."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:61
msgid "Reconciling invoice payments"
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:63
msgid ""
"The easiest way of reconciling a payment with an invoice is to do so on the "
"invoice directly."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:66
msgid ""
"When validating a new invoice, Odoo will warn you that an outstanding "
"payment for this customer or vendor is available. In this case, you can "
"reconcile this payment to the invoice near the totals at the bottom, under "
"\"Outstanding Payments\"."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:75
msgid "Reconciling all your outstanding payments and invoices"
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:77
msgid ""
"If you want to reconcile all outstanding payments and invoices at once "
"(instead of doing so one by one), you can use the batch reconciliation "
"feature within Odoo."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:81
msgid ""
"The batch reconciliation feature is available from the dashboard on the "
"Customer Invoices card and the Vendor Bills card for reconciling Accounts "
"Receivable and Payable, respectively."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:88
msgid ""
"The payments matching tool will open all unreconciled customers or vendors "
"and will give you the opportunity to process them all one by one, doing the "
"matching of all their payments and invoices at once."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:95
msgid ""
"During the reconciliation, if the sum of the debits and credits do not "
"match, it means there is still a remaining balance that either needs to be "
"reconciled at a later date, or needs to be written off directly."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:100
msgid "Transferring money from one bank account to another"
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:102
msgid ""
"Just like making a customer or vendor payment, you transfer cash internally "
"between your bank accounts from the dashboard or from the menus up top."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:109
msgid ""
"This will take you to the same screen you have for receiving and making "
"payments."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:116
msgid ""
"When making an internal transfer from one bank account to another, select "
"the bank you want to apply the transfer from in the dashboard, and in the "
"register payments screen, you select the transfer to account. Do not go "
"through this process again in the other bank account or else you will end up"
" with two journal entries for the same transaction."
msgstr ""

#: ../../accounting/receivables/customer_payments/recording.rst:124
msgid ":doc:`credit_cards`"
msgstr ""