msgid "**Odoo Accounting** is a full featured accounting app. Accountant productivity is at the core of its development with features such as AI-powered invoice recognition, synchronization with your bank accounts, smart matching suggestions, etc."
msgid "Odoo uses the double-entry bookkeeping system, whereby every entry needs a corresponding and opposite counterpart in a different account, with one account debited and the other credited. It ensures that all transactions are recorded accurately and consistently and that the accounts always balance."
msgid "Both accrual and cash basis accounting are supported in Odoo. This allows reporting income and expense either when the transaction occurs (accrual basis) or when the payment is made or received (cash basis)."
msgid "Several companies can be managed within the same database. Each company has its :doc:`chart of accounts <accounting/get_started/chart_of_accounts>`, which is also useful to generate consolidation reports. Users can access several companies but can only work on a single company's accounting at a time."
msgid "A :doc:`multi-currency <accounting/get_started/multi_currency>` environment with an automated exchange rate to ease international transactions is available in Odoo. Every transaction is recorded in the company's default currency; for transactions occurring in another currency, Odoo stores both the value in the company's currency and the transactions' currency value. Odoo generates currency gains and losses after reconciling the journal items."
msgid "Odoo Accounting supports more than 70 countries. It provides the central standards and mechanisms common to all nations, and thanks to country-specific modules, local requirements are fulfilled. Fiscal positions exist to address regional specificities like the chart of accounts, taxes, or any other requirements."
msgid "By default, there is a single account for the account receivable entries and one for the account payable entries. As transactions are linked to your **contacts**, you can run a report per customer, vendor, or supplier."
msgid "The **Partner Ledger** report displays the balance of your customers and suppliers. It is available by going to :menuselection:`Accounting --> Reporting --> Partner Ledger`."
msgid "Once the tax report has been generated for a period, Odoo locks it and prevents the creation of new journal entries involving VAT. Any correction to customer invoices or vendor bills has to be recorded in the next period."
msgid "Depending on the country's localization, an XML version of the tax report can be generated to be uploaded to the VAT platform of the relevant taxation authority."
msgid "The bank synchronization system directly connects with your bank institution to automatically import all transactions into your database. It gives an overview of your cash flow without logging into an online banking system or waiting for paper bank statements."
msgid "Both periodic (manual) and perpetual (automated) inventory valuations are supported in Odoo. The available methods are standard price, average price, :abbr:`LIFO (Last-In, First-Out)` and :abbr:`FIFO (First-In, First-Out).`"
msgid "Retained earnings are the portion of income retained by a business. Odoo calculates current year earnings in real-time, so no year-end journal or rollover is required. The profit and loss balance is automatically reported on the balance sheet report."
msgid "The :guilabel:`Accounting Firms` mode can be activated by going to :menuselection:`Accounting --> Configuration --> Settings --> Accounting Firms mode`. When enabled:"
msgid "The :guilabel:`Total (tax incl.)` field appears to speed up and control the encoding by automating line creation with the right account and tax;"
msgid "You can manage as many bank or cash accounts as needed on your database. Configuring them well allows you to have all your banking data up-to-date and ready for :doc:`reconciliation <bank/reconciliation>` with your journal entries."
msgid "In Odoo Accounting, each bank account has a dedicated journal set to post all entries in a dedicated account. Both the journal and the account are automatically created and configured whenever you add a bank account."
msgid "To connect your bank account to your database, go to :menuselection:`Accounting --> Configuration --> Banks: Add a Bank Account`, select your bank in the list, click on :guilabel:`Connect`, and follow the instructions."
msgid "If your banking institution is not available in Odoo, or if you don't want to connect your bank account to your database, you can configure your bank account manually."
msgid "To manually add a bank account, go to :menuselection:`Accounting --> Configuration --> Banks: Add a Bank Account`, click on :guilabel:`Create it` (at the bottom right), and fill out the form."
msgid "A default bank journal is available and can be used to configure your bank account by going to :menuselection:`Accounting --> Configuration --> Accounting: Journals --> Bank`. Open it and edit the different fields to match your bank account information."
msgid "To create a new cash journal, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals`, click on :guilabel:`Create` and select :guilabel:`Cash` in the :guilabel:`Type` field."
msgid "A default cash journal is available and can be used straight away. You can review it by going to :menuselection:`Accounting --> Configuration --> Accounting: Journals --> Cash`."
msgid "To edit an existing bank journal, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals` and select the journal you want to modify."
msgid "The :guilabel:`Profit Account` is used to register a profit when the ending balance of a cash register differs from what the system computes, while the :guilabel:`Loss Account` is used to register a loss when the ending balance of a cash register differs from what the system computes."
msgid "If you need to **edit your bank account details**, click on the external link arrow next to your :guilabel:`Account Number`. On the new page, click on the external link arrow next to your :guilabel:`Bank` and update your bank information accordingly. These details are used when registering payments."
msgid ":guilabel:`Undefined yet`, which should be selected when you don’t know yet if you will synchronize your bank account with your database or not."
msgid "The outstanding accounts are defined by default. If necessary, you can update them by going to :menuselection:`Accounting --> Configuration --> Settings --> Default Accounts` and update your :guilabel:`Outstanding Receipts Account` and :guilabel:`Outstanding Payments Account`."
msgid "You can also set specific outstanding accounts for any journal with the :ref:`type <chart-of-account/type>` :guilabel:`Bank` or :guilabel:`Cash`."
msgid "From your :guilabel:`Accounting Dashboard`, click on the menu selection ⋮ of the journal you want to configure, and click on :guilabel:`Configuration`, then open the :guilabel:`Incoming/Outgoing Payments` tab. To display the outstanding accounts column, click on the toggle button and check the :guilabel:`Outstanding Receipts/Payments accounts`, then update the account."
msgid "If you do not specify an outstanding payments account or an outstanding receipts account for a specific journal, Odoo uses the default outstanding accounts."
msgid "If your main bank account is added as an outstanding receipts account or outstanding payments account, when a payment is registered, the invoice or bill's status is directly set to :guilabel:`Paid`."
msgid "To check if your bank is compatible with Odoo, go to `Odoo Accounting Features <https://www.odoo.com/page/accounting-features>`_, and click on :guilabel:`See list of supported institutions`."
msgid "To be able to use this service, you need to have a valid Odoo Enterprise subscription. So make sure that your database is registered with your Odoo Enterprise contract. We also use a proxy between your database and the third party provider so, in case of a connection error, please check that you don't have a firewall or a proxy blocking the following address:"
msgid "You can start synchronization either by going to the Accounting app and :menuselection:`Accounting Dashboard --> Configuration --> Banks: Add a Bank Account`."
msgid "If you have any issues during your first synchronization, please verify that your web browser doesn't block pop-ups and that your ad-blocker is disabled."
msgid "When choosing the date for the first bank statement synchronization, pick the date when you start recording accounting transaction on your Odoo accounting database. For example, if you import your closing balance in Odoo on the 31/12/2022 and you start recording accounting transactions on the 01/01/2023, your synchronization date should be 01/01/2023."
msgid "You must provide a phone number during your first synchronization to secure your account. We ask for such information because we don't want your data falling into the wrong hands. Therefore, if we detect suspicious activities on your account, we block all requests coming from your account, and you need to reactivate it using that phone number."
msgid "The third-party provider may request more information in order to connect with your bank institution. This information is not stored on Odoo's servers."
msgid "By default, transactions fetched from an online source are grouped inside the same statement, and one bank statement is created per month. You can change the bank statement creation periodicity in your journal settings."
msgid "You can find all your synchronizations by going to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`."
msgid "After your first synchronization, the created journals are synchronized by default every 12 hours. If you wish, you can synchronize manually by clicking on the :guilabel:`Synchronize Now` button on the dashboard."
msgid "Or you can go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`, select your institution and then click on the :guilabel:`fetch transactions` button."
msgid "Some institutions do not allow transactions to be fetched automatically. For such institutions, during the automatic synchronization of the account, you receive an error message asking you to disable the automatic synchronization. This message can be found in the chatter of your online synchronizations. In this case, make sure to perform manual synchronizations."
msgid "To report a connection error to the `Odoo support <https://www.odoo.com/help>`_, go to :menuselection:`Accounting Dashboard--> Configuration --> Accounting: Online Synchronization`, select the connection that failed, and copy the error description and the reference."
msgid "If you are unable to reconnect using the :guilabel:`Fetch Account` button, please contact the `support <https://www.odoo.com/help>`_ directly with your client id or the reference of the error listed in the chatter."
msgid "To do so, go to :menuselection:`Apps --> Update Apps List`, remove the default filter in the search bar and type `account_online_synchronization`. You can then click on :guilabel:`Install`. Finally, make sure all your users refresh their Odoo page by pressing CTRL+F5."
msgid "You can find them directly in the synchronization menu (:menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`). It is not possible to resynchronize these connections; you have to make new ones."
msgid "The process is not intended to work in real-time as third party providers synchronize your accounts at different intervals. To force the synchronization and fetch the statements, go to your :guilabel:`Accounting Dashboard`, and click on the :guilabel:`Synchronize Now` button. You can also synchronize and fetch transactions through :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`. Some providers only allow one refresh per day, so it is possible that clicking on :guilabel:`Synchronize Now` does not get your latest transactions if you already performed such action earlier in the day."
msgid "A transaction can be visible on your bank account but not be fetched if it has the status :guilabel:`Pending`. Only transactions with the :guilabel:`Posted` status will be retrieved. If the transaction is not **Posted** yet, you will have to wait until the status changes."
msgid "This means that banking institutions are not yet fully supported by our Third Party Provider. Bugs or other problems may arise. Odoo does not support technical problems that occur with banks in the Beta phase, but the user may still choose to connect. Connecting with these banks contributes to the development process since the Provider will have real data and feedback from the connection."
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."
msgid "During your first synchronization, you selected the bank accounts you decided to synchronize with Odoo. If you didn't synchronize any of your accounts, you can go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization` to click on the :guilabel:`Fetch Account` button on the connection."
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>`_."
msgid "You can update your credentials by going to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Online Synchronization`,open the connection you want to update your credentials and click on the :guilabel:`Update Credentials` button."
msgid "**Enable Banking** is a third-party provider aggregating banking information from bank accounts all in one place. It offers non-intrusive connectivity to ASPSPs' official APIs across Europe without storing data."
msgid "**Ponto** is a service that allows companies and professionals to aggregate their accounts in one place and directly see all their transactions within one app. It is a third-party solution that is continuously expanding the number of bank institutions that can be synchronized with Odoo."
msgid "Ponto is a paid third-party provider that can handle the synchronization between your bank accounts and Odoo. `Its pricing is 4€/month per account/integration <https://myponto.com/en#pricing>`_."
msgid "Select your country, your bank institutions, give your consent to Ponto, and follow the steps on-screen to link your bank account with your Ponto account."
msgid "Search your institution, make sure to select the right institution. By selecting the institution, you can verify that the third party provider is Ponto."
msgid "At some point, you will have to authorize the accounts you want to access in Odoo. Please select **all the accounts** you want to synchronize. Even the ones coming from other banking institutions."
msgid "You have to authorize all the accounts you want to access in Odoo, but Odoo will filter the accounts based on the institution you selected in the second step."
msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Online Synchronization` and select the institution you want to fetch the other accounts. Click on *Fetch Accounts* button to start the flow."
msgid "Every **3 months** (90 days) you must re-authorize the connection between your bank account and Ponto. This must be done from the `Ponto website <https://myponto.com>`_. If you do not do this, the synchronization will stop for these accounts."
msgid "**Salt Edge** is a third-party provider that aggregates banking information from your bank accounts. It supports ~5000 institutions in more than 50 countries."
msgid "After giving your phone number, you are asked for an email address. This email address is used to create your Salt Edge account. Please make sure you enter a valid email address, as otherwise, you will not be able to access your Salt Edge account."
msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Online Synchronization` and select the institution you want to update credentials. Click on the *Update Credentials* button to start the flow and follow the steps."
msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Online Synchronization` and select the institution to fetch the new accounts. Click on the *Fetch Accounts* button to start the flow and follow the steps."
msgid "Odoo can't permanently delete the connection you have created with the banking institution. However, it can revoke the consent you gave so that Odoo won't be able to access your account anymore. The error you are seeing is probably a message telling you that the consent was revoked, but the record could not be deleted as it still exists within Salt edge. If you want to remove the connection completely, please connect to your `Salt Edge account <https://www.saltedge.com/dashboard>`_ and manually delete your synchronization. Once this is done, you can go back to Odoo to delete the record."
msgid "You have probably already synchronized your bank account with Salt Edge, please check on your `dashboard <https://www.saltedge.com/dashboard>`_ that you don't already have a connection with the same credentials."
msgid "In case you already have a synchronization with the same credentials present on your Salt Edge dashboard and this synchronization has not been created with Odoo, please delete it and create it from your Odoo database."
msgid "In case you already have a connection with the same credentials present on your Salt Edge dashboard and this synchronization was created with Odoo, you will normally be able to find it by going to :menuselection:`Accounting --> Configuration --> Online Synchronization`. Please make sure to do an *Update Credentials* to reactivate the connection."
msgid "In Odoo, every transaction is recorded in the default currency of the company, and reports are all based on that default currency. When you have a bank account in a foreign currency, for every transaction, Odoo stores two values:"
msgid "Currency rates are updated automatically using the web services of a banking institution. By default, Odoo uses the European Central Bank's web services but other options are available."
msgid "To work with multiple currencies, go to :menuselection:`Accounting --> Configuration --> Settings --> Currencies` and tick :guilabel:`Multi-Currencies`. Under :guilabel:`Post Exchange difference entries in:`, provide a :guilabel:`Journal`, a :guilabel:`Gain Account`, a :guilabel:`Loss Account`, and then click on :guilabel:`Save`."
msgid "Once Odoo is configured to support multiple currencies, they are all created by default, but not necessarily active. To activate the new currencies, click on :guilabel:`Activate Other Currencies` under the :guilabel:`Multi-Currencies` setting or go to :menuselection:`Accounting --> Configuration --> Accounting: Currencies`."
msgid "When the currencies are activated, you can choose to **automate** the currency rate update, or leave it on **manual**. To configure the rate update, go back to :menuselection:`Accounting --> Configuration --> Settings --> Currencies`, check :guilabel:`Automatic Currency Rates`, set :guilabel:`Interval` to your desired frequency, and then click on :guilabel:`Save`. You also have the option to choose the :guilabel:`Service` you wish to obtain currency rates from."
msgid "In the accounting application, go to :menuselection:`Accounting --> Configuration --> Journals` and create a new one. Enter a :guilabel:`Journal Name` and set the :guilabel:`Type` to `Bank`. In the :guilabel:`Journal Entries` tab, enter a **short code**, a **currency**, and then finally click on the :guilabel:`Bank Account` field to create a new account. In the pop-up window of the account creation, enter a name, a code (ex.: 550007), set its type to `Bank and Cash`, set a currency type, and save. When you are back on the **journal**, click on the :guilabel:`Account Number` field, and in the pop-up window, fill out the :guilabel:`Account Number`, :guilabel:`Bank` of your account, and save."
msgid "Upon creation of the journal, Odoo automatically links the bank account to the journal. It can be found under :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts`."
msgid "To pay a bill in a foreign currency, simply select the currency next to the :guilabel:`Journal` field and register the payment. Odoo automatically creates and posts the foreign **exchange gain or loss** as a new journal entry."
msgid "This report gives an overview of all unrealized amounts in a foreign currency on your balance sheet, and allows you to adjust an entry or manually set an exchange rate. To access this report, go to :menuselection:`Reporting --> Management: Unrealized Currency Gains/Losses`. From here, you have access to all open entries in your **balance sheet**."
msgid "If you wish to use a different currency rate than the one set in :menuselection:`Accounting --> Configuration --> Settings --> Currencies`, click the :guilabel:`Exchange Rates` button and change the rate of the foreign currencies in the report."
msgid "When manually changing **exchange rates**, a yellow banner appears allowing you to reset back to Odoo's rate. To do so, simply click on :guilabel:`Reset to Odoo's Rate`."
msgid "In order to update your **balance sheet** with the amount of the :guilabel:`adjustment` column, click on the :guilabel:`Adjustment Entry` button. In the pop-up window, select a :guilabel:`Journal`, :guilabel:`Expense Account` and :guilabel:`Income Account` to calculate and process the **unrealized gains and losses**."
msgid "You can set the date of the report in the :guilabel:`Date` field. Odoo automatically reverses the booking entry to the date set in :guilabel:`Reversal Date`."
msgid "**Bank reconciliation** is the process of matching your :doc:`bank transactions <transactions>` with your business records, such as :doc:`customer invoices <../customer_invoices>`, :doc:`vendor bills <../vendor_bills>`, and :doc:`payments <../payments>`. Not only is this compulsory for most businesses, but it also offers several benefits, such as reduced risk of errors in financial reports, detection of fraudulent activities, and improved cash flow management."
msgid "click the :guilabel:`Reconcile items` button to display all transactions Odoo pre-selected for reconciliation. You can remove the :guilabel:`Not Matched` filter from the search bar to include previously reconciled transactions."
msgid "The counterpart entries section on the bottom right displays the options to match the selected bank transaction. Multiple tabs are available, including :ref:`reconciliation/existing-entries`, :ref:`reconciliation/batch-payments`, :ref:`reconciliation/manual-operations`, and :guilabel:`Discuss`, which contains the chatter for the selected bank transaction."
msgid "The resulting entry section on the top right displays the selected bank transaction matched with the counterpart entries and includes any remaining debits or credits. In this section, you can validate the reconciliation or mark it as :guilabel:`To Check`. Any :ref:`reconciliation model buttons <reconciliation/button>` are also available in the resulting entry section."
msgid "Transactions can be matched automatically with the use of :doc:`reconciliation models <reconciliation_models>`, or they can be matched with :ref:`existing entries <reconciliation/existing-entries>`, :ref:`batch payments <reconciliation/batch-payments>`, :ref:`manual operations <reconciliation/manual-operations>`, and :ref:`reconciliation model buttons <reconciliation/button>`."
msgid "Define the counterpart. There are several options for defining a counterpart, including :ref:`matching existing entries <reconciliation/existing-entries>`, :ref:`manual operations <reconciliation/manual-operations>`, :ref:`batch payments <reconciliation/batch-payments>`, and :ref:`reconciliation model buttons <reconciliation/button>`."
msgid "If the resulting entry isn't fully balanced, balance it by adding another existing counterpart entry or writing it off with a :ref:`manual operation <reconciliation/manual-operations>`."
msgid "If you aren't sure how to reconcile a particular transaction and would like to deal with it later, use the :guilabel:`To Check` button instead. All transactions marked as :guilabel:`To Check` can be displayed using the :guilabel:`To Check` filter."
msgid "Bank transactions are posted on the **journal's suspense account** until reconciliation. At this point, reconciliation modifies the transaction journal entry by replacing the bank suspense account with the corresponding receivable, payable, or outstanding account."
msgid "This tab contains matching entries Odoo automatically pre-selects according to the reconciliation models. The entry order is based on :doc:`reconciliation models <reconciliation_models>`, with suggested entries appearing first."
msgid "`Batch payments <payments/batch-payments>`_ allow you to group different payments to ease reconciliation. Use the :guilabel:`Batch Payments` tab to find batch payments for customers and vendors. Similarly to the :guilabel:`Match Existing Entries` tab, the :guilabel:`Batch Payments` tab has a search bar that allows you to search for specific batch payments."
msgid "If there isn't an existing entry to match the selected transaction, you may instead wish to reconcile the transaction manually by choosing the correct account and amount. Then, complete any of the relevant optional fields."
msgid "You can use the :guilabel:`fully paid` option to reconcile a payment, even in cases where only a partial payment is received. A new line appears in the resulting entry section to reflect the open balance registered on the Account Receivable by default. You can choose another account by clicking on the new line in the resulting entry section and selecting the :guilabel:`Account` to record the open balance."
msgid "Use a :doc:`reconciliation model <reconciliation_models>` button for manual operations that are frequently used. These custom buttons allow you to quickly reconcile bank transactions manually and can also be used in combination with existing entries."
msgid "Reconciliation models are used to automate the :doc:`bank reconciliation <reconciliation>` process, which is especially handy when dealing with recurring entries like bank fees. Reconciliation models can also be helpful in handling :doc:`cash discounts <../customer_invoices/cash_discounts>`."
msgid "The reconciliation models are available by going to :menuselection:`Accounting --> Configuration --> Banks: Reconciliation Models`. For each reconciliation model, a :guilabel:`Type` must be set. Three types of models exist:"
msgid ":guilabel:`Button to generate counterpart entry`: a button is created in the resulting entry section of the bank reconciliation view. If clicked, this button generates a counterpart entry to reconcile with the active transaction based on the rules set in the model. The rules specified in the model determine the counterpart entry's account(s), amount(s), label(s), and analytic distribution;"
msgid ":guilabel:`Rule to suggest counterpart entry`: used for recurring transactions to match the transaction to a new entry based on conditions that must match the information on the transaction;"
msgid ":guilabel:`Rule to match invoices/bills`: used for recurring transactions to match the transaction to existing invoices, bills, or payments based on conditions that must match the information on the transaction."
msgid "In Odoo, different models are available by default depending on the company's fiscal localization. These can be updated if needed. Users can also create their own reconciliation models by clicking :guilabel:`New`."
msgid "If a record matches with several reconciliation models, the first one in the *sequence* of models is applied. You can rearrange the order by dragging and dropping the handle next to the name."
msgid "This model should be at the top of the *sequence* of models, as it enables Odoo to suggest matching existing invoices or bills with a bank transaction based on set conditions."
msgid "Odoo automatically reconciles the payment when the :guilabel:`Auto-validate` option is selected, and the model conditions are perfectly met. In this case, it expects to find on the bank statement's line the invoice/payment's reference (as :guilabel:`Label` is selected) and the partner's name (as :guilabel:`Partner is set` is selected) to suggest the correct counterpart entry and reconcile the payment automatically."
msgid "This model suggests a customer invoice or vendor bill that partially matches the payment when the amount received is slightly lower than the invoice amount, for example in the case of **cash discounts**. The difference is reconciled with the account indicated in the :guilabel:`counterpart entries` tab."
msgid "This model suggests a counterpart entry according to the rules set in the model. In this case, the reconciliation model :guilabel:`Type` is :guilabel:`Rule to suggest counterpart entry`, and the :guilabel:`Label` can be used for example, to identify the information referring to the :guilabel:`Bank fees` in the label of the transaction."
msgid "`Regular expressions <https://regexone.com/>`_, often abbreviated as **Regex**, can be used in Odoo in various ways to search, validate, and manipulate data within the system. Regex can be powerful but also complex, so it's essential to use it judiciously and with a good understanding of the patterns you're working with."
msgid "To use regular expressions in your reconciliation models, set the :guilabel:`Transaction Type` to :guilabel:`Match Regex` and add your expression. Odoo automatically retrieves the transactions that match your Regex expression and the conditions specified in your model."
msgid "Partner mapping allows you to establish rules for automatically matching transactions to the correct partner account, saving time and reducing the risk of errors that can occur during manual reconciliation. For example, you can create a partner mapping rule for incoming payments with specific reference numbers or keywords in the transaction description. When an incoming payment meets these criteria, Odoo automatically maps it to the corresponding customer's account."
msgid "To create a partner mapping rule, go to the :guilabel:`Partner Mapping` tab and enter the :guilabel:`Find Text in Label`, :guilabel:`Find Text in Notes`, and :guilabel:`Partner`."
msgid "Importing transactions from your bank statements allows keeping track of bank account transactions and reconciling them with the ones recorded in your accounting."
msgid ":doc:`Bank synchronization <bank_synchronization>` automates the process. However, if you do not want to use it or if your bank is not yet supported, other options exist:"
msgid "After setting the necessary formatting options and mapping the file columns with their related Odoo fields, you can run a :guilabel:`Test` and :guilabel:`Import` your bank transactions."
msgid "You can also record your bank transactions manually. To do so, go to :guilabel:`Accounting Dashboard`, click on the :guilabel:`Bank` journal, and then on :guilabel:`New`. Make sure to fill out the :guilabel:`Partner` and :guilabel:`Label` fields to ease the reconciliation process."
msgid "A **bank statement** is a document provided by a bank or financial institution that lists the transactions that have occurred in a particular bank account over a specified period of time."
msgid "In Odoo Accounting, it is optional to group transactions by their related statement, but depending on your business flow, you may want to record them for control purposes."
msgid "If you want to compare the ending balances of your bank statements with the ending balances of your financial records, *don't forget to create an opening transaction* to record the bank account balance as of the date you begin synchronizing or importing transactions. This is necessary to ensure the accuracy of your accounting."
msgid "To access a list of statements, go to your :guilabel:`Accounting Dashboard`, click on the vertical ellipsis (:guilabel:`⋮`) button next to the bank or cash journal you want to check, then on :guilabel:`Statements`"
msgid "Open the bank reconciliation view by clicking on the name of the bank journal, and identify the transaction corresponding to the last transaction of your bank statement. Click on the :guilabel:`STATEMENT` button when hovering on the upper separator line."
msgid "Open the list of transactions by clicking on the name of the bank journal and switching to the list view. Select all the transactions corresponding to the bank statement, and, in the :guilabel:`Statement` column, select an existing statement or create a new one by typing its reference, clicking on :guilabel:`Create and edit...`, filling out the statement's details, and saving."
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."
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."
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."
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."
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."
msgid "The system generates invoice which are initially set to the Draft state. While these invoices remain unvalidated, they have no accounting impact within the system. There is nothing to stop users from creating their own draft invoices."
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."
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."
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."
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."
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. \""
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."
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."
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."
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.\""
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."
msgid "**Cash discounts** are reductions in the amount a customer must pay for goods or services offered as an incentive for paying their invoice promptly. These discounts are typically a percentage of the total invoice amount and are applied if the customer pays within a specified time. Cash discounts can help the company maintain a steady cash flow."
msgid "You issue a €100 invoice on the 1st of January. The full payment is due within 30 days, and you also offer a 2% discount if your customer pays you within seven days."
msgid "To grant cash discounts to customers, you must first set up the :ref:`type of tax reduction <cash-discounts/tax-reductions>`, verify the :ref:`gain and loss accounts <cash-discounts/gain-loss-accounts>`, and configure new :ref:`payment terms <cash-discounts/payment-terms>`."
msgid "To configure how the tax reduction is applied, go to :menuselection:`Accounting --> Configuration --> Settings`, and in the :guilabel:`Taxes` section, in the :guilabel:`Cash Discount Tax Reduction` feature, select one of the three following options:"
msgid "The tax is always reduced. The base amount used to compute the tax is the discounted amount, whether the customer benefits from the discount or not."
msgid "The tax is reduced only if the customer pays early. The base amount used to compute the tax is the same as the sale: if the customer benefits from the reduction, then the tax is reduced. This means that, depending on the customer, the tax amount can vary after the invoice is issued."
msgid "You issue a €100 invoice (tax-excluded) on the 1st of January, with a 21% tax rate. The full payment is due within 30 days, and you also offer a 2% discount if your customer pays you within seven days."
msgid ":ref:`Tax grids <tax-returns/tax-grids>`, which are used for the tax report, are correctly computed according to the :ref:`type of tax reduction <cash-discounts/tax-reductions>` you configured."
msgid "The **type of cash discount tax reduction** may be correctly pre-configured, depending on your :ref:`fiscal localization package <fiscal_localizations/packages>`."
msgid "With a cash discount, the amount you earn depends on whether the customer benefits from the cash discount or not. This inevitably leads to gains and losses, which are recorded on default accounts."
msgid "To modify these accounts, go to :menuselection:`Accounting --> Configuration --> Settings`, and in the :guilabel:`Default Accounts` section, select the accounts you want to use for the :guilabel:`Cash Discount Gain account` and :guilabel:`Cash Discount Loss account`."
msgid "Cash discounts are defined on :doc:`payment terms <payment_terms>`. Configure them to your liking by going to :menuselection:`Accounting --> Configuration --> Payment Terms`, and make sure to fill out the fields :guilabel:`Discount %` and :guilabel:`Discount Days`."
msgid "Apply a cash discount to a customer invoice by selecting the :ref:`payment terms you created <cash-discounts/payment-terms>`. Odoo automatically computes the correct amounts, tax amounts, due dates, and accounting records."
msgid "Under the :guilabel:`Journal Items` tab, you can display the discount details by clicking on the \"toggle\" button and adding the :guilabel:`Discount Date` and :guilabel:`Discount Amount` columns."
msgid "When you record a payment or reconcile your bank statements, Odoo takes the customer payment's date into account to define if they can benefit from the cash discount or not."
msgid "If your customer pays the discount amount *after* the discount date, you can always decide whether to mark the invoice as fully paid with a write-off or as partially paid."
msgid "**Cash rounding** is required when the lowest physical denomination of currency, or the smallest coin, is higher than the minimum unit of account."
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."
msgid "When editing a draft invoice, open the *Other Info* tab, go to the *Accounting Information* section, and select the appropriate *Cash Rounding Method*."
msgid "A **credit/debit note**, or **credit/debit memo**, is a document issued to a customer that notifies them that they have been *credited/debited* a certain amount."
msgid "Debit notes are less common but are most frequently used to track debts owed by customers or to vendors because of modifications to confirmed customer invoices or vendor bills."
msgid "Issuing a credit/debit note is the only legal way to cancel, refund, or modify a validated invoice. Do not forget to **register the payment** afterward if you need to send money back to your customer and/or validate the :doc:`return </applications/sales/sales/products_prices/returns>` if a storable product is returned."
msgid "You can create a credit note from scratch by going to :menuselection:`Accounting --> Customers --> Credit Notes`, and by clicking on :guilabel:`Create`. Filling out a credit note form works the same way as an invoice form."
msgid "However, most of the time, credit notes are generated directly from the related invoices. To do so, go to :menuselection:`Accounting --> Customers --> Invoices`, open the related **customer invoice**, and click on :guilabel:`Add Credit Note`."
msgid "A credit note sequence starts with `R` and is followed by the number of the related document (e.g., RINV/2019/0004 is related to the invoice INV/2019/0004)."
msgid "When selecting the :guilabel:`Partial Refund` option, Odoo creates a draft credit note already prefilled with all the necessary information from the original invoice. This is the option to choose if you wish to do a partial refund or if you want to modify any detail of the credit note."
msgid "When selecting the :guilabel:`Full Refund` option, Odoo creates a credit note, automatically validates it, and reconciles it with the related invoice."
msgid "When selecting the :guilabel:`Full refund and new draft invoice` option, Odoo creates a credit note, automatically validates it, reconciles it with the related invoice, and opens a new draft invoice prefilled with the same details from the original invoice."
msgid "You can create a debit note from scratch by going to :menuselection:`Accounting --> Customers --> Invoices` or by clicking on the related invoice you wish to issue a debit note for. On the invoice form view, click :guilabel:`Add debit note`, fill in the information, and click :guilabel:`Create`."
msgid "You can either create a credit note from scratch by going to :menuselection:`Accounting --> Vendors --> Refund`, and by clicking on :guilabel:`Create`; or by opening the related **vendor bill**, and clicking on :guilabel:`Add Credit Note`."
msgid "Go to :menuselection:`Accounting --> Vendors --> Bills`, open the related bill you wish to record a debit note for, and click :guilabel:`Add debit note`. Fill in the information, and click :guilabel:`Create debit note`."
msgid "Issuing a credit/debit note from an invoice/bill creates a **reverse entry** that zeroes out the journal items generated by the original invoice."
msgid "Companies often have multiple locations, and it is common that a customer invoice should be sent to one address and the delivery should be sent to another. Odoo's **Customer Addresses** feature is designed to handle this scenario by making it easy to specify which address to use for each case."
msgid "To specify a sales order's invoice and delivery addresses, first go to :menuselection:`Accounting --> Configuration --> Settings`. In the :guilabel:`Customer Invoices` section, enable :guilabel:`Customer Addresses` and click :guilabel:`Save`."
msgid "On quotations and sales orders, there are now fields for :guilabel:`Invoice Address` and :guilabel:`Delivery Address`. If the customer has an invoice or delivery address listed on their contact record, the corresponding field will use that address by default, but any contact's address can be used instead."
msgid "Delivery orders and their delivery slip reports use the address set as the :guilabel:`Delivery Address` on the sales order. By default, invoice reports show both the shipping address and the invoice address to assure the customer that the delivery is going to the correct location."
msgid "Emails also go to different addresses. The quotation and sales order are sent to the main contact's email, as usual, but the invoice is sent to the email of the address set as the :guilabel:`Invoice Address` on the sales order."
msgid "**Deferred revenues**, or **unearned revenue**, are payments made in advance by customers for products yet to deliver or services yet to render."
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."
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."
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."
msgid "Odoo Accounting handles deferred revenues by spreading them in multiple entries that are automatically created in *draft mode* and then posted periodically."
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."
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."
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."
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."
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."
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."
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."
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`_)."
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."
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*."
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."
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."
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`."
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."
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`_)."
msgid "EDI, or electronic data interchange, is the inter-company communication of business documents, such as purchase orders and invoices, in a standard format. Sending documents according to an EDI standard ensures that the machine receiving the message can interpret the information correctly. Various EDI file formats exist and are available depending on your company's country."
msgid "EDI feature enables automating the administration between companies and might also be required by some governments for fiscal control or to facilitate the administration."
msgid "Go to :menuselection:`Accounting --> Configuration --> Journals --> Customer Invoices --> Advanced Settings --> Electronic Invoicing` and enable the formats you need for this journal."
msgid "Once an electronic invoicing format is enabled, XML documents are generated when clicking on :guilabel:`Confirm` in documents such as invoices, credit notes, etc. These documents are either visible in the attachment section, or embedded in the PDF."
msgid "For E-FFF, the xml file only appears after having generated the PDF (:guilabel:`Print` or :guilabel:`Send & Print` button), since the PDF needs to be embedded inside the xml."
msgid "Every PDF generated from Odoo contains a :guilabel:`Factur-X` XML file (for interoperability purpose). For German and French companies, the option :guilabel:`Factur-X (PDF/A-3)` in addition enables validation checks on the invoice and generates a PDF/A-3 compliant file, required by plaftorms like Chorus Pro."
msgid "European Payments Council quick response codes, or **EPC QR codes**, are two-dimensional barcodes that customers can scan with their **mobile banking applications** to initiate a **SEPA credit transfer (SCT)** and pay their invoices instantly."
msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and activate the :guilabel:`QR Codes` feature in the :guilabel:`Customer Payments` section."
msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open your bank journal, then fill out the :guilabel:`Account Number` and :guilabel:`Bank` under the :guilabel:`Bank Account Number` column."
msgid "EPC QR codes are added automatically to your invoices. Customers whose bank supports making payments via EPC QR codes will be able to scan the code and pay the invoice."
msgid "In the :guilabel:`Other Info` tab, the account indicated in the :guilabel:`Recipient Bank` field is used to receive your customer's payment. Odoo automatically populates this field with your IBAN by default and uses it to generate the EPC QR code."
msgid "If you want to issue an invoice without an EPC QR code, remove the IBAN indicated in the :guilabel:`Recipient Bank` field, under the :guilabel:`Other Info` tab of the invoice."
msgid ":abbr:`Incoterms (International Commercial Terms)` are standardized trade terms used in international transactions to define the rights and responsibilities of buyers and sellers. They establish the obligations related to the delivery of goods, the transfer of risks, and the distribution of costs between the parties involved. Incoterms specify important details, such as the point at which the risk and costs transfer from the seller to the buyer, the responsibility for transportation, insurance, customs clearance, and other relevant aspects of the transaction."
msgid "You can set a default Incoterm rule to **automatically** populate the Incoterm field on all newly created invoices and bills. Under :menuselection:`Accounting/Invoicing --> Configuration --> Settings`, scroll down to the :guilabel:`Customer Invoices` section, and select an Incoterm in the :guilabel:`Default Incoterm` field."
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)."
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:"
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."
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)."
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."
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."
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."
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."
msgid "For subscriptions, an invoice is triggered periodically, automatically. The frequency of the invoicing and the services/products invoiced are defined on the contract."
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."
msgid "It is useful for people who use a numbering from another software and who want to continue the current year without starting over from the beginning."
msgid "Odoo uses OCR and artificial intelligence technologies to recognize the content of the documents. Vendor bills and customer invoices forms are automatically created and populated based on scanned invoices."
msgid "A 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."
msgid "Payment terms are not to be confused with :doc:`down payment invoices </applications/sales/sales/invoicing/down_payment>`. If, for a specific order, you issue multiple invoices to your customer, that is neither a payment term nor an installment plan but an invoicing policy."
msgid "This page is about the *payment terms* feature, not :doc:`terms & conditions <terms_conditions>`, which can be used to declare contractual obligations regarding content use, return policies, and other policies surrounding the sale of goods and services."
msgid "Tick the :guilabel:`Display terms on invoice` checkbox to display a breakdown of each payment and its due date on the invoice report, if desired."
msgid "In the :guilabel:`Terms` section, add a set of rules (terms) to define what needs to be paid and by which due date(s). Defining terms automatically calculates the payments' due date(s). This is particularly helpful for managing **installment plans** (:dfn:`payment terms with multiple terms`)."
msgid "To add a term, click on :guilabel:`Add a line`, define its :guilabel:`Due Type` and :guilabel:`Value`, and fill out the appropriate fields to define when the term is due, including any :doc:`discounts <cash_discounts>`. Due dates are calculated by taking the invoice/bill date, first adding the :guilabel:`Months`, and then adding the :guilabel:`Days`. If the :guilabel:`End of month` toggle is enabled, the due date will then be the end of that month, plus any :guilabel:`Days after End of month`."
msgid "To test that your payment terms are configured correctly, enter an invoice amount and invoice date in the :guilabel:`Example` section to generate the payments that would be due and their due dates using these payment terms."
msgid "**Contacts:** To automatically set default payment terms on a contact's new sales orders, invoices, and bills. This can be modified in the contact form, under the :guilabel:`Sales & Purchase` tab."
msgid "Setting payment terms on a vendor bill is mostly useful for managing vendor terms with multiple installments or cash discounts. Otherwise, manually setting the **due date** is enough. If payment terms are already defined, empty the field to select a date."
msgid "This makes for easier :doc:`follow-ups </applications/finance/accounting/payments/follow_up>` and :doc:`reconciliation </applications/finance/accounting/bank/reconciliation>` since Odoo takes each due date into account, rather than just the balance due date. It also helps to get an accurate :ref:`aged receivable report <customer-invoices/aging-report>`."
msgid "In this example, an invoice of $1000 has been issued with the following payment terms: *30% is due on the day of issuance, and the balance is due at the end of the following month.*"
msgid "Sending direct mail can be an effective strategy for grabbing people's attention, especially when their email inboxes are overflowing. With Odoo, you have the ability to send invoices and follow-up reports through postal mail worldwide, all from within your database."
msgid "Open your invoice, click on :guilabel:`Send & Print` and select :guilabel:`Send by Post`. Make sure your customer’s address is set correctly, including the country, before sending the letter."
msgid "Margins must be **5 mm** on all sides. As Odoo forces the outer margins by filling them with white before sending the snailmail, it can results in the user's custom being cut off if it protrudes into the margins. To check the margins, activate the :ref:`developer mode <developer-mode>`, go to :menuselection:`General Settings --> Technical --> Reporting section: Paper Format`."
msgid "Pingen (Odoo Snailmail service provider) scans the area to process the address, so if something gets written outside the area, it is not counted as part of the address."
msgid "Snailmail is an :doc:`/applications/essentials/in_app_purchase` service that requires prepaid stamps (=credits) to work. Sending one document consumes one stamp."
msgid "To buy stamps, go to :menuselection:`Accounting --> Configuration --> Settings --> Customer invoices: Snailmail`, click on :guilabel:`Buy credits`, or go to :menuselection:`Settings --> In-App Purchases: Odoo IAP`, and click on :guilabel:`View my Services`."
msgid "Specifying terms and conditions is essential to establish important contractual points, such as return and refunds, warranty, and after-sale services."
msgid "You can add default terms and conditions at the bottom of all customer invoices, sales orders, and quotations, either as text or a link to a web page."
msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the :guilabel:`Customer Invoices`, enable :guilabel:`Default Terms & Conditions`. By default, the :guilabel:`Add a Note` option is selected, and the terms and conditions are displayed at the bottom of the document. Enter the terms and conditions in the text box below."
msgid "You can also add a PDF version of your terms and conditions as an attachment when sending the document via email. Edit the email templates if you want to include them by default."
msgid "Alternatively, to display the terms and conditions on a web page, select the :guilabel:`Add a link to a Web Page` option and click :guilabel:`Save`. Click :guilabel:`Update Terms`, edit the content, and click :guilabel:`Save`. The link to that page is then added as a note in your document."
msgid "You can edit the layout and content of the page using the :doc:`Website </applications/websites/website>` app. If the Website app is activated, the :guilabel:`Edit in Website Builder` option then replaces :guilabel:`Update Terms`."
msgid "When you first open your Odoo Accounting app, the :guilabel:`Accounting Dashboard` welcomes you with a step-by-step onboarding banner, a wizard that helps you get started. This onboarding banner is displayed until you choose to close it."
msgid "The settings visible in the onboarding banner can still be modified later by going to :menuselection:`Accounting --> Configuration --> Settings`."
msgid "Odoo Accounting automatically installs the appropriate **Fiscal Localization Package** for your company, according to the country selected at the creation of the database. This way, the right accounts, reports, and taxes are ready-to-go. :ref:`Click here <fiscal_localizations/packages>` for more information about Fiscal Localization Packages."
msgid "Define the **Fiscal Years**’ opening and closing dates, which are used to generate reports automatically, and set your **Tax Return Periodicity**, along with a reminder to never miss a tax return deadline."
msgid "You can also change these settings by going to :menuselection:`Accounting --> Configuration --> Settings --> Fiscal Periods` and updating the values."
msgid "Connect your bank account to your database and have your bank statements synced automatically. To do so, find your bank in the list, click :guilabel:`Connect`, and follow the instructions on-screen."
msgid "If your Bank Institution can’t be synchronized automatically, or if you prefer not to sync it with your database, you can also configure your bank account manually by typing its name, clicking :guilabel:`Create your Bank Account`, and filling out the form."
msgid ":guilabel:`Bank`: click :guilabel:`Create and edit` to configure the bank's details. Add the bank institution's :guilabel:`Name` and its :guilabel:`Identifier Code` (BIC or SWIFT)."
msgid ":guilabel:`Code`: this code is your Journal's :guilabel:`Short Code`, as displayed in Odoo. By default, Odoo creates a new Journal with this short code."
msgid ":guilabel:`Journal`: This field is displayed if you have an existing bank journal that is not linked yet to a bank account. If so, then select the :guilabel:`Journal` you want to use to record the financial transactions linked to this bank account or create a new one by clicking :guilabel:`Create and Edit`."
msgid "This menu allows you to create new taxes, (de)activate, or modify existing taxes. Depending on the :doc:`localization package <../fiscal_localizations>` installed on your database, taxes required for your country are already configured."
msgid "Basic settings are displayed on this page to help you review your Chart of Accounts. To access all the settings of an account, click on the :guilabel:`Setup` button at the end of the line."
msgid "There is another step-by-step onboarding banner that helps you take advantage of your Odoo Invoicing and Accounting apps. The Invoicing onboarding banner is the one that welcomes you if you use the Invoicing app rather than the Accounting app."
msgid "This form allows you to add your company’s details, such as the name, address, logo, website, phone number, email address, and Tax ID or VAT number. These details are then displayed on your documents, such as invoices."
msgid "You can also change the company's details by going to :menuselection:`Settings --> General Settings`, scrolling down to the :guilabel:`Companies` section, and :guilabel:`Update Info`."
msgid "Use this button to create and link a bank account in Odoo. To add additional bank accounts, go to :guilabel:`Invoicing --> Configuration --> Add a Bank Account` and :ref:`configure the fields <bank_accounts/create>`."
msgid "You can also change the invoice layout by going to :menuselection:`Settings --> General Settings`, scrolling down to the :guilabel:`Companies` section, and clicking :guilabel:`Configure Document Layout`."
msgid "Add your **bank account number** and a link to your **General Terms & Condition** in the footer. This way, your contacts can find the full content of your GT&C online without having to print them on the invoices you issue."
msgid "*Average cost valuation* (AVCO) is an inventory valuation method that evaluates cost based on the total cost of goods bought or produced during a period, divided by the total number of items on-hand. Inventory valuation is used to:"
msgid "Because |AVCO| uses the weighted average to evaluate the cost, it is a good fit for companies that sell only a few different products in large quantities. In Odoo, this costing analysis is *automatically updated* each time products are received."
msgid "Thus, when shipments are returned to their supplier, Odoo automatically generates accounting entries to reflect the change in inventory valuation. However, Odoo does **not** automatically update the |AVCO| calculation, because :ref:`this can potentially create inconsistencies with inventory valuation <inventory/avg_price/leaving_inventory>`."
msgid "This document addresses a specific use case for theoretical purposes. For instructions on how to set up and use |AVCO|, refer to the :doc:`inventory valuation configuration <../../../inventory_and_mrp/inventory/product_management/inventory_valuation/inventory_valuation_config>` doc."
msgid "To use average cost inventory valuation on a product, navigate to :menuselection:`Inventory --> Configuration --> Product Categories` and select the category that will be using |AVCO|. On the product category page, set :guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory Valuation` to `Automated`."
msgid "The average cost method adjusts the inventory valuation when products are received in the warehouse. This section explains how it works, but if the explanation is unnecessary, skip to the :ref:`return to supplier use case <inventory/avg_cost/return>` section."
msgid "**Purchase Price**: estimated price of products at the reception of products (since vendor bills may arrive later). The amount includes not only the price for the products, but also added costs, such as shipping, taxes, and :ref:`landed costs <inventory/reporting/landed_costs>`. At reception of the vendor bill, this price is adjusted;"
msgid "When products leave the warehouse, the average cost **does not** change. Read about why the average cost valuation is **not** adjusted :ref:`here <inventory/avg_price/leaving_inventory>`."
msgid "To understand how the average cost of a product changes with each shipment, consider the following table of warehouse operations and stock moves. Each is a different example of how the average cost valuation is affected."
msgid "In the first warehouse operation, `8` tables are received at `$10` each. The average cost is calculated using the :ref:`formula <inventory/avg_cost/formula>`:"
msgid "In the table's :guilabel:`Product Category` field in the :guilabel:`General Information` tab of the product form, click the :guilabel:`➡️ (arrow)` icon, to open an :guilabel:`External Link` to edit the product category. Set the :guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory Valuation` to `Automated`."
msgid "Next, check the inventory valuation record generated by the product reception by navigating to :menuselection:`Inventory --> Reporting --> Inventory Valuation`. Select the drop-down for `Table`, and view the :guilabel:`Total Value` column for the *valuation layer* (:dfn:`inventory valuation at a specific point in time = on-hand quantity * unit price`). The 8 tables in-stock are worth $80."
msgid "When the product category's :guilabel:`Costing Method` is set to :guilabel:`AVCO`, then the average cost of a product is also displayed on the :guilabel:`Cost` field, under the :guilabel:`General Information` tab, on the product page itself."
msgid "For outgoing shipments, :ref:`outbound products have no effect on the average cost valuation <inventory/avg_cost/definite_rule>`. Although the average cost valuation is not recalculated, the inventory value still decreases because the product is removed from stock and delivered to the customer location."
msgid "Because 10 tables are being sent out to customers, the *incoming quantity* is `-10`. The previous average cost (`$12`) is used in lieu of a vendor's *purchase price*;"
msgid "Only `2` tables remain after shipping out `10` tables from `12`. So the current *inventory value* (`$24`) is divided by the on-hand quantity (`2`);"
msgid "To verify this in Odoo, sell `10` tables in the *Sales* app, validate the delivery, and then review the inventory valuation record by going to in :menuselection:`Inventory --> Reporting --> Inventory Valuation`. In the topmost valuation layer, delivering `10` tables reduces the product's value by `-$120`."
msgid "**Note**: What is not represented in this stock valuation record is the revenue made from this sale, so this decrease is not a loss to the company."
msgid "Because the price paid to suppliers can differ from the price the product is valued at with the |AVCO| method, Odoo handles returned items in a specific way."
msgid "In other words, returns to vendors are perceived by Odoo as another form of a product exiting the warehouse. To Odoo, because the table is valued at $12 per unit, the inventory value is reduced by `$12` when the product is returned; the initial purchase price of `$10` is unrelated to the table's average cost."
msgid "To return a single table that was purchased for `$10`, navigate to the receipt in the *Inventory* app for the :ref:`8 tables purchased in Exercise 1 <inventory/avg_cost/ex-1>` by going to the :guilabel:`Inventory Overview`, clicking on :guilabel:`Receipts`, and selecting the desired receipt."
msgid "Then, click :guilabel:`Return` on the validated delivery order, and modify the quantity to `1` in the reverse transfer window. This creates an outgoing shipment for the table. Select :guilabel:`Validate` to confirm the outgoing shipment."
msgid "Return to :menuselection:`Inventory --> Reporting --> Inventory Valuation` to see how the outgoing shipment decreases the inventory value by $12."
msgid "To demonstrate this error, the table below displays a scenario in which 1 table is shipped to a customer and another is returned to a supplier at the purchased price."
msgid "Use the average cost to value the return. This does not mean the company gets $12 back for a $10 purchase; the item returned for $10 is valued internally at $12. The inventory value change represents a product worth $12 no longer being accounted for in company assets."
msgid "In addition to using |AVCO|, companies that use **Anglo-Saxon accounting** also keep a holding account that tracks the amount to be paid to vendors. Once a vendor delivers an order, **inventory value** increases based on the vendor price of the products that have entered the stock. The holding account (called **stock input**) is credited and only reconciled once the vendor bill is received."
msgid "The table below reflects journal entries and accounts. The *stock input* account stores the money intended to pay vendors when the vendor bill has not yet been received. To balance accounts when returning products that have a price difference between the price the product is **valued at** and the price it was bought for, a *price difference* account is created."
msgid "At product reception, Odoo ensures companies can pay for goods that were purchased by preemptively moving an amount matching the price of received goods into the :doc:`liability account </applications/finance/accounting/get_started/cheat_sheet>`, **Stock Input**. Then, once the bill has been received, the amount in the holding account is transferred to *Accounts Payable*. Transfers into this account means the bill has been paid. **Stock Input** is reconciled once the vendor bill is received."
msgid "Inventory valuation is a method of calculating how much each in-stock product is worth internally. Since there is a difference between the price the product is **valuated at** and the price the product was actually **purchased for**, the **Inventory Valuation** account is unrelated to the crediting and debiting operations of the **Stock Input** account."
msgid "Odoo generates an accounting journal entry when shipments that use |AVCO| costing method are received. Configure a :guilabel:`Price Difference Account` by selecting the :guilabel:`➡️ (arrow)` icon next to the :guilabel:`Product Category` field on the product page."
msgid "Under :guilabel:`Account Properties`, create a new :guilabel:`Price Difference Account` by typing in the name of the account and clicking :guilabel:`Create and Edit`. Then set the account :guilabel:`Type` as `Expenses`, and click :guilabel:`Save`."
msgid "Then, receive the shipment in the *Purchase* app or *Inventory* app, and navigate to the :menuselection:`Accounting app --> Accounting --> Journal Entries`. In the list, find the :guilabel:`Reference` that matches the warehouse reception operation for the relevant product."
msgid "Click on the line for 8 tables. This accounting journal entry shows that when the 8 tables were received, the `Stock Valuation` account increased by `$80`. Conversely, the **Stock Input** account (set as `Stock Interim (Received)` account by default) is credited `$80`."
msgid "In this example, a company starts with zero units of a product, table, in stock. Then, 8 tables are received from the vendor. When the bill is received from vendor for 8 tables:"
msgid "Credit **Accounts payable** `$80`. This account stores the amount the company owes others, so accountants use the amount to write checks to vendors."
msgid "Once the vendor requests payment, navigate to the :menuselection:`Purchase app --> Orders --> Purchase` and select the :abbr:`PO (Purchase Order)` for 8 tables. Inside the :abbr:`PO (Purchase Order)`, select :guilabel:`Create Bill`."
msgid "Switch to the :guilabel:`Journal Items` tab to view how `$80` is transferred from the holding account, `Stock Interim (Received)` to `Accounts Payable`. :guilabel:`Confirm` the bill to record the payment to the vendor."
msgid "In the :ref:`above example table <inventory/avg_price/price-table>`, when 10 products are delivered to a customer, the **Stock Input** account is untouched because there are no new products coming in. To put it simply:"
msgid "In the accounting journal entry invoicing a customer for 10 tables, the accounts **Product Sales**, **Tax Received**, and **Accounts Receivable** all pertain to the sale of the product. **Accounts Receivable** is the account where the customer payment will be received."
msgid "Anglo-Saxon accounting recognizes the cost of goods sold (COGS) once the sale is made. So, up until the product is sold, scrapped, or returned, costs of keeping the product in stock are not accounted for. The **Expense** account is debited `$120` to log the costs of storing 10 tables during this period of time."
msgid "In the :ref:`above example table <inventory/avg_price/price-table>`, when returning 1 product to a vendor purchased at `$10`, a company expects `$10` in the **Accounts Payable** account from the vendor. However, **Stock Input** account must be debited `$12` because the average cost is `$12` at the time of the return. The missing `$2` is accounted for in the :guilabel:`Price Difference Account`, which is set up in the product's :guilabel:`Product Category`."
msgid "Behavior of *price difference accounts* varies from localization. In this case, the account is intended to store differences between vendor price and *automated* inventory valuation methods."
msgid "Debit **Stock Input** account `$10` to move the table from stock to stock input. This move is to indicate that the table is to be processed for an outgoing shipment."
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. The chart of accounts can be found under :menuselection:`Accounting-->Configuration-->Chart of Accounts`."
msgid "When browsing your chart of accounts, you can sort the accounts by :guilabel:`Code`, :guilabel:`Account Name`, or :guilabel:`Type`, but other options are available in the drop-down menu :guilabel:`(⋮)`."
msgid "The country you select during the creation of your database (or additional company in your database) determines which :doc:`fiscal localization package <../../fiscal_localizations>` 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."
msgid "To create a new account, go to :menuselection:`Accounting-->Configuration-->Chart of Accounts`, click :guilabel:`Create`, and fill in (at the minimum) the required fields (:guilabel:`Code, Account Name, Type`)."
msgid "Some **account types** can **automate** the creation of :ref:`assets <assets-automation>` entries, :ref:`deferred expenses <deferred-expenses-automation>` entries, and :ref:`deferred revenues <deferred-revenues-automation>` entries. To **automate** entries, click :guilabel:`Setup` on an account line and go to the :guilabel:`Automation` tab."
msgid ":guilabel:`Create in draft`: whenever a transaction is posted on the account, a draft entry is created but not validated. You must first fill out the corresponding form."
msgid ":guilabel:`Create and validate`: you must also select a :guilabel:`Deferred Expense Model`. Whenever a transaction is posted on the account, an entry is created and immediately validated."
msgid "In the :guilabel:`Setup` menu of an account, select a **default tax** to be applied when this account is chosen for a product sale or purchase."
msgid "Some accounting reports require **tags** to be set on the relevant accounts. To add a tag, under :guilabel:`Setup`, click the :guilabel:`Tags` field and select an existing tag or :guilabel:`Create` a new one."
msgid "**Account groups** are useful to list multiple accounts as *sub-accounts* of a bigger account and thus consolidate reports such as the **Trial Balance**. By default, groups are handled automatically based on the code of the group. For example, a new account `131200` is going to be part of the group `131000`. You can attribute a specific group to an account in the :guilabel:`Group` field under :guilabel:`Setup`."
msgid "To create a new account group, activate :ref:`developer mode <developer-mode>` and head to :menuselection:`Accounting app-->Configuration-->Account Groups`. Here, create a new group and enter the :guilabel:`name, code prefix, and company` to which that group account should be available. Note that you must enter the same code prefix in both :guilabel:`From` and :guilabel:`to` fields."
msgid "To display your **Trial Balance** report with your account groups, go to :menuselection:`Accounting-->Reporting-->Trial Balance`, then open the :guilabel:`Options` menu and select :guilabel:`Hierarchy and Subtotals`."
msgid "For example, an invoice paid with a credit card can be marked as :guilabel:`paid` if reconciled with its payment. Therefore, the account used to record credit card payments needs to be configured as **allowing reconciliation**."
msgid "To do so, check the :guilabel:`Allow Reconciliation` box in the account's settings, and :guilabel:`Save`; or enable the button from the chart of accounts view."
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: check the :guilabel:`Deprecated` box in the account's settings, and :guilabel:`Save`."
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)."
msgid "**Assets** represent the company's wealth and the goods it owns. Fixed assets include buildings and offices, while current assets include bank accounts and cash. The money owed by a client is an asset. An employee is not an asset."
msgid "**Liabilities** are obligations from past events that the company will have to pay in the future (utility bills, debts, unpaid suppliers). Liabilities could also be defined as a source of financing which is provided to the company, also called *leverage*."
msgid "**Equity** is the amount of the funds contributed by the owners of the company (founders or shareholders) plus previously retained earnings (or losses). Each year, net profits (or losses) may be reported as retained earnings or distributed to the shareholders (as a dividend)."
msgid "An **asset** is a resource with economic value that an individual, corporation, or country owns or controls with the expectation that it will provide a future benefit. Assets are reported on a company's balance sheet. They are bought or created to increase a firm's value or benefit its operations."
msgid "The **cost of goods sold** (COGS, or also known as \"Cost of Sale\") refers to the sale of goods' costs (e.g., the cost of the materials and labor used to create the goods)."
msgid "**Operating expenses** (OPEX) include administration, sales and R&D salaries, rent and utilities, miscellaneous costs, insurances, and anything beyond the costs of products sold or the cost of sale."
msgid "The **chart of accounts** lists all the company's accounts: both Balance sheet accounts and P&L accounts. Every transaction is recorded by debiting and crediting multiple accounts in a journal entry. In a way, a chart of accounts is like a company's DNA!"
msgid "Every account listed in the chart of accounts belongs to a specific category. In Odoo, each account has a unique code and belongs to one of these categories:"
msgid "**Subordinated debts** are the amount of money lent by a third party to a company to finance its activities. In the event of the dissolution of a company, these third parties are reimbursed before the shareholders."
msgid "**Fixed assets** are tangible (i.e., physical) items or properties that a company purchases and uses to produce its goods and services. Fixed assets are long-term assets. This means the assets have a useful life of more than one year. They also include properties, plants, and equipments (also known as \"PP&E\") and are recorded on the balance sheet with that classification."
msgid "The **current assets** account is a balance sheet line item listed under the Assets section, which accounts for all company-owned assets that can be converted to cash within one year. Current assets include cash, cash equivalents, accounts receivable, stock inventory, marketable securities, prepaid liabilities, and other liquid assets."
msgid "**Current liabilities** are a company's short-term financial obligations due within one year. An example of a current liability is money owed to suppliers in the form of accounts payable."
msgid "A **bank account** is a financial account maintained by a bank or other financial institution in which the financial transactions between the bank and a customer are recorded."
msgid "A **cash account**, or cash book, may refer to a ledger in which all cash transactions are recorded. The cash account includes both the cash receipts and the cash payment journals."
msgid "An **expense** is the costs of operations a company bears to generate revenues. It is simply defined as the cost one is required to spend on obtaining something. Common expenses include supplier payments, employee wages, factory leases, and equipment depreciation."
msgid "The term \"**income**\" generally refers to the amount of money, property, and other transfers of value received over a set period of time in exchange for services or products."
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."
msgid ":doc:`Reconciliation <../../accounting/bank/reconciliation>` is the process of linking journal items of a specific account and matching credits and debits."
msgid "Its primary purpose is to link payments to their related invoices to mark them as paid. This is done by doing a reconciliation on the accounts receivable account and/or the accounts payable account."
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:"
msgid "**matched with a previously recorded payment**: a payment is registered when a check is received from a customer, then matched when checking the bank statement."
msgid "**recorded as a new payment**: the payment's journal entry is created and reconciled with the related invoice when processing the bank statement."
msgid "Odoo should automatically reconcile most transactions; only a few should need manual review. When the bank reconciliation process is finished, the balance on the bank account in Odoo should match the bank statement's balance."
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."
msgid "Odoo allows you to issue invoices, receive bills, and record transactions in currencies other than the main currency configured for your company. You can also set up bank accounts in other currencies and run reports on your foreign currency activities."
msgid "The **main currency** is defined by default according to the company's country. You can change it by going to :menuselection:`Accounting --> Configuration --> Settings --> Currencies` and changing the currency in the :guilabel:`Main Currency` setting."
msgid "Go to :menuselection:`Accounting --> Configuration --> Currencies`, and enable the currencies you wish to use by toggling the :guilabel:`Active` button."
msgid "To manually create and set a currency rate, go to :menuselection:`Accounting --> Configuration --> Currencies`, click on the currency you wish to change the rate of, and under the :guilabel:`Rates` tab, click :guilabel:`Add a line` to create a new rate."
msgid "When you activate a second currency for the first time, :guilabel:`Automatic Currency Rates` appears under :menuselection:`Accounting Dashboard --> Configuration --> Settings --> Currencies`. By default, you have to click on the **Update now** button (:guilabel:`🗘`) to update the rates."
msgid "Odoo can update the rates at regular intervals. To do so, change the :guilabel:`Interval` from :guilabel:`Manually` to :guilabel:`Daily`, :guilabel:`Weekly`, or :guilabel:`Monthly`. You can also select the web service from which you want to retrieve the latest currency rates by clicking on the :guilabel:`Service` field."
msgid "You can define which journal and accounts to use to **post exchange difference entries** by going to :menuselection:`Accounting --> Configuration --> Settings --> Default Accounts` and editing the :guilabel:`Journal`, :guilabel:`Gain Account`, and :guilabel:`Loss Account`."
msgid "If you receive a payment for a customer invoice one month after it was issued, the exchange rate has likely changed since. Therefore, this fluctuation implies some profit or loss due to the exchange difference, which Odoo automatically records in the default **Exchange Difference** journal."
msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Charts of Accounts` and select a currency in the field :guilabel:`Account Currency`. If left empty, all active currencies are handled instead of just one."
msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open the journal you want to edit, and select a currency in the field :guilabel:`Currency`."
msgid "To register a payment in a currency other than your company's main currency, click on the :guilabel:`Register Payment` payment button of your document and, in the pop-up window, select a **currency** in the :guilabel:`Amount` field."
msgid "When creating or importing bank transactions, the amount is in the company's main currency. To input a **foreign currency**, select a currency in the :guilabel:`Foreign Currency`. Once selected, enter the :guilabel:`Amount` in your main currency for it to automatically get converted in the foreign currency in the :guilabel:`Amount in Currency field`."
msgid "A **VAT unit** is a group of VAT-taxable enterprises that are legally independent of each other but are closely linked financially, organizationally, and economically and therefore considered the same VAT-taxable enterprise. **VAT units** are not mandatory, but if created, constituent companies of the unit must belong to the same **country**, use the same **currency**, and one company must be designated as the **representative** company of the **VAT unit**. **VAT units** receive a specific **tax ID** intended only for **tax returns**. **Constituent** companies keep their **tax ID** used for **commercial purposes**."
msgid "Enterprise **A** owes €300.000,00 of VAT taxes and enterprise **B** can recover €280.000,00 of VAT taxes. They form up as a **VAT unit** so that the two amounts balance out and must conjointly only pay €20.000,00 of VAT taxes."
msgid "To configure a **VAT unit**, go to :menuselection:`Settings --> General Settings`, scroll down to the :guilabel:`Companies` section, and click :guilabel:`Manage Companies`. Select the company to serve the **representative** role, and in the :guilabel:`General Information` tab, fill in the mandatory fields for the .XML export when exporting the **tax report**: :guilabel:`Company Name`, :guilabel:`Address`, :guilabel:`VAT`, :guilabel:`Currency`, :guilabel:`Phone`, and :guilabel:`Email`."
msgid "Then, click on the :guilabel:`VAT Units` tab, :guilabel:`Add a line`, and either select an existing **VAT unit**, or create a new one. Enter a **name** for the unit, :guilabel:`Country` of the constituent companies and tax report, the :guilabel:`Companies`, the :guilabel:`Main Company` that serves the **representative** role, and the :guilabel:`Tax ID` of the **VAT unit**."
msgid "As transactions between constituents of the same **VAT unit** are not subject to VAT, it is possible to create a :doc:`tax mapping (fiscal position) <../taxes/fiscal_positions>` to avoid the application of VAT on inter-constituent transactions."
msgid "Be sure a constituent company has been selected before, then go to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, and :guilabel:`Create` a new **fiscal position**. Click the :guilabel:`Tax Mapping` tab, select the :guilabel:`Tax on Product` usually applied for **non-constituent** transactions, and in :guilabel:`Tax to Apply`, select the 0% tax to apply for **constituent** transactions."
msgid "Then, assign the fiscal position by opening the **Contacts** app. Search for a **constituent** company, and open the contact's **card**. Click the :guilabel:`Sales & Purchase` tab, and in the :guilabel:`Fiscal Position` field, input the **fiscal position** created for the **VAT unit**. Repeat the process for each **constituent** company card form, on each company database."
msgid "The **representative** company can access the aggregated tax report of the **VAT unit** by going to :menuselection:`Accounting --> Reporting --> Tax Report`, and selecting the **VAT unit** in :guilabel:`Tax Unit`. This report contains the aggregated transactions of all **constituents** and the .XML export contains the name and VAT number of the **main** company."
msgid "If a payment is **linked to an invoice or bill**, it reduces/settles the amount due on the invoice. Multiple payments on the same invoice are possible."
msgid "If a payment is **not linked to an invoice or bill**, the customer has an outstanding credit with the company, or the company has an outstanding debit with a vendor. Those outstanding amounts reduce/settle unpaid invoices/bills."
msgid "When clicking :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a new journal entry and changes the amount due according to the payment amount. The counterpart is reflected in an :ref:`outstanding <bank/outstanding-accounts>` **receipts** or **payments** account. At this point, the customer invoice or vendor bill is marked as :guilabel:`In payment`. Then, when the outstanding account is reconciled with a bank transaction line, the invoice or vendor bill changes to the :guilabel:`Paid` status."
msgid "The :icon:`fa-info-circle` information icon next to the payment line displays more information about the payment. To access additional information, such as the related journal, click :guilabel:`View`."
msgid "If a payment is (un)reconciled in a different currency, a journal entry is automatically created to post the currency exchange gains/losses (reversal) amount."
msgid "If a payment is (un)reconciled and an invoice with cash-basis taxes, a journal entry is automatically created to post the cash-basis tax (reversal) amount."
msgid "If the main bank account is set as an :ref:`outstanding account <bank/outstanding-accounts>`, and the payment is registered in Odoo (not through a related bank transaction), invoices and bills are directly registered as :guilabel:`Paid`."
msgid "When a new payment is registered via :menuselection:`Customers / Vendors --> Payments`, it is not directly linked to an invoice or bill. Instead, the account receivable or the account payable is matched with the **outstanding account** until it is manually matched with its related invoice or bill."
msgid "A blue banner appears when validating a new invoice/bill and an **outstanding payment** exists for this specific customer or vendor. To match it with the invoice or bill, click :guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`."
msgid "Group payments allow combining outgoing and incoming payments from the same contact into a single payment to simplify the process and improve payment usability. To register a group payment:"
msgid "The invoices or bills are now marked as :guilabel:`In payment` until they are reconciled with the corresponding bank transactions. The credit notes or refunds are marked as :guilabel:`Paid`."
msgid "Batch payments allow grouping payments from multiple contacts to ease :doc:`reconciliation <bank/reconciliation>`. They are also useful when depositing :doc:`checks <payments/checks>` to the bank or for :doc:`SEPA payments <payments/pay_sepa>`. To do so, go to :menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors --> Batch Payments`. In the list view of payments, to group several payments in a batch, select them and click :menuselection:`Action --> Create Batch Payment`."
msgid "The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and allows them to be processed individually, matching all payments and invoices in one place. Go to the :guilabel:`Accounting Dashboard`, click the :icon:`fa-ellipsis-v` (:guilabel:`dropdown menu`) button from the :guilabel:`Customer Invoices` or :guilabel:`Vendor Bills` journals, and select :guilabel:`Payments Matching`, or go to :menuselection:`Accounting --> Accounting --> Reconciliation`."
msgid "During the :doc:`reconciliation <bank/reconciliation>`, if the sum of the debits and credits does not match, there is a remaining balance. This either needs to be reconciled at a later date or written off directly."
msgid "Use the batch reconciliation feature to reconcile several outstanding payments or invoices simultaneously for a specific customer or vendor. Go to :menuselection:`Accounting --> Reporting --> Aged Receivable / Aged Payable`. All transactions that have not yet been reconciled for that contact are visible, and when a customer or vendor is selected, the :guilabel:`Reconcile` option is displayed."
msgid "To register a partial payment, click on :guilabel:`Register Payment` from the related invoice or bill. In the case of a partial payment (when the :guilabel:`Amount` paid is less than the total remaining amount on the invoice or the bill), the :guilabel:`Payment Difference` field displays the outstanding balance. There are two options:"
msgid ":guilabel:`Mark as fully paid`: Select an account in the :guilabel:`Post Difference In` field and change the :guilabel:`Label` if needed. A journal entry will be created to balance the accounts payable or receivable with the selected account."
msgid "Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The next step is :doc:`reconciling <bank/reconciliation>` it with the related bank transaction line to finalize the payment workflow and mark the invoice or bill as :guilabel:`Paid`."
msgid "A **batch deposit** is a convenient way to group customer payments and deposit them into your bank account. The feature lets you list multiple payments and generate a detailed deposit slip with a batch reference. This reference can be used when reconciling to match bank statement lines with transactions in the batch deposit."
msgid "Go to :menuselection:`Accounting --> Configuration --> Settings --> Customer Payments` and tick :guilabel:`Batch Payments` to activate the feature."
msgid "Before performing a batch deposit, it is necessary to register each transaction's payment. To do so, open the corresponding customer invoice and click :guilabel:`Register Payment`. In the pop-up window, select the :guilabel:`Journal` linked to your bank account and :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`, and click :guilabel:`Create Payment`."
msgid "To add payments to a batch deposit, go to :menuselection:`Accounting --> Customers --> Batch Payments`, and click :guilabel:`New`. Next, select the :guilabel:`Bank` and choose :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`."
msgid "Once the bank transactions are on your database, you can reconcile bank statement lines with the batch payment. To do so, go to the :guilabel:`Accounting Dashboard` and click :guilabel:`Reconcile Items` on the related bank account. Go to the :guilabel:`Batch Payments` tab to select a specific batch and click :guilabel:`Validate` to finalize the process."
msgid "SEPA, the Single Euro Payments Area, is a payment-integration initiative of the European Union for simplification of bank transfers denominated in euros. With **SEPA Direct Debit** (SDD), your customers can sign a mandate that authorizes you to collect future payments from their bank accounts. This is particularly useful for recurring payments based on a subscription."
msgid "Go to :menuselection:`Accounting app --> Configuration --> Settings`, activate :guilabel:`SEPA Direct Debit (SDD)`, and click on :guilabel:`Save`. Enter your company's :guilabel:`Creditor Identifier`. This number is provided by your bank institution, or the authority responsible for delivering them."
msgid "The :abbr:`SDD (sepa direct debit)` Mandate is the document that your customers sign to authorize you to collect money directly from their bank accounts."
msgid "To create a new mandate, go to :menuselection:`Accounting app --> Customers --> Direct Debit Mandates`, on :guilabel:`Create`, and fill out the form. Export the PDF file by clicking on :guilabel:`Print`. It is then up to your customer to sign this document. Once done, upload the signed file and click on :guilabel:`Validate` to start running the mandate."
msgid "Make sure that the **IBAN bank accounts details** are correctly recorded on the debtor’s contact form, under the :guilabel:`Accounting` tab, and in your own :doc:`Bank Account <../bank>` settings."
msgid "SDD can be used as a payment method both on your **eCommerce** or on the **Customer Portal** by activating SDD as a **Payment Provider**. With this method, your customers can create and sign their mandates themselves."
msgid "To do so, go to :menuselection:`Accounting --> Configuration --> Payment Providers`, click on *SEPA Direct Debit*, and set it up according to your needs. To do so, go to :menuselection:`Accounting app --> Configuration --> Payment Acquirers`, click on :guilabel:`SEPA Direct Debit`."
msgid "Make sure to change the :guilabel:`State` field to :guilabel:`Enabled`, and to check :guilabel:`Online Signature`, as this is necessary to let your customers sign their mandates."
msgid "Direct debit mandates are closed automatically after their :guilabel:`End Date`. If this field is left blank, the mandate keeps being **Active** until it is **Closed** or **Revoked**."
msgid "Clicking on :guilabel:`Close` updates the mandate’s end day to the current day. This means that invoices issued after the present day will not be processed with an SDD payment."
msgid "Clicking on :guilabel:`Revoke` disables the mandate immediately. No SDD payment can be registered anymore, regardless of the invoice’s date. However, payments that have already been registered are still included in the next SDD `.xml` file."
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 <https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-credit-transfer-customer-psp-implementation>`_, which ensures compatibility with the banks."
msgid "To generate your `.xml` file of multiple pending SDD payments, you can create a batch payment. To do so, go to :menuselection:`Accounting app --> Customers --> Payments`, select the needed payments, then click on :guilabel:`Action`, and finally :guilabel:`Create a batch Payment`. Once you click on :guilabel:`Validate`, the `.xml` file is directly available for download."
msgid "There are two ways to handle payments received by checks in Odoo, either by using :ref:`outstanding accounts <checks/outstanding-account>` or by :ref:`bypassing the reconciliation process <checks/reconciliation-bypass>`."
msgid "Both methods produce the same data in your accounting at the end of the process. But if you have checks that have not been cashed in, the **Outstanding Account** method reports these checks in the **Outstanding Receipts** account. However, funds appear in your bank account whether or not they are reconciled, as the bank value is reflected at the moment of the bank statement."
msgid "When you receive a check, you :doc:`record a payment <../bank/reconciliation>` by check on the invoice. Then, when your bank account is credited with the check's amount, you reconcile the payment and statement to move the amount from the **Outstanding Receipt** account to the **Bank** account."
msgid "You can create a new payment method named *Checks* if you would like to identify such payments quickly. To do so, go to :menuselection:`Accounting --> Configuration --> Journals --> Bank`, click the :guilabel:`Incoming Payments` tab, and :guilabel:`Add a line`. As :guilabel:`Payment Method`, select :guilabel:`Manual`, enter `Checks` as name, and :guilabel:`Save`."
msgid "When you receive a check, you :doc:`record a payment <../bank/reconciliation>` on the related invoice. The amount is then moved from the **Account Receivable** to the **Bank** account, bypassing the reconciliation and creating only **one journal entry**."
msgid "To do so, you *must* follow the following setup. Go to :menuselection:`Accounting --> Configuration --> Journals --> Bank`. Click the :guilabel:`Incoming Payments` tab and then :guilabel:`Add a line`, select :guilabel:`Manual` as :guilabel:`Payment Method`, and enter `Checks` as :guilabel:`Name`. Click the toggle menu button, tick :guilabel:`Outstanding Receipts accounts`, and in the :guilabel:`Outstanding Receipts accounts` column, and set the :guilabel:`Bank` account for the **Checks** payment method."
msgid "Once you receive a customer check, go to the related invoice (:menuselection:`Accounting --> Customer --> Invoices)`, and click :guilabel:`Register Payment`. Fill in the payment information:"
msgid "Then, once you receive the bank statements, match this statement with the check of the **Outstanding Receipts** account. This produces the following **journal entry**:"
msgid "If you use this approach to manage received checks, you get the list of checks that have not been cashed in the **Outstanding Receipt** account (accessible, for example, from the general ledger)."
msgid "With this approach, you bypass the use of **outstanding accounts**, effectively getting only one journal entry in your books and bypassing the reconciliation:"
msgid "A follow-up message can be sent to customers when a payment is overdue. Odoo helps you identify late payments and allows you to schedule and send the appropriate reminders using **follow-up actions** that automatically trigger one or more actions according to the number of overdue days. You can send your follow-ups via different means, such as email, post, or SMS."
msgid "To configure a :guilabel:`Follow-Up Action`, go to :menuselection:`Accounting --> Configuration --> Follow-up Levels`, and select or create (a) new follow-up level(s). Several follow-up actions are available by default under the :guilabel:`Notification` tab, and the **name** as well as the **number of days** can be changed. The follow-up :guilabel:`Actions` available are:"
msgid "You can use a pre-filled template for your messages by selecting a :guilabel:`Content Template`. To change the template used, hover over the field and click the :guilabel:`-->`. If enabled, SMS messages have a specific :guilabel:`Sms Template` field."
msgid "It is possible to automatically send a reminder by enabling the :guilabel:`Automatic` option, and attaching the *open* invoice(s) by enabling :guilabel:`Attach Invoices`, within a specific follow-up action."
msgid "By clicking on the :guilabel:`Activity` tab, scheduling activities (tasks) is possible. That way, an activity is automatically scheduled when the follow-up is triggered. To do so, enable :guilabel:`Schedule Activity`, and select a :guilabel:`Responsible` person for the task. Choose an :guilabel:`Activity Type`, and enter a :guilabel:`Summary` on how to handle the activity, if desired."
msgid "Overdue invoices you need to follow up on are available in :menuselection:`Accounting --> Customers --> Follow-up Reports`. By default, Odoo filters by :guilabel:`Overdue Invoices`, but you can also filter by :guilabel:`In need of action` in the :guilabel:`Filters` menu."
msgid "When selecting an invoice, you can see all of the customer's unpaid invoices (overdue or not), with the due dates of late invoices appearing in red. You can exclude invoices from a reminder by clicking :guilabel:`Exclude from Follow-ups`. You can set either :guilabel:`Automatic` or :guilabel:`Manual` reminders as well as a :guilabel:`Responsible` person for that customer."
msgid "You can :guilabel:`Attach Invoices` and change the content templates from this view. When done, click :guilabel:`Send` or :guilabel:`Send & Print`."
msgid "If it is not the right time for a reminder, you can specify the :guilabel:`Next Reminder` date. You will get the next report according to the next reminder date set."
msgid "To know whether a customer usually pays late or not, you can set a trust level by marking them as :guilabel:`Good Debtor`, :guilabel:`Normal Debtor`, or :guilabel:`Bad Debtor` on their follow-up report. To do so, click on the bullet next to the customer's name and select a trust level."
msgid "You can send reminder emails in batches from the :guilabel:`Follow-up Reports` page. To do so, select all the reports you would like to process, click on the :guilabel:`Action` gear icon, and select :guilabel:`Process follow-ups`."
msgid "In order to track vendor conditions, we use **Payment Terms** in Odoo. They allow keeping track of due dates on invoices. Examples of **Payment Terms** are:"
msgid "To create them, go to :menuselection:`Accounting --> Configuration --> Invoicing: Payment Terms` and click on :guilabel:`Create` to add new terms or click existing ones to modify them."
msgid "Once **Payment Terms** are defined, you can assign them to your vendor by default. To do so, go to :menuselection:`Vendors --> Vendors`, select a vendor, click the :guilabel:`Sales & Purchase` tab, and select a specific **Payment Term**. This way, every time you purchase from this vendor, Odoo automatically proposes the chosen Payment Term."
msgid "To track amounts to be paid to the vendors, use the **Aged Payable** report. To access it, go to :menuselection:`Accounting --> Reporting --> Partner Reports: Aged Payable`. This report gives you a summary per vendor of the amounts to pay, compared to their due date (the due date being computed on each bill using the terms). This report tells you how much you will have to pay within the following months."
msgid "You can get a list of all your vendor bills by going to :menuselection:`Vendors --> Bills`. To view only the bills that you need to pay, click :menuselection:`Filters --> Bills to Pay`. To view only overdue payments, select the :guilabel:`Overdue` filter instead."
msgid "In Odoo, internal money transfers can be made in a few clicks. You need at least either two bank accounts, two cash journals, or one bank account and one cash journal."
msgid "An internal transfer account is automatically created on your database based on your company's localization and depending on your country’s legislation. If needed, the default :guilabel:`Internal transfer account` can be modified by going to :menuselection:`Accounting app --> Configuration --> Settings` and then under the :guilabel:`Default Accounts` section."
msgid "At least two bank accounts are needed to make internal transfers. Refer to :doc:`Bank and cash accounts section <../bank>` to see how to add an additional bank account to your database."
msgid "From the Accounting Dashboard, click on the drop-down selection button (:guilabel:`⋮`) on one of your banks. In the :guilabel:`New` column click on :guilabel:`Internal Transfer` and enter the information related to the transfer."
msgid ":guilabel:`Save` and :guilabel:`Confirm` to register your internal transfer. The money is now booked in the transfer account and another payment is **automatically** created in the destination journal (Bank B)."
msgid "There are one outstanding payment and one outstanding receipt pending in your two bank account journals, because the bank statement confirming the sending and receiving of the money has not been booked yet."
msgid "The next step is to book the bank statements to finalize the transaction by creating, :doc:`importing <../bank/transactions>`, or :doc:`synchronizing <../bank/bank_synchronization>` your :guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and click on the :guilabel:`Reconcile` button."
msgid "To make it more convenient for your customers to pay the invoices you issue, you can activate the **Invoice Online Payment** feature, which adds a *Pay Now* button on their **Customer Portal**. This allows your customers to see their invoices online and pay directly with their favorite payment method, making the payment process much easier."
msgid "By default, \":doc:`Wire Transfer </applications/finance/payment_providers/wire_transfer>`\" is the only payment provider activated, but you still have to fill out the payment details."
msgid "To activate the Invoice Online Payment, go to :menuselection:`Accounting --> Configuration --> Settings --> Customer Payments`, enable **Invoice Online Payment**, and click on *Save*."
msgid "After issuing the invoice, click on *Send & Print* and send the invoice by email to the customer. They will receive an email with a link that redirects them to the invoice on their **Customer Portal**."
msgid "Following recent changes in Odoo 16, you might be warned that disabling the :guilabel:`Invoice Online Payment` setting will uninstall modules. If you want to disable the feature without uninstalling modules, follow the steps below to install the module **Payment - Account / Invoice Online Payment Patch**."
msgid "If your Odoo database is created after the module **Payment - Account / Invoice Online Payment Patch** was released, you don't have anything to do."
msgid "To check if the module is already installed, go to :guilabel:`Apps`, remove the `Apps` filter, and search for `account_payment`. If the module **Payment - Account / Invoice Online Payment Patch** is present and marked as installed, your Odoo database is already up-to-date and you are able to disable the feature without side-effect."
msgid "The possibility to disable the :guilabel:`Invoice Online Payment` setting without side-effect is made available through a new Odoo module; to be able to install it, you must make sure that your Odoo source code is up-to-date."
msgid "If you use Odoo with an on-premise setup or through a partner, you must update your installation as detailed in :doc:`this documentation page </administration/on_premise/update>`, or by contacting your integrating partner."
msgid "To do so, activate the :ref:`developer mode <developer-mode>`, and go to :menuselection:`Apps --> Update Apps List`. A wizard will ask for confirmation."
msgid "You should never install new modules in your production database without first testing them in a duplicate or staging environment. For Odoo.com customers, a duplicate database can be created from the database management page. For Odoo.sh users, you should use a staging or duplicate database. For on-premise users, you should use a staging environment---contact your integrating partner for more information regarding how to test a new module in your particular setup."
msgid "The module should now be available in your :guilabel:`Apps` menu. Remove the ``Apps`` filter and search for ``account_payment``; the module :guilabel:`Payment - Account / Invoice Online Payment Patch` should be available for installation. If you cannot find the module after having updated the list of available modules, it means your Odoo source code is not up-to-date; refer to step one of this page."
msgid "Once you decide to pay a supplier bill, you can select to pay by check. You can then print all the payments registered by check. Finally, the bank reconciliation process will match the checks you sent to suppliers with actual bank statements."
msgid "To activate the checks payment method, go to :menuselection:`Accounting --> Configuration --> Settings`, and scroll down to the :guilabel:`Vendor Payments` section. There, you can activate the payment method as well as set up the :guilabel:`Check Layout`."
msgid "Once the :guilabel:`Checks` setting is activated, the **Checks** payment method is automatically set up in the :guilabel:`Outgoing Payments` tabs of **bank** journals."
msgid "Some countries require specific modules to print checks; such modules may be installed by default. For instance, the :guilabel:`U.S. Checks Layout` module is required to print U.S. checks."
msgid "To register a payment, open any supplier bill from the menu :menuselection:`Purchases --> Vendor Bills`. Once the supplier bill is validated, you can register a payment. Set the :guilabel:`Payment Method` to :guilabel:`Checks` and validate the payment."
msgid "On your :guilabel:`Accounting Dashboard` in the :guilabel:`Bank` Journal, you can see the number of checks registered. By clicking on :guilabel:`Checks to print` you have got the possibility to print the reconciled checks."
msgid "SEPA, the Single Euro Payments Area, is a payment-integration initiative of the European Union to simplify bank transfers denominated in euros. SEPA allows you to send payment orders to your bank to automate bank wire transfers."
msgid "When paying a bill in Odoo, you can select SEPA mandates as a payment option. At the end of the day, you can generate the SEPA file containing all bank wire transfers and upload it to your online banking interface to process the payments."
msgid "By default, the file follows the SEPA Credit Transfer **'pain.001.001.03'** specifications. This is a well-defined standard among banks. However, for Swiss and German companies, other formats are used **'pain.001.001.03.ch.02'** for Switzerland and **'pain.001.003.03'** for Germany."
msgid "Once the payments are processed by your bank, you can directly import the account statement in Odoo. The bank reconciliation process will seamlessly match the SEPA orders you sent to your bank with actual bank statements."
msgid "To pay suppliers with SEPA, you must activate the **SEPA Credit Transfer** setting. To do so, go to :menuselection:`Accounting --> Configuration --> Settings --> Vendor Payments: SEPA Credit Transfer (SCT)`. By activating the setting and filling out your company data, you will be able to use the SCT option when paying your vendor."
msgid "According to the localization package installed, the **SEPA Direct Debit** and **SEPA Credit Transfer** modules may be installed by default. If not, they need to be :ref:`installed <general/install>`."
msgid "From the accounting dashboard, click on the drop-down menu (:guilabel:`⋮`) on your bank journal and select :guilabel:`Configuration`. Click the :guilabel:`Outgoing Payments` tab, and, if not already present, add :guilabel:`SEPA Credit Transfer` under :guilabel:`Payment Method`."
msgid "Make sure to specify the IBAN account number (domestic account numbers do not work with SEPA) and the BIC (bank identifier code) in the :guilabel:`Journal Entries` tab."
msgid "You can register any vendor payments made with SEPA. To do so, go to :menuselection:`Accounting --> Vendors --> Payments`. When creating your payment, select :guilabel:`SEPA Credit Transfer` as the :guilabel:`Payment Method`."
msgid "The first time you pay a vendor with SEPA, you have to fill in the :guilabel:`Recipient Bank Account` field with the bank name, IBAN, and BIC (Bank Identifier Code). Odoo automatically verifies if the IBAN format is respected."
msgid "Once your payment is registered, do not forget to confirm it. You can also pay vendor bills from the bill directly using the :guilabel:`Register Payment` button at the top of a vendor bill. The form is the same, but the payment is directly linked to the bill and will be automatically reconciled with it."
msgid "Odoo includes **generic** and **dynamic** reports available for all countries, regardless of the :doc:`localization package <../../finance/fiscal_localizations>` installed:"
msgid "To expand the lines of a report and view its details, click the :icon:`fa-caret-right` (:guilabel:`right arrow`) on the left. Then click the :icon:`fa-caret-down` (:guilabel:`down arrow`) to the right of the account, journal entry, payment, invoice, etc. to :guilabel:`Annotate` and view the details."
msgid "The :guilabel:`Profit and Loss` report (or **Income Statement**) shows your company's net income by deducting expenses from revenue for the reporting period."
msgid "The contribution of all sales made by your business **minus** any direct costs needed to make those sales *and* fixed overheads your company has (electricity, rent, taxes to be paid as a result of those sales, etc.)."
msgid "How much cash is expected in or out of your business in the next month, i.e., the balance of your **Sales account** for the month **minus** the balance of your **Purchases account** for the month."
msgid "Also referred to as the **current ratio**, this is the ratio of current assets (:dfn:`assets that could be turned into cash within a year`) to the current liabilities (:dfn:`liabilities that will be due in the next year`). It is typically used to measure a company's ability to service its debt."
msgid "The :guilabel:`General Ledger` report shows all transactions from all accounts for a selected date range. The initial summary report shows the totals for each account. To expand an account and view its details, click the :icon:`fa-caret-right` (:guilabel:`right arrow`) on the left. This report is useful for reviewing each transaction that occurred during a specific period."
msgid "The :guilabel:`Aged Payable` report displays information on individual bills, credit notes, and overpayments you owe and how long these have gone unpaid."
msgid "The :guilabel:`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."
msgid "The :guilabel:`Tax Report` shows the :guilabel:`NET` and :guilabel:`TAX` amounts for all the taxes grouped by type (:guilabel:`Sales`/:guilabel:`Purchases`)."
msgid "Analytic accounting helps you track costs and revenues, as well as analyze the profitability of a project or service. When creating your journal entries, the analytic widget allows the distribution of costs in one or more analytic accounts."
msgid "Access your existing analytic accounts by going to :menuselection:`Accounting --> Configuration --> Analytic Accounting: Analytic Accounts`. To create a new analytic account, click :guilabel:`New`, and fill in the required information:"
msgid "You can access the analytic plans by going to :menuselection:`Accounting --> Configuration --> Analytic Accounting: Analytic Plans`. Click :guilabel:`New` to create a new plan."
msgid ":guilabel:`Mandatory`: if selected, an orange bullet is visible in the widget next to the plan until the analytic distribution is done (the bullet then turns to green); it is not possible to confirm the entry if no analytic account is selected;"
msgid ":guilabel:`Subplans`: can be created to have a more complex analytic structure. Click the :guilabel:`Subplans` smart button, and then :guilabel:`New` to add a subplan;"
msgid "Add a plan in the :guilabel:`Analytic` column when creating an invoice or bill. This field is mandatory only if you previously linked your analytic plan to at least one analytic account. After adding the plan, a **widget** opens where you can fill in the different information. You can add **tags** to reflect the related analytic accounts and decide how to split the costs between the accounts by modifying the percentage."
msgid "To create a new analytic distribution model, go to :menuselection:`Accounting --> Configuration --> Analytic Distribution Models`, click :guilabel:`New` and set the conditions your model has to meet to automatically apply:"
msgid ":guilabel:`Partner Category`: this field is not visible by default: add it by clicking on the columns selection button, and tick the :guilabel:`Partner Category` box. Add the partner category for which the analytic distribution will be used;"
msgid ":guilabel:`Product Category`: this field is not visible by default: add it by clicking on the columns selection button, and tick the :guilabel:`Product Category` box. Select a product category for which the analytic distribution will be used;"
msgid ":guilabel:`Analytic Distribution`: if the above conditions are met, the :guilabel:`Analytic plan` defined in this field as well as the distribution to be applied between the different analytic accounts is selected automatically on the entry."
msgid "To **mass edit** several entries simultaneously, go to :menuselection:`Accounting --> Accounting --> Journal items`, and select the ones that need to be updated. Add the required distribution in the :guilabel:`Analytic Distribution` column, and click on the :guilabel:`floppy disk` icon to save. The analytic distribution template pops up, and you can save it for later use."
msgid "Managing budgets is an essential part of running a business. Budgets help people become more intentional with how money is spent and direct people to organize and prioritize their work to meet financial goals. They allow the planning of a desired financial outcome and then measure the actual performance against the plan. Odoo manages budgets using both **general** and **analytic accounts**."
msgid "To define budgetary positions, go to :menuselection:`Accounting --> Configuration --> Management: Budgetary Positions` and :guilabel:`New`. Add a :guilabel:`Name` to your budgetary position and select the :guilabel:`Company` it applies to. Click :guilabel:`Add a line` to add one or more accounts."
msgid "We just started a project with *Smith & Co*, and we would like to budget the income and expenses of that project. We plan on having a revenue of 1000, and we don’t want to spend more than 700."
msgid "First, we need to define what accounts relate to our project’s expenses. Go to :menuselection:`Accounting --> Configuration --> Management: Budgetary positions`, and click :guilabel:`New` to add a position. Add the accounts wherein expenses will be booked."
msgid "Odoo needs to know which costs or expenses are relevant to a specified budget, as the above general accounts may be used for different projects. Go to :menuselection:`Accounting --> Configuration --> Analytic Accounting: Analytic Accounts` and click :guilabel:`New` to add a new **Analytic Account** called *Smith & Co*."
msgid "The :guilabel:`Plan` field has to be completed. Plans group multiple analytic accounts; they distribute costs and benefits to analyze business performance. **Analytic Plans** can be created or configured by going to :menuselection:`Accounting --> Configuration --> Analytic Accounting: Analytic Plans`."
msgid "Let’s set our targets. We specified that we expect to gain 1000 with this project, and we would like not to spend more than 700. Go to :menuselection:`Accounting --> Management: Budgets` and click :guilabel:`New` to create a new budget for *Smith & Co* project."
msgid "First, fill in your :guilabel:`Budget Name`. Then, select the :guilabel:`Period` wherein the budget is applicable. Next, add the :guilabel:`Budgetary Position` you want to track, define the related :guilabel:`Analytic Account`, and add the :guilabel:`Planned Amount`."
msgid "Go to :menuselection:`Accounting --> Management: Budgets` and find the *Smith & Co* Project to see how it evolves according to the expenses or income for the related analytic account."
msgid "The :guilabel:`Practical Amount` evolves when a new journal entry related to your analytic account and an account from your budgetary position is created."
msgid "The :guilabel:`Theoretical Amount` represents the amount of money you theoretically could have spent or should have received based on the date. For example, suppose your budget is 1200 for 12 months (January to December), and today is 31 of January. In that case, the theoretical amount will be 100 since this is the actual amount that could have been made."
msgid "Odoo comes with a powerful and easy-to-use reporting framework. The engine allows you to create new reports, such as **tax reports**, or **balance sheets** and **income statements** with **specific groupings** and **layouts**."
msgid "To create a new report, go to :menuselection:`Accounting --> Configuration --> Management: Accounting Reports`. From here, you can either create a :ref:`root report <customize-reports/root>` or a :ref:`variant <customize-reports/variants>`."
msgid "Root reports can be regarded as generic, neutral accounting reports. They serve as models on which local accounting versions are built. If a report has no root report, it is considered to be a root report itself."
msgid "When creating a new root report, you need to create a **menu item** for it. To do so, open the report and then, on that same report, click on :menuselection:`Action --> Create Menu Item`. Refresh the page; the report is now available under :menuselection:`Accounting --> Reporting`."
msgid "Variants are country-specific versions of root reports and, therefore, always refer to a root report. To create a variant, select a generic (root) report in the :guilabel:`Root Report` field when creating a new report."
msgid "When a root report is opened from one of the accounting app's main menus, all its variants are displayed in the variant selector in the top right corner of the view."
msgid "After having created a report (either root or variant), you need to fill it with lines. You can either create a new one by clicking on :guilabel:`Add a line`, or modify an existing line by clicking on it. All lines *require* a :guilabel:`Name`, and can have an optional additional :guilabel:`Code` (of your choice) if you wish to use their value in formulas."
msgid "Each line can contain one or multiple **expressions**. Expressions can be seen as **sub-variables** needed by a report line. To create an expression, click on :guilabel:`Add a line` *within* a line report."
msgid "When creating an expression, you must attribute a :guilabel:`label` used to refer to that expression. Therefore, it has to be **unique** among the expressions of each line. Both a :guilabel:`Computation Engine` and a :guilabel:`Formula` must also be indicated. The **engine** defines how your **formula(s)** and **subformula(s)** are interpreted. It is possible to mix expressions using different computation engines under the same line if you need to."
msgid "The result is the number of sub-lines of this expression. If the parent line has a group-by value, this will correspond to the number of distinct grouping keys in the matched move lines. Otherwise, it will be the number of matched move lines."
msgid "A formula made for this engine consists of a name used to match tax tags. If such tags do not exist when creating the expression, they will be created."
msgid "When evaluating the expression, the expression computation can roughly be expressed as: **(amount of the move lines with** `+` **tag)** `-` **(amount of the move lines with** `-` **tag)**."
msgid "If the formula is `tag_name`, the engine matches tax tags `+tag_name` and `-tag_name`, creating them if necessary. To exemplify further: two tags are matched by the formula. If the formula is `A`, it will require (and create, if needed) tags `+A` and `-A`."
msgid "Use this engine when you need to perform arithmetic operations on the amounts obtained for other expressions. Formulas here are composed of references to expressions separated by one of the four basic arithmetic operators (addition `+`, subtraction `-`, division `/`, and multiplication `*`). To refer to an expression, type in its parent line's **code** followed by a period `.` and the expression's **label** (ex. **code.label**)."
msgid "The value of the arithmetic expression will be returned only if it is strictly between the provided bounds. Otherwise, it will be brought back to the closest bound."
msgid "The value of the arithmetic expression will be returned only if the value of the expression denoted by the provided line code and expression label is greater than the provided bound. Otherwise, the result will be `0`."
msgid "The value of the arithmetic expression will be returned only if the value of the expression denoted by the provided line code and expression label is lower than the provided bound. Otherwise, the result will be `0`."
msgid "This formula adds the balances of the move lines made on accounts whose codes start with `21` and `10`, and subtracts the balance of the ones on accounts with the prefix `5`."
msgid "You can apply 'sub-filtering' on **credits and debits** using the `C` and `D` suffixes. In this case, an account will only be considered if its prefix matches, *and* if the total balance of the move lines made on this account is **credit/debit**."
msgid "Account `210001` has a balance of -42 and account `210002` has a balance of 25. The formula `21D` only matches the account `210002`, and hence returns 25. `210001` is not matched, as its balance is *credit*."
msgid "This formula adds the balances of the move lines made on accounts whose code starts with `21` *if* it is debit (`D`) and `10` *if* it is credit (`C`), but ignores prefixes `101`, `102`, and subtracts the balance of the ones on accounts with the prefix `5`, ignoring the prefix `57`."
msgid "In addition to using code prefixes to include accounts, you can also match them with **account tags**. This is especially useful, for example, if your country lacks a standardized chart of accounts, where the same prefix might be used for different purposes across companies."
msgid "The balances of accounts tagged as *my_module.my_tag* will be summed with those of accounts linked to the tag with ID *42* and accounts with the code prefix `10`"
msgid "The 'external value' engine is used to refer to **manual** and **carryover values**. Those values are not stored using `account.move.line`, but with `account.report.external.value`. Each of these objects directly points to the expression it impacts, so very little needs to be done about their selection here."
msgid "This engine is a means for developers to introduce custom computation of expressions on a case-by-case basis. The formula is the name of a **python function** to call, and the subformula is a **key** to fetch in the **dictionary** returned by this function. Use it only if you are making a custom module of your own."
msgid "Reports can have an **indefinite number** of columns to display. Each column gets its values from the **expressions** declared on the **lines**. The field :guilabel:`expression_label` of the column gives the label of the expressions whose value is displayed. If a line has no **expression** in that field, then nothing is displayed for it in this column. If multiple columns are required, you must use different **expression** labels."
msgid "When using the **period comparison** feature found under the :guilabel:`Options` tab of an accounting report, all columns are repeated in and for each period."
msgid "Tax authorities in some countries require companies to **prove their posted accounting entries are inalterable**, meaning that once an entry has been posted, it can no longer be changed."
msgid "To do so, Odoo can use the **SHA-256 algorithm** to create a unique fingerprint for each posted entry. This fingerprint is called a hash. The hash is generated by taking an entry's essential data (the values of the `name`, `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and `partner_id` fields), concatenating it, and inputting it to the SHA-256 hash function, which then outputs a fixed size (256-bit) string of characters. The hash function is deterministic (:dfn:`the same input always creates the same output`): any minor modification to the original data would completely change the resulting hash. Consequently, the SHA-256 algorithm is often used, among others, for data integrity verification purposes."
msgid "In addition, the previous entry's hash is always added to the next entry to form a **hash chain**. This is used to ensure a new entry is not added afterward between two posted entries, as doing so would break the hash chain."
msgid "Hashes generated by the SHA-256 algorithm are theoretically not unique, as there is a finite number of possible values. However, this number is exceptionally high: 2²⁵⁶, which is a lot bigger than the number of atoms in the known universe. This is why hashes are considered unique in practice."
msgid "To start using the hashing function, go to :menuselection:`Accounting --> Configuration > Journals`. Open the journal for which you want to activate the feature, go to the :guilabel:`Advanced Settings` tab, and enable :guilabel:`Lock Posted Entries with Hash`."
msgid "To download the data inalterability check report, go to :menuselection:`Accounting --> Configuration --> Settings --> Reporting` and click on :guilabel:`Download the Data Inalterability Check Report`."
msgid "The report's first section is an overview of all your journals and their configuration. Under the inalterability check column, you can see whether or not a journal's posted entries are locked with a hash (V) or not (X). The coverage column tells you when a journal's posted entries started being locked."
msgid "The second section gives you the result of the data consistency check for each hashed journal. You can view the first hashed entry and its corresponding hash and the last hashed entry and its corresponding hash."
msgid "Goods movements without transfer of ownership (e.g., stock relocations or moves of goods before or after outsourced production or processing, and after maintenance or repair);"
msgid "Although the Intrastat system continues to be used, the term Intrastat is not used in the `latest legislation <http://data.europa.eu/eli/reg/2019/2152/2022-01-01>`_, referring instead to *intra-Union trade in goods statistics*."
msgid "Enable the Intrastat report by going to :menuselection:`Accounting --> Configuration --> Settings`. Under the :guilabel:`Customer Invoices` section, tick :guilabel:`Intrastat` and then :guilabel:`Save`."
msgid "You can set a default :ref:`transaction code <intrastat/transaction-code>` for all newly created invoice and refund transactions. Under :menuselection:`Accounting --> Configuration --> Settings`, select a :guilabel:`Default invoice transaction code` and/or a :guilabel:`Default refund transaction code` and then :guilabel:`Save`. The code will be set automatically on all respective invoice lines."
msgid "The region code is **only used by Belgian companies**. Under :menuselection:`Accounting --> Configuration --> Settings`, select the :guilabel:`Company Intrastat Region` where the company is located and then :guilabel:`Save`."
msgid "If your warehouses are located in more than one region, you can define the region code at the level of each warehouse instead. To do so, go to :menuselection:`Inventory --> Configuration --> Warehouses`, select a warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`."
msgid "Commodity codes are internationally recognized reference numbers used to classify goods depending on their **nature**. Intrastat uses the `Combined Nomenclature <https://taxation-customs.ec.europa.eu/customs-4/calculation-customs-duties/customs-tariff/combined-nomenclature_en>`_."
msgid "To add a commodity code, go to :menuselection:`Accounting --> Customers --> Products` and select a product. Under the :guilabel:`Accounting` tab, set the product's :guilabel:`Commodity Code`."
msgid "Depending on the nature of the goods, it is necessary to specify either the product's weight in kilos (without packaging) or the product's supplementary unit, such as square meter (`m2`), number of items (`p/st`), liter (`l`), or gram (`g`)."
msgid "To add a product's weight or supplementary unit, go to :menuselection:`Accounting --> Customers --> Products` and select a product. Under the :guilabel:`Accounting` tab, depending on the commodity code set, either fill in the product :guilabel:`Weight` or its :guilabel:`Supplementary Units`."
msgid "To add the product's country of origin, go to :menuselection:`Accounting --> Customers --> Products` and select a product. Under the :guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`."
msgid "Transaction codes are used to identify a transaction's nature. :ref:`Default transaction codes <intrastat/default-transaction-codes>` can be set for invoice and refund transactions."
msgid "To set a transaction code on an invoice line, create an invoice or a bill, click the columns selection button, tick :guilabel:`Intrastat`, and use the newly-added :guilabel:`Intrastat` column to select a transaction code."
msgid "`National Bank of Belgium - Intrastat: Nature of transactions from January 2022 <https://www.nbb.be/doc/dd/onegate/data/new_natures_of_transaction_2022_en.pdf>`_"
msgid "The partner country represents the vendor's country for bills and the customer's country for invoices. It is automatically filled in using the country set in the contact's :guilabel:`Country` field."
msgid "To edit the partner country manually, create an invoice or a bill, click the :guilabel:`Other Info` tab, and select the :guilabel:`Intrastat Country`."
msgid "To add the transport code, create an invoice or a bill, go to the :guilabel:`Other info` tab, and select the :guilabel:`Intrastat Transport Mode`."
msgid "Two fields from the partner's contact form are used with Intrastat: :guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually set <intrastat/partner-country>` on the invoice or bill."
msgid "Generate the report by going to :menuselection:`Accounting --> Reporting --> Audit Reports: Intrastat Report`. It is automatically computed based on the :ref:`default configuration <intrastat/general-configuration>` and the information found on the :ref:`products <intrastat/product-configuration>`, :ref:`invoices and bills <intrastat/invoice-bill-configuration>`, and :ref:`partners <intrastat/partner>`."
msgid "You can create Odoo external API keys either :ref:`for a single database <silverfin/api-singledb>` (hosting: Odoo Online, On-premise, and Odoo.sh) or :ref:`for all databases managed by a single user <silverfin/api-multipledb>` (hosting: Odoo Online)."
msgid "To add an API key to a **single** database, connect to the database, enable the :ref:`developer mode <developer-mode>`, click on the user menu, and then :guilabel:`My Profile` / :guilabel:`Preferences`. Under the :guilabel:`Account Security` tab, click on :guilabel:`New API Key`, confirm your password, give a descriptive name to your new key, and copy the API key."
msgid "To add an API key to **all** databases managed by a single user at the same time **(the easiest method for fiduciaries)**, navigate to `Odoo's website <https://www.odoo.com>`_ and sign in with your administrator account. Next, open `your account security settings in developer mode <https://www.odoo.com/my/security?debug=1>`_, click on :guilabel:`New API Key`, confirm your password, give a descriptive name to your new key, and copy the new API key."
msgid "It has been created to meet the legal requirements of specific locations, where amounts must be transferred from period to period (for example, because the total of the line is negative)."
msgid "The feature is activated by default in countries where it is required, such as Belgium, France, and Italy. There is no specific configuration required."
msgid "In this case, as per local regulation, grid 81 of the tax report may contain a negative amount. But it must be declared to the government as zero, and the negative amount should be carried over to the next period."
msgid "If we go to :menuselection:`Accounting app --> Reporting --> Tax Report`, a pop-up on line 81 explains that the amount will be carried over in the next period."
msgid "At the time of the tax closing period, the tax report shows that the amount was carried over from the previous period. It also indicates the amount that will be carried over to this line in the next period based on the existing transactions and the carryover from the previous period."
msgid "Companies with a registered :abbr:`VAT (Value Added Tax)` number must submit a **tax return** on a monthly or quarterly basis, depending on their turnover and the registration regulation. A tax return - or VAT return - gives the tax authorities information about the taxable transactions made by the company. The **output tax** is charged on the number of goods and services sold by a business, while the **input tax** is the tax added to the price when goods or services are purchased. Based on these values, the company can calculate the tax amount they have to pay or be refunded."
msgid "You can find additional information about VAT and its mechanism on this page from the European Commission: `\"What is VAT?\" <https://ec.europa.eu/taxation_customs/business/vat/what-is-vat_en>`_."
msgid "The configuration of the **Tax Return Periodicity** allows Odoo to compute your tax return correctly and also to send you a reminder to never miss a tax return deadline."
msgid "Odoo generates tax reports based on the :guilabel:`Tax Grids` settings that are configured on your taxes. Therefore, it is crucial to make sure that all recorded transactions use the right taxes. You can see the :guilabel:`Tax Grids` by opening the :guilabel:`Journal Items` tab of any invoice and bill."
msgid "To configure your tax grids, go to :menuselection:`Accounting --> Configuration --> Taxes`, and open the tax you want to modify. There, you can edit your tax settings, along with the tax grids that are used to record invoices or credit notes."
msgid "Taxes and reports are usually already pre-configured in Odoo: a :ref:`fiscal localization package <fiscal_localizations/packages>` is installed according to the country you select at the creation of your database."
msgid "Any new transaction whose accounting date prior to the :guilabel:`Tax Lock Date` has its tax values moved to the next open tax period. This is useful to make sure that no change can be made to a report once its period is closed."
msgid "Therefore, we recommend locking your tax date before working on your :guilabel:`Closing Journal Entry`. This way, other users cannot modify or add transactions that would have an impact on the :guilabel:`Closing Journal Entry`, which can help you avoid some tax declaration errors."
msgid "Once all the transactions involving taxes have been posted for the period you want to report, open the :guilabel:`Tax Report` by going to :menuselection:`Accounting --> Reporting --> Tax Report`. Select the period you want to declare using the date filter to have an overview of the tax report. From the report, click :guilabel:`PDF` or :guilabel:`XLSX` to download the desired format of the tax report, or click :guilabel:`Save` to save the report to the Documents app. The report includes all the values to report to the tax authorities, along with the amount to be paid or refunded."
msgid "If you forgot to lock your tax date before clicking on :guilabel:`Closing Journal Entry`, then Odoo automatically locks your fiscal period on the same date as the accounting date of your entry. This safety mechanism can prevent some fiscal errors, but it is advised to lock your tax date manually before, as described above."
msgid "Year-end closing is vital for maintaining financial accuracy, complying with regulations, making informed decisions, and ensuring transparency in reporting."
msgid "By default, the fiscal year is set to last 12 months and end on December 31st. However, its duration and end date can vary due to cultural, administrative, and economic considerations."
msgid "To modify these values, go to :menuselection:`Accounting --> Configuration --> Settings`. Under the :guilabel:`Fiscal Periods` section, change the :guilabel:`Last Day` field if necessary."
msgid "If the period lasts *more* than or *less* than 12 months, enable :guilabel:`Fiscal Years` and :guilabel:`Save`. Go back to the :guilabel:`Fiscal Periods` section and click :guilabel:`➜ Fiscal Years`. From there, click :guilabel:`Create`, give it a :guilabel:`Name`, and both a :guilabel:`Start Date` and :guilabel:`End Date`."
msgid "Once the set fiscal period is over, Odoo automatically reverts to the default periodicity, taking into account the value specified in the :guilabel:`Last Day` field."
msgid "Make sure all bank accounts are fully :doc:`reconciled <../bank/reconciliation>` up to year-end, and confirm that the ending book balances match the bank statement balances."
msgid "Reconcile all transactions in the cash and bank accounts by running the :ref:`aged receivables <reporting/aged-receivable>` and :ref:`aged payables <reporting/aged-payable>` reports."
msgid "Optionally, run :ref:`payments matching <accounting/payments/matching>` to validate any open vendor bills and customer invoices with their payments. While this step is optional, it could assist the year-end closing process if all outstanding payments and invoices are reconciled, potentially finding errors or mistakes in the system."
msgid "If the accountant is going through the year-end audit, they may want to have paper copies of all balance sheet items (such as loans, bank accounts, prepayments, sales tax statements, etc.) to compare these with the balances in Odoo."
msgid "During this process, it is good practice to set a :guilabel:`Journal Entries Lock Date` to the last day (inclusive) of the preceding fiscal year by going to :menuselection:`Accounting --> Accounting --> Lock Dates`. This way, the accountant can be confident that nobody changes the transactions while auditing the books. Users from the *accountant* access group can still create and modify entries."
msgid "Odoo uses a unique account type called **current year's earnings** to display the amount difference between the **income** and **expenses** accounts."
msgid "The chart of accounts can only contain one account of this type. By default, it is a 999999 account named :guilabel:`Undistributed Profits/Losses`."
msgid "To allocate the current year's earnings, create a miscellaneous entry to book them to any equity account. Once done, confirm whether or not the current year's earnings in the **balance sheet** is correctly reporting a balance of zero. If that is the case, set an :guilabel:`All Users Lock Date` to the last day of the fiscal year by going to :menuselection:`Accounting --> Accounting --> Lock Dates`."
msgid "A specific year-end closing entry is **optional** in order to close out the **profit and loss statement**. The reports are created in real-time, meaning that the profit and loss statement corresponds directly with the year-end date specified in Odoo. Therefore, any time the **income statement** is generated, the beginning date corresponds with the beginning of the **fiscal year** and all account balances should equal zero."
msgid "There are numerous types of **taxes**, and their application varies greatly, depending mostly on your company's localization. To make sure they are recorded with accuracy, Odoo's tax engine supports all kinds of uses and computations."
msgid "**Default Taxes** define which taxes are automatically selected when there is no other indication about which tax to use. For example, Odoo prefills the **Taxes** field with the Default Taxes when you create a new product or add a new line on an invoice."
msgid "To change your **Default Taxes**, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes --> Default Taxes`, select the appropriate taxes for your default **Sales Tax** and **Purchase Tax**, and click on *Save*."
msgid "**Default Taxes** are automatically set up according to the country selected at the creation of your database, or when you set up a :ref:`fiscal localization package <fiscal_localizations/packages>` for your company."
msgid "As part of your :ref:`fiscal localization package <fiscal_localizations/packages>`, most of your country's sales taxes are already preconfigured on your database. However, only a few of them are activated by default, so that you can activate only the ones relevant for your business."
msgid "To activate Sale Taxes, go to :menuselection:`Accounting --> Configuration --> Taxes` and use the *Activate* toggle button to activate or deactivate a tax."
msgid "The **Tax Name** as you want to display it for backend users. This is the :ref:`label <taxes/labels>` you see while editing Sales Orders, Invoices, Products, etc."
msgid "Make sure that the tax sequence is correct, as the order in which they are may impact the taxes' amounts computation, especially if one of the taxes :ref:`affects the base of the subsequent ones <taxes/base-subsequent>`."
msgid "You can use **None** for taxes that you want to include in a :ref:`Group of Taxes <taxes/computation>` but that you don't want to list along with other Sales or Purchase taxes."
msgid "The label of the tax, as displayed on each invoice line in the **Taxes** column. This is the :ref:`label <taxes/labels>` visible to *front end* users, on exported invoices, on their Customer Portals, etc."
msgid "Select to which **Tax Group** the tax belongs. The Tax Group name is the :ref:`label <taxes/labels>` displayed above the *Total* line on exported invoices, and the Customer Portals."
msgid "Tax groups include different iterations of the same tax. This can be useful when you must record differently the same tax according to :doc:`Fiscal Positions <taxes/fiscal_positions>`."
msgid "In the example above, we see a 0% tax for Intra-Community customers in Europe. It records amounts on specific accounts and with specific tax grids. Still, to the customer, it is a 0% tax. That's why the :ref:`Label on the Invoice <taxes/label-invoices>` indicates *0% EU*, and the Tax Group name, above the *Total* line, indicates *0%*."
msgid "If you need to define prices accurately, both tax-included and tax-excluded, please refer to the following documentation: :doc:`taxes/B2B_B2C`."
msgid "**Invoices**: By default, the Line Subtotals displayed on your invoices are *Tax-Excluded*. To display *Tax-Included* Line Subtotals, go to :menuselection:`Accounting --> Configuration --> Settings --> Customer Invoices`, and select *Tax-Included* in the **Line Subtotals Tax Display** field, then click on *Save*."
msgid "**eCommerce**: By default, the prices displayed on your eCommerce website are *Tax-Excluded*. To display *Tax-Included* prices, go to :menuselection:`Website --> Configuration --> Settings --> Pricing`, and select *Tax-Included* in the **Product Prices** field, then click on *Save*."
msgid "The order in which you add the taxes on a product line has no effect on how amounts are computed. If you add taxes directly on a product line, only the tax sequence determines the order in which they are applied."
msgid "To reorder the sequence, go to :menuselection:`Accounting --> Configuration --> Taxes`, and drag and drop the lines with the handles next to the tax names."
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."
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."
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%:"
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:"
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:"
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."
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."
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."
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."
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:"
msgid "Under the :guilabel:`Users` tab, add the users requiring access to the price type. Add B2C users in the B2C group and B2B users in the B2B group."
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."
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**."
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."
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:"
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)"
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€."
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€."
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."
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."
msgid "Avalara's *AvaTax* is a cloud-based tax software. Integrating *AvaTax* with Odoo provides real-time and region-specific tax calculations when users sell, purchase, and invoice items in Odoo. *AvaTax* tax calculation is supported with every United Nations charted country, including inter-border transactions."
msgid "*AvaTax* is only available for integration with databases/companies that have locations in the United States and Canada. This means the fiscal position/country of a database can only be set to the United States or Canada. For more information, reference this documentation: :ref:`avatax/fiscal_country`."
msgid "*AvaTax* accounts for location-based tax rates for each state, county, and city. It improves remittance accuracy by paying close attention to laws, rules, jurisdiction boundaries, and special circumstances (like, tax holidays, and product exemptions). Companies who integrate with *AvaTax* can maintain control of tax-calculations in-house with this simple :abbr:`API (application programming interface)` integration."
msgid "*AvaTax* is **not** supported in Odoo's *Point of Sale* app, because a dynamic tax calculation model is excessive for transactions within a single delivery address, such as stores or restaurants."
msgid "To use *AvaTax*, an account with Avalara is required for the setup. If one has not been set up yet, connect with Avalara to purchase a license: `Avalara: Let's Talk <https://www.avalara.com/us/en/get-started.html>`_."
msgid "Upon account setup, take note of the *AvaTax* :guilabel:`Account ID`. This will be needed in the :ref:`Odoo setup <avatax/credentials>`. In Odoo, this number is the :guilabel:`API ID`."
msgid "Then, `create a basic company profile <https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Create_a_Basic_company_profile.html&_LANG=enus>`_."
msgid "Collect essential business details for the next step: locations where tax is collected, products/services sold (and their sales locations), and customer tax exemptions, if applicable. Follow the Avalara documentation for creating a basic company profile:"
msgid "`Add company information <https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_your_company_information.html&_LANG=enus>`_."
msgid "`Tell us where the company collects and pays tax <https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Tell_us_where_you_collect_and_pay_tax.html&_LANG=enus>`_."
msgid "`Verify jurisdictions and activate the company <https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Verify_your_jurisdictions_and_activate_your_company.html&_LANG=enus>`_."
msgid "`Add other company locations for location-based filing <https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_other_company_locations_for_location-based_filing.html&_LANG=enus>`_."
msgid "`Add a marketplace to the company profile <https://community.avalara.com/support/s/document-item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_marketplace_transactions_to_your_company_profile.html&_LANG=enus>`_."
msgid "Navigate to either Avalara's `sandbox <https://sandbox.admin.avalara.com/>`_ or `production <https://admin.avalara.com/>`_ environment. This will depend on which type of Avalara account the company would like to integrate."
msgid "Log in to create the :guilabel:`License Key`. Go to :menuselection:`Settings --> License and API Keys`. Click :guilabel:`Generate License Key`."
msgid "A warning appears stating: `If your business app is connected to Avalara solutions, the connection will be broken until you update the app with the new license key. This action cannot be undone.`"
msgid "Generating a new license key breaks the connection with existing business apps using the *AvaTax* integration. Make sure to update these apps with the new license key."
msgid "If this will be the first :abbr:`API (application programming interface)` integration being made with *AvaTax* and Odoo, then click :guilabel:`Generate license key`."
msgid "If this is an additional license key, ensure the previous connection can be broken. There is **only** one license key associated with each of the Avalara sandbox and production accounts."
msgid "Copy this key to a safe place. It is **strongly encouraged** to backup the license key for future reference. This key cannot be retrieved after leaving this screen."
msgid "Verify that the Odoo database contains necessary data. The country initially set up in the database determines the fiscal position, and aids *AvaTax* in calculating accurate tax rates."
msgid "Under the :guilabel:`Taxes` section, set the :guilabel:`Fiscal Country` feature to :guilabel:`United States` or :guilabel:`Canada`. Then, click :guilabel:`Save`."
msgid "All companies operating under the Odoo database should have a full and complete address listed in the settings. Navigate to the :menuselection:`Settings app`, and under the :guilabel:`Companies` section, ensure there is only one company operating the Odoo database. Click :guilabel:`Update Info` to open a separate page to update company details."
msgid "If there are multiple companies operating in the database, click :guilabel:`Manage Companies` to load a list of companies to select from. Update company information by clicking into the specific company."
msgid "Database administrators should ensure that the :guilabel:`Street...`, :guilabel:`Street2...`, :guilabel:`City`, :guilabel:`State`, :guilabel:`ZIP`, and :guilabel:`Country` are all updated for the companies."
msgid "Next, ensure that the Odoo *AvaTax* module is installed. To do so, navigate to the :menuselection:`Apps application`. In the :guilabel:`Search...` bar, type in `avatax`, and press :kbd:`Enter`. The following results populate:"
msgid "Should *AvaTax* be needed for Odoo *Subscriptions*, or for delivery tax in Odoo *eCommerce*, then install those modules individually by clicking on :guilabel:`Install`."
msgid "To integrate the *AvaTax* :abbr:`API (application programming interface)` with Odoo, go to :menuselection:`Accounting app --> Configuration --> Settings` section. The :guilabel:`AvaTax` fields in the :guilabel:`Taxes` section is where the *AvaTax* configurations are made and the credentials are entered in."
msgid "First, select the :guilabel:`Environment` in which the company wishes to use *AvaTax* in. It can either be :guilabel:`Sandbox` or :guilabel:`Production`."
msgid "For help determining which *AvaTax* environment to use (either :guilabel:`Production` or :guilabel:`Sandbox`), visit: `Sandbox vs Production environments <https://knowledge.avalara.com/bundle/fzc1692293626742/page/sandbox-vs-production.html>`_."
msgid "Now, the credentials can be entered in. The *AvaTax* :guilabel:`Account ID` should be entered in the :guilabel:`API ID` field, and the :guilabel:`License Key` should be entered in the :guilabel:`API Key` field."
msgid "The :guilabel:`Account ID` can be found by logging into the *AvaTax* portal (`sandbox <https://sandbox.admin.avalara.com/>`_ or `production <https://admin.avalara.com/>`_). In the upper-right corner, click on the initials of the user and :guilabel:`Account`. The :guilabel:`Account ID` is listed first."
msgid "For the :guilabel:`Company Code` field, enter the Avalara company code for the company being configured. Avalara interprets this as `DEFAULT`, if it is not set. The :guilabel:`Company Code` can be accessed in the Avalara management portal."
msgid "First, log into the *AvaTax* portal (`sandbox <https://sandbox.admin.avalara.com/>`_ or `production <https://admin.avalara.com/>`_). Then, navigate to :menuselection:`Settings --> Manage Companies`. The :guilabel:`Company Code` value is located in the row of the :guilabel:`Company` in the :guilabel:`Company Code` column."
msgid "There are two transactional settings in the Odoo *AvaTax* settings that can be configured: :guilabel:`Use UPC` and :guilabel:`Commit Transactions`."
msgid "If the checkbox next to :guilabel:`Use UPC` is ticked, the transactions will use Universal Product Codes (UPC), instead of custom defined codes in Avalara. Consult a certified public accountant (CPA) for specific guidance."
msgid "Should the :guilabel:`Commit Transactions` checkbox be ticked, then, the transactions in the Odoo database will be committed for reporting in *AvaTax*."
msgid "The *Address Validation* feature ensures that the most up-to-date address by postal standards is set on a contact in Odoo. This is important to provide accurate tax calculations for customers."
msgid "For accurate tax calculations, it is best practice to enter a complete address for the contacts saved in the database. However, *AvaTax* can still function by implementing a best effort attempt using only the :guilabel:`Country`, :guilabel:`State`, and :guilabel:`Zip code`. These are the three minimum required fields."
msgid "Manually :guilabel:`Validate` the address by navigating to the :menuselection:`Contacts app`, and selecting a contact. Now that the *AvaTax* module has been configured on the database, a :guilabel:`Validate` button appears directly below the :guilabel:`Address`."
msgid "Click :guilabel:`Validate`, and a pop-up window appears with a :guilabel:`Validated Address` and :guilabel:`Original Address` listed. If the :guilabel:`Validated Address` is the correct mailing address for tax purposes, click :guilabel:`Save Validated`."
msgid "All previously-entered addresses for contacts in the Odoo database will need to be validated using the manually validate process outlined above. Addresses are not automatically validated if they were entered previously. This only occurs upon tax calculation."
msgid "After entering all the above information into the *AvaTax* setup on Odoo, click :guilabel:`Test connection`. This ensures the :guilabel:`API ID` and :guilabel:`API KEY` are correct, and a connection is made between Odoo and the *AvaTax* application programming interface (API)."
msgid "Upon finishing the configuration and settings of the *AvaTax* section, click the :guilabel:`Sync Parameters` button. This action synchronizes the exemption codes from *AvaTax*."
msgid "Next, navigate to :menuselection:`Accounting app --> Configuration --> Accounting: Fiscal Positions`. A :guilabel:`Fiscal Position` is listed named, :guilabel:`Automatic Tax Mapping (AvaTax)`. Click it to open *AvaTax's* fiscal position configuration page."
msgid "Optionally, tick the checkbox next to the field labeled: :guilabel:`Detect Automatically`. Should this option be ticked, then, Odoo will automatically apply this :guilabel:`Fiscal Position` for transactions in Odoo."
msgid "Enabling :guilabel:`Detect Automatically` also makes specific parameters, such as :guilabel:`VAT required`, :guilabel:`Foreign Tax ID`, :guilabel:`Country Group`, :guilabel:`Country`, :guilabel:`Federal States`, or :guilabel:`Zip Range` appear. Filling these parameters filters the :guilabel:`Fiscal Position` usage. Leaving them blank ensures all calculations are made using this :guilabel:`Fiscal Position`."
msgid "Should the :guilabel:`Detect Automatically` checkbox not be ticked, each customer will need to have the :guilabel:`Fiscal Position` set on their :guilabel:`Sales and Purchase` tab of the contact record. To do so, navigate to :menuselection:`Sales app --> Order --> Customers`, or :menuselection:`Contacts app --> Contacts`. Then, select a customer or contact to set the fiscal position on."
msgid "Navigate to the :guilabel:`Sales and Purchase` tab, and down to the section labeled, :guilabel:`Fiscal Position`. Set the :guilabel:`Fiscal Position` field to the fiscal position for the customer."
msgid "Upon selecting the checkbox option for :guilabel:`Use AvaTax API` a new :guilabel:`AvaTax` tab appears. Click into this tab to reveal two different settings."
msgid "The first setting is the :guilabel:`AvaTax Invoice Account`, while the second is, :guilabel:`AvaTax Refund Account`. Ensure both accounts are set for smooth end-of-year record keeping. Consult a certified public accountant (CPA) for specific guidance on setting both accounts."
msgid "Before using the integration, specify an :guilabel:`Avatax Category` on the product categories. Navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`. Select the product category to add the :guilabel:`AvaTax Category` to. In the :guilabel:`AvaTax Category` field, select a category from the drop-down menu, or :guilabel:`Search More...` to open the complete list of options."
msgid "*AvaTax* Categories may be set on individual products, as well. To set the :guilabel:`Avatax Category` navigate to :menuselection:`Inventory app --> Products --> Products`. Select the product to add the :guilabel:`Avatax Category` to. Under the :guilabel:`General Information` tab, on the far-right, is a selector field labeled: :guilabel:`Avatax Category`. Finally, click the drop-down menu, and select a category, or :guilabel:`Search More...` to find one that is not listed."
msgid "Mapping an :guilabel:`AvaTax Category` on either the *Product* or *Product Category* should be completed for every *Product* or *Product Category*, depending the route that is chosen."
msgid "Avalara's (*AvaTax*) management console offers account management options including: viewing/editing the transactions sent from Odoo to *AvaTax*, details on how the taxes are calculated, tax reporting, tax exemption management, and tax return resources."
msgid "To access the console, first, navigate to either Avalara's `sandbox <https://sandbox.admin.avalara.com/>`_ or `production <https://admin.avalara.com/>`_ environment. This will depend on which type of account was set in the :doc:`integration <../avatax>`. Log in to the management console."
msgid "For more information see Avalara's documentation: `Activate your Communications Customer Portal account <https://community.avalara.com/support/s/document-item?language=en_US&bundleId=qvv1656594440497&topicId=Activate_your_Communications_Customer_Portal_account.html&_LANG=enus>`_."
msgid "To access transactions, click in the :guilabel:`Transactions` link on the main dashboard upon logging into the :ref:`avatax/portal`. To manually access the *Transactions* page, while logged into the Avalara console, navigate to :menuselection:`Transactions --> Transactions`."
msgid "Click into a transaction to reveal more details about the transaction. These details include sections on :guilabel:`Invoice detail`, :guilabel:`Additional info`, and :guilabel:`Customer info`. Click :icon:`fa-pencil` :guilabel:`Edit document details` to make changes to the transaction."
msgid "A :guilabel:`Discount` can be added to adjust the invoice. This is especially useful in cases where the transaction has already synced with Avalara / *AvaTax*, and changes need to be made afterward."
msgid "Filter transactions on the :guilabel:`Transactions` page, by setting the :guilabel:`From` and :guilabel:`To` fields, and configuring other fields to filter by, including:"
msgid ":guilabel:`Document Status`: any of the following options, :guilabel:`All`, :guilabel:`Voided`, :guilabel:`Committed`, :guilabel:`Uncommitted`, or :guilabel:`Locked`."
msgid ":guilabel:`Document Type`: any of the following selections, :guilabel:`All`, :guilabel:`Sales Invoice`, :guilabel:`Purchase Invoice`, :guilabel:`Return Invoice`, :guilabel:`Inventory Transfer Inbound Invoice`, :guilabel:`Inventory Transfer Outbound Invoice`, or :guilabel:`Customs Invoice`."
msgid "On the :guilabel:`Transactions` page, transactions will be listed below, according to the set :ref:`avalara/portal-filter`, located in the top half of the page. The following columns are available by default, to sort by ascending or descending order:"
msgid ":guilabel:`Doc Status`: either of the following options, :guilabel:`All`, :guilabel:`Voided`, :guilabel:`Committed`, :guilabel:`Uncommitted`, or :guilabel:`Locked`."
msgid "Additional columns can be added by clicking the :icon:`fa-cog` :guilabel:`Customize columns`. On the resulting popover window, click the drop-down menu for the :guilabel:`column` that should be changed."
msgid ":guilabel:`Doc status`: any of the following options, :guilabel:`All`, :guilabel:`Voided`, :guilabel:`Committed`, :guilabel:`Uncommitted`, or :guilabel:`Locked`."
msgid ":guilabel:`Doc type`: any of the following selections, :guilabel:`All`, :guilabel:`Sales Invoice`, :guilabel:`Purchase Invoice`, :guilabel:`Return Invoice`, :guilabel:`Inventory Transfer Inbound Invoice`, :guilabel:`Inventory Transfer Outbound Invoice`, or :guilabel:`Customs Invoice`."
msgid "For more information on *AvaTax* transactions, refer to this Avalara documentation: `Transactions <https://community.avalara.com/support/s/document-item?language=en_US&bundleId=qvv1656594440497&topicId=transactions.html&_LANG=enus>`_."
msgid "While on the :ref:`avalara/portal-transactions`, click :icon:`fa-download` :guilabel:`Import transactions` or :icon:`fa-upload` :guilabel:`Export transactions` to import or export transactions."
msgid "To access reporting, navigate to the :menuselection:`Reports` link in the top menu of the Avalara management console. Next, select from one of the available reporting tabs: :guilabel:`Transactions reports`, :guilabel:`Liability & tax return reports`, or :guilabel:`Exemption reports`."
msgid "Additionally, there is a :guilabel:`Favorites` tab and :guilabel:`Downloads` tab. The :guilabel:`Favorites` tab contains any favorited report configurations for the Avalara user. The :guilabel:`Downloads` tab contains a list view where the user can download the high-volume transaction reports created in the last 30 days."
msgid "Depending on the report size, the following two options are available in the section labeled, :guilabel:`Select the approximate number of transactions for your report`: :guilabel:`Create and download the report instantly` (for small reports) and :guilabel:`Create and download the report in the background` (for larger reports). Select one or the other depending on the volume of transactions in this report."
msgid "Finally, under the section labeled, :guilabel:`Report preview and export` make a selection of the file type to download. Either a :guilabel:`.PDF` or :guilabel:`.XLS` can be chosen. Alternatively, the file can be previewed by selecting the :guilabel:`Preview` option."
msgid "After making all the configurations, click :guilabel:`Create report` to download the report. Click :icon:`fa-star-o` :guilabel:`Make this report a favorite` to save the report configuration to the user's favorites."
msgid "Access this list by clicking on the :guilabel:`Reports` option in the top menu of the Avalara management console, and scroll to the bottom of the page."
msgid "Additional jurisdictions (tax locations) can be added in the Avalara management console. Navigate to either Avalara's `sandbox <https://sandbox.admin.avalara.com/>`_ or `production <https://admin.avalara.com/>`_ environment. This will depend on which type of account was set in the :doc:`integration <../avatax>`."
msgid "Next, navigate to :menuselection:`Settings --> Where you collect tax`. Choose between the three different tabs, depending on the business need. The first tab is :guilabel:`Sales and use tax`, where tax can be collected for the United States. Click the :icon:`fa-plus` :guilabel:`Add to where you collect sales and use tax` to add another location where the company collects sales and use tax."
msgid "The second option, is the :guilabel:`VAT/GST` tab where the :icon:`fa-plus` :guilabel:`Add a country or territory where you collect VAT/GST` can be selected to add another country or territory where the company collects VAT/GST."
msgid "Finally, on the far-right, is the :guilabel:`Customs duty` tab, where a country can be added where the company collects customs duty. Simply click on the :icon:`fa-plus` :guilabel:`Add a country where you calculate customs duty` icon below the tab."
msgid "Tax exemption certificates for customers can be added into the Avalara management console, so that *AvaTax* is aware of which customers may be exempt from paying certain taxes. To add an *exception certificate* navigate to :menuselection:`Exemptions --> Customer certificates`. From there, click on the :icon:`fa-plus` :guilabel:`Add a certificate` to configure an exemption."
msgid "An Avalara subscription to Exemption Certificate Management (ECM) is required in order to attach certificate images, and to be ready for an audit. For more on subscribing to this add-on, visit `Avalara <https://community.avalara.com/support/s/document-item?language=en_US&bundleId=hff1682048150115_hff1682048150115&topicId=fol1682356576230.html&_LANG=enus>`_."
msgid "Avalara's services include tax return services, for when it is time to file taxes at the end of the year. To access Avalara's tax services log, into the `management portal <https://admin.avalara.com/>`_. Then, from the main dashboard, click :guilabel:`Returns`. Avalara will prompt the Avalara user to log in for security purposes, and redirect the user to the *Returns* portal."
msgid "Click :guilabel:`Get started` to begin the tax return process. For more information, refer to this Avalara documentation: `About Managed Returns <https://community.avalara.com/support/s/document-item?language=en_US&bundleId=hps1656397152776_hps1656397152776&topicId=Learn_about_Managed_Returns.html&_LANG=enus>`_."
msgid "AvaTax is a tax calculation software that can be integrated with Odoo in the United States and Canada. Once the :doc:`integration setup <../avatax>` is complete, the calculated tax is simple and automatic."
msgid "Automatically calculate taxes on Odoo quotations and invoices with AvaTax by confirming the documents during the sales flow. Alternatively, calculate the taxes manually by clicking the :guilabel:`Compute taxes using Avatax` button while these documents are in draft mode."
msgid "The tax calculation is triggered during the following :ref:`automatic trigger <avatax/automatic-triggers>` and :ref:`manual trigger <avatax/manual-triggers>` circumstances."
msgid "Use the :guilabel:`Avalara Partner Code` field that is available on customer records, quotations, and invoices to cross-reference data in Odoo and AvaTax. This field is located under the :menuselection:`Other info` tab of the sales order or quotation in the :guilabel:`Sales` section."
msgid "On the customer record, navigate to *Contacts app* and select a contact. Then open the :guilabel:`Sales & Purchase` tab and the :guilabel:`Avalara Partner Code` under the :guilabel:`Sales` section."
msgid "Synchronization occurs with AvaTax, when the *invoice* is created in Odoo. This means the sales tax is recorded with Avalara (AvaTax software developer)."
msgid "After confirming a quotation and validating the delivery, click :guilabel:`Create Invoice`. Indicate whether it is a :guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)`, or :guilabel:`Down payment (fixed amount)`."
msgid "Then click :guilabel:`Create and view invoice`. The recorded taxes can be seen in the :guilabel:`Journal Items` tab of the invoice. There will be different taxes depending on the location of the :guilabel:`Delivery Address`."
msgid "An invoice cannot be :guilabel:`Reset to draft` because this causes de-synchronization with the AvaTax Portal. Instead, click :guilabel:`Add credit note` and state: `Sync with AvaTax Portal`. See this documentation: :doc:`../../../accounting/customer_invoices/credit_notes`."
msgid "Add a fixed price discount to a valuable customer by click :guilabel:`Add a line` on the customer's invoice. Add the product discount and set the :guilabel:`Price` to either a positive or negative value. To recalculate the taxes, click :guilabel:`Compute taxes using Avatax`."
msgid "It is possible to log Avalara/*AvaTax* actions in Odoo for further analysis, or verification of functionality. Logging is accessible through the *AvaTax* settings."
msgid "To view the logs, click on :guilabel:`Show logs` to the right of the :guilabel:`Start logging for 30 minutes`. This reveals a detailed list of Avalara/*AvaTax* actions. This list is sortable by the following columns:"
msgid "This field populates a raw transcription of the transaction, which involves the creation (or adjustment) of a sales invoice using the Avalara *AvaTax* API."
msgid "The transaction includes details, such as addresses for shipping from and to, line items describing the products or services, tax codes, tax amounts, and other relevant information."
msgid "The :guilabel:`Message` contains the calculated taxes for different jurisdictions and confirms the creation (or adjustment) of the transaction."
msgid "Custom fields can be made using Odoo *Studio*. Click the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` menu to the far-right of the header row. Then click :icon:`fa-plus` :guilabel:`Add custom field`. This action opens Odoo *Studio*."
msgid "Odoo *Studio* requires a *custom* pricing plan. Consult the database's customer success manager for more information on switching plans. Or to see if Odoo *Studio* is included in the database's current pricing plan. See this documentation: :doc:`../../../../studio`."
msgid "Cash basis taxes are due when the payment is made, as opposed to standard taxes that are due when the invoice is confirmed. Reporting your income and expenses to the government based on the cash basis method is mandatory in some countries and under some conditions."
msgid "You sell a product in the 1st quarter of your fiscal year, and the payment is received in the 2nd quarter. Based on the cash basis method, the tax you must pay is for the 2nd quarter."
msgid "Then, define the :guilabel:`Tax Cash Basis Journal`. Click on the external link button next to the journal to update its default properties such as the :guilabel:`Journal Name`, :guilabel:`Type` or :guilabel:`Short Code`."
msgid "Once this is done, go to :menuselection:`Accounting --> Configuration --> Accounting: Taxes` to configure your taxes. You can either :guilabel:`Create` a new tax or update an existing one by clicking on it."
msgid "In the :guilabel:`Advanced Options` tab, decide of the :guilabel:`Tax Exigilibity`. Select :guilabel:`Based on Payment`, so the tax is due when the payment of the invoice is received. You can then also define the :guilabel:`Cash Basis Transition Account` where the tax amount is recorded as long as the original invoice has not been reconciled."
msgid "To illustrate the impact of cash basis taxes on accounting transactions, let's take an example with the sales of a product that costs 1,000$, with a cash basis tax of 15%."
msgid "The journal items :guilabel:`Income account` vs. :guilabel:`Income account` are neutral, but they are needed to ensure correct tax reports in Odoo with accurate base tax amounts."
msgid "Using a default :guilabel:`Base Tax Received Account` is recommended so your balance is at zero and your income account is not polluted by unnecessary accounting movements. To do so, go to :menuselection:`Configuration --> Settings --> Taxes`, and select a :guilabel:`Base Tax Received Account` under :guilabel:`Cash Basis`."
msgid "EU intra-community distance selling involves the cross-border trade of goods and services from vendors registered for VAT purposes to individuals (B2C) located in a European Union member state. The transaction is conducted remotely, typically through online platforms, mail orders, telephone, or other means of communication."
msgid "EU intra-community distance selling is subject to specific VAT rules and regulations. The vendor must charge VAT per the VAT rate applicable in the buyer's country."
msgid "The **EU Intra-community Distance Selling** feature helps you comply with this regulation by creating and configuring new **fiscal positions** and **taxes** based on your company's country. To enable it, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`, tick :guilabel:`EU Intra-community Distance Selling`, and :guilabel:`Save`."
msgid "Whenever you add or modify taxes, you can automatically update your fiscal positions. To do so, go to :menuselection:`Accounting/Invoicing --> Settings --> Taxes --> EU Intra-community Distance Selling` and click on the :guilabel:`Refresh tax mapping`."
msgid "The :abbr:`OSS (One-Stop Shop)` system introduced by the European Union simplifies VAT collection for **cross-border** sales of goods and services. It primarily applies to business-to-consumer **(B2C)** cases. With the OSS, businesses can register for VAT in their home country and use a single online portal to handle VAT obligations for their sales within the EU. There are **two primary schemes**: the **Union OSS** scheme for cross-border services and the **Import OSS** scheme for goods valued at or below €150."
msgid "To generate **OSS sales** or **OSS imports** reports and submit them onto the OSS portal, go to :menuselection:`Accounting --> Reporting --> Tax Report`, click :guilabel:`Report: Generic Tax report`, and select either :guilabel:`OSS Sales` or :guilabel:`OSS Imports`. Once selected, click on :guilabel:`PDF`, :guilabel:`XLSX`, or :guilabel:`XML` in the top-left corner. This generates the currently-opened report in the selected format. Once generated, log into the platform of your competent federal authority to submit it onto the OSS portal."
msgid "Default taxes and accounts are set on products and customers to create new transactions on the fly. However, depending on the customers' and providers' localization and business type, using different taxes and accounts for a transaction might be necessary."
msgid "They can be applied :ref:`automatically <fiscal_positions/automatic>`, :ref:`manually <fiscal_positions/manual>`, or :ref:`assigned to a partner <fiscal_positions/partner>`."
msgid "To edit or create a fiscal position, go to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, and open the entry to modify or click on :guilabel:`New`."
msgid "The mapping only works with *active* taxes. Therefore, make sure they are active by going to :menuselection:`Accounting --> Configuration --> Taxes`."
msgid "To automatically apply a fiscal position following a set of conditions, go to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, open the fiscal position to modify, and tick :guilabel:`Detect Automatically`."
msgid "The fiscal positions' **sequence** defines which fiscal position is applied if all conditions set on multiple fiscal positions are met simultaneously."
msgid "For example, suppose the first fiscal position in a sequence targets *country A* while the second fiscal position targets a *country group* that comprises *country A*. In that case, only the first fiscal position will be applied to customers from *country A*."
msgid "To manually select a fiscal position, open a sales order, invoice, or bill, go to the :guilabel:`Other Info` tab and select the desired :guilabel:`Fiscal Position` before adding product lines."
msgid "To define which fiscal position must be used by default for a specific partner, go to :menuselection:`Accounting --> Customers --> Customers`, select the partner, open the :guilabel:`Sales & Purchase` tab, and select the :guilabel:`Fiscal Position`."
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."
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."
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**."
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`):"
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."
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)."
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."
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."
msgid "The Odoo TaxCloud integration has begun its decommissioning, starting in Odoo 17. New installations are prohibited in Odoo 17. In Odoo 18, the TaxCloud module(s) will **not** exist at all. Odoo recommends the use of the Avatax platform, instead."
msgid "TaxCloud calculates the sales tax rate in real time for every state, city, and special jurisdiction in the United States. It keeps track of which products are exempt from sales tax, and in which states each exemption applies."
msgid "Register an account on `TaxCloud.com <https://taxcloud.com/register>`_ and complete the setup. Once you go live, get the :guilabel:`TaxCloud API Keys` by clicking on :guilabel:`Stores`, then :guilabel:`Get Details`."
msgid "Add the store's :guilabel:`Login ID` under :guilabel:`API ID` and the store's :guilabel:`Key` under :guilabel:`API KEY`. Click on :guilabel:`Save`."
msgid "Click the :guilabel:`Refresh` button (:guilabel:`🗘`) next to :guilabel:`Default Category` to import the TIC :dfn:`Taxability Information Codes` product categories from TaxCloud. Some categories may imply specific tax rates or exemptions."
msgid "Select a :guilabel:`Default Category` and :guilabel:`Save`. The :guilabel:`Default Category` is applied when no :guilabel:`TaxCloud Category` is set on your products or product categories, or when no product is found on an order/invoice."
msgid "If you need to use more than one TIC category (i.e., the :guilabel:`Default Category`), go to the product's :guilabel:`General Information` tab and select a :guilabel:`TaxCloud Category`."
msgid "If you want to configure multiple products simultaneously, ensure they share the same :guilabel:`Product Category` and click on the external link button (:guilabel:`🡕`) to set a :guilabel:`TaxCloud Category` on the :guilabel:`Product Category` instead."
msgid "If you set a :guilabel:`TaxCloud Category` on a product and another on its :guilabel:`Product Category`, Odoo only considers the :guilabel:`TaxCloud Category` found on the product itself."
msgid "A :guilabel:`TaxCloud Category` set on a **parent product category** does not apply to its **child product categories**. For example, if you set :guilabel:`TaxCloud Category` on the *All* :guilabel:`Product Category`, it is not applied to the *All/Sales* :guilabel:`Product Category`."
msgid "Make sure your company address is complete, including the state and the ZIP code. Go to :menuselection:`Settings --> Companies: Update Info` to open and edit your company address."
msgid "To make sure the new taxes generated by the TaxCloud integration are created with the correct **Tax Payable** account, create a **user-defined default**. This process should be repeated for each one of your companies that uses TaxCloud."
msgid "A user-defined default impacts all records at creation. It means that **every** new tax is set up to record income in the specified Tax Payable account unless the tax is manually edited to specify a different income account (or if another user-defined default takes precedence)."
msgid "To do so, go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Chart of Accounts`, find the company's :guilabel:`Tax Payable` account, and click on :guilabel:`Setup`. Take note of the number after `id=` in the URL string; it is the **Tax Payable account ID** and will be used later."
msgid "Activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Settings --> Technical --> Actions: User-defined Defaults` and click on :guilabel:`Create`."
msgid "Use the search bar to filter for the :guilabel:`Tax Repartition Line` model, and use it a second time to filter for the :guilabel:`Account` field. Select the line with :guilabel:`Tax Repartition Line` under the :guilabel:`Model` column."
msgid "Once you are back to the :guilabel:`User-defined Defaults` creation, enter the **Tax Payable account ID** you took note of earlier under the :guilabel:`Default Value (JSON format)` field."
msgid "Sales taxes are calculated in Odoo based on :doc:`fiscal positions <fiscal_positions>`. A fiscal position for the United States is created when enabling TaxCloud."
msgid "You can configure Odoo to automatically detect to which customers the fiscal position should be applied. To do so, go to :menuselection:`Accounting Dashboard --> Configuration --> Accounting: Fiscal Positions` and select :guilabel:`Automatic Tax Mapping (TaxCloud)`. Enable :guilabel:`Detect Automatically` and then :guilabel:`Save`."
msgid "Now, this fiscal position is automatically set on any order or invoice if the customer country is *United States*. This triggers the automated tax computation."
msgid "If you use the **Coupon** or **Promotion Programs**, the integration with TaxCloud might behave unexpectedly. Indeed, as TaxCloud does not accept lines with negative amounts as part of the tax computation, the amount of the lines added by the promotion program must be deduced from the total of the lines it impacts."
msgid "This means, amongst other complications, that orders using coupons or promotions with a TaxCloud fiscal position **must** be invoiced completely - you cannot create invoices for partial deliveries, etc."
msgid "Another unexpected behavior is possible. For example, you sell a product for which you have a promotion program that provides a 50% discount. If the product's tax rate is 7%, the tax rate computed from the TaxCloud integration displays 3.5%. This happens because the discount is included in the price sent to TaxCloud. However, in Odoo, the discount is on another line entirely. Still, the tax computation is correct. Indeed, a 3.5% tax on the full price is the equivalent of a 7% tax on half the price, but this might be unexpected from a user point of view."
msgid "**VAT Information Exchange System** - abbreviated **VIES** - is a tool provided by the European Commission that allows you to check the validity of VAT numbers of companies registered in the European Union."
msgid "Odoo provides a feature to **Verify VAT Numbers** when you save a contact. This helps you make sure that your contacts provided you with a valid VAT number without leaving Odoo interface."
msgid "To enable this feature, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`, enable the **Verify VAT Numbers** feature, and click on *Save*."
msgid "In Odoo, we can register vendor bills **manually** or **automatically**, while the **Aged Payable report** provides an overview of all outstanding bills to help us pay the correct amounts on time."
msgid "Vendor bills can be automatically created by **sending an email** to an :ref:`email alias <invoice-digitization/email-alias>` associated with the purchase journal, or by **uploading a PDF** in :menuselection:`Accounting --> Vendors --> Bills` and then clicking :guilabel:`Upload`."
msgid ":guilabel:`Vendor`: Odoo automatically fills some information based on the vendor's registered information, previous purchase orders, or bills."
msgid ":guilabel:`Bill Reference`: add the sales order reference provided by the vendor and is used to do the :ref:`matching <accounting/payments/matching>` when you receive the products."
msgid ":guilabel:`Auto-Complete`: select a past bill/purchase order to automatically complete the document. The :guilabel:`Vendor` field should be completed prior to completing this field."
msgid "Click :guilabel:`Confirm` when the document is completed. The status of your document changes to :guilabel:`Posted` and a journal entry is generated based on the configuration on the invoice."
msgid "Select the :guilabel:`Journal`, the :guilabel:`Payment Method`, the :guilabel:`Amount` you wish to pay (full or partial payment), and the :guilabel:`Currency`. In the case of a partial payment (when the :guilabel:`Amount` paid is less than the total remaining amount on the vendor bill), the :guilabel:`Payment Difference` field displays the outstanding balance. You have two options:"
msgid ":guilabel:`Mark as fully paid`: In this case, select an account in the :guilabel:`Post Difference In` field and change the :guilabel:`Label` if needed. A journal entry will be created to balance the account receivable with the selected account."
msgid "The :guilabel:`Memo` field is filled automatically if the :guilabel:`Payment Reference` has been set correctly in the vendor bill. If the field is empty, select the vendor invoice number as a reference."
msgid "To get an overview of your open vendor bills and their related due dates, you can use the **Aged Payable report**. Go to :menuselection:`Accounting --> Reporting --> Partner Reports: Aged payable`."
msgid "By clicking the :guilabel:`Save` button, you can export the information available on the screen as a PDF or XLSX file and save it in the folder of your choice."
msgid "You might receive several bills for the same purchase order if your vendor is in back-order and is sending you invoices as they ship the products, or if your vendor is sending you a partial bill or asking for a deposit."
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**."
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."
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."
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."
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."
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."
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."
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."
msgid "The **Straight Line Depreciation Method** divides the initial Depreciable Value by the number of depreciations planned. All depreciation entries have the same amount."
msgid "The **Declining Depreciation Method** multiplies the Depreciable Value by the **Declining Factor** for each entry. Each depreciation entry has a lower amount than the previous entry. The last depreciation entry doesn't use the declining factor but instead has an amount corresponding to the balance of the depreciable value so that it reaches $0 by the end of the specified duration."
msgid "The **Declining Then Straight Line Depreciation Method** uses the Declining Method, but with a minimum Depreciation equal to the Straight Line Method. This method ensures a fast depreciation at the beginning, followed by a constant one afterward."
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`)."
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>`."
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*."
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."
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."
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."
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."
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."
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*."
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."
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`."
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."
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`)."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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`_)."
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."
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*."
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."
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`."
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."
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`_)."
msgid "Odoo uses :abbr:`OCR (optical character recognition)` and artificial intelligence technologies to recognize the content of the documents. Vendor bill and customer invoice forms are automatically created and populated based on the scanned invoices."
msgid "In :menuselection:`Accounting --> Configuration --> Settings --> Digitization`, check the box :guilabel:`Document Digitization` and choose whether :guilabel:`Vendor Bills` and :guilabel:`Customer Invoices` (this includes customer credit notes) should be processed automatically or on demand."
msgid "If you enable the :guilabel:`Single Invoice Line Per Tax` option, only one line is created per tax in the new bill, regardless of the number of lines on the invoice."
msgid "From the :guilabel:`Accounting Dashboard`, click on the :guilabel:`Upload` button of your vendor bills journal. Alternatively, go to :menuselection:`Accounting --> Customers --> Invoices` or :menuselection:`Accounting --> Vendors --> Bills` and select :guilabel:`Upload`."
msgid "You can configure your connected scanner to send scanned documents to an email alias. Emails sent to these aliases are converted into new draft customer invoices or vendor bills."
msgid "You can modify the email alias of a journal. To do so, go to the :guilabel:`Settings` app. Under :guilabel:`General Settings: Discuss`, enable :guilabel:`Custom Email Servers`, add an :guilabel:`Alias Domain`, and :guilabel:`Save`."
msgid "The email alias is now available in the :guilabel:`Advanced Settings` tab of the journal. Emails sent to this address will be converted automatically into new invoices or bills."
msgid "If you use the :doc:`Documents </applications/productivity/documents>` app, you can automatically send your scanned invoices to the :guilabel:`Finance` workspace (e.g., `inbox-financial@example.odoo.com`)."
msgid "The default email aliases `vendor-bills@` and `customer-invoices@` followed by the :guilabel:`Alias Domain` you set are automatically created for the :guilabel:`Vendor Bills` and :guilabel:`Customer Invoices` journals, respectively. Emails sent to these addresses are converted automatically into new invoices or bills."
msgid "To change a default email alias, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals`. Select the journal you want to edit, click on the :guilabel:`Advanced Settings` tab, and edit the `Email Alias`."
msgid "According to your settings, the document is either processed automatically, or you need to click on :guilabel:`Send for digitization` to do it manually."
msgid "Once the data is extracted from the PDF, you can correct it if necessary by clicking on the respective tags (available in :guilabel:`Edit` mode) and selecting the proper information instead."
msgid "It is essential to review and correct (if needed) the information uploaded during digitization. Then, you have to post the document by clicking on :guilabel:`Confirm`. In this manner, the AI learns, and the system identifies the correct data for future digitizations."
msgid "The **invoice digitization** is an In-App Purchase (IAP) service that requires prepaid credits to work. Digitizing one document consumes one credit."
msgid "To buy credits, go to :menuselection:`Accounting --> Configuration --> Settings --> Digitization` and click on :guilabel:`Buy credits`, or go to :menuselection:`Settings --> Odoo IAP` and click on :guilabel:`View My Services`."
msgid "Enterprise Odoo users with a valid subscription get free credits to test IAP features before deciding to purchase more credits for the database. This includes demo/training databases, educational databases, and one-app-free databases."
msgid "Odoo **Expenses** streamlines the management of expenses. After an employee submits their expenses in Odoo, the expenses are reviewed by management and accounting teams. Once approved, payments can then be processed and disbursed back to the employee for reimbursement(s)."
msgid "The first step to track expenses is to configure the different types of expenses for the company (managed as *expense categories* in Odoo). Each category can be as specific or generalized as needed. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories` to view the current expensable categories in a default list view."
msgid "To create a new expense category, click :guilabel:`New`. A product form will appear, with the description field labeled :guilabel:`Product Name`."
msgid "Expense categories are managed like products in Odoo. The expense category form follows the standard product form in Odoo, and the information entered is similar. Expense products will be referred to as expense categories throughout this document since the main menu refers to these as :guilabel:`Expense Categories`."
msgid "Only two fields are required, the :guilabel:`Product Name` and the :guilabel:`Unit of Measure`. Enter the :guilabel:`Product Name` in the field, and select the :guilabel:`Unit of Measure` from the drop-down menu (most products will be set to :guilabel:`Units`)."
msgid "The *Sales* app is where specification on the units of measure are created and edited (e.g. units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and ensure `Units of Measure` is enabled in the `Product Catalog` section. Click on the :guilabel:`Units of Measure` internal link to :doc:`view, create, and edit the units of measure <../inventory_and_mrp/inventory/product_management/configure/uom>`."
msgid "The :guilabel:`Cost` field on the product form is populated with a value of `0.00` by default. When a specific expense should always be reimbursed for a particular price, enter that amount in the :guilabel:`Cost` field. Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will report the actual cost when submitting an expense report."
msgid "The :guilabel:`Cost` field is always visible on the expense category form, but the :guilabel:`Sales Price` field is *only* visible if the :guilabel:`Sales Price` is selected under the :guilabel:`Re-Invoice Expenses` section. Otherwise, the :guilabel:`Sales Price` field is hidden."
msgid "**Meals**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense for a meal, they enter the actual amount of the bill and will be reimbursed for that amount. An expense for a meal costing $95.23 would equal a reimbursement for $95.23."
msgid "**Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for \"mileage\", they enter the number of miles driven in the :guilabel:`Quantity` field, and are reimbursed 0.30 per mile they entered. An expense for 100 miles would equal a reimbursement for $30.00."
msgid "**Monthly Parking**: Set the :guilabel:`Cost` to `75.00`. When an employee logs an expense for \"monthly parking\", the reimbursement would be for $75.00."
msgid "**Expenses**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense that is not a meal, mileage, or monthly parking, they use the generic :guilabel:`Expenses` product. An expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and the reimbursement would be for $350.00."
msgid "Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It is recommended to check with the accounting department to determine the correct account to reference in this field as it will affect reports."
msgid "Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields, if applicable. It is considered good practice to use a tax that is configured with :ref:`Tax Included in Price <taxes/included-in-price>`. Taxes will be automatically configured if this is set."
msgid "To record a new expense, begin in the main :menuselection:`Expenses` app dashboard, which presents the default :guilabel:`My Expenses` view. This view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses`."
msgid ":guilabel:`Description`: Enter a short description for the expense in the :guilabel:`Description` field. This should be short and informative, such as `lunch with client` or `hotel for conference`."
msgid ":guilabel:`Category`: Select the expense category from the drop-down menu that most closely corresponds to the expense. For example, an airplane ticket would be appropriate for an expense :guilabel:`Category` named :guilabel:`Air Travel`."
msgid "If the expense is for one single item/expense, and the category selected was for a single item, enter the cost in the :guilabel:`Total` field (the :guilabel:`Quantity` field is hidden)."
msgid "If the expense is for multiples of the same item/expense with a fixed price, the :guilabel:`Unit Price` is displayed. Enter the quantity in the :guilabel:`Quantity` field, and the total cost is automatically updated with the correct total (the :guilabel:`Unit Price` x the :guilabel:`Quantity` = the total). Be advised, the word \"total\" does not appear, the total cost simply appears below the :guilabel:`Quantity`."
msgid "For example, in the case of mileage driven, the :guilabel:`Unit Price` is populated as the cost *per mile*. Set the :guilabel:`Quantity` to the *number of miles* driven, and the total is calculated."
msgid ":guilabel:`Included Taxes`: If taxes were configured on the expense category, the tax percentage and amount appear automatically after entering either the :guilabel:`Total` or the :guilabel:`Quantity`."
msgid "When a tax is configured on an expense category, the :guilabel:`Included Taxes` value will update in real time as the :guilabel:`Total` or :guilabel:`Quantity` is updated."
msgid ":guilabel:`Paid By`: Click the radio button to indicate who paid for the expense and should be reimbursed. If the employee paid for the expense (and should be reimbursed) select :guilabel:`Employee (to reimburse)`. If the company paid directly instead (e.g. if the company credit card was used to pay for the expense) select :guilabel:`Company`. Depending on the expense category selected, this field may not appear."
msgid ":guilabel:`Expense Date`: Using the calendar module, enter the date the expense was incurred. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows to navigate to the correct month, then click on the specific day to enter the selection."
msgid ":guilabel:`Customer to Reinvoice`: If the expense is something that should be paid for by a customer, select the :abbr:`SO (Sales Order)` and customer that will be invoiced for this expense from the drop-down menu. All sales orders in the drop-down menu list both the :abbr:`SO (Sales Order)` as well as the company the sales order is written for, but after the expense is saved, the customer name disappears and only the :abbr:`SO (Sales Order)` is visible on the expense."
msgid "A customer wishes to have an on-site meeting for a custom garden (design and installation) and agrees to pay for the expenses associated with it (such as travel, hotel, meals, etc.). All expenses tied to that meeting would indicate the sales order for the custom garden (which also references the customer) as the :guilabel:`Customer to Reinvoice`."
msgid ":guilabel:`Analytic Distribution`: Select the account(s) the expense should be written against from the drop-down menu for either :guilabel:`Projects`, :guilabel:`Departments`, or both. Multiple accounts can be listed for each category if needed. Adjust the percentage for each analytic account by typing in the percentage value next to the account."
msgid ":guilabel:`Company`: If multiple companies are set up, select the company this expense should be filed for from the drop-down menu. The current company will automatically populate this field."
msgid "After the expense is created, the next step is to attach a receipt. Click the :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate to the receipt to be attached, and click :guilabel:`Open`. The new receipt is recorded in the chatter, and the number of receipts will appear next to the :guilabel:`📎 (paperclip)` icon beneath the expense form. More than one receipt can be attached to an individual expense, as needed. The number of receipts attached to the expense will be noted on the paperclip icon."
msgid "First, in the main :guilabel:`Expenses` app dashboard view (this view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses`), click :guilabel:`Scan`, and a file explorer pops up. Navigate to the receipt to be uploaded, click on it to select it, and then click :guilabel:`Open`."
msgid "The receipt is scanned, and a new entry is created with today's date as the :guilabel:`Expense Date`, and any other fields it can populate based on the scanned data, such as the total. Click on the new entry to open the individual expense form, and make any changes needed. The scanned receipt appears in the chatter."
msgid "Instead of individually creating each expense in the *Expenses* app, expenses can be automatically created by sending an email to an email alias."
msgid "To do so, first, an email alias needs to be configured. Go to :menuselection:`Expenses app --> Configuration --> Settings`. Ensure :guilabel:`Incoming Emails` is enabled."
msgid "If the domain alias needs to be set up, :guilabel:`Setup your domain alias` will appear beneath the incoming emails check box instead of the email address field. Refer to this documentation for setup instructions and more information: :doc:`/applications/websites/website/configuration/domain_names`. Once the domain alias is configured, the email address field will be visible beneath the incoming emails section."
msgid "Next, enter the email address to be used in the email field, and then click :guilabel:`Save`. Now that the email address has been entered, emails can be sent to that alias to create new expenses without having to be in the Odoo database."
msgid "To submit an expense via email, create a new email and enter the product's *internal reference* code (if available) and the amount of the expense in the email subject. Next, attach the receipt to the email. Odoo creates the expense by taking the information in the email subject and combining it with the receipt."
msgid "To check an expense categories internal reference, go to :menuselection:`Expenses app --> Configuration --> Expense Categories`. If an internal reference is listed on the expense category, it is listed in the :guilabel:`Internal Reference` column."
msgid "To add an internal reference on an expense category, click on the category to open the form. Enter the internal reference in the field. Beneath the :guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use this reference as a subject prefix when submitting by email.`"
msgid "For security purposes, only authenticated employee emails are accepted by Odoo when creating an expense from an email. To confirm an authenticated employee email address, go to the employee card in the :menuselection:`Employees` app, and refer to the :guilabel:`Work Email`"
msgid "When expenses are ready to submit (such as at the end of a business trip, or once a month), an *expense report* needs to be created. Go to the main :menuselection:`Expenses` app dashboard, which displays a default :guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My Expenses --> My Expenses`."
msgid "Expenses are color coded by status. Any expense with a status of :guilabel:`To Report` (expenses that still need to be added to an expense report) the text appears in blue. All other statuses (:guilabel:`To Submit`, :guilabel:`Submitted`, and :guilabel:`Approved`) the text appears in black."
msgid "First, select each individual expense for the report by clicking the check box next to each entry, or quickly select all the expenses in the list by clicking the check box next to :guilabel:`Expense Date`."
msgid "Another way to quickly add all expenses that are not on an expense report is to click :guilabel:`Create Report` without selecting any expenses, and Odoo will select all expenses with a status of :guilabel:`To Submit` that are not already on a report."
msgid "Any expense can be selected from the :guilabel:`My Expenses` list, regardless of status. The :guilabel:`Create Report` button is visible as long as there is a minimum of 1 expense with a status of :guilabel:`To Report` selected. When the :guilabel:`Create Report` button is clicked, only expenses with a status of :guilabel:`To Submit` that are *not* currently on another expense report will appear in the newly created expense report."
msgid "Once the expenses have been selected, click the :guilabel:`Create Report` button. The new report appears with all the expenses listed in the :guilabel:`Expense` tab. If there is a receipt attached to an individual expense, a :guilabel:`📎 (paperclip)` icon appears next to the :guilabel:`Customer to Reinvoice` and :guilabel:`Analytic Distribution` columns."
msgid "When the report is created, the date range for the expenses appears in the :guilabel:`Expense Report Summary` field by default. It is recommended to edit this field with a short summary for each report to help keep expenses organized. Enter a short description for the expense report (such as `Client Trip NYC`, or `Repairs for Company Car`) in the :guilabel:`Expense Report Summary` field. Next, select a :guilabel:`Manager` from the drop-down menu to assign a manager to review the report. If needed, the :guilabel:`Journal` can be changed. Use the drop-down menu to select a different :guilabel:`Journal`."
msgid "If some expenses are not on the report that should be, they can still be added. Click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense` tab. A pop up appears with all the available expenses that can be added to the report (with a status of :guilabel:`To Submit`). Click the check box next to each expense to add, then click :guilabel:`Select`. The items now appear on the report that was just created. If a new expense needs to be added that does *not* appear on the list, click :guilabel:`New` to create a new expense and add it to the report."
msgid "Go to the main :menuselection:`Expenses` app dashboard (also accessed by going to :menuselection:`Expenses app --> My Expenses --> My Expenses`)"
msgid "When an expense report is completed, the next step is to submit the report to a manager for approval. Reports must be individually submitted, and cannot be submitted in batches. Open the specific report from the list of expense reports (if the report is not already open). To view all expense reports, go to :menuselection:`Expenses app --> My Expenses --> My Reports`."
msgid "If the list is large, grouping the results by status may be helpful since only reports that have a :guilabel:`To Submit` status need to be submitted, reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not."
msgid "The :guilabel:`To Submit` expenses are easily identifiable not just from the :guilabel:`To Submit` status, but the text appears in blue, while the other expenses text appears in black."
msgid "The status of each report is shown in the :guilabel:`Status` column on the right. If the :guilabel:`Status` column is not visible, click the :guilabel:`Additional Options (two dots)` icon at the end of the row, and enable :guilabel:`Status`."
msgid "Click on a report to open it, then click :guilabel:`Submit To Manager`. After submitting a report, the next step is to wait for the manager to approve it."
msgid "In Odoo, not just anyone can approve expense reports— only users with the necessary rights (or permissions) can. This means that a user must have at least *Team Approver* rights for the *Expenses* app. Employees with the necessary rights can review expense reports, approve or reject them, and provide feedback thanks to the integrated communication tool."
msgid "If the *Settings* app is not available, then certain rights are not set on the account. Check the :guilabel:`Access Rights` tab of a user's card in the :menuselection:`Settings` app. the :guilabel:`Administration` section (bottom right of the :guilabel:`Access Rights` tab) is set to one of three options:"
msgid "Click on an individual to view their card, which displays the :guilabel:`Access Rights` tab in the default view. Scroll down to the :guilabel:`Human Resources` section. Under :guilabel:`Expenses`, there are four options:"
msgid ":guilabel:`Administrator`: The user can view and approve any expense report, as well as access the reporting and configuration menus in the *Expenses* app."
msgid "Users who are able to approve expense reports (typically managers) can easily view all expense reports they have access rights to. Go to :menuselection:`Expenses app --> Expense Reports`, and a list appears with all expense reports that have a status of either :guilabel:`To Submit`, :guilabel:`Submitted`, :guilabel:`Approved`, :guilabel:`Posted`, or :guilabel:`Done`. Expense reports with a status of :guilabel:`Refused` are hidden in the default view."
msgid "When viewing expense reports, there is a panel of filters that can be enabled or disabled on the left side. The three categories that filters can be applied on are :guilabel:`Status`, :guilabel:`Employee`, and :guilabel:`Company`. To view only expense reports with a particular status, enable the specific status filter to display the expense reports with only that status. Disable the specific status filter to hide the reports with that status. To view expense reports for a particular employee and/or company, enable the specific employee name filter and/or company filter in the :guilabel:`Employee` and :guilabel:`Company` sections."
msgid "Reports can be approved in two ways (individually or several at once) and refused only one way. To approve multiple expense reports at once, remain in the list view. First, select the reports to approve by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list."
msgid "Only reports with a status of :guilabel:`Submitted` can be approved. It is recommended to only display the submitted reports by adjusting the status filter on the left side by only having the :guilabel:`Submitted` filter enabled."
msgid "If a report is selected that is unable to be approved, the :guilabel:`Approve Report` button **will not appear**, indicating there is a problem with the selected report(s)."
msgid "To approve an individual report, click on a report to go to a detailed view of that report. In this view, several options are presented: :guilabel:`Approve`, :guilabel:`Report in Next Payslip`, :guilabel:`Refuse`, or :guilabel:`Reset to draft`. Click :guilabel:`Approve` to approve the report."
msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to Refuse Expense` field, and then click :guilabel:`Refuse`."
msgid "Team managers can easily view all the expense reports for their team members. While in the :guilabel:`Expense Reports` view, click the drop-down arrow in the right-side of the search box, and click on :guilabel:`My Team` in the :guilabel:`Filters` section. This presents all the reports for the manager's team."
msgid "If more information is needed, such as a missing receipt, communication is easy from the chatter. In an individual report, simply click :guilabel:`Send message` to open the message text box. Type in a message, tagging the proper person (if needed), and post it to the chatter by clicking :guilabel:`Send`. The message is posted in the chatter, and the person tagged will be notified via email of the message, as well as any followers."
msgid "The only people that can be tagged in a message are *followers*. To see who is a follower, click on the :guilabel:`👤 (person)` icon to display the followers of the expense."
msgid "Once an expense report is approved, the next step is to post the report to the accounting journal. To view all expense reports, go to :menuselection:`Expenses app --> Expense Reports`. To view only the expense reports that have been approved and need to be posted, adjust the filters on the left side so that only the :guilabel:`Approved` status is enabled."
msgid "Just like approvals, expense reports can be posted in two ways (individually or several at once). To post multiple expense reports at once, remain in the list view. First, select the reports to post by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list. Next, click :guilabel:`Post Entries`."
msgid "To post an individual report, click on a report to go to the detailed view of that report. In this view, several options are presented: :guilabel:`Post Journal Entries`, :guilabel:`Report In Next Payslip`, :guilabel:`Refuse`, or :guilabel:`Reset to Draft`. Click :guilabel:`Post Journal Entries` to post the report."
msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to Refuse Expense` field, and then click :guilabel:`Refuse`. Refused reports can be viewed by going to :menuselection:`Expenses app --> Expense Reports`, then adjusting the filters on the left so that only :guilabel:`Refused` is selected. This will only show the refused expense reports."
msgid "After an expense report is posted to an accounting journal, the next step is to reimburse the employee. To view all the expense reports to pay, go to :menuselection:`Expenses app --> Expense Reports --> Reports To Pay`."
msgid "Just like approvals and posting, expense reports can be paid in two ways (individually or several at once). To pay multiple expense reports at once, remain in the list view. First, select the reports to pay by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list. Next, click :guilabel:`Register Payment`."
msgid "To pay an individual report, click on a report to go to a detailed view of that report. Click :guilabel:`Register Payment` to pay the employee."
msgid "A :guilabel:`Register Payment` pop-up appears, and the :guilabel:`Journal`, :guilabel:`Payment Method`, and :guilabel:`Payment Date` can be modified, if needed. When the selections are correct, click :guilabel:`Create Payment` to send the payment to the employee."
msgid "To pay an individual report, click on a report in the list view to go to a detailed view of that report. Click :guilabel:`Register Payment` to pay the employee. A :guilabel:`Register Payment` pop-up appears, but when paying an individual expense report instead of several at once, more options appear in the pop-up. In addition to the :guilabel:`Journal`, :guilabel:`Payment Method`, and :guilabel:`Payment Date` fields, a :guilabel:`Recipient Bank Account`, :guilabel:`Amount`, and :guilabel:`Memo` field appear. Select the employee's bank account from the drop-down menu to directly deposit the payment to their account. When all other selections are correct, click :guilabel:`Create Payment` to send the payment to the employee."
msgid "If expenses are tracked on customer projects, expenses can be automatically charged back to the customer. This is done by creating an expense, referencing the :abbr:`SO (Sales Order)` the expense should be added to, and then creating the expense report. Next, managers approve the expense report, and the accounting department posts the journal entries. Finally, once the expense report is posted to a journal, the expense(s) appears on the :abbr:`SO (Sales Order)` that was referenced. The sales order can then be invoiced, thus invoicing the customer for the expense."
msgid "First, specify the invoicing policy for each expense category. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories`. Click on the expense category to open the expense category form. Under the :guilabel:`Invoicing` section, click the radio button next to the desired selection for :guilabel:`Re-Invoicing Expenses`. Options are :guilabel:`None`, :guilabel:`At cost`, and :guilabel:`Sales price`."
msgid "First, when :ref:`creating a new expense <expenses/new>`, the correct information needs to be entered in order to re-invoice a customer. Select the *sales order* the expense will appear on in the :guilabel:`Customer to Reinvoice` section, from the drop-down menu. Next, select the :guilabel:`Analytic Account` the expense will be posted to. After the expense(s) are created, the expense report needs to be :ref:`created <expenses/report>` and :ref:`submitted <expenses/submit>` as usual."
msgid "Selecting a :guilabel:`Customer to Reinvoice` when creating an expense is critical, since this is what causes the expenses to be automatically invoiced after an expense report is approved."
msgid "The :guilabel:`Customer to Reinvoice` field can be modified *until an expense report is* **approved**, then the field is no longer able to be modified."
msgid "Only employees with permissions (typically managers or supervisors) can :ref:`approve expenses <expenses/approve>`. Before approving an expense report, ensure the :guilabel:`Analytic Distribution` is set on every expense line of a report. If an :guilabel:`Analytic Distribution` is missing, assign the correct account(s) from the drop-down menu, and then click :guilabel:`Approve` or :guilabel:`Refuse`."
msgid "The accounting department is typically responsible for :ref:`posting journal entries <expenses/post>`. Once an expense report is approved, it can then be posted. The :abbr:`SO (Sales Order)` is **only** updated *after the journal entries are posted*. One the journal entries are posted, the expenses now appear on the referenced :abbr:`SO (Sales Order)`."
msgid "Once the :abbr:`SO (Sales Order)` has been updated, it is time to invoice the customer. After the expense report has been approved and the journal entries have been posted, click the :guilabel:`Sales Orders` smart button to open the :abbr:`SO (Sales Order)`. The expenses to be re-invoiced are now on the :abbr:`SO (Sales Order)`."
msgid "More than one :abbr:`SO (Sales Order)` can be referenced on an expense report. If more than one :abbr:`SO (Sales Order)` is referenced, the :guilabel:`Sales Orders` smart button will list the number of :abbr:`SO (Sales Order)`'s. If multiple :abbr:`SO (Sales Order)`'s are listed, the :guilabel:`Sales Orders` smart button opens a list view of all the :abbr:`SO (Sales Order)`'s on the expense report. Click on a :abbr:`SO (Sales Order)` to open the individual :abbr:`SO (Sales Order)`."
msgid "Next, click :guilabel:`Create Invoice`, and select if the invoice is for a :guilabel:`Regular invoice`, a :guilabel:`Down payment (percentage)`, or a :guilabel:`Down payment (fixed amount)` by clicking the radio button next to it. Then, click :guilabel:`Create Invoice`. The customer has now been invoiced for the expenses."
msgid "**Fiscal Localization Packages** are country-specific modules that install pre-configured taxes, fiscal positions, chart of accounts, and legal statements on your database. Some additional features, such as the configuration of specific certificates, are also added to your Accounting app, following your fiscal administration requirements."
msgid "To install a new package, go to :menuselection:`Accounting --> Configuration --> Fiscal Localization`, click on **Install More Packages**, and install your country's module."
msgid "These packages require you to fine-tune your chart of accounts according to your needs, activate the taxes you use, and configure your country-specific statements and certifications."
msgid "Odoo Accounting can be used in many countries out of the box by installing the appropriate module. Here is a list of all :ref:`fiscal localization package <fiscal_localizations/packages>` that are available on Odoo."
msgid "Default :ref:`fiscal localization package <fiscal_localizations/packages>`, which represents the minimal configuration to operate in Argentina under the :abbr:`AFIP (Administración Federal de Ingresos Públicos)` regulations and guidelines."
msgid "(optional) Allows the user to see Identification Type and AFIP Responsibility in the eCommerce checkout form in order to create electronic invoices."
msgid "Once the localization modules are installed, the first step is to set up the company's data. In addition to the basic information, a key field to fill in is the :guilabel:`AFIP Responsibility Type`, which represents the fiscal obligation and structure of the company."
msgid "In Accounting, there are three different :guilabel:`Chart of Accounts` packages to choose from. They are based on a company's AFIP responsibility type, and consider the difference between companies that do not require as many accounts as the companies that have more complex fiscal requirements:"
msgid "Testing is provided so that the companies can test their databases until they are ready to move into the **Production** environment. As these two environments are completely isolated from each other, the digital certificates of one instance are not valid in the other one."
msgid "To select a database environment, go to :menuselection:`Accounting --> Settings --> Argentinean Localization` and choose either :guilabel:`Prueba (Testing)` or :guilabel:`Produccion (Production)`."
msgid ":guilabel:`Generate Certificate Sign Request (Odoo)`. When this option is selected, a file with extension `.csr` (certificate signing request) is generated to be used in the AFIP portal to request the certificate."
msgid ":guilabel:`Generate Certificate (AFIP)`. Access the AFIP portal and follow the instructions described in `this document <https://drive.google.com/file/d/17OKX2lNWd1bjUt3NxfqcCKBkBh-Xlpo-/ view>`_ to get a certificate."
msgid ":guilabel:`Upload Certificate and Private Key (Odoo)`. Once the certificate is generated, upload it to Odoo using the :guilabel:`Pencil` icon next to the field :guilabel:`Certificado` and select the corresponding file."
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>`_. Furthermore, Odoo allows the user to test electronic invoicing locally without a Homologation Certificate. The following message will be in the chatter when testing locally:"
msgid "As part of the Argentinean localization, document types defined by the AFIP are now available in the **Partner form**. Information is essential for most transactions. There are six :guilabel:`Identification Types` available by default, as well as 32 inactive types."
msgid "In Argentina, the document type and corresponding transactions associated with customers and vendors is defined by the AFIP Responsibility type. This field should be defined in the **Partner form**."
msgid "As part of the localization module, the taxes are created automatically with their related financial account and configuration, e.g., 73 taxes for :guilabel:`Responsable Inscripto`."
msgid "Some Argentinean taxes are not commonly used for all companies, and those less common options are labeled as inactive in Odoo by default. Before creating a new tax, be sure to check if that tax is not already included as inactive."
msgid "In some Latin American countries, like Argentina, some accounting transactions such as invoices and vendor bills are classified by document types defined by the governmental fiscal authorities. In Argentina, the `AFIP <https://www.afip.gob.ar/>`__ is the governmental fiscal authority that defines such transactions."
msgid "The document type is an essential piece of information that needs to be clearly displayed in printed reports, invoices, and journal entries that list account moves."
msgid "Each document type can have a unique sequence per journal where it is assigned. As part of the localization, the document type includes the country in which the document is applicable (this data is created automatically when the localization module is installed)."
msgid "For Argentina, the :guilabel:`Document Types` include a letter that helps indicate the type of transaction or operation. For example, when an invoice is related to a(n):"
msgid "The documents included in the localization already have the proper letter associated with each :guilabel:`Document Type`, so there is no further configuration necessary."
msgid "The onditions applied based on the type of issuer and receiver (e.g., the type of fiscal regime of the buyer and the type of fiscal regime of the vendor)."
msgid "In the Argentinean localization, the journal can have a different approach depending on its usage and internal type. To configure journals, go to :menuselection:`Accounting --> Configuration --> Journals`."
msgid "For sales and purchase journals, it's possible to activate the option :guilabel:`Use Documents`, which enables a list of :guilabel:`Document Types` that can be related to the invoices and vendor bills. For more detail on invoices, please refer to the section :ref:`2.3 document types <document-types>`."
msgid "If the sales or purchase journals do not have the :guilabel:`Use Documents` option activated, they will not be able to generate fiscal invoices, meaning, their use case will be mostly limited to monitoring account moves related to internal control processes."
msgid "The :guilabel:`AFIP POS System` is a field only visible for the **Sales** journals and defines the type of AFIP POS that will be used to manage the transactions for which the journal is created."
msgid ":guilabel:`wsfev1: Electronic Invoice`: is the most common service, which is used to generate invoices for document types A, B, C, M with no detail per item;"
msgid ":guilabel:`wsbfev1: Electronic Fiscal Bond`: is for those who invoice capital goods and wish to access the benefit of the Electronic Tax Bonds granted by the Ministry of Economy. For more details go to: `Fiscal Bond <https://www.argentina.gob.ar/acceder-un-bono-por-fabricar-bienes-de-capital>`__;"
msgid ":guilabel:`wsfexv1: Electronic Exportation Invoice`: is used to generate invoices for international customers and transactions that involve exportation processes, the document type related is type \"E\"."
msgid ":guilabel:`AFIP POS Address`: is the field related to the commercial address registered for the POS, which is usually the same address as the company. For example, if a company has multiple stores (fiscal locations) then the AFIP will require the company to have one AFIP POS per location. This location will be printed in the invoice report;"
msgid ":guilabel:`Unified Book`: when the AFIP POS System is Preimpresa, then the document types (applicable to the journal) with the same letter will share the same sequence. For example:"
msgid "When creating :guilabel:`Purchase Journals`, it's possible to define whether they are related to document types or not. In the case where the option to use documents is selected, there would be no need to manually associate the document type sequences, since the document number is provided by the vendor."
msgid "**Invoice for a customer IVA Responsable Inscripto, prefix A** is the type of document that shows all the taxes in detail along with the customer's information."
msgid "**Invoice for an end customer, prefix B** is the type of document that does not detail the taxes, since the taxes are included in the total amount."
msgid "The most common :guilabel:`Document Type` will be defined automatically for the different combinations of AFIP responsibility type but it can be updated manually by the user before confirming the invoice."
msgid "When using electronic invoices, if all the information is correct then the invoice is posted in the standard way unless there is an error that needs to be addressed. When error messages pop up, they indicate both the issue that needs attention along with a proposed solution. If an error persists, the invoice remains in draft until the issue is resolved."
msgid ":guilabel:`A. Tax excluded`: in this case the taxed amount needs to be clearly identified in the report. This condition applies when the customer has the following AFIP Responsibility type of **Responsable Inscripto**;"
msgid ":guilabel:`B. Tax amount included`: this means that the taxed amount is included as part of the product price, subtotal, and totals. This condition applies when the customer has the following AFIP Responsibility types:"
msgid "For electronic invoices that include :guilabel:`Services`, the AFIP requires to report the service starting and ending date, this information can be filled in the tab :guilabel:`Other Info`."
msgid "If the dates are not selected manually before the invoice is validated, the values will be filled automatically with the first and last day of the invoice's month."
msgid "Invoices related to :guilabel:`Exportation Transactions` require that a journal uses the AFIP POS System **Expo Voucher - Web Service** so that the proper document type(s) can be associated."
msgid "When the customer selected in the invoice is configured with an AFIP responsibility type :guilabel:`Cliente / Proveedor del Exterior` - :guilabel:`Ley N° 19.640`, Odoo automatically assigns the:"
msgid "The :guilabel:`Electronic Fiscal Bond` is used for those who invoice capital goods and wish to access the benefit of the Electronic Tax Bonds granted by the Ministry of Economy."
msgid "For SME invoices, there are several document types that are classified as **MiPyME**, which are also known as **Electronic Credit Invoice** (or **FCE** in Spanish). This classification develops a mechanism that improves the financing conditions for small and medium-sized businesses, and allows them to increase their productivity, through the early collection of credits and receivables issued to their clients and/or vendors."
msgid "A bank account type CBU must be related to the emisor, otherwise the invoice cannot be validated, having an error message such as the following."
msgid "use the :guilabel:`Credit and Debit Note` buttons, so all the information from the invoice is transferred to the new :guilabel:`Credit and Debit Note`;"
msgid "the same currency as the source document must be used. When using a secondary currency there is an exchange difference if the currency rate is different between the emission day and the payment date. It is possible to create a credit/debit note to decrease/increase the amount to pay in ARS."
msgid "the :guilabel:`Credit Note`, is created to annulate the FCE document, in this case the field :guilabel:`FCE, is Cancellation?` must be *empty* (false)."
msgid "The :guilabel:`PDF Report` related to electronic invoices that have been validated by the AFIP includes a barcode at the bottom of the format which represents the CAE number. The expiration date is also displayed as it is a legal requirement."
msgid "For auditing and troubleshooting purposes, it is possible to obtain detailed information of an invoice number that has been previously sent to the AFIP. To retrieve this information, activate the :ref:`developer mode <developer-mode>`, then go to the :menuselection:`Accounting` menu and click on the button :guilabel:`Consult Invoice` button in AFIP."
msgid "It is also possible to retrieve the last number used in AFIP for a specific document type and POS Number as a reference for any possible issues on the sequence synchronization between Odoo and AFIP."
msgid "Based on the purchase journal selected for the vendor bill, the :guilabel:`Document Type` is now a required field. This value is auto-populated based on the AFIP Responsibility type of Issuer and Customer, but the value can be changed if necessary."
msgid "The :guilabel:`Document Number` field needs to be registered manually and the format will be validated automatically. However, in case the format is invalid, a user error will be displayed indicating the correct format that is expected."
msgid "The vendor bill number is structured in the same way as the customer invoices, excepted that the document sequence is entered by the user using the following format: *Document Prefix - Letter - Document Number*."
msgid "As most companies have internal controls to verify that the vendor bill is related to an AFIP valid document, an automatic validation can be set in :menuselection:`Accounting --> Settings --> Argentinean Localization --> Validate document in the AFIP`, considering the following levels:"
msgid ":guilabel:`Available:` the verification is done. In case the number is not valid, it only displays a warning but still allows the vendor bill to be posted;"
msgid "With the vendor validation settings enabled, a new button shows up on the vendor bills inside of Odoo, labeled :guilabel:`Verify on AFIP`, which is located next to the :guilabel:`AFIP Authorization code` field."
msgid "In case the vendor bill cannot be validated in AFIP, a value of :guilabel:`Rejected` will be displayed on the dashboard and the details of the invalidation will be added to the chatter."
msgid "The vendor bill will be registered using one item for each product that is part of the VAT base amount, and an additional item to register the amount of the exempt concept."
msgid "The vendor bill will be registered using one item for each product that is part of the VAT base amount, and the perception tax can be added in any of the product lines. As a result, there will be one tax group for the VAT and another for the perception. The perception default value is always :guilabel:`0.10`."
msgid "To edit the VAT perception and set the correct amount, you should use the :guilabel:`Pencil` icon that is the next to the :guilabel:`Perception` amount. After the VAT perception amount has been set, the invoice can then be validated."
msgid "To install the *Third Party and Deferred/Electronic Checks Management* module, go to :menuselection:`Apps` and search for the module by its technical name `l10n_latam_check` and click the :guilabel:`Activate` button."
msgid "Once all the configurations are made for the Argentinian electronic invoice flow, it is also needed to complete certain configurations for the own checks and the third party checks flows."
msgid "Configure the bank journal used to create your own checks by going to :menuselection:`Accounting --> Configuration --> Journals`, selecting the bank journal, and opening the :guilabel:`Outgoing Payments` tab."
msgid ":guilabel:`Checks` should be available as a :guilabel:`Payment Method`. If not, click :guilabel:`Add a line` and type `Checks` under :guilabel:`Payment Method` to add them"
msgid "On the payment registration modal, select the bank journal from which the payment is to be made and set the :guilabel:`Check Cash-In Date`, and the :guilabel:`Amount`."
msgid "To manage current checks, the :guilabel:`Check Cash-In Date` field must be left blank or filled in with the current date. To manage deferred checks, the :guilabel:`Check Cash-In Date` must be set in the future."
msgid "To manage your existing own checks, navigate to :menuselection:`Accounting --> Vendors --> Own Checks`. This window shows critical information such as the dates when checks need to be paid, the total quantity of checks, and the total amount paid in checks."
msgid "It is important to note that the list is pre-filtered by checks that are still *not reconciled* with a bank statement - that were not yet debited from the bank - which can be verified with the :guilabel:`Is Matched with a Bank Statement` field. If you want to see all of your own checks, delete the :guilabel:`No Bank Matching` filter by clicking on the :guilabel:`X` symbol."
msgid "To cancel an own check created in Odoo, navigate to :menuselection:`Accounting --> Vendors --> Own Checks` and select the check to be canceled, then click on the :guilabel:`Void Check` button. This will break the reconciliation with the vendor bills and the bank statements and leave the check in a **canceled** state."
msgid "In order to register payments using third party checks, two specific journals need to be configured. To do so, navigate to :menuselection:`Accounting --> Configuration --> Journals` and create two new journals:"
msgid "In the :guilabel:`Journal Entries` tab, set :guilabel:`Cash Account`: to `1.1.1.02.010 Cheques de Terceros`, input a :guilabel:`Short Code` of your choice, and select a :guilabel:`Currency`"
msgid "For new incoming third party checks, go to :menuselection:`Incoming Payments tab --> Add a line` and select :guilabel:`New Third Party Checks`. This method is used to create *new* third party checks."
msgid "For incoming and outgoing existing third party checks, go to :menuselection:`Incoming Payments tab --> Add a line` and select :guilabel:`Existing Third Party Checks`. Repeat the same step for the :guilabel:`Outgoing Payments` tab. This method is used to receive and/or pay vendor bills using already *existing* checks, as well as for internal transfers."
msgid "The *Rejected Third Party Checks* journal also needs to be created and/or configured. This journal is used to manage rejected third party checks and can be utilized to send checks rejected at the moment of collection or when coming from vendors when rejected."
msgid "In the :guilabel:`Journal Entries` tab, set :guilabel:`Cash Account`: to `1.1.1.01.002 Rejected Third Party Checks`, input a :guilabel:`Short Code` of your choice, and select a :guilabel:`Currency`"
msgid "To register a *new* third party check for a customer invoice, click the :guilabel:`Register Payment` button. In the pop-up window, you must select :guilabel:`Third Party Checks` as journal for the payment registration."
msgid "Select :guilabel:`New Third Party Checks` as :guilabel:`Payment Method`, and fill in the :guilabel:`Check Number`, :guilabel:`Payment Date`, and :guilabel:`Check Bank`. Optionally, you can manually add the :guilabel:`Check Issuer Vat`, but this is automatically filled by the customer's VAT number related to the invoice."
msgid "To pay a vendor bill with an *existing* check, click the :guilabel:`Register Payment` button. In the pop-up window, you must select :guilabel:`Third Party Checks` as journal for the payment registration."
msgid "Select :guilabel:`Existing Third Party Checks` as :guilabel:`Payment Method`, and select a check from the :guilabel:`Check` field. The field shows all **available existing checks** to be used as payment for vendor bills."
msgid "When an **existing third party check** is used, you can review the operations related to it. For example, you can see if a third party check made to pay a customer invoice was later used as an existing third party check to pay a vendor bill."
msgid "To do so, either go to :menuselection:`Accounting --> Customers --> Third Party Checks` or :menuselection:`Accounting --> Vendors --> Own Checks` depending on the case, and click on a check. In the :guilabel:`Check Current Journal` field, click on :guilabel:`=> Check Operations` to bring up the check's history and movements."
msgid "As part of the localization installation, financial reporting for Argentina was added to the :guilabel:`Accounting` dashboard. Access these reports by navigating to :menuselection:`Accounting --> Reporting --> Argentinean Reports`"
msgid "The :guilabel:`Sales VAT` book report can be exported in a `.zip` file :guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` files to upload in the AFIP portal."
msgid "The :guilabel:`Purchases VAT` book report can be exported in a `.zip` file :guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` files to upload in the AFIP portal."
msgid "Pivot table where you can validate the gross income in each jurisdiction. Affidavit for the corresponding taxes to pay, therefore it is not sent to the AFIP."
msgid "Pivot table where you can validate the gross purchases in each jurisdiction. Affidavit for the corresponding taxes to pay, therefore it is not sent to the AFIP."
msgid "The Employment Hero module synchronizes payslip accounting entries (e.g., expenses, social charges, liabilities, taxes) from Employment Hero to Odoo automatically. Payroll administration is still done in Employment Hero. We only record the journal entries in Odoo."
msgid "Configure the **Employment Hero API** by going to :menuselection:`Accounting --> Configuration --> Settings`. More fields become visible after clicking on :guilabel:`Enable Employment Hero Integration`."
msgid "The API syncs the journal entries from Employment Hero to Odoo and leaves them in draft mode. The reference includes the Employment Hero payslip entry ID in brackets for the user to easily retrieve the same record in Employment Hero and Odoo."
msgid "By default, the synchronization happens once per week. You can fetch the records manually by going to :menuselection:`Accounting --> Configuration --> Settings` and, in the :guilabel:`Enable Employment Hero Integration` option, click on :guilabel:`Fetch Payruns Manually`."
msgid "For the API to work, you need to create the same accounts as the default accounts of your Employment Hero business (**same name and same code**) in Odoo. You also need to choose the correct account types in Odoo to generate accurate financial reports."
msgid ":ref:`Install <general/install>` the following modules to get all the features of the Belgian localization, following the :abbr:`IFRS(International Financial Reporting Standards)` rules."
msgid "The Belgian chart of accounts includes pre-configured accounts as described in the :abbr:`PCMN(Plan Comptable Minimum Normalisé)`. To add a new account, click :guilabel:`New`. A new line appears. Fill it in, click :guilabel:`Save`, and then :guilabel:`Setup` to configure it further."
msgid "Default Belgian taxes are created automatically when the :guilabel:`Belgium - Accounting` and the :guilabel:`Belgium - Accounting Reports` modules are installed. Each tax impacts the Belgian :guilabel:`Tax Report`, available by going to :menuselection:`Accounting --> Reporting --> Statements Reports: Tax Report`."
msgid "In Belgium, the standard VAT rate is **21%**, but there are lower rates for some categories of goods and services. An intermediate rate of **12%** is applied on social housing and food served in restaurants, while a reduced rate of **6%** applies to most basic goods, such as food, water supply, books, and medicine. A **0%** rate applies to some exceptional goods and services, such as some daily and weekly publications, as well as recycled goods."
msgid "In Belgium, some taxes are not fully deductible, such as taxes on the maintenance of cars. This means a part of these taxes is considered as an expense."
msgid "In Odoo, you can configure non-deductible taxes by creating tax rules for these taxes and linking them to the corresponding accounts. This way, the system automatically calculates the taxes and allocates them to the appropriate accounts."
msgid ":guilabel:`Add a line`, then select :guilabel:`on tax` in the :guilabel:`Based on` column and enter the **non-deductible** percentage in the :guilabel:`%` column;"
msgid "Once you have created a non-deductible tax, you can apply it to your transactions by selecting the appropriate tax during the encoding of bills and credit notes. The system automatically calculates the tax amount and allocates it to the corresponding accounts based on the tax rules configured."
msgid "You can access Belgian-specific versions of reports by clicking on the **book** icon when on a report and selecting its Belgian version: **(BE)**."
msgid "The **disallowed expenses report** is available by going to :menuselection:`Accounting --> Reporting --> Management: Disallowed Expenses`. It allows financial results in real-time, and periodic changes. This report is generated based on the **disallowed expenses categories** that you can reach by going to :menuselection:`Accounting --> Configuration --> Management: Disallowed Expenses Categories`. Some categories already exist by default but do not have any rates. Click on :guilabel:`Set Rates` to update a specific category."
msgid "You can add multiple rates for various dates. In that case, the rate used to calculate the expense depends on the date at which it is calculated, and the rate set for that date."
msgid "If you have the **Fleet** app installed, tick the :guilabel:`Car Category` box when applicable. This makes the vehicle mandatory while booking a vendor bill."
msgid "To link a disallowed expenses category with a specific account, go to :menuselection:`Accounting --> Configuration --> Acounting: Chart of Accounts`. Find the account you want, and click on :guilabel:`Setup`. Add the :guilabel:`Disallowed Expense category` in the :guilabel:`Disallowed Expenses` field. From now, when an expense is created with this account, the disallowed expense is calculated based on the rate mentioned in the :guilabel:`Disallowed Expense category`."
msgid "In Belgium, 31% of **restaurant** expenses are non-deductible. Create a new **disallowed expenses category** and set both :guilabel:`Related Account(s)` and :guilabel:`Current Rate`."
msgid "In Belgium, the deductible percentage varies from car to car and, therefore, should be indicated for each vehicle. To do so, open :menuselection:`Fleet` and select a vehicle. In the :guilabel:`Tax info` tab, go to the :guilabel:`Disallowed Expenses Rate` section and click on :guilabel:`Add a line`. Add a :guilabel:`Start Date` and a :guilabel:`%`. The amounts go in the same account for all car expenses."
msgid "When you create a bill for car expenses, you can link each expense to a specific car by filling the :guilabel:`Vehicle` column, so the right percentage is applied."
msgid "The :guilabel:`vehicle split` option available in the disallowed expenses report allows you to see the rate and disallowed amount for each car."
msgid "Annually, a **281.50 fee form** must be reported to the fiscal authorities. To do so, the tag `281.50` must be added on the **contact form** of the entities concerned by the **281.50** fee. To add the tag, open :menuselection:`Contacts`, select the person or company you want to create a **281.50 fee form** for, and add the `281.50` tag in the :guilabel:`Tags` field."
msgid "Then, depending on the nature of the expense, add the corresponding `281.50` tag on the impact accounts. To do so, go to :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts`, and click on :guilabel:`Setup` to add the corresponding `281.50` tag on the impacted accounts, i.e., :guilabel:`281.50 - Commissions`, depending on the nature of the expense."
msgid "You can create a **325 form** by going to :menuselection:`Accounting --> Reporting --> Belgium: Create 325 form`. A new page pops up: select the right options and click :guilabel:`Generate 325 form`. To open an already generated **325 form**, go to :menuselection:`Accounting --> Reporting --> Belgium: Open 325 forms`."
msgid "**CODA** is an electronic XML format used to import Belgian bank statements. You can download CODA files from your bank and import them directly into Odoo by clicking :guilabel:`Import Statement` from your :guilabel:`Bank` journal on your dashboard."
msgid "The :guilabel:`Belgium - Import Bank CODA Statements` module is installed by default when the :guilabel:`Belgium - Accounting` and the :guilabel:`Belgium - Accounting Reports` modules are installed."
msgid "**SODA** is an electronic XML format used to import accounting entries related to salaries. SODA files can be imported into the journal you use to record salaries by going to your Accounting **dashboard** and clicking :guilabel:`Upload` in the related journal card form."
msgid "Odoo supports the **E-FFF** and **Peppol BIS Billing 3.0 (UBL)** electronic invoicing formats. To enable them, go to :menuselection:`Accounting --> Configuration --> Journals --> Customer Invoices --> Advanced Settings --> Electronic Invoicing`, and tick :guilabel:`E-FFF (BE)` and :guilabel:`Peppol BIS Billing 3.0`."
msgid "In Belgium, if an early payment discount is offered on an invoice, the tax is calculated based on the discounted total amount, whether the customer benefits from the discount or not."
msgid "In Belgium, the owner of a cooking business such as a restaurant or food truck is required by law to use a government-certified **Cash Register System** for their receipts. This applies if their yearly earnings (excluding VAT, drinks, and take-away food) exceed 25,000 euros."
msgid "This government-certified system entails the use of a :ref:`certified POS system <belgium/certified-pos>`, along with a device called a :ref:`Fiscal Data Module <belgium/fdm>` (or **black box**) and a :ref:`VAT Signing Card <belgium/vat>`."
msgid "Do not forget to register as *foodservice industry manager* on the `Federal Public Service Finance registration form <https://www.systemedecaisseenregistreuse.be/fr/enregistrement>`_."
msgid "The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online**, **Odoo.sh**, and **On-Premise**. Please refer to the following table to ensure that your POS system is certified."
msgid "A `certified POS system <https://www.systemedecaisseenregistreuse.be/systemes-certifies>`_ must adhere to rigorous government regulations, which means it operates differently from a non-certified POS."
msgid "The :doc:`cash rounding <../../sales/point_of_sale/pricing/cash_rounding>` feature must be activated and set to a :guilabel:`Rounding Precision` of `0,05` and a :guilabel:`Rounding Method` set as :guilabel:`Half-Up`."
msgid "Taxes must be set as included in the price. To set it up, go to :menuselection:`Point of Sale --> Configuration --> Settings`, and from the :guilabel:`Accounting` section, open the :guilabel:`Default Sales Tax` form by clicking the arrow next to the default sales tax field. There, click :guilabel:`Advanced Options` and enable :guilabel:`Included in Price`."
msgid "At the start of a POS session, users must click :guilabel:`Work in` to clock in. Doing so allows the registration of POS orders. If users are not clocked in, they cannot make POS orders. Likewise, they must click :guilabel:`Work Out` to clock out at the end of the session."
msgid "An FDM, or **black box**, is a government-certified device that works together with the Point of Sale application and saves your POS orders information. Concretely, a **hash** (:dfn:`unique code`) is generated for each POS order and added to its receipt. This allows the government to verify that all revenue is declared."
msgid "Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC04 <https://www.systemedecaisseenregistreuse.be/fr/systemes-certifies#FDM%20certifiés>`_ is supported by Odoo. `Contact the manufacturer (GCV BMC) <https://www.boîtenoire.be/contact>`_ to order one."
msgid "Once the module is activated, add your VAT number to your company information. To set it up, go to :menuselection:`Settings --> Companies --> Update Info`, and fill in the :guilabel:`VAT` field. Then, enter a national registration number for every staff member who operates the POS system. To do so, go to the :guilabel:`Employees` app and open an employee form. There, go to :menuselection:`HR settings tab --> Attendance/Point of Sale`, and fill in the :guilabel:`INSZ or BIS number` field."
msgid "To input your information, click on your avatar, go to :menuselection:`My Profile --> Preference tab`, and enter your INSZ or BIS number in the designated field."
msgid "You must configure the :abbr:`FDM (Fiscal Data Module)` directly in the production database. Utilizing it in a testing environment may result in incorrect data being stored within the FDM."
msgid "In order to use an :abbr:`FDM (Fiscal Data Module)`, you need a registered IoT Box. To register your IoT box, you must contact us through our `support contact form <https://www.odoo.com/help>`_ and provide the following information:"
msgid "Once your IoT box is certified, :doc:`connect <../../general/iot/config/connect>` it to your database. To verify that the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the :guilabel:`IOT Device` section, which should display the FDM."
msgid "Then, add the IoT to your POS. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select your POS, scroll down to the :guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field."
msgid "When you open a POS session and make your initial transaction, you are prompted to enter the PIN provided with your :abbr:`VSC (VAT signing card)`. The card is delivered by the :abbr:`FPS (Service Public Federal Finances)` upon `registration <https://www.systemedecaisseenregistreuse.be/fr/enregistrement>`_."
msgid "With the Brazilian localization you can automatically compute sales taxes for goods using AvaTax (Avalara) through API calls, also configure taxes for services."
msgid "For the goods tax computation part, you need to configure the :ref:`contacts <brazil/contacts>`, :ref:`company <brazil/company>`, :ref:`products <brazil/products>`, and :ref:`create an account in Avatax <brazil/avatax-account>` from the Odoo general settings."
msgid "Default :ref:`fiscal localization package <fiscal_localizations/packages>` - adds accounting characteristics for the Brazilian localization, which represent the minimum configuration required for a company to operate in Brazil. The module's installation automatically loads: the chart of accounts, taxes, and required fields to properly configure the contact."
msgid "Adds a simple tax report that helps check the tax amount per tax group in a given period of time. Also adds the P&L and BS adapted for the Brazilian market."
msgid "Add Brazilian tax calculation via Avatax and all necessary fields needed to configure Odoo in order to properly use Avatax and send the needed fiscal information to retrieve the correct taxes."
msgid "If you are a simplified regime, you need to configure the ICMS rate under :menuselection:`Accounting --> Configuration --> Settings --> Taxes --> Avatax Brazil`."
msgid "Avalara AvaTax is a tax calculation provider that can be integrated in Odoo to automatically compute taxes by taking into account the company, contact (customer), product, and transaction information to retrieve the correct tax to be used."
msgid "Odoo is a certified partner of Avalara Brazil, which means that Avalara experts reviewed workflows covered within the scope of the integration."
msgid "Using this integration requires :doc:`In-App-Purchases (IAPs) </applications/essentials/in_app_purchase>` to compute taxes. Every time you compute taxes, an API call is made, using credits from your |IAP| credits balance."
msgid "To activate AvaTax in Odoo, you need to create an account. To do so, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`, and, in the :guilabel:`AvaTax Brazil` section, add the email address you want to use to log in to the AvaTax portal, and click on :guilabel:`Create account`. This email is used as the administrator email address in AvaTax."
msgid "You will receive an email with a token and a link to create your password. Click on this link and copy-paste the token to allocate your desired password."
msgid "If you intend first to try the integration on a testing or sandbox database, using an alternate email address is recommended, as you won't be able to re-use the same email address on your production database."
msgid "You can start using AvaTax in Odoo without creating a password and accessing the Avalara Portal; for Odoo, the only requirement to start using the Avalara Tax Computation Engine is to create an account from the settings page."
msgid "The :doc:`chart of accounts </applications/finance/accounting/get_started/chart_of_accounts>` is installed by default as part of the data set included in the localization module. The accounts are mapped automatically in their corresponding taxes, and the default account payable and account receivable fields."
msgid "Taxes are automatically created when installing the Brazilian localization. Taxes are already configured, and some of them are used by Avalara when computing taxes on the sales order or invoice."
msgid "Taxes can be edited, or more taxes can be added. For example, some taxes used for services need to be manually added and configured, as the rate may differ depending on the city where you are offering the service."
msgid "When configuring a tax used for a service that is included in the final price (when the tax is not added or subtracted on top of the product price), set the :guilabel:`Tax Computation` to :guilabel:`Percentage of Price Tax Included`, and, on the :guilabel:`Advanced Options` tab, check the :guilabel:`Included in Price` option."
msgid "For more information on configuring taxes to fit your needs better, please go to the :doc:`taxes functional documentation </applications/finance/accounting/taxes>`."
msgid "Do not delete taxes, as they are used for the AvaTax tax computation. If deleted, Odoo creates them again when used in an |SO| or invoice and computing taxes with AvaTax, but the account used to register the tax needs to be re-configured in the tax's :guilabel:`Definition` tab, under the :guilabel:`Distribution for invoices` and :guilabel:`Distribution for refunds` sections."
msgid ":guilabel:`Source of Origin` (Indicates the origin of the product, which can be foreign or domestic, among other possible options depending on the specific use case)"
msgid "Odoo automatically creates three products to be used for transportation costs associated with sales. These are named `Freight`, `Insurance`, and `Other Costs`. They are already configured, if more need to be created, duplicate and use the same configuration (configuration needed: :guilabel:`Product Type` `Service`, :guilabel:`Transportation Cost Type` `Insurance`, `Freight`, or `Other Costs`)"
msgid "The :guilabel:`CPF`, :guilabel:`IE`, :guilabel:`IM`, and :guilabel:`SUFRAMA code` fields are are hidden until the :guilabel:`Country` is set to `Brazil`."
msgid ":guilabel:`ICMS Taxpayer Type`: taxpayer type determines if the contact is within the ICMS regime, if it is exempt, or if it is a non-taxpayer."
msgid "To compute taxes on sale orders and invoices, it is necessary to have a :guilabel:`Fiscal Position` with the :guilabel:`Detect Automatically` and the :guilabel:`Use AvaTax API` options enabled."
msgid "The :guilabel:`Fiscal Position` must be set to `Automatic Tax Mapping (Avalara Brazil)` for any of these actions to compute taxes automatically."
msgid "Watch the two webinar recordings below for a general presentation of the localization, and search the playlist for tutorials to discover practical workflows while using Odoo in Chile."
msgid "Adds the minimal accounting features required for a company to operate in Chile under the :abbr:`SII (Servicio de Impuestos Internos)` regulations and guidelines."
msgid "Includes all technical and functional requirements to generate and receive electronic invoices online based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations."
msgid "Includes all technical and functional requirements to generate and receive electronic invoices digitally based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations."
msgid "Includes technical and functional requirements to generate electronic invoices for exporting goods based on the :abbr:`SII (Servicio de Impuestos Internos)` and customs regulations."
msgid "Includes all technical and functional requirements to generate delivery guides via web service based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations."
msgid "All features are only available if the company already completed the `SII Sistema de Facturación de Mercado <https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_ certification process."
msgid "Navigate to :menuselection:`Settings --> Companies: Update Info` and ensure the following company information is up-to-date and correctly filled in:"
msgid "Next, navigate to :menuselection:`Accounting --> Configuration --> Settings --> Chilean Localization` and follow the instructions to configure the:"
msgid ":guilabel:`SII - Test`: for test databases using test :abbr:`CAFs (Folio Authorization Code)` obtained from the :abbr:`SII (Servicio de Impuestos Internos)`. In this mode, the direct connection flows can be tested, with the files being sent to the :abbr:`SII (Servicio de Impuestos Internos)`."
msgid ":guilabel:`SII - Demo Mode`: files are created and accepted automatically in demo mode but are **not** sent to the :abbr:`SII (Servicio de Impuestos Internos)`. For this reason, rejection errors or *Accepted with Objections* will not appear in this mode. Every internal validation can be tested in demo mode. Avoid selecting this option in a production database."
msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` :guilabel:`Email Box Electronic Invoicing` can be defined to receive your customers' claim and acceptance emails. Enabling this option from :menuselection:`Accounting --> Configuration --> Settings --> Chilean Localization` is necessary if you want to use *Email Box Electronic Invoicing* as the :abbr:`DTE (Documentos Tributarios Electrónicos)` incoming email server."
msgid "In order to receive your SII documents, it's necessary to set up your own email server. More information on how to do this can be found in this documentation: :doc:`../../general/email_communication/email_servers`"
msgid ":guilabel:`Local Server`: uses a local script to fetch emails and create new records. The script can be found in the :guilabel:`Configuration` section with this option selected."
msgid ":guilabel:`Gmail OAuth Authentication`: requires your Gmail API credentials to be configured in the general settings. A direct link to the configuration can be found in the :guilabel:`Login Information` section."
msgid ":guilabel:`DTE Server`: enable this option. By checking this option, this email account will be used to receive the electronic invoices from the suppliers, and communications from the :abbr:`SII (Servicio de Impuestos Internos)` regarding the electronic invoices issued. In this case, this email should match both emails declared on the :abbr:`SII (Servicio de Impuestos Internos)` site in the section: *ACTUALIZACION DE DATOS DEL CONTRIBUYENTE*, *Mail Contacto SII* and *Mail Contacto Empresas*."
msgid "Before going live, it is recommended to archive or remove all emails related to vendor bills that are not required to be processed in Odoo from your inbox."
msgid "A digital certificate in `.pfx` format is required to generate the electronic invoice signature. To add one, click :guilabel:`Configure Signature Certificates` under the :guilabel:`Signature Certificates` section. Then, click :guilabel:`New` to configure the certificate:"
msgid ":guilabel:`Subject Serial Number`: depending on the certificate format, the field might not be automatically populated. In that case, enter the certificate's legal representative :abbr:`RUT (Rol Único Tributario)`."
msgid ":guilabel:`Certificate Owner`: select one if you need to restrict the certificate for a specific user. Leave the field empty to share it with all billing users."
msgid "The official currency rate is provided by `Chilean mindicador.cl <https://mindicador.cl>`_. Navigate to :menuselection:`Accounting --> Configuration --> Settings --> Currencies: Automatic Currency Rates` to set an :guilabel:`Interval` for when the rate is automatically updated, or to select another :guilabel:`Service`."
msgid "Configuring partner contacts is also required to send :abbr:`SII (Servicio de Impuestos Internos)` electronic invoices. Open the :menuselection:`Contacts` app to do so and fill in the following fields on a new or existing contact form."
msgid "The :guilabel:`DTE Email` is the email used for sending electronic documents and must be set in the contact that will be part of an electronic document."
msgid "Document types are created automatically upon installation of the localization module, and can be managed by navigating to :menuselection:`Accounting --> Configuration --> Document Types`."
msgid "The *purchase* transactions can be managed with a single journal, but sometimes companies use more than one journal in order to handle some accounting transactions that are not related to vendor bills. This configuration can easily be set by using the following model."
msgid "To create a sales journal, navigate to :menuselection:`Accounting --> Configuration --> Journals`. Then, click the :guilabel:`New` button, and fill in the following required information:"
msgid ":guilabel:`Point of sale type`: if the sales journal will be used for electronic documents, the option :guilabel:`Online` must be selected. Otherwise, if the journal is used for invoices imported from a previous system or if you are using the :abbr:`SII (Servicio de Impuestos Internos)` portal *Facturación MiPyme*, you can use the option :guilabel:`Manual`."
msgid ":guilabel:`Use Documents`: check this field if the journal will use document types. This field is only applicable to purchase and sales journals that can be related to the different sets of document types available in Chile. By default, all the sales journals created will use documents."
msgid "Next, from the :guilabel:`Jounal Entries` tab, define the :guilabel:`Default Income Account` and :guilabel:`Dedicated Credit Note Squence` in the :guilabel:`Accounting Information` section. Configuring these fields is required for one of the debit notes :ref:`use cases <chile/use-cases>`."
msgid "A *folio authorization code* (CAF) is required for each document type that will be issued electronically. The :abbr:`CAF (Folio Authorization Code)` is a file the :abbr:`SII (Servicio de Impuestos Internos)` provides to the issuer with the folios/sequences authorized for the electronic invoice documents."
msgid "Your company can request multiple folios and obtain several :abbr:`CAFs (Folio Authorization Codes)` linked to different folio ranges. These :abbr:`CAFs (Folio Authorization Code)` are shared within all journals, so you only need one active :abbr:`CAF (Folio Authorization Code)` per document type, and it will be applied to all journals."
msgid "Please refer to the `SII documentation <https://palena.sii.cl/dte/mn_timbraje.html>`_ to check the details on how to acquire the :abbr:`CAF (Folio Authorization Code)` files."
msgid "The :abbr:`CAFs (Folio Authorization Code)` required by the :abbr:`SII (Servicio de Impuestos Internos)` are different from production to test (certification mode). Make sure you have the correct :abbr:`CAF (Folio Authorization Code)` set depending on your environment."
msgid "Once the :abbr:`CAF (Folio Authorization Code)` files have been acquired from the :abbr:`SII (Servicio de Impuestos Internos)` portal, they need to be uploaded in the database by navigating to :menuselection:`Accounting --> Configuration: Chilean SII --> CAFs`. Then, click the :guilabel:`New` begin the configuration. On the :abbr:`CAF (Folio Authorization Code)` form, upload your :abbr:`CAF (Folio Authorization Code)` file by clicking the :guilabel:`Upload your file` button and then click :guilabel:`Save`."
msgid "Once uploaded, the status changes to :guilabel:`In Use`. At this moment, when a transaction is used for this document type, the invoice number takes the first folio in the sequence."
msgid "The document types have to be active before uploading the :abbr:`CAF (Folio Authorization Code)` files. In case some folios have been used in the previous system, the next valid folio has to be set when the first transaction is created."
msgid "The chart of accounts is installed by default as part of the data set included in the localization module. The accounts are mapped automatically in:"
msgid "As part of the localization module, taxes are created automatically with their related financial account and configuration. These taxes can be managed from :menuselection:`Accounting --> Configuration --> Taxes`."
msgid "In the Chilean localization, the electronic invoice workflow includes customer invoice issuance and vendor bill reception. The following diagram explains how information is shared to the :abbr:`SII (Servicio de Impuestos Internos)`, customers, and vendors."
msgid "After the partners and journals are created and configured, the invoices are created in the standard way. For Chile, one of the differences is the document type that is automatically selected based on the taxpayer. The document type can be changed manually if needed on the invoice by navigating to :menuselection:`Accounting --> Customers --> Invoices`."
msgid ":guilabel:`Documents type 33` electronic invoice must have at least one item with tax, otherwise the :abbr:`SII (Servicio de Impuestos Internos)` rejects the document validation."
msgid "Once all invoice information is filled, either manually or automatically when generated from a sales order, validate the invoice. After the invoice is posted:"
msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` :abbr:`SII (Servicio de Impuestos Internos)` status is set as :guilabel:`Pending` to be sent."
msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` status is updated automatically by Odoo with a scheduled action that runs every day at night, if the response from the :abbr:`SII (Servicio de Impuestos Internos)` is needed immediately, you can do it manually as well by following the :abbr:`DTE (Documentos Tributarios Electrónicos)` status workflow:"
msgid "The first step is to send the :abbr:`DTE (Documentos Tributarios Electrónicos)` to the :abbr:`SII (Servicio de Impuestos Internos)`. This can be sent manually by clicking the :guilabel:`Enviar Ahora` button. This generates a :guilabel:`SII Tack number` for the invoice, which is used to check the details sent by the :abbr:`SII (Servicio de Impuestos Internos)` via email. Then, the :guilabel:`DTE status` is updated to :guilabel:`Ask for Status`."
msgid "Once the :abbr:`SII (Servicio de Impuestos Internos)` response is received, Odoo updates the :guilabel:`DTE status`. To do it manually, click on the button :guilabel:`Verify on SII`. The result can either be :guilabel:`Accepted`, :guilabel:`Accepted With Objection` or :guilabel:`Rejected`."
msgid "There are intermediate statuses in the :abbr:`SII (Serviciqo de Impuestos Internos)` before acceptance or rejection. It's recommended to **NOT** continuously click :guilabel:`Verify in SII` for smooth processing."
msgid ":guilabel:`Accepted`: indicates the invoice information is correct, our document is now fiscally valid and it's automatically sent to the customer."
msgid ":guilabel:`Accepted with objections`: indicates the invoice information is correct, but a minor issue was identified, nevertheless the document is now fiscally valid and it's automatically sent to the customer."
msgid ":guilabel:`Rejected`: indicates the invoice information is incorrect and must be corrected. Details are sent to emails you registered in the :abbr:`SII (Servicio de Impuestos Internos)`. If it is properly configured in Odoo, the details are also retrieved in the chatter once the email server is processed."
msgid "When the invoice is created, as a result of another fiscal document, the information related to the originator document must be registered in the :guilabel:`Cross-Reference` tab. This tab is commonly used for credit or debit notes, however, in some cases it can be used for customer invoices, as well. In the case of the credit and debit notes, they are set automatically by Odoo."
msgid "Once the invoice is accepted and validated by the :abbr:`SII (Servicio de Impuestos Internos)` and the PDF is printed, it includes the fiscal elements that indicate that the document is fiscally valid."
msgid "If you are hosted in Odoo SH or On-Premise, you should manually install the `pdf417gen <https://pypi.org/project/pdf417gen/>`_ library. Use the following command to install it: :command:`pip install pdf417gen`."
msgid "Once the invoice has been accepted by the :abbr:`SII (Servicio de Impuestos Internos)`, **it can not be cancelled in Odoo**. In case you get a claim for your customer, the correct way to proceed is with a credit note to either cancel the invoice or correct it. Please refer to the :ref:`chile/credit-notes` section for more details."
msgid "There are multiple reasons behind a rejection from the :abbr:`SII (Servicio de Impuestos Internos)`, but these are some of the common errors you might have and how to solve them:"
msgid "**Hint:** the :abbr:`RUT (Rol Único Tributario)` entered is not allowed to invoice electronically, make sure the company :abbr:`RUT (Rol Único Tributario)` is correct and is valid in the :abbr:`SII (Servicio de Impuestos Internos)` to invoice electronically."
msgid "**Error:** `Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element is not expected. Expected is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).`"
msgid "**Hint:** this error indicates that most likely, your company has not passed the `Certification process <https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_ in the :abbr:`SII (Servicio de Impuestos Internos)` - Sistema de Facturación de Mercado. If this is the case, please contact your Account Manager or Customer Support as this certification is not part of the Odoo services, but we can give you some alternatives. If you already passed the certification process, this error appears when a user different from the owner of the certificate is trying to send :abbr:`DTE (Documentos Tributarios Electrónicos)` files to the :abbr:`SII (Servicio de Impuestos Internos)`."
msgid "The :abbr:`SII's (Servicio de Impuestos Internos)` :abbr:`RUT (Rol Único Tributario)` number (this should be correct by default) is incorrect or missing."
msgid "When a cancellation or correction is needed over a validated invoice, a credit note must be generated. It is important to consider that a :abbr:`CAF (Folio Authorization Code)` file is required for the credit note, which is identified as :guilabel:`Document Type` :guilabel:`61` in the :abbr:`SII (Servicio de Impuestos Internos)`. Please refer to the :ref:`CAF section <chile/caf-documentation>` for more information on the process to load the :abbr:`CAF (Folio Authorization Code)` on each document type."
msgid "In case you need to cancel or invalidate an invoice, navigate to :menuselection:`Accounting --> Customers --> Invoices` and select the desired invoice. Then, use the button :guilabel:`Add Credit Note` and select :guilabel:`Full Refund`, in this case the :abbr:`SII (Servicio de Impuestos Internos)` reference code is automatically set to :guilabel:`Anula Documento de referencia`."
msgid "If a correction in the invoice information is required, for example the street name on the original invoice is wrong, then use the button :guilabel:`Add Credit Note`, select :guilabel:`Partial Refund` and select the option :guilabel:`Only Text Correction`. In this case the :guilabel:`SII Reference Code` field is automatically set to :guilabel:`Corrects Referenced Document Text`."
msgid "When a correction on the amounts is required, use the button :guilabel:`Add Credit note` and select :guilabel:`Partial Refund`. In this case the :guilabel:`SII Reference Code` is automatically set to :guilabel:`Corrige el monto del Documento de Referencia`."
msgid "In Chilean localization, debit notes, in addition to credit notes, can be created using the :guilabel:`Add Debit Note` button, with two main use cases."
msgid "The primary use case for debit notes is to increase the value of an existing invoice. To do so, select option :guilabel:`3. Corrige el monto del Documento de Referencia` for the :guilabel:`Reference Code SII` field."
msgid "In Chile, debits notes are used to cancel a valid credit note. To do this, click the :guilabel:`Add Debit Note` button and select the :guilabel:`1: Anula Documentos de referencia` option for the :guilabel:`Reference Code SII` field."
msgid "As part of the Chilean localization, you can configure your incoming email server to match the one you have registered in the :abbr:`SII (Servicio de Impuestos Internos)` in order to:"
msgid "If all the commercial information is correct on your vendor bill, then you can accept the document using the :guilabel:`Aceptar Documento` button. Once this is done, the :guilabel:`DTE Acceptation Status` changes to :guilabel:`Accepted` and an email of acceptance is sent to the vendor."
msgid "In case there is a commercial issue or the information is not correct on your vendor bill, you can claim the document before validating it, using the :guilabel:`Claim` button. Once this is done, the :guilabel:`DTE Acceptation Status` changes to :guilabel:`Claim` and a rejection email is sent to the vendor."
msgid "If you claim a vendor bill, the status changes from :guilabel:`Draft` to :guilabel:`Cancel` automatically. Considering this as best practice, all the claimed documents should be canceled as they won't be valid for your accounting records."
msgid "Once all configurations have been made for :ref:`electronic invoices <chile/electronic-invoice>` (e.g., uploading a valid company certificate, setting up master data, etc.), the electronic purchase invoices need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation <chile/caf-documentation>` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic purchase invoices."
msgid "Electronic purchase invoices are useful when vendors are not obligated to expedite an electronic vendor bill for your purchase. Still, your obligations require a document to be sent to the :abbr:`SII (Servicio de Impuestos Internos)` as proof of purchase."
msgid "To generate an electronic purchase invoice from a vendor bill, the bill must be created in a purchase journal with the *Use Documents* feature enabled. It is possible to modify an existing purchase journal or create a new one in the following process."
msgid "To modify the existing purchase journal, or create a new purchase journal, navigate to :menuselection:`Accounting --> Configuration --> Journals`. Then, click the :guilabel:`New` button, and fill in the following required information:"
msgid "To generate this type of document, it is necessary to create a vendor bill in Odoo. To do so, navigate to :menuselection:`Accounting --> Vendors --> Bills`, and click the :guilabel:`New` button."
msgid "When all of the electronic purchase invoice information is filled, select the option :guilabel:`(46) Electronic Purchase Invoice` in the :guilabel:`Document Type` field:"
msgid "Odoo automatically updates the *DTE Status* every night using a scheduled action. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, click the :guilabel:`Send now to SII` button."
msgid "To install the :guilabel:`Delivery Guide` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery Guide`."
msgid ":guilabel:`Chile - E-Invoicing Delivery Guide` has a dependency with :guilabel:`Chile - Facturación Electrónica`. Odoo will install the dependency automatically when the :guilabel:`Delivery Guide` module is installed."
msgid "The *Delivery Guide* module includes the ability to send the :abbr:`DTE (Documentos Tributarios Electrónicos)` to :abbr:`SII (Servicio de Impuestos Internos)` and the stamp in PDF reports for deliveries."
msgid "Once all configurations have been made for :ref:`electronic invoices <chile/electronic-invoice>` (e.g., uploading a valid company certificate, setting up master data, etc.), delivery guides need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation <chile/caf-documentation>` to check the details on how to acquire the :abbr:`CAF (Folio Authorization Code)` for electronic Delivery Guides."
msgid "Electronic delivery guides are used to move stock from one place to another and they can represent sales, sampling, consignment, internal transfers, and basically any product move."
msgid "When a sales order is created and confirmed, a delivery order is generated. After validating the delivery order, the option to create a delivery guide is activated."
msgid "`No se encontró una secuencia para la guía de despacho. Por favor, establezca el primer número dentro del campo número para la guía de despacho`"
msgid "This warning message means the user needs to indicate the next sequence number Odoo has to take to generate the delivery guide (e.g. next available :abbr:`CAF (Folio Authorization Code)` number), and only happens the first time a delivery guide is created in Odoo. After the first document has been correctly generated, Odoo takes the next available number in the :abbr:`CAF (Folio Authorization Code)` file to generate the following delivery guide."
msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is automatically created and added to the :guilabel:`chatter`."
msgid "The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled action that runs every night. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now to SII` button."
msgid "Delivery guide will have fiscal elements that indicate that the document is fiscally valid when printed (if hosted in *Odoo SH* or on *On-premise* remember to manually add the :guilabel:`pdf417gen` library mentioned in the :ref:`Invoice PDF report section <chile/electronic-invoice-pdf-report>`)."
msgid "To install the :guilabel:`Electronic Receipt` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`."
msgid ":guilabel:`Chile - Electronic Receipt` has a dependency with :guilabel:`Chile - Facturación Electrónica`. Odoo will install the dependency automatically when the :guilabel:`E-invoicing Delivery Guide` module is installed."
msgid "Once all configurations have been made for :ref:`electronic invoices <chile/electronic-invoice>` (e.g., uploading a valid company certificate, setting up master data, etc.), electronic receipts need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation <chile/caf-documentation>` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts."
msgid "Electronic receipts are useful when clients do not need an electronic invoice. By default, there is a partner in the database called :guilabel:`Anonymous Final Consumer` with a generic :abbr:`RUT (Rol Único Tributario)` `66666666-6` and taxpayer type of :guilabel:`Final Consumer`. This partner can be used for electronic receipts or a new record may be created for the same purpose."
msgid "Although electronic receipts should be used for final consumers with a generic :abbr:`RUT (Rol Único Tributario)`, it can also be used for specific partners. After the partners and journals are created and configured, the electronic receipts are created in the standard way as electronic invoice, but the type of document :guilabel:`(39) Electronic Receipt` should be selected in the invoice form:"
msgid "When all of the electronic receipt information is filled, manually (or automatically) proceed to validate the receipt from the sales order. By default, :guilabel:`Electronic Invoice` is selected as the :guilabel:`Document Type`, however in order to validate the receipt correctly, make sure to edit the :guilabel:`Document Type` and change to :guilabel:`Electronic Receipt`."
msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is created automatically and added to the :guilabel:`chatter`."
msgid "The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled action that runs every day at night. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now to SII` button."
msgid "Please refer to the :ref:`DTE Workflow <chile/electronic-invoice-validation>` for electronic invoices as the workflow for electronic receipt follows the same process."
msgid "To install the :guilabel:`Electronic Exports of Goods` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Electronic Exports of Goods for Chile`."
msgid "Once all configurations have been made for :ref:`electronic invoices <chile/electronic-invoice>` (e.g., uploading a valid company certificate, setting up master data, etc.), electronic exports of goods need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation <chile/caf-documentation>` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts."
msgid "Electronic invoices for the export of goods are tax documents that are used not only for the :abbr:`SII (Servicio de Impuestos Internos)` but are also used with customs and contain the information required by it."
msgid "When creating an electronic exports of goods invoice, these new fields in the :guilabel:`Other Info` tab are required to comply with Chilean regulations."
msgid "Once the invoice is accepted and validated by the :abbr:`SII (Servicio de Impuestos Internos)` and the PDF is printed, it includes the fiscal elements that indicate that the document is fiscally valid and a new section needed for customs."
msgid "This report presents the accounts in detail (with their respective balances), classifying them according to their origin and determining the level of profit or loss that the business had within the evaluated period of time."
msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Balance Sheet` and selecting in the :guilabel:`Report` field the option :guilabel:`Chilean Fiscal Balance (8 Columns) (CL)`."
msgid "The form *F29* is a new system that the :abbr:`SII (Servicio de Impuestos Internos)` enabled to taxpayers, and that replaces the *Purchase and Sales Books*. This report is integrated by Purchase Register (CR) and the Sales Register (RV). Its purpose is to support the transactions related to VAT, improving its control and declaration."
msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Tax Reports` and selecting the :guilabel:`Report` option :guilabel:`Propuesta F29 (CL)`."
msgid "It is possible to set the :abbr:`PPM (Provisional Monthly Payments rate)` and the :guilabel:`Proportional Factor for the fiscal year` from the :menuselection:`Accounting --> Configuration --> Settings`."
msgid "Odoo's Colombian localization package provides accounting, fiscal, and legal features for databases in Colombia – such as chart of accounts, taxes, and electronic invoicing."
msgid "In addition, a series of videos on the subject is also available. These videos cover how to start from scratch, set up configurations, complete common workflows, and provide in-depth looks at some specific use cases as well."
msgid "Default :ref:`fiscal localization package <fiscal_localizations/packages>`. This module adds the base accounting features for the Colombian localization: chart of accounts, taxes, withholdings, and identification document type."
msgid "This module includes the features required for integration with Carvajal, and generates the electronic invoices and support documents related to the vendor bills, based on |DIAN| regulations."
msgid "Alternatively, activate :ref:`developer mode <developer-mode>` and navigate to :menuselection:`General Setting --> Company --> Update Info --> Contact`. Then, edit the contact form and configure the following information:"
msgid ":guilabel:`Identification Number`: Select the :guilabel:`Identification Type` (`NIT`, `Cédula de Ciudadanía`, `Registro Civil`, etc.). When the :guilabel:`Identification Type` is `NIT`, the :guilabel:`Identification Number` **must** have the *verification digit* at the end of the ID prefixed by a hyphen (`-`)."
msgid ":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company (`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen de tributación simple, `R-99-PN` No Aplica)."
msgid "Once the modules are installed, the user credentials **must** be configured, in order to connect with Carvajal Web Service. To do so, navigate to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the required configuration information provided by Carvajal:"
msgid ":guilabel:`Colombia Template Code`: Select one of the two available templates (`CGEN03` or `CGNE04`) to be used in the PDF format of the electronic invoice."
msgid "Once Odoo and Carvajal are fully configured and ready for production, deactivate the :guilabel:`Test mode` checkbox to use the production database."
msgid "Navigate to :menuselection:`Accounting --> Configuration --> Settings`, and scroll to the :guilabel:`Colombian Electronic Invoicing` section, in order to find the :guilabel:`Report Configuration` fields. Here the header information for each report type can be configured."
msgid "Partner contacts can be created in the *Contacts* app. To do so, navigate to :menuselection:`Contacts`, and click the :guilabel:`Create` button."
msgid "Complete the full :guilabel:`Address`, including the :guilabel:`City`, :guilabel:`State`, and :guilabel:`ZIP` code. Then, complete the identification and fiscal information."
msgid "Identification types, defined by the |DIAN|, are available on the partner form, as part of the Colombian localization. Colombian partners **must** have their :guilabel:`Identification Number` (VAT) and :guilabel:`Document Type` set."
msgid "When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification Number` needs to be configured in Odoo, including the *verification digit at the end of the ID, prefixed by a hyphen (`-`)*."
msgid "The partner's responsibility codes (section 53 in the :abbr:`RUT (Registro único tributario)` document) are included as part of the electronic invoicing module, as it is required by the |DIAN|."
msgid ":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company (`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen de tributación simple, or `R-99-PN` No Aplica)."
msgid "When adding general information on the product form, it is required that either the :guilabel:`UNSPSC Category` (:guilabel:`Accounting` tab), or :guilabel:`Internal Reference` (:guilabel:`General Information` tab) field is configured. Be sure to :guilabel:`Save` the product once configured."
msgid "If sales transactions include products with taxes, the :guilabel:`Value Type` field in the :guilabel:`Advanced Options` tab needs to be configured per tax. Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`, :guilabel:`Fuente`) are also included. This configuration is used to display taxes correctly in the invoice PDF."
msgid "Once the |DIAN| has assigned the official sequence and prefix for the electronic invoice resolution, the sales journals related to the invoice documents **must** be updated in Odoo. To do so, navigate to :menuselection:`Accounting --> Configuration --> Journals`, and select an existing sales journal, or create a new one with the :guilabel:`Create` button."
msgid "On the sales journal form, input the :guilabel:`Journal Name`, :guilabel:`Type`, and set a unique :guilabel:`Short Code` in the :guilabel:`Journals Entries` tab. Then, configure the following data in the :guilabel:`Advanced Settings` tab:"
msgid "Once the |DIAN| has assigned the official sequence and prefix for the *support document* related to vendor bills, the purchase journals related to their supporting documents need to be updated in Odoo. The process is similar to the configuration of the :ref:`sales journals <co-journals>`."
msgid "The :doc:`chart of accounts </applications/finance/accounting/get_started/chart_of_accounts>` is installed by default as part of the localization module, the accounts are mapped automatically in taxes, default account payable, and default account receivable. The chart of accounts for Colombia is based on the PUC (Plan Unico de Cuentas)."
msgid "Electronic invoices are generated and sent to both the |DIAN| and customer through Carvajal's web service integration. These documents can be created from your sales order or manually generated. To create a new invoice, go to :menuselection:`Accounting --> Customers --> Invoices`, and select :guilabel:`Create`. On the invoice form configure the following fields:"
msgid "After the invoice confirmation, an XML file is created and sent automatically to Carvajal. The invoice is then processed asynchronously by the E-invoicing service UBL 2.1 (Colombia). The file is also displayed in the chatter."
msgid "The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`EDI Documents` tab, with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is displayed with the initial value :guilabel:`To Send`. To process the invoice manually, click on the :guilabel:`Process Now` button."
msgid "After validating the electronic invoice, 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. If everything is correct the :guilabel:`Electronic Invoicing` field value changes to :guilabel:`Sent`."
msgid "A :file:`.zip` containing the legal electronic invoice (in XML format) and the invoice in (PDF format) is downloaded and displayed in the invoice chatter:"
msgid "The process for credit notes is the same as for invoices. To create a credit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click :guilabel:`Add Credit Note`, and complete the following information:"
msgid ":guilabel:`Full refund and new draft invoice`: Use this option if the credit note is auto-validated and reconciled with the invoice. The original invoice is duplicated as a new draft."
msgid ":guilabel:`Use Specific Journal`: Select the journal for your credit note or leave it empty if you want to use the same journal as the original invoice."
msgid "The process for debit notes is similar to credit notes. To create a debit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click the :guilabel:`Add Debit Note` button, and enter the following information:"
msgid ":guilabel:`Use Specific Journal`: Select the printer point for your debit note, or leave it empty if you want to use the same journal as the original invoice."
msgid "With master data, credentials, and the purchase journal configured for support documents related to vendor bills, you can start using *support documents*."
msgid "Support documents for vendor bills can be created from your purchase order or manually. Go to :menuselection:`Accounting --> Vendors --> Bills` and fill in the following data:"
msgid "During the XML validation, the most common errors are related to missing master data (*Contact Tax ID*, *Address*, *Products*, *Taxes*). In such cases, error messages are shown in the chatter after updating the electronic invoice status."
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 :guilabel:`Retry` button."
msgid "This report is a certification to vendors for withholdings made for the Colombian Industry and Commerce (ICA) tax. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en ICA`."
msgid "This report issues a certificate on the amount withheld from vendors for VAT withholding. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en IVA`."
msgid "This certificate is issued to partners for the withholding tax that they have made. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en Fuente`."
msgid "With the Ecuadorian localization you can generate electronic documents with its XML, Fiscal folio, with electronic signature and direct connection to tax authority SRI."
msgid "The default :doc:`fiscal localization package <../fiscal_localizations>`, adds accounting characteristics for the Ecuadorian localization, which represent the minimum configuration required for a company to operate in Ecuador according to the guidelines set by the :abbr:`SRI (servicio de rentas internas)`. The module's installation automatically loads: Chart of Accounts, taxes, documents types, tax support types. Additionally, the generation of forms 103 and 104 are automatic."
msgid "Includes all the technical and functional requirements to generate and validate :doc:`Electronics Documents <../accounting/customer_invoices/electronic_invoicing>`, based on the Technical documentation published by the SRI. The authorized documents are: Invoices, Credit Notes, Debit Notes, Withholdings and Purchase liquidations."
msgid "When you install a database from scratch selecting `Ecuador` as the country, Odoo automatically installs the base module :guilabel:`Ecuadorian - Accounting`."
msgid "To configure your company information, go to the :guilabel:`Contacts` app and search the name given to your company or activate :ref:`developer mode <developer-mode>` and go to :menuselection:`Company --> Contact` and then edit the contact to configure the following information:"
msgid "To upload your information for electronic documents go to :menuselection:`Accounting --> Configuration --> Settings` and search for :command:`Ecuadorian Localization`."
msgid ":guilabel:`Use production servers`: check the checkbox if your company is going to do electronic documents in the production environment. If you want to use the testing environment for electronic documents then keep the checkbox unchecked."
msgid ":guilabel:`Special tax contributor number`: if your company is qualified as a special taxpayer, fill out this field with it's corresponding tax contributor number."
msgid "When configuring the withholdings in the configuration menu, these suggested withholdings are only for domestic suppliers when no withholdings are setup on their *Taxpayer Type*. Moreover, the Credit Card withholding set up is always used when a Credit or Debit Card SRI Payment Metho is used."
msgid "This configuration only applies if you are qualified as a *Withholding Agent* by the SRI, otherwise skip this step. To configure your VAT withholding, go to :menuselection:`Accounting --> Accounting --> Configuration --> Ecuadorian SRI: Taxpayer Type SRI`."
msgid "You must configure the withholding percentage that applies for each type of taxpayer, specify the :guilabel:`Goods VAT Withholding` and the :guilabel:`Services VAT Withholding`."
msgid "Printer points need to be configured for each type of electronic document that you need. For example: Customer Invoice, Credit Notes, and Debit Notes"
msgid "Customer Invoice, Credit Notes and Debit Notes need to use the same journal as the :guilabel:`Emission Point`, and the :guilabel:`Entity Point` should be unique per journal."
msgid "A Withholding Journal must be defined, go to go to :menuselection:`Accounting --> Configuration --> Accounting: Journals` where you need to configure the following information:"
msgid "In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic Invoicing` checkbox to enable the sending of electronic invoicing for the withholding."
msgid "When using Purchase Liquidations, a specific journal must be created, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals` and configure the following information:"
msgid "The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` is installed by default as part of the set of data included in the localization module, the accounts are mapped automatically in Taxes, Default Account Payable, Default Account Receivable."
msgid "The chart of accounts for Ecuador is based on the most updated version of Superintendency of Companies, which is grouped in several categories and is compatible with NIIF accounting."
msgid "Check the :guilabel:`Company` option on top if it is a contact with RUC, or check :guilabel:`Individual` if it is a contact with cedula or passport."
msgid "The :guilabel:`SRI Taxpayer Type` has inside the configuration of which VAT and Profit withholding will apply when you use this contact on Vendor Bill, and then create a withholding from there."
msgid ":guilabel:`Tax Grids`: configure the codes of 104 form if it is a IVA tax and configure the codes of 103 form if it is a income tax withholding code."
msgid "Once the Ecuador module is installed, the most common taxes are automatically configured. If you need to create an additional one, you can do so, for which you must base yourself on the configuration of the existing taxes."
msgid "Some accounting transactions like *Customer Invoices* and *Vendor Bills* are classified by document types. These are defined by the government fiscal authorities, in this case by the SRI."
msgid "Each document type can have a unique sequence per journal where it is assigned. As part of the localization, the document type includes the country on which the document is applicable; also the data is created automatically when the localization module is installed."
msgid ":guilabel:`Customer invoices` are electronic documents that, when validated, are sent to SRI. These documents can be created from your sales order or manually. They must contain the following data:"
msgid "The :doc:`Customer credit note <../accounting/customer_invoices/credit_notes>` is an electronic document that, when validated, is sent to SRI. It is necessary to have a validated (posted) invoice in order to register a credit note. On the invoice there is a button named :guilabel:`Credit note`, click on this button to be directed to the :guilabel:`Create credit note` form, then complete the following information:"
msgid ":guilabel:`Full Refund`: use this option if the credit note is for the total invoice and you need the credit note to be auto-validated and reconciled with the invoice."
msgid ":guilabel:`Full refund and new draft invoice`: use this option if the credit note is for the total invoice and you need the credit note to be auto-validated and reconciled with the invoice, and auto-create a new draft invoice."
msgid ":guilabel:`Use Specific Journal`: select the printer point for your credit note, or leave it empty if you want to use the same journal as the original invoice."
msgid "When the :guilabel:`Partial Refund` option is used, you can change the amount of the credit note and then validate it. Before validating the credit note, review the following information:"
msgid "The :guilabel:`Customer debit note` is an electronic document that, when validated, is sent to SRI. It is necessary to have a validated (posted) invoice in order to register a debit note. On the invoice there is a button named :guilabel:`Debit Note`, click on this button to be directed to the :guilabel:`Create debit note` form, then complete the following information:"
msgid "The :guilabel:`Customer withholding` is a non-electronic document for your company, this document is issued by the client in order to apply a withholding to the sale."
msgid "It is necessary to have a validated (posted) invoice in order to register a customer withholding. On the invoice there is a button named :guilabel:`Add Withhold`, click on this button to be directed to the :guilabel:`Customer withholding` form, then complete the following information:"
msgid "The :guilabel:`Vendor bill` is a non-electronic document for your company, this document is issued by your vendor when your company generates a purchase."
msgid "When creating the purchase withholding, verify that the bases (base amounts) are correct. If you need to edit the amount of the tax in the :guilabel:`Vendor bill`, click the :guilabel:`Edit` button. Otherwise, from the :guilabel:`Journal Items` tab click the :guilabel:`Edit` button and set the adjustment to go where you want."
msgid "Companies issue this type of electronic document when they purchase, and the vendor does not issue an invoice due to one or more of the following cases:"
msgid "Purchase of goods or services from natural persons not registered with a RUC, who due to their cultural level or hardiness are not able to issue sales receipts or customer invoices."
msgid "These types of electronic documents can be created from the :guilabel:`Purchase Order` or manually from the :guilabel:`Vendor Bills` form view. It must contain the following data:"
msgid ":guilabel:`Document number`: type the document number (sequence), you will only have to do this once, then the sequence will be automatically assigned for the next documents."
msgid "It is necessary to have an invoice in a validated state in order to register a :guilabel:`Purchase withholding`. On the invoice, there is a button named :guilabel:`Add Withhold`, click on this button to be directed to the :guilabel:`Withholding` form, then complete the following information:"
msgid ":guilabel:`Withhold lines`: The taxes appear automatically according to the configuration of products and vendors, you should review if the taxes and tax support are correct, and, if it is not correct, you can edit and select the correct taxes and tax support."
msgid "You can't change the tax support for one that was not included in the configuration of the taxes used on the :guilabel:`Vendor Bill`. To do so, go to the tax applied on the :guilabel:`Vendor Bill` and change the :guilabel:`Tax Support` there."
msgid "The system suggests a VAT withholding of 30% with tax support 01, you can add your VAT withholding of 70% in a new line with the same tax support, the system will allow you as long as the total of the bases matches the total from the :guilabel:`Vendor Bill`."
msgid "In Ecuador, there are fiscal reports that the company presents to SRI. In Odoo, we have two of the main financial reports used by companies. These are the reports 103 and 104."
msgid "To get these reports go to the :guilabel:`Accounting` app and select :menuselection:`Reporting --> Statements Reports --> Tax Report` and then filter by `Tax Report 103` or `Tax Report 104`."
msgid "You can see the information needed to report, which includes base and tax amounts, which also includes the tax code within the parenthesis in order to report it to the SRI."
msgid "To issue electronic documents, ensure your company is configured as explained in the :ref:`electronic invoice <l10n_ec/configure-your-company>` section."
msgid "In the :abbr:`ATS (Anexo Transaccional Simplificado)`, every document generated in Odoo (invoices, vendor bills, sales and purchases withholdings, credit notes, and debit notes) will be included."
msgid "When generating a vendor bill, it is necessary to register the authorization number from the invoice that the vendor generated for the purchase. To do so, go to :menuselection:`Accounting --> Vendors --> Bills` and select the bill. Then, enter the number from the vendor's invoice in the :guilabel:`Authorization Number` field."
msgid "When generating a credit note or debit note manually or through importation, it is necessary to link this note to the sales invoice that is being modified by it."
msgid "Remember to add all required information to the documents before downloading the :abbr:`ATS (Anexo Transaccional Simplificado)` file. For example, add the *Authorization Number* and the *SRI Payment Method* on documents, when needed."
msgid "To generate the :abbr:`ATS (Anexo Transaccional Simplificado)` report, go to :menuselection:`Accounting --> Reports --> Tax Report` and choose a time period for the desired :abbr:`ATS (Anexo Transaccional Simplificado)` report, then click :guilabel:`ATS`."
msgid "When downloading the :abbr:`ATS (Anexo Transaccional Simplificado)` report, Odoo generates a warning pop-up alerting the user if a document(s) has missing or incorrect data. Nevertheless, the user can still download the XML file."
msgid "You must register your Odoo ERP system on your ETA portal to get your API credentials. You need these codes to :ref:`configure your Odoo Accounting app <egypt/e-invoicing-configuration>`."
msgid "Next, go to the :guilabel:`Representatives` section and then click on :guilabel:`Register ERP`. Fill out the :guilabel:`ERP Name` (e.g., ``Odoo``) and leave the other fields empty."
msgid "To connect your Odoo database to your ETA portal account, go to :menuselection:`Accounting --> Configuration --> Settings --> ETA E-Invoicing Settings`, and set the :guilabel:`ETA Client ID` and :guilabel:`ETA Secret` that you retrieved when you :ref:`registered Odoo on your ETA portal <egypt/e-invoicing-eta-portal>`. Set an invoicing threshold if needed."
msgid "**Credentials** for preproduction and production environments are different. Make sure to update them on Odoo when you move from one environment to another."
msgid "E-invoicing works with a set of codes provided by the ETA. You can use the `ETA documentation <https://sdk.preprod.invoicing.eta.gov.eg/codes/>`_ to code your business attributes."
msgid "Most of these codes are handled automatically by Odoo, provided that your :ref:`branches <egypt/e-invoicing-branches>`, :ref:`customers <egypt/e-invoicing-customers>`, and :ref:`products <egypt/e-invoicing-products>` are correctly configured."
msgid "Most of the taxes codes are already configured on Odoo in the :guilabel:`ETA Code (Egypt)` field. We advise you to make sure these codes match your company's taxes."
msgid "Name the journal according to your company's branch and set the :guilabel:`Type` as :guilabel:`Sales`. Next, open the :menuselection:`Advanced Settings` tab and fill out the :guilabel:`Egyptian ETA settings` section:"
msgid "The contact selected in the :guilabel:`Branch` field must be set as a :guilabel:`Company` (**not** as an :guilabel:`Individual`), and the :guilabel:`Address` and :guilabel:`Tax ID` fields must be filled out."
msgid ":guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled :doc:`Units of Measure <../../inventory_and_mrp/inventory/product_management/configure/uom>`."
msgid "Each person who needs to electronically sign invoices needs a specific USB key to authenticate and send invoices to the ETA portal through an ERP."
msgid "Once the installation is complete, the installer displays your **access token** for the Odoo Local Proxy. Copy the token and save it in a safe place for later use."
msgid "Input a :guilabel:`Company` name, the :guilabel:`ETA USB Pin` given to you by your USB key provider, and the :guilabel:`Access Token` provided at the end of the :ref:`local proxy installation <egypt/e-invoicing-local-proxy>`, then click on :guilabel:`Save`."
msgid "You must :doc:`install <../../general/apps_modules>` the **France - Adding Mandatory Invoice Mentions (Decree no. 2022-1299)** (`l10n_fr_invoice_addr`) module to comply with the `local legislation <https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000046383394>`_."
msgid "An FEC :dfn:`Fichier des Écritures Comptables` audit file contains all the accounting data and entries recorded in all the accounting journals for a financial year. The entries in the file must be arranged in chronological order."
msgid "Since January 1st, 2014, every French company is required to produce and transmit this file upon request by the tax authorities for audit purposes."
msgid "To make the onboarding of new users easier, Odoo Enterprise's French :ref:`fiscal localization package <fiscal_localizations/packages>` includes the **FEC Import** feature (module name: ``l10n_fr_fec_import``), which enables the import of existing FEC files from older software."
msgid "To enable this feature, go to :menuselection:`Accounting --> Configuration --> Settings --> Accounting Import`, enable **FEC Import**, and *Save*."
msgid "Should multiple files contain any \"Reports à Nouveaux\" (RAN) with the starting balance of the year, you might need to cancel those entries in the User Interface. Odoo makes those entries (RAN) useless."
msgid "The FEC CSV file has a plain text format representing a data table, with the first line being a header and defining the list of fields for each entry, and each following line representing one accounting entry, in no predetermined order."
msgid "If the check passes, then the file is read in full, kept in memory, and scanned. Accounting entities are imported one type at a time, in the following order."
msgid "Accounts in Odoo generally have a number of digits that are default for the fiscal localization. As the FEC module is related to the French localization, the default number of relevant digits is 6."
msgid "This means that the account codes the trailing zeroes are right-trimmed, and that the comparison between the account codes in the FEC file and the ones already existing in Odoo is performed only on the first six digits of the codes."
msgid "The account code `65800000` in the file is matched against an existing `658000` account in Odoo, and that account is used instead of creating a new one."
msgid "An account is technically flagged as *reconcilable* if the first line in which it appears has the `EcritureLet` field filled out, as this flag means that the accounting entry is going to be reconciled with another one."
msgid "In case the line somehow has this field not filled out, but the entry still has to be reconciled with a payment that hasn't yet been recorded, this isn't a problem anyway; the account is flagged as reconcilable as soon as the import of the move lines requires it."
msgid "As the **type** of the account is not specified in the FEC format, **new** accounts are created with the default type *Current Assets* and then, at the end of the import process, they are matched against the installed Chart of Account templates. Also, the *reconcile* flag is also computed this way."
msgid "The journal type is also not specified in the format (as per the accounts) and therefore it is at first created with the default type `general`."
msgid "Users can merge partners with the Data Cleaning App, where Vendors and Customers or similar partner entries may be merged by the user, with assistance from the system that groups them by similar entries."
msgid "Entries are immediately posted and reconciled after submission, using the `EcritureLet` field to do the matching between the entries themselves."
msgid "The `EcritureNum` field represents the name of the moves. We noticed that sometimes it may not be filled out. In this case, the field `PieceRef` is used."
msgid "There is a rounding tolerance with a currency-related precision on debit and credit (i.e., 0.01 for EUR). Under this tolerance, a new line is added to the move, named *Import rounding difference*, targeting the accounts:"
msgid "Should the `EcritureNum` not be filled out, it may also happen that the `PieceRef` field is also not suited to determine the move name (it may be used as an accounting move line reference) leaving no way to actually find which lines are to be grouped in a single move, and effectively impeding the creation of balanced moves."
msgid "One last attempt is made, grouping all lines from the same journal and date (`JournalLib`, `EcritureDate`). Should this grouping generate balanced moves (sum(credit) - sum(debit) = 0), then each different combination of journal and date creates a new move."
msgid "If a line has the partner information specified, the information is copied to the accounting move itself if the targeted Journal is of type *payable* or *receivable*."
msgid "If you have installed the French :ref:`fiscal localization package <fiscal_localizations/packages>`, you should be able to download the FEC. To do so, go to :menuselection:`Accounting --> Reporting --> France --> FEC`."
msgid "If you do not see the submenu **FEC**, go to :menuselection:`Apps`, remove the *Apps* filter, then search for the module named **France-FEC** and make sure it is installed."
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."
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 :doc:`upgrade to Odoo Enterprise </administration/on_premise/community_to_enterprise>` or contact your Odoo service provider."
msgid "If you use **Odoo Point of Sale**, :ref:`install <general/install>` the **France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 bis)** module by going to :menuselection:`Apps`, removing the *Apps* filter, then searching for *l10n_fr_pos_cert*, and installing the module."
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."
msgid "To install the module in any system created before December 18th 2017, you should update the modules list. To do so, activate the :ref:`developer mode <developer-mode>`. Then go to the *Apps* menu and press *Update Modules List* in the top-menu."
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."
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."
msgid "To ensure inalterability, every order or journal entry is encrypted upon validation. This number (or hash) is calculated from the key data of the document as well as from the hash of the precedent documents."
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."
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`."
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."
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."
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."
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."
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."
msgid "`Item 88 of Finance Law 2016 <https://www.legifrance.gouv.fr/affichTexteArticle.do?idArticle=JORFARTI000031732968&categorieLien=id&cidTexte=JORFTEXT000031732865>`_"
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."
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."
msgid "The **Kassensicherungsverordnung** (The Act on Protection against Manipulation of Digital Records) requires that electronic record-keeping systems - including the :doc:`point of sale </applications/sales/point_of_sale>` systems - must be equipped with a **Technical Security System** (also called **TSS** or **TSE**)."
msgid "The only VAT rates allowed are given by fiskaly. You can check these rates by consulting: `fiskaly DSFinV-K API: VAT Definition <https://developer.fiskaly.com/api/dsfinvk/v0/#tag/VAT-Definition>`_."
msgid "If your database was created before June 2021, :ref:`upgrade <general/upgrade>` your **Point of Sale** app (`point_of_sale`) and the **Restaurant** module (`pos_restaurant`)."
msgid ":ref:`Install <general/install>` the **Germany - Certification for Point of Sale** (`l10n_de_pos_cert`) and **Germany - Certification for Point of Sale of type restaurant** (`l10n_de_pos_res_cert`) modules."
msgid "To register your company, go to :menuselection:`Settings --> General Settings --> Companies --> Update Info`, fill out the following fields and *Save*."
msgid "To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the point of sale you want to edit, then check the box next to **Create TSS** and *Save*."
msgid "Whenever you close a PoS session, the orders' details are sent to the :abbr:`DSFinV-K (Digitale Schnittstelle der Finanzverwaltung für Kassensysteme)` service of fiskaly."
msgid "Leave the **Point of Sale** field blank if you want to export the data of all your points of sale. Specify a Point of Sale if you want to export this specific PoS' data only."
msgid "As you can see, the **State** is *Pending*. This means that the export has been successfully triggered and is being processed. You have to click on *Refresh State* to check if it is ready."
msgid "**GoBD** stands for *Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff*. In short, it is a **guideline for the proper management and storage of books, records, and documents in electronic form, as well as for data access**, that is relevant for the German tax authority, tax declaration, and balance sheet."
msgid "These principles have been written and published by the Federal Ministry of Finance (BMF) in November 2014. Since January 2015, **they have become the norm** and replace previously accepted practices linked to computer-based accounting. Several changes have been made by the BMF in 2019 and January 2020 to specify some of the content and due to the development of digital solutions (cloud hosting, paperless companies, etc.)."
msgid "If you can, the best way to understand GoBD is to Read the `Official GoBD text <https://ao.bundesfinanzministerium.de/ao/2021/Anhaenge/BMF-Schreiben-und-gleichlautende-Laendererlasse/Anhang-64/anhang-64.html>`_. It is a bit long but quite readable for non-experts. But in short, here is what to expect:"
msgid "The **GoBD is binding for companies that have to present accounts, which includes SMEs, freelancers, and entrepreneurs, to the financial authorities**. As such, **the taxpayer himself is the sole responsible** for the complete and exhaustive keeping of fiscal-relevant data (above-mentioned financial and related data)."
msgid "The user must distribute tasks within its organization to the relevant positions (*control*) and verify that the tasks are properly and completely performed (*supervision*). The result of these controls must be recorded (*documentation*), and should errors be found during these controls, appropriate measures to correct the situation should be put into place (*prevention*)."
msgid "**The taxpayer must secure the system against any data loss due to deletion, removal, or theft of any data**. If the entries are not sufficiently secured, the bookkeeping will be regarded as not in accordance with the GoBD guidelines."
msgid "If Odoo is used in the cloud, regular backups are part of the Odoo Online service. In addition, regular backups can be downloaded and backed up on external systems."
msgid "In some cases, data has to be kept for ten years or more, so always have backups saved. It is even more important if you decide to change software provider."
msgid "Considering GoBD only applies between the taxpayer and the financial authority, **the software editor can by no means be held responsible for the accurate and compliant documentation of financial transactional data of their users**. It can merely provide the necessary tools for the user to respect the software related guidelines described in the GoBD."
msgid "The key words, when it comes to GoBD, are: **traceable, verifiable, true, clear, and continuous**. In short, you need to have audit-proof archiving in place and Odoo provides you with the means to achieve all of these objectives:"
msgid "Each record in Odoo is stamped with the creator of the document, the creation date, the modification date, and who modified it. In addition, relevant fields are tracked thus it can be seen which value was changed by whom in the chatter of the relevant object."
msgid "All financial data must be recorded in the system, and there can be no gaps. Odoo ensures that there is no gap in the numbering of the financial transactions. It is the responsibility of the user to encode all financial data in the system. As most financial data in Odoo is generated automatically, it remains the responsibility of the user to encode all vendor bills and miscellaneous operations completely."
msgid "Odoo ensures with the correct configuration that the correct accounts are used. In addition, the control mechanisms between purchase orders and sales orders and their respective invoices reflect the business reality. It is the responsibility of the user to scan and attach the paper-based vendor bill to the respective record in Odoo. *Odoo Document helps you automate this task*."
msgid "As most financial data in Odoo is generated by the transactional objects (for example, the invoice is booked at confirmation), Odoo ensures out-of-the-box timely record-keeping. It is the responsibility of the user to encode all incoming vendor bills in a timely manner, as well as the miscellaneous operations."
msgid "Financial data stored in Odoo is per definition ordered and can be reordered according to most fields present in the model. A specific ordering is not enforced by the GoBD, but the system must ensure that a given financial transaction can be quickly found by a third-party expert. Odoo ensures this out-of-the-box."
msgid "With the German Odoo localization, Odoo is in standard configured in such a way that the inalterability clause can be adhered to without any further customization."
msgid "In the case of fiscal control, the fiscal authority can request three levels of access to the accounting system (Z1, Z2, Z3). These levels vary from direct access to the interface to the handover of the financial data on a storage device."
msgid "In case of a handover of the financial data on a storage device, the format is **not** enforced by the GoBD. It can be, for example, in XLS, CSV, XML, Lotus 123, SAP-format, AS/400-format, or else. Odoo supports the CSV and XLS-export of financial data out-of-the-box. The GoBD **recommends** the export in a specific XML-based GoBD-format (see \"Ergänzende Informationen zur Datenntträgerüberlassung\" §3) but it is not binding."
msgid "The GoBD clearly states that due to the nature of a state of the art accounting software, their configuration possibilities, changing nature, and various forms of use, **no legally binding certification can be given**, nor can the software be made liable towards a public authority. Third-party certificates can indeed have **an informative value** for customers to make software buying decisions but are by no means legally binding or of any other legal value (A. 12, § 181)."
msgid "A GoBD certificate states nothing more than that if you use the software according to its guidelines, the software will not refrain you from respecting the GoBD. These certifications are very expensive in terms of time and cost, and their value is very relative. Thus we focus our efforts on ensuring GoBD compliance rather than pay for a marketing tool which does not, however, offer our customer any legal certainty."
msgid "The BMF actually states the following in the `Official GoBD text <https://ao.bundesfinanzministerium.de/ao/2021/Anhaenge/BMF-Schreiben-und-gleichlautende-Laendererlasse/Anhang-64/anhang-64.html>`_:"
msgid "180. Positive attestations on the correctness of the bookkeeping - and thus on the correctness of IT-based bookkeeping systems - are not issued either in the context of a tax field audit or in the context of binding information."
msgid "181. \"Certificates\" or \"attestations\" from third parties can serve as a decision criterion for the company when selecting a software product, but develop from the in margin no. 179 is not binding on the tax authorities."
msgid "The previous content was `automatically translated from German with Google Translate <https://translate.google.com/?sl=de&tl=en&text=180.%0APositivtestate%20zur%20Ordnungsm%C3%A4%C3%9Figkeit%20der%20Buchf%C3%BChrung%20-%20und%20damit%20zur%20Ordnungsm%C3%A4%C3%9Figkeit%20DV-gest%C3%BCtzter%20Buchf%C3%BChrungssysteme%20-%20werden%20weder%20im%20Rahmen%20einer%20steuerlichen%20Au%C3%9Fenpr%C3%BCfung%20noch%20im%20Rahmen%20einer%20verbindlichen%20Auskunft%20erteilt.%0A%0A181.%0A%E2%80%9EZertifikate%E2%80%9C%20oder%20%E2%80%9ETestate%E2%80%9C%20Dritter%20k%C3%B6nnen%20bei%20der%20Auswahl%20eines%20Softwareproduktes%20dem%20Unternehmen%20als%20Entscheidungskriterium%20dienen%2C%20entfalten%20jedoch%20aus%20den%20in%20Rz.%20179%20genannten%20Gr%C3%BCnden%20gegen%C3%BCber%20der%20Finanzbeh%C3%B6rde%20keine%20Bindungswirkung.%20&op=translate>`_."
msgid "You must register on the :abbr:`NIC (National Informatics Centre)` e-Invoice portal to get your **API credentials**. You need these credentials to :ref:`configure your Odoo Accounting app <india/e-invoicing-configuration>`."
msgid "Log in to the `NIC e-Invoice portal <https://einvoice1.gst.gov.in/>`_ by clicking :guilabel:`Login` and entering your :guilabel:`Username` and :guilabel:`Password`;"
msgid "After that, you should receive an :abbr:`OTP (one-time password)` code on your registered mobile number. Enter the OTP code and click :guilabel:`Verify OTP`;"
msgid "Select :guilabel:`Through GSP` for the API interface, set :guilabel:`Tera Software Limited` as GSP, and type in a :guilabel:`Username` and :guilabel:`Password` for your API. Once it is done, click :guilabel:`Submit`."
msgid "To enable the e-Invoice service in Odoo, go to :menuselection:`Accounting --> Configuration --> Settings --> Indian Electronic Invoicing`, and enter the :guilabel:`Username` and :guilabel:`Password` previously set for the API."
msgid "To automatically send e-Invoices to the NIC e-Invoice portal, you must first configure your *sales* journal by going to :menuselection:`Accounting --> Configuration --> Journals`, opening your *sales* journal, and in the :guilabel:`Advanced Settings` tab, under :guilabel:`Electronic Data Interchange`, enable :guilabel:`E-Invoice (IN)` and save."
msgid "Once an invoice is validated, a confirmation message is displayed at the top. Odoo automatically uploads the JSON-signed file of validated invoices to the NIC e-Invoice portal after some time. If you want to process the invoice immediately, click :guilabel:`Process now`."
msgid "You can check the document's :abbr:`EDI (electronic data interchange)` status under the :guilabel:`EDI Document` tab or the :guilabel:`Electronic invoicing` field of the invoice."
msgid "Once an invoice is validated and submitted, the invoice PDF report can be printed. The report includes the :abbr:`IRN (Invoice Reference Number)`, :guilabel:`Ack. No` (acknowledgment number) and :guilabel:`Ack. Date` (acknowledgment date), and QR code. These certify that the invoice is a valid fiscal document."
msgid "If you want to cancel an e-Invoice, go to the :guilabel:`Other info` tab of the invoice and fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Then, click :guilabel:`Request EDI cancellation`. The status of the :guilabel:`Electronic invoicing` field changes to :guilabel:`To Cancel`."
msgid "Once you request to cancel the e-Invoice, Odoo automatically submits the JSON-signed file to the NIC e-Invoice portal. You can click :guilabel:`Process now` if you want to process the invoice immediately."
msgid "You must register on the :abbr:`NIC (National Informatics Centre)` E-Way bill portal to create your **API credentials**. You need these credentials to :ref:`configure your Odoo Accounting app <india/e-waybill-configuration>`."
msgid "Log in to the `NIC E-Way bill portal <https://ewaybillgst.gov.in/>`_ by clicking :guilabel:`Login` and entering your :guilabel:`Username` and :guilabel:`Password`;"
msgid "Check if :guilabel:`Tera Software Limited` is already on the registered GSP/ERP list. If so, use the username and password used to log in to the NIC portal. Otherwise, follow the next steps;"
msgid "Select :guilabel:`Add/New`, select :guilabel:`Tera Software Limited` as your GSP Name, create a :guilabel:`Username` and a :guilabel:`Password` for your API, and click :guilabel:`Add`."
msgid "To set up the E-Way bill service, go to :menuselection:`Accounting --> Configuration --> Settings --> Indian Electronic WayBill --> Setup E-Way bill`, and enter your :guilabel:`Username` and :guilabel:`Password`."
msgid "You can manually send an E-Way bill by clicking :guilabel:`Send E-Way bill`. To send the E-Way bill automatically when an invoice or a bill is confirmed, enable :guilabel:`E-Way bill (IN)` in your :ref:`Sales or Purchase journal <india/e-invoicing-journals>`."
msgid "Odoo automatically uploads the JSON-signed file to the government portal after some time. Click :guilabel:`Process now` if you want to process the invoice immediately."
msgid "You can print the invoice PDF report once you have submitted the E-Way bill. The report includes the **E-Way bill number** and the **E-Way bill validity date**."
msgid "If you want to cancel an E-Way bill, go to the :guilabel:`E-Way bill` tab of the related invoice and fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Then, click :guilabel:`Request EDI Cancellation`."
msgid "Once you request to cancel the E-Way bill, Odoo automatically submits the JSON-signed file to the government portal. You can click :guilabel:`Process Now` if you want to process the invoice immediately."
msgid "Log into the `GST portal <https://services.gst.gov.in/services/login>`_ by entering your :guilabel:`Username` and :guilabel:`Password`, and go to :guilabel:`My Profile` on your **profile menu**;"
msgid "Go to :menuselection:`Accounting --> Configuration --> Settings --> Indian GST Service` and enter the :guilabel:`GST Username`. Click :guilabel:`Send OTP`, enter the code, and finally, :guilabel:`Validate`."
msgid "When the :guilabel:`Indian GST Service` is configured, you can file your GST return. Go to :menuselection:`Accounting --> Reporting --> India --> GST Return periods` and create a new **GST Return Period** if it does not exist. GST Return file-in is done in **three steps** in Odoo:"
msgid "The user can verify the :ref:`GSTR-1 <india/gstr-1_report>` report before uploading it to the **GST portal** by clicking :guilabel:`GSTR-1 Report`;"
msgid "If the **GSTR-1** report is correct, then click :guilabel:`Push to GSTN` to send it to the **GST portal**. The status of the :guilabel:`GSTR-1` report changes to :guilabel:`Sending`;"
msgid "After a few seconds, the status of the **GSTR-1** report changes to :guilabel:`Waiting for Status`. It means that the **GSTR-1** report has been sent to the :guilabel:`GST Portal` and is being verified on the :guilabel:`GST Portal`;"
msgid "Once more, after a few seconds, the status either changes to :guilabel:`Sent` or :guilabel:`Error in Invoice`. The status :guilabel:`Error in Invoice` indicates that some of the invoices are not correctly filled out to be validated by the **GST portal**;"
msgid "If the state of the **GSTR-1** is :guilabel:`Error in Invoice`, invoices can be checked for errors in the :guilabel:`Log Note`. Once issues have been resolved, the user can click :guilabel:`Push to GSTN` to submit the file again on the **GST portal**."
msgid "Click :guilabel:`Mark as Filed` after filing the **GSTR-1** report on the **GST portal**. The status of the report changes to :guilabel:`Filed` in **Odoo**."
msgid "Click :guilabel:`Fetch GSTR-2B Summary` to retrieve the **GSTR-2B** summary. After a few seconds, the status of the report changes to :guilabel:`Waiting for Reception`. This means Odoo is trying to receive the **GSTR-2B** report from the **GST portal**;"
msgid "Once more, after a few seconds, the status of the **GSTR-2B** changes to the :guilabel:`Being Processed`. It means Odoo is reconciling the **GSTR-2B** report with your Odoo bills;"
msgid "If the status is :guilabel:`Partially Matched`, you can make changes in bills by clicking :guilabel:`View Reconciled Bills`. Once it is done, click :guilabel:`re-match`."
msgid "The :ref:`GSTR-3 <india/gstr-3_report>` report is a monthly summary of **sales** and **purchases**. This return is auto-generated by extracting information from **GSTR-1** and **GSTR-2**."
msgid "Users can compare the **GSTR-3** report with the **GSTR-3** report available on the **GST portal** to verify if they match by clicking :guilabel:`GSTR-3 Report`;"
msgid "Once the **GSTR-3** report has been verified by the user and the tax amount on the **GST portal** has been paid. Once paid, the report can be **closed** by clicking :guilabel:`Closing Entry`;"
msgid "In :guilabel:`Closing Entry`, add the tax amount paid on the **GST portal** using challan, and click :guilabel:`POST` to post the :guilabel:`Closing Entry`;"
msgid "The :guilabel:`GSTR-1` report is divided into sections. It displays the :guilabel:`Base` amount, :abbr:`CGST (Central Goods and Services Tax)`, :abbr:`SGST (State Goods and Service Tax)`, :abbr:`IGST (Integrated Goods and Services Tax)`, and :guilabel:`CESS` for each section."
msgid "The **E-Faktur Module** is installed by default with the Indonesian localization module. It allows one to generate a CSV file for one tax invoice or for a batch of tax invoices to upload to the **Tax Office e-Faktur** application."
msgid "This information is used in the FAPR line in the effect file format. You need to set a VAT number on the related partner of your Odoo company. If you don't, it won't be possible to create an e-Faktur from an invoice."
msgid "You need to set the checkbox *ID PKP* to generate e-fakturs for a customer. You can use the VAT field on the customer's contact to set the NPWP needed to generate the e-Faktur file. If your customer does not have an NPWP, just enter the NIK in the same VAT field."
msgid "Go to :menuselection:`Accounting --> Customers --> e-Faktur`. In order to be able to export customer invoices as e-Faktur for the Indonesian government, you need to put here the ranges of numbers you were assigned by the government. When you validate an invoice, a number will be assigned based on these ranges. Afterwards, you can filter the invoices still to export in the invoices list and click on *Action*, then on *Download e-Faktur*."
msgid "After receiving new serial numbers from the Indonesian Revenue Department, you can create a set of tax invoice serial numbers group through this list view. You only have to specify the Min and Max of each serial numbers' group and Odoo will format the number automatically to a 13-digits number, as requested by the Indonesia Tax Revenue Department."
msgid "Create an invoice from :menuselection:`Accounting --> Customers --> Invoices`. If the invoice customer's country is Indonesia and the customer is set as *ID PKP*, Odoo will allow you to create an e-Faktur."
msgid "Odoo will automatically pick the next available serial number from the e-Faktur number table (see the :ref:`section above <localization_indonesia/tax_invoice_sn>`) and generate the e-faktur number as a concatenation of Kode Transaksi and serial number. You can see this from the invoice form view under the page *Extra Info* in the box *Electronic Tax*."
msgid "Once the invoice is posted, you can generate and download the e-Faktur from the *Action* menu item *Download e-faktur*. The checkbox *CSV created* will be set."
msgid "The following codes are available when generating an e-Faktur. - 01 Kepada Pihak yang Bukan Pemungut PPN (Customer Biasa) - 02 Kepada Pemungut Bendaharawan (Dinas Kepemerintahan) - 03 Kepada Pemungut Selain Bendaharawan (BUMN) - 04 DPP Nilai Lain (PPN 1%) - 06 Penyerahan Lainnya (Turis Asing) - 07 Penyerahan yang PPN-nya Tidak Dipungut (Kawasan Ekonomi Khusus/ Batam) - 08 Penyerahan yang PPN-nya Dibebaskan (Impor Barang Tertentu) - 09 Penyerahan Aktiva (Pasal 16D UU PPN)"
msgid "Create a new invoice and set the canceled invoice in the *Replace Invoice* field. In this field, we can only select invoices in *Cancel* state from the same customer."
msgid "As you validate, Odoo will automatically use the same e-Faktur serial number as the canceled and replaced invoice replacing the third digit of the original serial number with *1* (as requested to upload a replacement invoice in the e-Faktur app)."
msgid "Configuring the company's information ensures your Accounting database is properly set up. To add information, go to :menuselection:`Settings --> General Settings`, and in the :guilabel:`Companies` section, click :guilabel:`Update info`. From here, fill out the fields:"
msgid "The :abbr:`SdI (Sistema di Interscambio)` is the electronic invoicing system used in Italy. It enables to send and receive electronic invoices to and from customers. The documents must be in XML format and formally validated by the system before being delivered."
msgid "To be able to receive invoices and notifications, the :abbr:`SdI (Sistema di Interscambio)` service must be notified that the user's files are to be sent to **Odoo** and processed on their behalf. To so, you must set up Odoo's :guilabel:`Codice Destinatario` on the **Agenzia Delle Entrate** portal."
msgid "In :menuselection:`Servizi Disponibili --> Fatturazione Elettronica --> Registrazione dell’indirizzo telematico dove ricevere tutte le fatture elettroniche`, insert Odoo's :guilabel:`Codice Destinatario` `K95IV18`, and confirm."
msgid "Odoo uses the **FatturaPA** :abbr:`EDI (Electronic Data Interchange)` format for the Italian localization and is enabled on the default journals when installed. When the **file processing authorization** has been set, all **invoices** and **bills** are automatically sent."
msgid "You can check the current status of an invoice by the :guilabel:`Electronic invoicing` field. The XML file can be found in the **chatter** of the invoice."
msgid "Since the files are transmitted through Odoo's server before being sent to the :abbr:`SdI (Sistema di Interscambio)` or received by your database, you need to authorize Odoo to process your files from your database. To do so, go to :menuselection:`Accounting --> Configuration --> Settings --> Electronic Document Invoicing`."
msgid "This mode simulates an environment in which invoices are sent to the government. In this mode, invoices need to be *manually* downloaded as XML files and uploaded to the **Agenzia delle Entrate**'s website."
msgid "This mode sends invoices to a non-production (i.e., test) service made available by the **Agenzia delle Entrate**. Saving this change directs all companies on the database to use this configuration."
msgid "Once a mode is selected, you need to accept the **terms and conditions** by ticking :guilabel:`Allow Odoo to process invoices`, and then :guilabel:`Save`. You can now record your transactions in Odoo Accounting."
msgid "Selecting either :guilabel:`Test (experimental)` or :guilabel:`Official` is **irreversible**. Once in :guilabel:`Official` mode, it is not possible to select :guilabel:`Test (experimental)` or :guilabel:`Demo`, and same for :guilabel:`Test (experimental)`. We recommend creating a separate database for testing purposes only."
msgid "When in :guilabel:`Test (Experimental)` mode, all invoices sent *must* have a partner using one of the following fake :guilabel:`Codice Destinatario` given by the **Agenzia Delle Entrate**: `0803HR0` - `N8MIMM9` - `X9XX79Z`. Any real production :guilabel:`Codice Destinario` of your customers will not be recognized as valid by the test service."
msgid "Many of the e-invoicing features are implemented using Odoo's tax system. As such, it is very important that taxes are properly configured in order to generate invoices correctly and handle other billing use cases. For example, specific configurations are required for the **reverse charge** type of taxes. In case of a **reverse charge** tax, the seller does *not* charge the customer for the VAT but, instead, the customer pays the VAT *themselves* to their government. There are **two** main types:"
msgid "To make an export invoice, make sure that the invoice lines all use a tax configured for **reverse charge**. The **Italian** localization contains an **example** of a reverse charge tax for export in the EU to be used as reference (`0% EU`, invoice label `00eu`), which can be found under :menuselection:`Accounting --> Configuration --> Taxes`. Exports are exempt from VAT, and therefore **reverse charge** taxes require the :guilabel:`Has exoneration of tax (Italy)` option ticked, with both the :guilabel:`Exoneration` kind and :guilabel:`Law Reference` filled in."
msgid "If you need to use a different kind of :guilabel:`Exoneration`, click :menuselection:`Action --> Duplicate` within the tax menu to create a copy of an existing similar tax. Then, select another :guilabel:`Exoneration`, and :guilabel:`Save`. Repeat this process as many times as you need different kind of :guilabel:`Exoneration` taxes."
msgid "On your invoice, select the corresponding tax you need in the :guilabel:`Taxes` field. You can find the following **additional info** by opening the **XML** file of the issued invoice:"
msgid ":guilabel:`Partita Iva` (**VAT number**): must contain the **VAT** number for **EU businesses** and `OO99999999999` (double 'O' **letter**, not 'zero') for **non-EU businesses**. In case of private customers without **VAT** number, use `0000000`;"
msgid "**Down payment** invoices are imported/exported with a different :guilabel:`Tipo Documento` code `TDO2` than regular invoices. Upon import of the invoice, it creates a regular vendor bill."
msgid "Simplified invoices and credit notes can be used to certify **domestic transactions** under **400 EUR** (VAT included). Its status is the same as a regular invoice, but with fewer information requirements."
msgid ":guilabel:`Company Info`: the **seller**'s full credentials (VAT/TIN number, name, full address) under :menuselection:`General Settings --> Companies (section)`;"
msgid "The 400 EUR threshold was defined in `the decree of the 10th of May 2019 in the Gazzetta Ufficiale <https://www.gazzettaufficiale.it/eli/id/2019/05/24/19A03271/sg>`_. We advise you to check the current official value."
msgid "The **deferred invoice** is an invoice that is **issued at a later time** than the sale of goods or the provision of services. A **deferred invoice** has to be issued at the latest within the **15th day** of the month following the delivery covered by the document."
msgid "It usually is a **summary invoice** containing a list of multiple sales of goods or services, carried out in the month. The business is allowed to **group** the sales into **one invoice**, generally issued at the **end of the month** for accounting purposes. Deferred invoices are default for **wholesaler** having recurrent clients."
msgid "If the goods are transported by a **carrier**, every delivery has an associated **Documento di Transporto (DDT)**, or **Transport Document**. The deferred invoice **must** indicate the details of all the **DDTs** information for better tracing."
msgid "E-invoicing of deferred invoices requires the `l10n_it_stock_ddt` :ref:`module <italy/modules>`. In this case, a dedicated :guilabel:`Tipo Documento` `TD24` is used in the e-invoice."
msgid "Italian companies buying goods or services from EU countries (or services from non-EU countries) must send the information contained within the bill received to the **Agenzia delle Entrate**. This allows you to complete tax-related information on your bill, and to send it. The seller must be set as :guilabel:`Cedente/Prestatore`, and the buyer as :guilabel:`Cessionario/Committente`. Contained within the **XML** document for the vendor bill, the vendor's credentials show as :guilabel:`Cedente/Prestatore`, and your company's credentials as :guilabel:`Cessionario/Committente`."
msgid "When inputting taxes in a vendor bill, it is possible to select **reverse charge** taxes. These are automatically activated in the Italian fiscal position. By going to :menuselection:`Accounting --> Configuration --> Taxes`, the `10%` and `22%` :guilabel:`Goods` and :guilabel:`Services` tax scopes are activated and preconfigured with the correct tax grids. These are set up automatically to ensure the correct booking of accounting entries and display of the tax report."
msgid "Odoo does not offer the `Conservazione Sostitutiva <https://www.agid.gov.it/index.php/it/piattaforme/conservazione>`_ requirements. Other providers and **Agenzia delle Entrate** supply free and certified storage to meet the requested conditions."
msgid "The Italian localization has a specific **tax grid** section for **reverse charge** taxes. These tax grids are identifiable by the :ref:`VJ <italy/grids>` tag, and can be found under :menuselection:`Accounting --> Reporting --> Audit Reports: Tax Report`."
msgid "San Marino and Italy have special agreements on e-invoicing operations. As such, **invoices** follow the regular **reverse charge** rules. Additional requirements are not enforced by Odoo, however, the user is requested by the **State** to:"
msgid "Use the generic :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Codice Destinatario` `2R4GTO8`. The invoice is then routed by a dedicated office in San Marino to the correct business."
msgid "When a **paper bill** is received from San Marino, any Italian company **must** submit that invoice to the **Agenzia delle Entrate** by indicating the e-invoice's :guilabel:`Tipo Documento` field with the special value `TD28`."
msgid "Odoo does **not** send invoices directly to the government as they need to be signed. If we see that the codice destinatario is 6 digits, then it is not sent to the PA automatically, but you can download the XML, sign it with an external program and send it through the portal."
msgid "For invoices and bills intended to the **Pubblica Amministrazione (B2G)**, a **Digital Qualified Signature** is required for all files sent through the :abbr:`SdI (Sistema di Interscambio)`. The **XML** file must be certified using a certificate that is either:"
msgid "To ensure the effective traceability of payments by public administrations, electronic invoices issued to the public administrations must contain:"
msgid "The :abbr:`CIG (Codice Identificativo Gara)`, except in cases of exclusion from traceability obligations provided by law n. 136 of August 13, 2010;"
msgid "If the **XML** file requires it, the **Agenzia Delle Entrate** can *only* proceed payments of electronic invoices when the **XML** file contains a :abbr:`CIG (Codice Identificativo Gara)` and :abbr:`CUP (Codice Unico di Progetto)`. For each electronic invoice, it is **necessary** to indicate the :abbr:`CUU (Codice Univoco Ufficio)`, which represents the unique identifier code that allows the :abbr:`SdI (Sistema di Interscambio)` to correctly deliver the electronic invoice to the recipient office."
msgid "The :abbr:`Codice Unico di Progetto)` and the :abbr:`CIG (Codice Identificativo Gara)` must be included in one of the **2.1.2** (DatiOrdineAcquisto), **2.1.3** (Dati Contratto), **2.1.4** (DatiConvenzione), **2.1.5** (Date Ricezione), or **2.1.6** (Dati Fatture Collegate) information blocks. These correspond to the elements named :guilabel:`CodiceCUP` and :guilabel:`CodiceCIG` of the electronic invoice **XML** file, whose table can be found on the government `website <http://www.fatturapa.gov.it/>`_."
msgid "The :abbr:`CUU (Codice Univoco Ufficio)` must be included in the electronic invoice corresponding to the element **1.1.4** (:guilabel:`CodiceDestinario`)."
msgid ":abbr:`Ri.Ba. (Ricevuta Bancaria)` is a payment method widely used in Italy where vendors request payments through their bank, which forwards the request to the customer's own bank and takes responsibility for the collection. This enables payment automation and reduces risks for the vendor."
msgid "Ri.Ba. are exclusively for **domestic payments** in Italy. For recurring international payments, please use `SEPA Direct Debt (SDD) <../accounting/payments/batch_sdd>`_"
msgid "The :guilabel:`SIA Code` identifies businesses within the Italian banking network and is used to receive money through specific payment methods. It consists of one letter and four digits (e.g., T1234) and can usually be found on the bank's portal or obtained by contacting the bank."
msgid "Payments of type :abbr:`Ri.Ba. (Ricevuta Bancaria)` can be registered from the :guilabel:`Invoices` (:menuselection:`Accounting --> Customers --> Invoices`)."
msgid "Once you press the :guilabel:`Validate` button for the Batch Payment, the :abbr:`Ri.Ba. (Ricevuta Bancaria)` file is generated and attached to the Batch Payment, so you can download it and upload it through your bank's web portal."
msgid "You also have to install the **Kenya Tremol Device EDI Integration** package to be able to report your taxes to the **Kenya Revenue Authority (KRA)** using the Tremol G03 Control Unit:"
msgid "The Kenya Revenue Authority (KRA) has decided to go digital for tax collection through the **Tax Invoice Management System (TIMS)**. As of December 1st, 2022, all VAT-registered persons should comply with TIMS. The goal is to reduce VAT fraud, increase tax revenue, and increase VAT compliance through standardization, validation, and transmission of invoices to KRA on a real-time or near real-time basis."
msgid "All VAT-registered taxpayers should use a **compliant tax register**. Odoo decided to develop the integration of the **Tremol G03 Control Unit (type C)**, which can be run locally through USB. This device validates invoices to ensure financial documents meet the new regulations and send the validated tax invoices directly to KRA. Installing a proxy server that provides a gateway between users and the internet is required."
msgid "Once it is loaded on your computer, a wizard opens. You have to read and agree with the terms of the agreement. On the next page, select the :guilabel:`type of install: Odoo IoT`. Then, click :guilabel:`Next` and :guilabel:`Install`. Once completed, click :guilabel:`Next`. Check the :guilabel:`Start Odoo` box to be redirected to Odoo automatically, and then click :guilabel:`Finish`."
msgid "A new page opens, confirming your :doc:`IoT Box <../../general/iot/config/connect>` is up and running. Connect your physical device **Tremol G03 Control Unit (type C)** to your laptop via USB. In the :guilabel:`IoT Device` section, check that your Tremol G03 Control Unit (type C) appears, confirming the connection between the device and your computer."
msgid "As a pre-requisite, check out that the :ref:`Kenyan Accounting modules <localization/kenya/configuration>` are installed on your database. Then, go to :menuselection:`Accounting --> Configuration --> Settings --> Kenya TIMS Integration section`, and check that the :guilabel:`control Unit Proxy Address` matches the address of the IoT box."
msgid "To send data to KRA, create a new invoice by going to :menuselection:`Accounting Dashboard --> Customer Invoice card` and clicking :guilabel:`New Invoice`. Upon confirmation of a new invoice, the :guilabel:`Send invoice to Fiscal Device` button appears. Clicking on it sends the invoice details to the device and from the device to the government. The :guilabel:`CU Invoice Number` field is now completed in your invoice, confirming the information has been sent."
msgid "If you click on :guilabel:`Send and Print`, a .pdf of the invoice is generated. The :guilabel:`Kenyan Fiscal Device Info` is mentioned on the document."
msgid "To verify KRA has received the invoice information, take the :guilabel:`CU Invoice Number` and enter it in the :guilabel:`Invoice Number Checker` section on `Kenya Revenue Authority website <https://itax.kra.go.ke/KRA-Portal>`_. Click :guilabel:`Validate` and find the invoice details."
msgid "Odoo's :ref:`fiscal localization package <fiscal_localizations/packages>` for Luxembourg includes the current **Standard Chart of Accounts (PCN 2020)**, effective since January 2020."
msgid "To do so, go to :menuselection:`Accounting --> Report --> Luxembourg --> Annual Tax Report`, click on :guilabel:`Create`, then define the annual period in the :guilabel:`Year` field."
msgid "The **simplified annual declaration** is automatically generated. You can manually add values in all the fields to get a **complete annual declaration**."
msgid "To help you complete it, you can use the information provided on the :guilabel:`Tax Report`. To do so, go to :menuselection:`Accounting --> Report --> Audit Reports --> Tax Report`, then click on the :guilabel:`Tax Report` dropdown menu and select the type of report you want to display."
msgid "**FAIA (Fichier d’Audit Informatisé AED)** is a standardized and structured file that facilitates the exchange of information between the taxpayers' accounting system and the tax office. It is the Luxembourgish version of the OECD-recommended SAF-T (Standard Audit File for Tax)."
msgid "Odoo can generate an XML file that contains all the content of an accounting period according to the rules imposed by the Luxembourg tax authorities on digital audit files."
msgid "A video on the Mexican localization is also available. This video covers how to implement this localization from scratch, including how to set up the configurations, how to complete common workflows, and provides an in-depth look at several specific use cases, as well."
msgid "The Odoo Mexican localization modules allow for the signing of electronic invoices, according to the specifications of the |SAT| for `version 4.0 of the CFDI <http://omawww.sat.gob.mx/ tramitesyservicios/Paginas/documentos/Anexo_20_Guia_de_llenado_CFDI.pdf>`_, a legal requirement, as of January 1, 2022. These modules also add relevant accounting reports (such as: the |DIOT|, enables foreign trade, and the creation of delivery guides)."
msgid "Choose a PAC (Proveedor Autorizado de Certificación / Authorized Certification Provider). Currently, Odoo works with the following |PAC|\\s: `Solución Factible <https://solucionfactible.com/>`_, `Quadrum (formerly Finkok) <https://cfdiquadrum.com.mx/>`_ and `SW Sapien - Smarter Web <https://sw.com.mx/>`_."
msgid "Have knowledge and experience with billing, sales, and accounting in Odoo. This documentation **only** contains the necessary information needed to use Odoo."
msgid ":ref:`Install <general/install>` the following modules to get all the features of the Mexican localization. The :doc:`Accounting <../accounting>` and *Contacts* modules are required to be installed for this configuration:"
msgid "The default :doc:`fiscal localization package <../fiscal_localizations>`, adds accounting characteristics for the Mexican localization, such as: the most common taxes and the chart of accounts – based on `the SAT account grouping code <https://www.gob.mx/cms/uploads/attachment/file/151586/codigo_agrupador.pdf>`_."
msgid "Includes all the technical and functional requirements to generate and validate :doc:`Electronics Documents <../accounting/customer_invoices/electronic_invoicing>` — based on the technical documentation published by the |SAT|. This allows you to send invoices (with or without addedums) and payment complements to the government."
msgid "When installing a database from scratch and selecting :guilabel:`Mexico` as the country, Odoo automatically installs the following modules: :guilabel:`Mexico - Accounting`, :guilabel:`EDI for Mexico`, and :guilabel:`EDI v4.0 for Mexico`."
msgid "The following modules are optional. It's recommended to install them *only* if meeting a specific requirement. Make sure that they are needed for the business."
msgid "Lets you create a *Carta Porte*: A bill of lading that proves to the government you are sending goods between A & B with a signed electronic document."
msgid "After installing the correct modules, the next step is to verify that your company is configured with the correct data. To do so, go to :menuselection:`Settings --> General Settings --> Companies`, and select :guilabel:`Update Info` under your company name."
msgid "Enter the full :guilabel:`Address` in the resulting form, including: :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| (:guilabel:`VAT` number)."
msgid "According to the requirements of the CFDI 4.0, the name of the main company contact **must** coincide with your business name registered in the |SAT|, without the legal entity abbreviation."
msgid "From a legal point of view, a Mexican company **must** use the local currency (MXN). Therefore, Odoo does not provide features to manage an alternative configuration. If you want to manage another currency, let MXN be the default currency and use a :doc:`pricelist <../../sales/sales/products_prices/prices/pricing>`, instead."
msgid "Next, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX) --> Fiscal Regime`, then select the regime that applies to your company from the drop-down list, and click :guilabel:`Save`."
msgid "If you want to test the Mexican localization, the company can be configured with a real address within Mexico (including all fields), and add `EKU9003173C9` as the :guilabel:`VAT` and `ESCUELA KEMPER URGATE` as the :guilabel:`Company Name`. For the :guilabel:`Fiscal Regime`, use :guilabel:`General de Ley Personas Morales`."
msgid "To create a contact that can be invoiced, go to :menuselection:`Contacts --> Create`. Then, enter the contact name, full :guilabel:`Address` including: :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| (:guilabel:`VAT` number)."
msgid "As with your own company, all of your contacts needs to have their correct business name registered in the |SAT|. This also applies to the :guilabel:`Fiscal Regime`, which needs to be added in the :guilabel:`MX EDI` tab."
msgid "The *Factor Type* field is pre-loaded in the default taxes. If new taxes are created, you need to make sure to configure this field. To do so, go to :menuselection:`Accounting --> Configuration --> Taxes`, then enable the :guilabel:`Factor Type` field in the :guilabel:`Advanced Options` tab for all records, with the :guilabel:`Tax Type` set as :guilabel:`Sales`."
msgid "One requirement of the CFDI 4.0 is that the resulting XML file needs (or does not need) to break down the taxes of the operation. There are three different possible values that are added in the XML file:"
msgid "To use the `03` value, navigate to :menuselection:`Contacts --> your customer's invoice --> MX EDI tab`, and activate the :guilabel:`No Tax Breakdown` checkbox."
msgid "The :guilabel:`No Tax Breakdown` value applies **only** to specific fiscal regimes and/or taxes. Consult your accountant first to see if it is needed for your business before making any modification."
msgid "When registering a payment, Odoo will carry out the movement of taxes from the *Cash Basis Transition Account* to the account set in the :guilabel:`Definition` tab. For such movement, a tax base account will be used: (`Base Imponible de Impuestos en Base a Flujo de Efectivo`) in the journal entry when reclassifying taxes. **Do not delete this account**."
msgid "If you create a new tax in :menuselection:`Accounting --> Configuration --> Taxes`, you need to add the correct :guilabel:`Tax Grids` for it (`IVA`, `ISR` or `IEPS`). Odoo **only** supports these three groups of taxes."
msgid "To configure products, go to :menuselection:`Accounting --> Customers --> Products`, then select a product to configure, or :guilabel:`Create` a new one. In the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product Category` field, select the category that represents the product. The process can be done manually, or through :doc:`a bulk import <../../essentials/export_import_data>`."
msgid "After you have processed your `Private Key (CSD) <https://www.sat.gob.mx/aplicacion/16660/genera-y-descarga-tus-archivos-a-traves-de-la-aplicacion- certifica>`_ with the |SAT|, you **must** register directly with the :ref:`PAC <mx-requirements>` of your choice before you start creating invoices from Odoo."
msgid "Once you've created your account with any of these providers, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the :guilabel:`MX PAC` section, enter the name of your |PAC| with your credentials (:guilabel:`PAC username` and :guilabel:`PAC password`)."
msgid "If you do not have credentials, but want to test the electronic invoicing, you can activate the :guilabel:`MX PAC test environment` checkbox, and select :guilabel:`Solucion Factible` as the |PAC|. You do not need to add a username or password for a test environment."
msgid "The `digital certificates of the company <https://www.gob.mx/tramites/ficha/certificado-de-sello-digital/SAT139>`_ must be uploaded within the :guilabel:`MX Certificates` section. To do so, navigate to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the :guilabel:`MX Certificates` section, select :guilabel:`Add a line`, and a window will open. Click :guilabel:`Create`, and from there, upload your digital :guilabel:`Certificate` (:file:`.cer` file), your :guilabel:`Certificate Key` (:file:`.key` file), and your :guilabel:`Certificate Password`. To finish, click on :guilabel:`Save & Close`."
msgid "If you still do not have one of the contracted |PAC|\\s and you want to test electronic invoicing, you can use the following |SAT| test certificates:"
msgid "The invoicing process in Odoo is based on `Annex 20 <http://omawww.sat.gob.mx/tramitesyservicios/Paginas/anexo_20.htm>`_ version 4.0 of electronic invoicing of the |SAT|."
msgid "While the document is in draft mode, changes can be made to it (the correct :guilabel:`Payment Way` or :guilabel:`Usage` that the customer might require can be added, for example.)"
msgid "After you :guilabel:`Confirm` the customer invoice, a blue message appears stating: :guilabel:`The invoice will be processed asynchronously by the following E-invoicing service: CFDI (4.0)`."
msgid "Pressing the :guilabel:`Process Now` button sends the document to the government so it can be signed. After receiving the signed document back from the government, the :guilabel:`Fiscal Folio` field appears on the document, and the XML file is attached in the chatter."
msgid "To send the signed invoice to your client by mail, you can send both the XML and PDF files together, directly from Odoo, by clicking the :guilabel:`Send & Print` button. You can also download the PDF file to your computer, by clicking the :guilabel:`Print` button, and selecting the desired print option."
msgid "The only addition to the :doc:`standard flow for credit notes <../accounting/customer_invoices/credit_notes>` is that, as a requirement of the |SAT|, there has to be a relation between a credit note and an invoice through the fiscal folio."
msgid "Because of this requirement, the field :guilabel:`CFDI Origin` adds this relation with a `01|`, followed by the fiscal folio of the original invoice."
msgid "For the :guilabel:`CFDI Origin` field to be automatically added, use the :guilabel:`Add Credit Note` button from the invoice, instead of creating it manually."
msgid "One addition of the Mexican localization is the :guilabel:`Payment Policy` field. According to the SAT documentation, there are two types of payments:"
msgid "To configure |PUE| invoices, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and either select an invoice :guilabel:`Due Date` within the same month, or choose a payment term that does not imply changing the due month (immediate payment, 15 days, 21 days, all falling within the current month)."
msgid "Some :guilabel:`Payment Terms` are already installed by default, and can be managed from :menuselection:`Accounting --> Configuration --> Payment Terms`."
msgid "To configure |PPD| invoices, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and select an invoice with a :guilabel:`Due Date` after the first day of the following month. This also applies if your :guilabel:`Payment Term` is due in the following month."
msgid "Because the |PPD| policy implies that an invoice is not going to get paid at the moment, the correct :guilabel:`Payment Way` for the |PPD| invoices is :guilabel:`99 - Por Definir` (To define)."
msgid "In both cases, the payment process in Odoo :doc:`is the same <../accounting/customer_invoices>`, the main difference being payments related to |PPD| invoices trigger the creation of a document type \"P\" (Pago)."
msgid "If a payment is related to a |PUE| invoice, it can be registered with the wizard, and be associated with the corresponding invoice. To do so, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and select an invoice. Then, click the :guilabel:`Register Payment` button. The invoice status changes to :guilabel:`In Payment`, since the payment is effectively validated when it is bank reconciled."
msgid "While this process is the same for PPD invoices, the addition of the creating an :doc:`electronic document <../accounting/customer_invoices/electronic_invoicing>` means some additional requirements are needed to correctly send the document to the |SAT|."
msgid "From an invoice, you need to confirm the specific :guilabel:`Payment Way` where you received the payment. Because of this, the :guilabel:`Payment Way` field **cannot** be set as `99 - Por Definir (To Define)`."
msgid "If you are going to add a bank account number in the :guilabel:`Accounting` tab of a customer's contact card, it must have a valid account number."
msgid "The exact configurations are in the `Anexo 20 of the SAT <http://omawww.sat.gob.mx/tramitesyservicios/Paginas/anexo_20.htm>`_. Usually, the :guilabel:`Bank Account` needs to be 10 or 18 digits for transfers, 16 for credit or debit cards."
msgid "If a payment is related to a signed invoice with the :guilabel:`Payment Policy` `PPD`, Odoo generates the corresponding payment complement automatically, once you click :guilabel:`Process Now`."
msgid "A payment in MXN **cannot** be used to pay multiple invoices in USD. Instead, the payment should be separated into multiple payments, using the :guilabel:`Register Payment` button on the corresponding invoices."
msgid "It is possible to cancel the EDI documents sent to the |SAT|. According to the `Reforma Fiscal 2022 <https://www.sat.gob.mx/consultas/91447/nuevo-esquema-de-cancelacion>`_, since January 1st, 2022, there are two requirements for this:"
msgid "There are four different cancellation reasons. In Odoo, you can cancel invoices with the reasons *01 Invoices sent with errors with a relation*, and *02 Invoices sent with errors without a relation*."
msgid "Odoo has certain limitations to canceling invoices in the |SAT|: The reasons 03 and 04 (*Operation did not take place* and *Nominative transactions related to a global invoice*, respectively) are not currently supported by Odoo. For this, you need to cancel the invoice directly in the |SAT|, and press :guilabel:`Retry` in the :guilabel:`SAT Status field`."
msgid "Begin by navigating to :menuselection:`Accounting --> Customers --> Invoices`, and select the old invoice. Copy the :guilabel:`Fiscal Folio` from the old invoice. Then, navigate to the new invoice, and in the :guilabel:`CFDI Origin` field, add the value `04|` and paste the :guilabel:`Fiscal Folio` of the old invoice after the value. Finally, sign the new document."
msgid "Next, navigate back to the old invoice, and notice the :guilabel:`Substituted By` field is now available. Click the :guilabel:`Request EDI Cancellation` button on the old invoice, and then click :guilabel:`Process Now` in the blue section that appears. The invoice status changes to :guilabel:`Canceled`, and a confirmation is logged in the chatter."
msgid "Now, the invoice should be canceled in the |SAT| as well. You can confirm this was done correctly, by pressing :guilabel:`Retry` in the |SAT| status field."
msgid "If the document was canceled more than 24 hours after its creation, you may need to ask the client to accept the cancellation in their “Buzón Tributario” directly from the `SAT website <https://www.sat.gob.mx/home>`_."
msgid "For this case, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and select the old invoice. From here, the only requirement is to click the :guilabel:`Request EDI Cancellation` button, and then click the :guilabel:`Process Now` button."
msgid "Because the field :guilabel:`Substituted By` does not appear when using this cancellation reason, the |SAT| should automatically detect that the cancellation reason is 02."
msgid "It is also possible to cancel *Payment Complements*. For this, go to the payment, via :menuselection:`Accounting --> Customers --> Payments`, and select :guilabel:`Request EDI Cancellation`. As with invoices, a blue button will appear. Click :guilabel:`Process now`, and the document will be sent to the |SAT|. After a few seconds, you can click :guilabel:`Retry` to confirm the current |SAT| status."
msgid "Just like invoices, when you create a new *Payment Complement*, you can add the relation of the original document, by adding a `04|` plus the fiscal folio in the :guilabel:`CFDI Origin` field."
msgid "If you use the :guilabel:`Customer` name `PUBLICO EN GENERAL`, an error will be triggered. This is a main change in the CFDI 4.0 that requires invoices with that specific name to need additional fields, which Odoo does not currently support. So, for a *CFDI to Public* to be created, you need to add any name to your customer that is **not** `PUBLICO EN GENERAL`. (For example: `CLIENTE FINAL`)."
msgid "In addition to this, it is required that the :guilabel:`ZIP` code of your company is added, the generic |RFC| is set as `XAXX010101000`, and the :guilabel:`Fiscal Regime` of your customer must be set as: `Sin obligaciones fiscales`."
msgid "The main currency in Mexico is MXN. While this is mandatory for all Mexican companies, it is possible to send and receive invoices (and payments) in different currencies. To enable the use of :doc:`multicurrency <../accounting/get_started/multi_currency>`, navigate to the :menuselection:`Accounting --> Settings --> Currencies`, and set :guilabel:`Mexican Bank` as the :guilabel:`Service` in the :guilabel:`Automatic Currency Rates` section. Then, set the :guilabel:`Interval` field to the frequency you wish to update the exchange rates."
msgid "There can be cases where you receive a payment in advance from a customer that needs to be applied to an invoice later. In order to do this in Odoo, it is required to properly link invoices to each other with the :guilabel:`CFDI Origin` field. To do so, it is necessary to have the :doc:`Sales <../../sales>` app installed."
msgid "`The official documentation for registration of down payments in Mexico <http://omawww.sat.gob.mx/tramitesyservicios/Paginas/documentos/Caso_uso_Anticipo.pdf>`_."
msgid "First, navigate to the :menuselection:`Sales` app to create a product `Anticipo` and configure it. The :guilabel:`Product Type` must be :guilabel:`Service`, and use the :guilabel:`UNSPSC Category` must be: `84111506 Servicios de facturación`."
msgid "Create a sales order with the total amount, and create a down payment (either using a percentage or fixed amount). Then, sign the document, and :guilabel:`Register the Payment`."
msgid "When the time comes for the customer to get the final invoice, create it again from the same sales order. In the :guilabel:`Create Invoices` wizard, select :guilabel:`Regular Invoice`, and uncheck :guilabel:`Deduct down payments`."
msgid "Then, copy the :guilabel:`Fiscal Folio` from the first invoice, and paste it into the :guilabel:`CDFI Origin` of the second invoice, adding the prefix `07|` before the value. Then, sign the document."
msgid "After this, create a credit note for the first invoice. Copy the :guilabel:`Fiscal Folio` from the second invoice, and paste it in the :guilabel:`CFDI Origin` of the credit note, adding the prefix `07|`. Then, sign the document."
msgid "With this, all electronic documents are linked to each other. The final step is to fully pay the new invoice. At the bottom of the new invoice, you can find the credit note in the :guilabel:`Outstanding credits` - add it as payment. Finally, register the remaining amount with the :guilabel:`Register Payment` wizard."
msgid "The external trade is a complement to a regular invoice that adds certain values in both the XML and PDF, to invoices with a foreign customer according to `SAT regulations <http://omawww.sat.gob.mx/tramitesyservicios/Paginas/complemento_comercio_exterior.htm>`_, such as:"
msgid "Since January 1, 2018, external trade is a requirement for taxpayers, who carry export operations of type A1. While the current CFDI is 4.0, the external trade is currently on version 1.1"
msgid "To configure your company contact for external trade, navigate to :menuselection:`Accounting --> Customers --> Customers`, and select your :guilabel:`Company`. While the CFDI 4.0 requirements ask you to add a valid :guilabel:`ZIP` code in your contact, the external trade complement adds the requirement that your :guilabel:`City` and the :guilabel:`State` must also be valid. All three fields must coincide with the `Official SAT Catalog <sat-catalog_>`_, or you will receive an error."
msgid "Add the :guilabel:`City` and :guilabel:`State` in the company's *contact*, not in the company itself. You can find your company's contact in :menuselection:`Accounting --> Customers --> Customers`."
msgid "The fields :guilabel:`Locality` and :guilabel:`Colony Code` are optional and can be added in the company directly in :menuselection:`Settings --> General Settings --> Companies`. These two fields have to coincide with the data in the |SAT|."
msgid "To configure the contact data for a foreign receiving client, navigate to :menuselection:`Accounting --> Customers --> Customers`, and select the foreign client's contact. The contact must have the following fields completed to avoid errors:"
msgid "In the :guilabel:`MX EDI` tab, you need to address if the customer receives goods for a period of time temporarily (:guilabel:`Temporary`) or permanently (:guilabel:`Definitive`)."
msgid "If the new contact was created by duplicating another existing contact from Mexico, make sure to delete any carried over information from the :guilabel:`Fiscal Regime` field. In addition, do not enable the :guilabel:`No Tax Breakdown` option. Selecting this option hides mandatory fields that are required for external trade contact configuration."
msgid "The `correct <https://www.ventanillaunica.gob.mx/vucem/Clasificador.html>`_ :guilabel:`Tariff Fraction` of the product in the :guilabel:`Accounting` tab."
msgid "Before creating an invoice, it is important to take into account that external trade invoices require to convert the amounts of your product into USD. Therefore, :doc:`multicurrency <../accounting/get_started/multi_currency>` **must** be enabled and *USD* **must** be activated in the :guilabel:`Currencies` section. The correct :guilabel:`Service` to run is :guilabel:`Mexican Bank`."
msgid "Then, with the correct exchange rate set up in :menuselection:`Accounting --> Settings --> Currency`, the only fields left are :guilabel:`Incoterm` and the optional :guilabel:`Certificate Source` in the :guilabel:`Other Info` tab."
msgid "A `Carta Porte <https://www.sat.gob.mx/consultas/68823/complemento-carta-porte->`_ is a bill of lading: a document that states the type, quantity, and destination of goods being carried."
msgid "On December 1st, 2021, version 2.0 of this CFDI was implemented for all transportation providers, intermediaries, and owners of goods. Odoo is able to generate a document type \"T\" (Traslado), which, unlike other documents, is created in a delivery order instead of an invoice or payment."
msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended`, :guilabel:`l10n_mx_edi_extended_40`, :guilabel:`l10n_mx_edi_stock` and :guilabel:`l10n_mx_edi_stock_40` have to be installed."
msgid "In addition to this, it is necessary to have the :doc:`Inventory <../../inventory_and_mrp/inventory>` and :doc:`Sales <../../sales/sales>` apps installed, as well."
msgid "Odoo does not support Carta Porte type document type \"I\" (Ingreso), air, or marine transport. Consult your accountant first if this feature is needed before doing any modifications."
msgid "**No Federal Highways**: Is used when the *Distance to Destination* is `less than 30 KM <http://omawww.sat.gob.mx/cartaporte/Paginas/documentos/PreguntasFrecuentes_Autotransporte.pdf>`_."
msgid "Other than the standard requirements of regular invoicing (The |RFC| of the customer, the UNSPSC code, etc.), if you are using *No Federal Highways*, no external configuration is needed."
msgid "For *Federal Transport*, several configurations have to be added to contacts, vehicle setups, and products. Those configurations are added to the XML and PDF files."
msgid "Like the external trade feature, the :guilabel:`Address` in both the company and the final customer must be complete. The :guilabel:`ZIP` code, :guilabel:`City`, and :guilabel:`State` must coincide with the `Official SAT Catalog for Carta Porte <sat-catalog_>_`."
msgid "The origin address used for the delivery guide is set in :menuselection:`Inventory --> Configuration --> Warehouses Management --> Warehouses`. While this is set as the company address by default, you can change it according to your correct warehouse address."
msgid "Another addition to this feature is the :guilabel:`Vehicle Setups` menu found in :menuselection:`Inventory --> Settings --> Mexico`. This menu lets you add all the information related to the vehicle used for the delivery order."
msgid "In the :guilabel:`Intermediaries` section, you must add the operator of the vehicle. The only mandatory fields for this contact are the :guilabel:`VAT` and :guilabel:`Operator Licence`."
msgid "Similar to regular invoicing, all products must have a :guilabel:`UNSPSC category`. In addition to this, there are two extra configurations for products involved in delivery guides:"
msgid "Creating a delivery guide of a product with the value `0` will trigger an error. As the :guilabel:`Weight` has been already stored in the delivery order, it is needed to return the products, and create the delivery order (and delivery guide) again with the correct amounts."
msgid "To create a delivery guide, first, you need to create and confirm a sales order from :menuselection:`Sales --> Sales Order`. This generates a :guilabel:`Delivery` smart button. Click it, and :guilabel:`Validate` the transfer."
msgid "After the status is set to :guilabel:`Done`, you can edit the transfer, and select the :guilabel:`Transport Type` (either :guilabel:`No Federal Highways` or :guilabel:`Federal Transport`)."
msgid "If your delivery guide has the type :guilabel:`No Federal Highways`, you can save the transfer, and then click :guilabel:`Generate Delivery Guide`. The resulting XML can be found in the chatter."
msgid "Other than the :guilabel:`UNSPSC` in all products, delivery guides that use :guilabel:`No Federal Highways` do not require any special configuration to be sent to the government."
msgid "If your delivery guide has the type, :guilabel:`Federal Transport`, the tab :guilabel:`MX EDI` appears. There, enter a value in :guilabel:`Distance to Destination (KM)` bigger than `0`, and select the :guilabel:`Vehicle Setup` used for this delivery."
msgid "Certain values in the :guilabel:`UNSPSC Category` are considered in the `official SAT catalog <http://omawww.sat.gob.mx/tramitesyservicios/Paginas/complemento_carta_porte.htm>`_ as *dangerous hazards*. These categories need additional considerations when creating a delivery guide with :guilabel:`Federal Transport`."
msgid "First, select your product from :menuselection:`Inventory --> Products --> Products`. Then, in the :guilabel:`Accounting` tab, the fields :guilabel:`Hazardous Material Designation Code (MX)` and :guilabel:`Hazardous Packaging (MX)` must be filled with the correct code from the |SAT| catalog."
msgid "In :menuselection:`Inventory --> Settings --> Mexico --> Vehicle Setup`, the data from the :guilabel:`Environment Insurer` and :guilabel:`Environment Insurance Policy` has to be filed, as well. After this, continue with the regular process to create a delivery guide."
msgid "A *customs declaration* (Pedimento Aduanero) is a fiscal document that certifies that all contributions to the fiscal entity (the |SAT|) has been paid for, including the import/export of goods."
msgid "According to the `Annex 20 <http://omawww.sat.gob.mx/tramitesyservicios/Paginas/anexo_20.htm>`_ of CFDI 4.0, in documents where the invoiced goods come from a first-hand import operation, the field, :guilabel:`Customs Number`, needs to be added to all lines of products involved with the operation."
msgid "To do so, the module :guilabel:`l10n_mx_edi_landing` must be installed, in addition to the :doc:`Inventory <../../inventory_and_mrp/inventory>`, :doc:`Purchase <../../inventory_and_mrp/purchase>` and :doc:`Sales <../../sales/sales>` apps."
msgid "Do not confuse this feature with external trade. The customs numbers are directly related to importing goods, while the external trade complement is related to exporting. Consult your accountant first if this feature is needed before doing any modifications."
msgid "In order to track the correct customs number for a specific invoice, Odoo uses :doc:`landed costs <../../inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs>`. Go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation`. Make sure that :guilabel:`Landed Costs` is activated."
msgid "Begin by creating a *service*-type product called, `Pedimento`. In the :guilabel:`Purchase` tab, activate :guilabel:`Is a Landed Cost`, and select a :guilabel:`Default Split Method`."
msgid "Then, configure the *storable products* that hold the customs numbers. To do so, create the storable products, and make sure the :guilabel:`Product Category` has the following configuration."
msgid "Create a purchase order from :menuselection:`Purchase --> Orders --> Purchase Order`. Then, confirm the order to display a :guilabel:`Receipt` smart button. Click on the :guilabel:`Receipt` smart button to :guilabel:`Validate` the receipt."
msgid "Go to :menuselection:`Inventory --> Operations --> Landed Costs`, and create a new record. Add the transfer that you just created, and both: the product `Pedimento` and :guilabel:`Customs number`."
msgid "Optionally, you can add a cost amount. After this, validate the landed cost. Once :guilabel:`Posted`, all products related to that receipt have the customs number assigned."
msgid "Finally, create an invoice from the sales order, and confirm it. The invoice line related to your product has a customs number in it. This number should match the customs number added in the *Landed Costs* record you created earlier."
msgid "For Mexico, `Electronic Accounting <https://www.sat.gob.mx/aplicacion/42150/envia-tu-contabilidad-electronica>`_ refers to the obligation to keep accounting records and entries through electronic means, and to enter accounting information on a monthly basis, through the |SAT| website."
msgid "The resulting XML files follow the requirements of the `Anexo Técnico de Contabilidad Electrónica 1.3 <https://www.gob.mx/cms/uploads/attachment/file/151135/Anexo24_05012015.pdf>`_."
msgid "In addition to this, you can generate the `DIOT <https://www.sat.gob.mx/declaracion/74295/presenta-tu-declaracion-informativa-de-operaciones-con- terceros-(diot)->`_: A report of vendor's journal entries that involve IVA taxes that can be exported in a :file:`.txt` file."
msgid "In order to use these reports, the modules :guilabel:`l10n_mx_reports`, :guilabel:`l10n_mx_reports_closing`, :guilabel:`l10n_mx_xml_polizas` and :guilabel:`l10n_mx_xml_polizas_edi` have to be installed, as well as the :doc:`Accounting <../accounting/get_started>`."
msgid "The specific characteristics and obligations of the reports that you send might change according to your fiscal regime. Always contact your accountant before sending any documents to the government."
msgid "The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` in México follows a specific pattern based on |SAT|'s' `Código agrupador de cuentas <http://omawww.sat.gob.mx/fichas_tematicas/buzon_tributario/Documents/codigo_agrupador.pdf>`_."
msgid "When a new account is created in :menuselection:`Accounting --> Configuration --> Chart of Accounts`, with the |SAT| encoding group pattern, the correct grouping code appears in :guilabel:`Tags`, and your account appears in the *COA* report."
msgid "You cannot use any pattern that ends a section with a 0 (such as `100.01.01`, `301.00.003` or `604.77.00`). This triggers errors in the report."
msgid "Once everything is set up, you can go to :menuselection:`Accounting --> Reporting --> Mexico --> COA`, and click the :guilabel:`SAT (XML)` button to generate an XML file containing all of your accounts, which will be ready to upload to the |SAT| website."
msgid "The trial balance reports the initial balance, credit, and total balance of your accounts, provided that you added their correct :ref:`encoding group <l10n_mx/chart-of-accounts>`."
msgid "This report can be generated monthly, and a corresponding XML file is created, if you go to :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance`, and click the :guilabel:`SAT (XML)` button. Select the month you want to download beforehand."
msgid "An additional report is the *Month 13*: a closing balance sheet that shows any adjustments or movements made in the accounting to close the year."
msgid "To generate this XML document, navigate to :menuselection:`Accounting --> Accounting --> Miscellaneous --> Journal Entries`, and create a new document. Here, add all amounts to modify, and balance the debit and/or credit of each one."
msgid "After this is done, click :guilabel:`Mark as Closing Entry`, and the report found in :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance Month 13`, contains the total amount of the year, plus all the additions of the journal entry."
msgid "By law, all transactions in Mexico must be recorded digitally. Since Odoo automatically creates all the underlying journal entries of your invoicing and payments, you can export your journal entries to comply with |SAT|'s audits and/or tax refunds."
msgid "To create the XML, go to :menuselection:`Accounting --> Reporting --> Audit Reports --> General Ledger`, and click :guilabel:`XML (Polizas)`. Here, you can select between four types of :guilabel:`Export` types:"
msgid "For :guilabel:`Tax audit`, or :guilabel:`Audit certification`, you need to write the :guilabel:`Order Number` provided by the |SAT|. For :guilabel:`Return of goods`, or :guilabel:`Compensation`, you need to write your :guilabel:`Process Number`, also provided by the |SAT|."
msgid "If you want to see this report without sending it, use `ABC6987654/99` for :guilabel:`Order Number` and `AB123451234512` for :guilabel:`Process Number`."
msgid "The DIOT (Declaración Informativa de Operaciones con Terceros / *Informative Declaration of Operations with Third Parties*) is an additional obligation with the |SAT|, where the current status of creditable and non-creditable payments, withholdings, and refunds of VAT from your vendor bills, are provided to the |SAT|."
msgid "Unlike other reports, the |DIOT| is uploaded to a software provided by the |SAT| that contains the A-29 form. In Odoo, you can download the records of your transactions as a :file:`.txt` file that can be uploaded to the form, avoiding direct capture of this data."
msgid "The transactions file contains the total amount of your payments registered in vendor bills, broken down into the corresponding types of IVA. The :guilabel:`VAT` and :guilabel:`Country` is mandatory for all vendors."
msgid "To get the |DIOT| report, go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third parties [DIOT]`. Select the month that suits you, and click :guilabel:`DIOT (TXT)` to download the :file:`.txt` file."
msgid "You need to fill the field, :guilabel:`L10N Mx Type of Operation`, in the :guilabel:`Accounting` tab of each one of your vendors to prevent validation errors. Make sure that your foreign customers have their country set up for :guilabel:`L10N Mx Nationality` to appear automatically."
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)**."
msgid "**l10n_pe**: Adds accounting features for the Peruvian localization, which represent the minimal configuration required for a company to operate in Peru and under the SUNAT regulations and guidelines. The main elements included in this module are: Chart of account, taxes, document types."
msgid "**l10n_pe_edi**: includes all technical and functional requirements to generate and validate Electronic Invoice, based on the SUNAT specification to create and process valid electronic documents, for more technical detail you can access the `SUNAT EDI specifications <https://cpe.sunat.gob.pe/node/88/>`_, that keeps track of new changes and updates. The features of this module are based on the resolutions published on the `SUNAT Legislation <https://www.sunat.gob.pe/legislacion/general/index.html/>`_."
msgid "Go to *Apps* and search for Peru, then click Install in the module Peru EDI. This module has a dependency with *Peru - Accounting*. In case this last one is not installed, Odoo installs it automatically within EDI."
msgid "In addition to the basic information in the Company, we need to set Peru as the Country, this is essential for the Electronic Invoice to work properly. The field **Address Type Code** represents the establishment code assigned by the SUNAT when companies register their RUC (Unique Contributor Registration):"
msgid "In case the Address type code is unknown, you can set it as the default value: 0000. Be aware that if an incorrect value is entered, the Electronic invoice validation might have errors."
msgid "The chart of accounts is installed by default as part of the set of data included in the localization module, the accounts are mapped automatically in:"
msgid "The chart of accounts for Peru is based on the most updated version of the :abbr:`PCGE (Plan Contable General Empresarial)`, which is grouped in several categories and is compatible with NIIF accounting."
msgid "Once the modules are installed and the basic information of your company is set, you need to configure the elements required for Electronic Invoice. For this, go to :menuselection:`Accounting --> Settings --> Peruvian Localization`."
msgid "As part of the requirements for Electronic Invoice in Peru, your company needs to select a Signature Provider that will take care of the document signing process and manage the SUNAT validation response. Odoo offers three options:"
msgid "The service requires Credits in order to process your electronic documents. Odoo provides 1000 credits for free in new databases. After these credits are consumed, you need to buy a Credit Package."
msgid "If you have a validation error and the document needs to be sent one more time, one additional credit will be charged. Therefore, it is paramount that you verify all information is correct before sending your document to the OSE."
msgid "In Odoo, once your enterprise contract is activated and you start working in Production, you need to buy credits once the first 1000 are consumed."
msgid "As Digiflow is the OSE used in the IAP, you need to affiliate it as the official OSE for your company on the SUNAT website. This is a simple process. For more information, please check `OSE Affiliation guide <https://drive.google.com/file/d/1BkrMTZIiJyi5XI0lGMi3rbMzHddOL1pa/view?usp=sharing>`_."
msgid "This option can be used as an alternative, instead of using the IAP services you can send your document validation directly to Digiflow. In this case you need to consider:"
msgid "Buy your own digital Certificate: For more detail regarding the official vendor list, and the process to acquire it, please refer to `SUNAT Digital Ceritifcates <https://cpe.sunat.gob.pe/informacion_general/certificados_digitales/>`_."
msgid "In case your company wants to sign directly with the SUNAT, it is possible to select this option in your configuration. In this case you need to consider: - Get the SUNAT Certification process accepted."
msgid "When using the testing environment and the IAP signature, you don’t need to buy testing credits for your transactions as all of them are validated by default."
msgid "In case you don’t use Odoo IAP, in order to generate the electronic invoice signature, a digital certificate with the extension ``.pfx`` is required. Proceed to this section and load your file and password."
msgid "The official currency exchange rate in Peru is provided by the Bank of Peru. Odoo can connect directly to its services and get the currency rate either automatically or manually."
msgid "Please refer to the next section in our documentation for more information about :doc:`multicurrencies <../accounting/get_started/multi_currency>`."
msgid "As part of the localization module the taxes are created automatically with their related financial account and electronic invoice configuration."
msgid "As part of the taxes configuration, there are three new fields required for electronic invoice, the taxes created by default have this data included, but in case you create new taxes make sure you fill in the fields:"
msgid "In some Latin American countries, including Peru, some accounting transactions like invoices and vendor bills are classified by document types, defined by the government fiscal authorities, in this case by the SUNAT."
msgid "Each document type can have a unique sequence per journal where it is assigned. As part of the localization, the Document Type includes the country on which the document is applicable;the data is created automatically when the localization module is installed."
msgid "This field is used to define if the journal uses Document Types. It is only applicable to Purchase and Sales journals, which are the ones that can be related to the different set of document types available in Peru. By default, all the sales journals created use documents."
msgid "As part of the Peruvian localization, the identification types defined by the SUNAT are now available on the Partner form, this information is essential for most transactions either on the sender company and in the customer, make sure you fill in this information in your records."
msgid "Additional to the basic information in your products, for the Peruvian localization, the UNSPC Code on the product is a required value to be configured."
msgid "Once you have configured your master data, the invoices can be created from your sales order or manually. Additional to the basic invoice information described on :doc:`our page about the invoicing process <../accounting/customer_invoices/overview>`, there are a couple of fields required as part of the Peru EDI:"
msgid "**Document type**: The default value is “Factura Electronica” but you can manually change the document type if needed and select Boleta for example."
msgid "**Operation type**: This value is required for Electronic Invoice and indicates the transaction type, the default value is “Internal Sale” but another value can be selected manually when needed, for example Export of Goods."
msgid "**EDI Affectation Reason**: In the invoice lines, additional to the Tax there is a field “EDI Affectation Reason” that determines the tax scope based on the SUNAT list that is displayed. All the taxes loaded by default are associated with a default EDI affection reason, if needed you can manually select another one when creating the invoice."
msgid "Once you check all the information in your invoice is correct, you can proceed to validate it. This action registers the account move and triggers the Electronic invoice workflow to send it to the OSE and the SUNAT. The following message is displayed at the top of the invoice:"
msgid "**To be Sent**: Indicates the document is ready to be sent to the OSE, this can be done either automatically by Odoo with a *cron* that runs every hour, or the user can send it immediately by clicking on the button “Sent now”."
msgid "**Sent**: Indicates the document was sent to the OSE and was successfully validated. As part of the validation a ZIP file is downloaded and a message is logged in the chatter indicating the correct Government validation."
msgid "In case there is a validation error the Electronic Invoice status remains in “To be sent” so the corrections can be made and the invoice can be sent again."
msgid "One credit is consumed each time that you send a document for validation, in this sense if an error is detected on an invoice and you send it one more time, two credits are consumed in total."
msgid "There are multiple reasons behind a rejection from the OSE or the SUNAT, when this happens Odoo sends a message at the top of the invoice indicating the error details and in the most common cases a hint to fix the issue."
msgid "In case the error is related to master data on the partner, customer or taxes, you can simply apply the change on the record (example customer identification type) and once it is done click on the Retry button."
msgid "If the error is related to some data recorded on the invoice directly (Operation type, missing data on the invoice lines), the correct solution is to reset the invoice to Draft, apply the changes, and then send the invoice again to the SUNAT for another validation."
msgid "After the invoice is accepted and validated by the SUNAT, the invoice PDF report can be printed. The report includes a QR code, indicating the invoice is a valid fiscal document."
msgid "Odoo’s Electronic IAP offers 1000 credits for free, after these credits are consumed in your production database, your company must buy new credits in order to process your transactions."
msgid "Once you run out of credits a red label is displayed at the top of the invoice indicating that additional credits are required, you can easily buy them by accessing the link provided in the message."
msgid "In the IAP service includes packages with different pricing based on the number of credits. The price list in the IAP is always displayed in EUR."
msgid "Some scenarios require an invoice cancellation, for example, when an invoice was created by mistake. If the invoice was already sent and validated by the SUNAT, the correct way to proceed is by clicking on the button Request Cancellation:"
msgid "**To Cancel**: Indicates the cancellation request is ready to be sent to the OSE, this can be done either automatically by Odoo with a *cron* that runs every hour, or the user can send it immediately by clicking on the button “Send now”. Once it is sent, a cancellation ticket is created, as a result the next message and CDR File are logged in the chatter:"
msgid "**Cancelled**: Indicates the cancellation request was sent to the OSE and was successfully validated. As part of the validation a ZIP file is downloaded and a message is logged in the chatter indicating the correct Government validation."
msgid "When a correction or refund is needed over a validated invoice, a credit note must be generated, for this just click on the button “Add Credit Note”, a part of the Peruvian localization you need to prove a Credit Reason selecting one of the options in the list."
msgid "As part of the Peruvian localization, besides creating credit notes from an existing document you can also create debit Notes. For this just use the button “Add Debit Note”."
msgid "The *Guía de Remisión Electrónica* (GRE) is an electronic document generated by the shipper to support the transportation or transfer of goods from one place to another, such as a warehouse or establishment. In Odoo, there are several configuration steps needed before you can successfully use this feature."
msgid "The use of the *guía de remisión electrónica* electronic document is mandatory and required by |SUNAT| for taxpayers who need to transfer their products, except those under the *Single Simplified Regime* (régimen único simplificado or RUS)."
msgid "The *Sender* delivery guide type is issued when a sale is made, a service is rendered (including processing), goods are assigned for use, or goods are transferred between premises of the same company and others."
msgid "This delivery guide is issued by the owner of the goods (i.e., the sender) at the beginning of the shipment. The sender delivery guide is supported in Odoo."
msgid "The *Private* transportation type option is used when the owner transfers goods using their own vehicles. In this case, a sender's delivery guide must be issued."
msgid "The *Public* transportation type option is used when an external carrier moves the goods. In this case, two delivery guides must be issued: the sender's delivery guide and the carrier's delivery guide."
msgid "The creation of the |GRE| delivery guide in Odoo **must** be sent directly to the |SUNAT|, regardless of the electronic document provider: IAP, Digiflow, or |SUNAT|."
msgid "Version 2.0 of the electronic delivery guide requires additional information on the general configuration, vehicles, contacts, and products. In the general configuration, it is necessary to add new credentials that you can retrieve from the |SUNAT| portal."
msgid "The |SUNAT| does not support a test environment. This means that any delivery guides that were generated by mistake **will** be sent to the |SUNAT|."
msgid "After following the steps to configure the :ref:`electronic invoicing <peru/accounting-settings>` and the :ref:`master data <peru/master_data>`, :ref:`install <general/install>` the :guilabel:`Peruvian - Electronic Delivery Note 2.0` module (`l10n_pe_edi_stock_20`)."
msgid "Next, you need to retrieve the *client ID* and *client secret* from |SUNAT|. To do so, follow the `manual de servicios web plataforma nueva GRE <https://cpe.sunat.gob.pe/sites/default/files/inline-files/Manual_Servicios_GRE.pdf>`_."
msgid "In the |SUNAT| portal, it is important to have the correct access rights enabled, as they may differ from the user set for electronic invoicing."
msgid "These credentials should be used to configure the delivery guide general settings from :menuselection:`Accounting --> Configuration --> Settings --> Peruvian Electronic Invoicing`."
msgid "It is required to follow the format `RUC + UsuarioSol` (e.g., `20557912879SOLUSER`) for the :guilabel:`Guide SOL User` field, depending on the user selected when generating the |GRE| API credentials in the |SUNAT| portal."
msgid "First, select :guilabel:`Individual` as the :guilabel:`Company Type`. Then, add the :guilabel:`Operator License` in the :guilabel:`Accounting` tab of the contact form."
msgid "First, select :guilabel:`Company` as the :guilabel:`Company Type`. Then, add the :guilabel:`MTC Registration Number`, :guilabel:`Authorization Issuing Entity`, and the :guilabel:`Authorization Number`."
msgid "To configure the available vehicles, navigate to :menuselection:`Inventory --> Configuration --> Vehicles` and fill in the vehicle form with the information needed for the vehicle:"
msgid "Make sure that the applicable information in the product form is fully configured. The :guilabel:`Partida Arancelaria` (Tariff Item) field needs to be completed."
msgid "Once the delivery from inventory is created during the sales workflow, make sure you complete the |GRE| fields on the top-right section of the transfer form for the fields:"
msgid "The delivery transfer has to be marked as *Done* for the :guilabel:`Generar Guia de Remision` button to appear on the left menu of the transfer form."
msgid "Once the transfer form is correctly validated by |SUNAT|, the generated XML file becomes available in the chatter. You can now print the delivery slip that shows the transfer details and the QR code validated by |SUNAT|."
msgid "At the moment, Odoo does not support the automation of prefixes for products. This can be done manually for each product output. This can also be done for non-storable products. However, keep in mind that there will be no traceability."
msgid "This error occurs when the weight on the product is set as `0.00`. To fix this, you need to cancel the waybill and recreate it. Make sure that you fix the weight on the product before creating the new waybill, or it will result in the same error."
msgid "This error is typically generated due to SOL user issues. Verify the user's connection with the |SUNAT|; the SOL user must be established with the company RUT + user ID. For example `2012188549JOHNSMITH`."
msgid "This error is not solvable from Odoo; it is advised you reach out to the |SUNAT| and verify the user. It may be necessary to create a new user."
msgid "This error occurs when the transfer reason is set as *other*. Please select another option. Following to the official documentation of the |SUNAT|'s waybill guide, the transfer reasons *03 (sale with shipment to third party)* or *12 (others)* does not work in Odoo, since you should not have an empty or blank customer."
msgid "For live clients using IAP, no credit is consumed (in theory) because it does not go through the OSE, i.e., these documents are directly sent to the |SUNAT|."
msgid "Odoo currently throws an error with a traceback instead of a message that the credentials are not correctly configured in the database. If this occurs on your database, please verify your credentials."
msgid ":ref:`Install <general/install>` the :guilabel:`🇵🇭 Philippines` :ref:`fiscal localization package <fiscal_localizations/packages>` to get all the default accounting features of the Philippine localization, such as a chart of accounts, taxes, and the BIR 2307 report. These provide a base template to get started with using Philippine accounting."
msgid "When creating a new database and selecting the `Philippines` as a country, the fiscal localization module **Philippines - Accounting** is automatically installed."
msgid "If the module is installed in an existing company, the **chart of accounts** and **taxes** will *not* be replaced if there are already posted journal entries."
msgid "A minimum configuration default chart of accounts is installed, and the following types of taxes are installed and linked to the relevant account:"
msgid "For the withholding taxes (:menuselection:`Configuration --> Taxes`), there is an additional :guilabel:`Philippines ATC` field under the :guilabel:`Philippines` tab."
msgid "When a company or an individual (not belonging to a company) contact is located in the Philippines, fill in the :guilabel:`Tax ID` field with their `Taxpayer Identification Number (TIN)`."
msgid "For both :guilabel:`Company` and :guilabel:`Individual`, the TIN should follow the `NNN-NNN-NNN-NNNNN` format. The branch code should follow the last digits of the TIN, or else it can be left as `00000`."
msgid "**BIR 2307** report data, also known as `Certificate of Creditable Tax Withheld at Source <https://www.bir.gov.ph/index.php/bir-forms/certificates.html>`_, can be generated for purchase orders and vendor payments with the applicable withholding taxes."
msgid "To generate a BIR 2307 report, select one or multiple vendor bills from the list view, and click :menuselection:`Action --> Download BIR 2307 XLS`."
msgid "The process above can also be used for a *single* vendor :doc:`payment <../accounting/payments>` if it is linked to one or more :doc:`vendor bills <../accounting/payments>` with applied withholding taxes."
msgid "When grouping payments for multiple bills, Odoo splits the payments based on the contact. From a payment, clicking :menuselection:`Action --> Download BIR 2307 XLS` generates a report that only includes vendor bills related to that contact."
msgid "Odoo cannot generate the BIR 2307 PDF report or DAT files directly. The generated :file:`Form_2307.xls` file can be exported to an *external* tool to convert it to BIR DAT or PDF format."
msgid "Starting January 1, 2023, companies registered for tax purposes in Romania must report their accounting data to the Romanian Tax Agency monthly or quarterly in the D.406 declaration."
msgid "Odoo provides all you need to export the data of this declaration in the SAF-T XML format, which you can validate and sign using the software provided by the Romanian Tax Agency."
msgid "Currently, Odoo only supports the generation of the monthly/quarterly D.406 declaration (containing journal entries, invoices, vendor bills, and payments). The yearly declaration (including assets) and the on-demand declaration (including inventory) are not yet supported."
msgid "Under :guilabel:`Settings --> General Settings`, in the **Companies** section, click :guilabel:`Update Info` and fill in the company's :guilabel:`Country`, :guilabel:`City`, and :guilabel:`Telephone Number`."
msgid "Provide your company's :abbr:`CUI (Codul Unic de Inregistrare)` number or :abbr:`CIF (*Codul de identificare fiscală*)` number (for foreign companies) in the :guilabel:`Company ID` field, without the `RO` prefix (e.g., `18547290`)."
msgid "If your company is **registered** for VAT in Romania, fill in the :guilabel:`Tax ID` field number, including the `RO` prefix (e.g., `RO18547290`). If the company is **not** registered for VAT in Romania, you **must not** fill in the :guilabel:`Tax ID` field."
msgid "Open the **Contacts** app and search for your company. Open your company's profile, and in the :guilabel:`Accounting` tab, click :guilabel:`Add a line` and add your **bank account number** if not informed already. Make sure the profile is set as :guilabel:`Company` above the **name**."
msgid "You must have at least one **contact person** linked to your company in the **Contacts** app. If no **contact person** is linked, create a new one by clicking :guilabel:`New`, set it as :guilabel:`Individual`, and select your company in the :guilabel:`Company name` field."
msgid "the chart of accounts for commercial companies (*PlanConturiBalSocCom*), which is installed by default when creating a company with the Romanian localization or;"
msgid "Under :guilabel:`Settings --> Accounting`, in the **Romanian localization** section, set the :guilabel:`Tax Accounting Basis` to reflect the accounting regulations and Chart of Accounts used by the company."
msgid "Fill in the :guilabel:`Country`, :guilabel:`City`, and :guilabel:`Zip Code` of each partner that appears in your invoices, vendor bills, or payments through the **Contacts** app."
msgid "For partners that are companies, you must fill in the VAT number (including the country prefix) in the :guilabel:`Tax ID` field. If the partner is a company based in Romania, you may instead fill in the CUI number (without the 'RO' prefix) in the :guilabel:`Company ID` field."
msgid "You must indicate the :guilabel:`Romanian SAF-T Tax Type` (3-digit number) and :guilabel:`Romanian SAF-T Tax Code` (6-digit number) on each of the taxes you use. This is already done for the taxes that exist by default in Odoo. To do so, go to :menuselection:`Accounting --> Configuration --> Taxes`, select the tax you wish to modify, click the :guilabel:`Advanced Options` tab, and fill in the **tax type** and **tax code** fields."
msgid "The **tax type** and **tax code** are codes defined by the Romanian Tax Agency for the **D.406 declaration**. These can be found in the Excel spreadsheet published as guidance for completing the declaration, which you can find on the `website of the Romanian Tax Agency <https://www.anaf.ro/anaf/internet/ANAF/despre_anaf/strategii_anaf/proiecte_digitalizare/saf_t/>`_."
msgid "For some types of goods transactions, the :guilabel:`Intrastat Code` (Cod NC) must be configured on the product, as it is required by Romanian law:"
msgid "To configure the :guilabel:`Intrastat Codes`, go to :menuselection:`Accounting --> Customers --> Products`, select a product, and in the :guilabel:`Accounting` tab, set a :guilabel:`Commodity Code`."
msgid "You must check the :guilabel:`Is self-invoice (RO)?` checkbox in the :guilabel:`Other Info` tab for any vendor bill that is a self-invoice (i.e. a vendor bill that you issued yourself in the absence of an invoice document received from a supplier)."
msgid "Download and install the *DUKIntegrator* validation software found on the `website of the Romanian Tax Agency <https://www.anaf.ro/anaf/internet/ANAF/despre_anaf/strategii_anaf/proiecte_digitalizare/saf_t/>`_."
msgid "Click on :guilabel:`Validare + creare PDF` to create an **unsigned** PDF containing your report, or :guilabel:`Validare + creare PDF semnat` to create a **signed** PDF containing your report."
msgid "If the *DUKIntegrator* validator detects errors or inconsistencies in your data, it generates a file that explains the errors. In this case, you need to correct those inconsistencies in your data before you can submit the report to the Romanian Tax Agency."
msgid "Go to :menuselection:`Settings --> General Settings --> Companies`, click :guilabel:`Update info`, and ensure the following company information is complete and up-to-date."
msgid "It is strongly recommended to thoroughly test all invoicing workflows using the Fatoora **simulation** portal first, as **any** invoice submitted to the regular Fatoora portal will be accounted for, which could lead to fines and penalties."
msgid "Log in on the `Fatoora portal <https://fatoora.zatca.gov.sa/>`_ using the company's ZATCA credentials. Then, click the :guilabel:`Fatoora Simulation Portal` button to switch to the simulation portal."
msgid "On Odoo, go to :menuselection:`Accounting --> Configuration --> Settings`. Under :guilabel:`ZATCA API Integration`, select the :guilabel:`Simulation (Pre-Production)` :guilabel:`API mode` and click :guilabel:`Save`."
msgid "Each sales journal on Odoo needs to be configured. To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open any sales journal (e.g., Customer Invoices), and go to the :guilabel:`ZATCA` tab. Once there, enter any :guilabel:`Serial Number` to identify the journal."
msgid "Next, click :guilabel:`Onboard Journal`. In the dialog box, providing an :abbr:`OTP (one-time password)` code is required. To retrieve it, open the `Fatoora simulation portal <https://fatoora.zatca.gov.sa/>`_, click :guilabel:`Onboard New Solution Unit/Device`, choose the number of OTP codes to generate (one per journal to configure), and click :guilabel:`Generate OTP Code`. Copy an OTP code, it into the dialog box on Odoo, and click :guilabel:`Request`."
msgid "When confirming an invoice, there is now an option to process the invoice, sending it directly the Fatoora simulation portal. Odoo displays the portal's response after each submission. Only rejected invoices can be reset to draft and edited on Odoo. Furthermore, at the end of each day, Odoo sends all unprocessed invoices to the portal."
msgid "When using a **0% tax** in a customer invoice, it is necessary to specify the reason behind such a rate. To configure taxes, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`, and open the tax to edit. Under the :guilabel:`Advanced Options`, select an :guilabel:`Exemption Reason Code` and click :guilabel:`Save`."
msgid "The sales journals initially linked to the simulation portal now needs to be linked to the regular portal. To do so, :ref:`onboard the journals <saudi-arabia/journals>` again, ensuring to use the regular `Fatoora portal <https://fatoora.zatca.gov.sa/>`_ this time."
msgid "To choose the one you want, go to :menuselection:`Accounting --> Configuration --> Settings`, then select a package in the :guilabel:`Fiscal localization` section."
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*."
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."
msgid "There exists two layouts for ISR: one with, and one without the bank coordinates. To choose which one to use, there is an option to print the bank information on the ISR. To activate it, go in :menuselection:`Accounting --> Configuration --> Settings --> Customer Invoices` and enable **Print bank on ISR**:"
msgid "To do so, you need to configure the Journal you usually use to issue invoices. Go to :menuselection:`Accounting --> Configuration --> Journals`, open the Journal you want to modify (By default, the Journal is named *Customer Invoices*), click en *Edit*, and open the *Advanced Settings* tab. In the **Communication Standard** field, select *Switzerland*, and click on *Save*."
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."
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%."
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\"`."
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."
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"
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."
msgid "To generate a sales and purchase tax report, go to :menuselection:`Accounting --> Reporting --> Tax Report`. Select a specific time or time range on the tax report, and click :guilabel:`VAT-202-01 (xlsx)` for purchase tax and :guilabel:`VAT-202-02 (xlsx)` for sales tax."
msgid "PND report data displays the summarized amounts of the applicable **withholding corporate income tax returns (domestic)** from vendor bills under the :guilabel:`PND53 (TH)` and :guilabel:`PND3 (TH)` tax reports. It is installed by default with the Thai localization."
msgid "Withholding corporate income tax returns (domestic) is the tax used in case the company has withheld the tax from “**Personal (PND3)**” or “**Corporate (PND53)**” services provided such as rental, hiring, transportation, insurance, management fee, consulting, etc."
msgid "The PND tax report allows users to generate a CSV file for bills to upload on the `RDprep for Thailand e-Filling application <https://efiling.rd.go.th/rd-cms/>`_."
msgid "To generate a PND CSV file, go to :menuselection:`Accounting --> Reporting --> Tax Report`, select a specific time or time range on the tax report, and click :guilabel:`PND3` or :guilabel:`PND53`."
msgid "This generates the :file:`Tax Report PND3.csv` and :file:`Tax Report PND53.csv` files that lists all the vendor bill lines with the applicable withholding tax."
msgid "Odoo cannot generate the PND or PDF report or **withholding tax certificate** directly. The generated :file:`Tax Report PND3.csv` and :file:`Tax Report PND53.csv` files must be exported to an external tool to convert them into a **withholding PND** report or a **PDF** file."
msgid "The **tax invoice PDF** report can be generated from Odoo through the **Invoicing** module. Users have the option to print PDF reports for normal invoices and tax invoices. To print out **tax invoices**, users can click on :guilabel:`Print Invoices` in Odoo. Regular invoices can be printed as **commercial invoices** by clicking on :menuselection:`Cog button (⚙️) --> Print --> Commercial Invoice`."
msgid "You can inform a company's **Headquarters** and **Branch number** in the **Contacts** app. Once in the app, open the **contact form** of the company and under the :guilabel:`Sales & Purchase` tab:"
msgid "Go to :menuselection:`Accounting --> Configuration --> Chart of Accounts` to view all default accounts available for the UAE localization package. You can filter by :guilabel:`Code` using the numbers on the far left or by clicking on :menuselection:`Group By --> Account Type`. You can :guilabel:`Enable`/:guilabel:`Disable` reconciliation or **configure** specific accounts according to your needs."
msgid "It is also advised to **keep the accounts below active**, as they are used either as transitory accounts by Odoo or are specific to the **UAE localization package**."
msgid "To access your taxes, go to :menuselection:`Accounting --> Configuration --> Taxes`. Activate/deactivate, or :doc:`configure </applications/finance/accounting/taxes/>` the taxes relevant to your business by clicking on them. Remember to only set tax accounts on the **5%** tax group, as other groups do not need closing. To do so, enable the :doc:`developer mode <../../general/developer_mode>` and go to :menuselection:`Configuration --> Tax Groups`. Then, set a :guilabel:`Tax current account (payable)`, :guilabel:`Tax current account (receivable)`, and an :guilabel:`Advance Tax payment account` for the **5%** group."
msgid "To update the currency exchange rates, go to :menuselection:`Accounting --> Configuration --> Settings --> Currencies`. Click on the update button (:guilabel:`🗘`) found next to the :guilabel:`Next Run` field."
msgid "By default, the UAE Central Bank exchange rates web service is used. Several other providers are available under the :guilabel:`Service` field."
msgid "The :guilabel:`UAE - Payroll` module creates the necessary **salary rules** in the Payroll app in compliance with the UAE rules and regulations. The salary rules are linked to the corresponding accounts in the **chart of accounts**."
msgid "To apply these rules to an employee's contract, go to :menuselection:`Payroll --> Contracts --> Contracts` and select the employee's contract. In the :guilabel:`Salary Structure Type` field, select :guilabel:`UAE Employee`."
msgid "**Salary attachments** are generated by going to :menuselection:`Contracts --> Salary Attachments`. Then, :guilabel:`Create` an attachment and select the :guilabel:`Employee` and the :guilabel:`Type (Attachment of Salary, Assignment of Salary, Child Support)`."
msgid "To prevent a rule from appearing on a paycheck, go to :menuselection:`Payroll --> Configuration --> Rules`. Click on :guilabel:`UAE Employee Payroll Structure`, select the rule to hide, and uncheck :guilabel:`Appears on Payslip`."
msgid "The provision is defined as the total monthly allowance *divided* by 30 and then *multiplied* by the number of days set in the field :guilabel:`Number of days` at the bottom of a contract's form."
msgid "The provision is then calculated via a salary rule associated with two accounts: the **End Of Service Indemnity (Expense account)** and the **End of Service Provision (Non-current Liabilities account)**. The latter is used to pay off the **end of service amount** by settling it with the **payables account**."
msgid "The UAE localization package allows the generation of invoices in English, Arabic, or both. The localization also includes a line to display the **VAT amount** per line."
msgid ":ref:`Install <general/install>` the :guilabel:`UK - Accounting` and the :guilabel:`UK - Accounting Reports` modules to get all the features of the UK localization."
msgid "The UK chart of accounts is included in the :guilabel:`UK - Accounting` module. Go to :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts` to access it."
msgid "Setup your :abbr:`CoA (chart of accounts)` by going to :menuselection:`Accounting --> Configuration --> Settings --> Accounting Import section` and choose to :guilabel:`Review Manually` or :guilabel:`Import (recommended)` your initial balances."
msgid "Go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes` to update the :guilabel:`Default Taxes`, the :guilabel:`Tax Return Periodicity` or to :guilabel:`Configure your tax accounts`."
msgid "The **UK - Accounting Reports** module enables you to comply with the `HM Revenue & Customs <https://www.gov.uk/government/organisations/hm-revenue-customs/>`_ requirements regarding `Making Tax Digital <https://www.gov.uk/government/publications/making-tax-digital/overview-of-making-tax-digital/>`_."
msgid "If your periodic submission is more than three months late, it is no longer possible to submit it through Odoo, as Odoo only retrieves open bonds from the last three months. Your submission has to be done manually by contacting HMRC."
msgid "Go to :menuselection:`Accounting --> Reporting --> Tax report` and click on :guilabel:`Connect to HMRC`. Enter your company information on the HMRC platform. You only need to do it once."
msgid "You can use dummy credentials to demo the HMRC flow. To do so, activate the :ref:`developer mode <developer-mode>` and go to :menuselection:`General Settings --> Technical --> System Parameters`. From here, search for `l10n_uk_reports.hmrc_mode` and change the value line to `demo`. You can get such credentials from the `HMRC Developer Hub <https://developer.service.hmrc.gov.uk/api-test-user>`_."
msgid "Only one company and one user can connect to HMRC simultaneously. If several UK-based companies are on the same database, the user who submits the HMRC report must follow these instructions before each submission:"
msgid "Go to :guilabel:`General Settings`, and in the :guilabel:`Users` section, click :guilabel:`Manage Users`. Select the user who is connected to HMRC."
msgid "Go to the :guilabel:`UK HMRC Integration` tab and click :guilabel:`Reset Authentication Credentials` or :guilabel:`Remove Authentication Credentials` button."
msgid "Odoo embeds several **payment providers** that allow your customers to pay online, on their *customer portals*, or on your *eCommerce website*. They can pay sales orders, invoices, or subscriptions with recurring payments using their favorite payment methods, such as **credit cards**."
msgid "Odoo apps delegate the handling of sensitive information to the certified payment provider so that you don't ever have to worry about PCI compliance. No sensitive information (such as credit card numbers) is stored on Odoo servers or Odoo databases hosted elsewhere. Instead, Odoo apps use a unique reference number for the data stored safely in the payment providers' systems."
msgid "Some of these online payment providers can also be added as :doc:`bank accounts <../finance/accounting/bank>`, but this is **not** the same process as adding them as payment providers. Payment providers allow customers to pay online, and bank accounts are added and configured in the Accounting app to do a :doc:`bank reconciliation <accounting/bank/reconciliation>`."
msgid "In addition to the regular payment providers that integrate with an API, such as Stripe, PayPal, or Adyen, Odoo bundles the :doc:`Demo payment provider <payment_providers/demo>`. This payment provider allows you to test business flows involving online payments. No credentials are required as the demo payments are dummy payments."
msgid "When selected, Odoo displays your payment information with a payment reference. You have to approve the payment manually once you have received it in your bank account."
msgid "Go to the payment provider's website, create an account, and make sure you have the API credentials requested for third-party use. These are necessary for Odoo to communicate with the payment provider."
msgid "In Odoo, navigate to the :guilabel:`Payment providers` by going to :menuselection:`Accounting --> Configuration --> Payment Providers` or :menuselection:`Website --> Configuration --> Payment Providers`."
msgid "The fields available in the :guilabel:`Credentials` tab depend on the payment provider. Refer to the :ref:`related documentation <payment_providers/supported_providers>` for more information."
msgid "Once you have enabled the payment provider, it is automatically published on your website. If you wish to unpublish it, click the :guilabel:`Published` button. Customers cannot make payments through an unpublished provider, but they can still manage :dfn:`(delete and assign to a subscription)` their existing tokens linked to such a provider."
msgid "If you wish to try the payment provider as a test, set the :guilabel:`State` field in the payment provider form to :guilabel:`Test mode`, then enter your provider's test/sandbox credentials in the :guilabel:`Credentials` tab."
msgid "You can change the payment provider’s appearance on your website in the :guilabel:`Configuration` tab of the selected payment provider. Modify its name in the :guilabel:`Displayed as` field and adapt the :guilabel:`Supported Payment Icons` if necessary."
msgid ":ref:`If the payment provider supports this feature <payment_providers/online_providers>`, customers can save their payment method details for later. To enable this feature, go to the :guilabel:`Configuration` tab of the selected payment provider and enable :guilabel:`Allow Saving Payment Methods`."
msgid "In this case, a **payment token** is created in Odoo to be used as a payment method for subsequent payments without the customer having to enter their payment method details again. This is particularly useful for the eCommerce conversion rate and subscriptions that use recurring payments."
msgid "To add or delete their saved payment method details, customers can click :guilabel:`Manage payment methods` in the :ref:`customer portal <users-portal-payment-methods>`."
msgid "Odoo is not `PCI <https://www.pcisecuritystandards.org>`_ DSS-certified because it does not store cardholder data or process payments. Instead, it outsources tokenization and payment to :ref:`external payment providers <payment_providers/online_providers>`, which means that as an Odoo customer, you only need to complete the minimal Self-Assessment Questionnaire (SAQ) with the provider to obtain the Attestation of Compliance (AoC) and achieve PCI compliance. Odoo should not be mentioned as a payment processor or a third-party service provider in the :abbr:`SAQ (Self-Assessment Questionnaire)`."
msgid ":ref:`If the payment provider supports this feature <payment_providers/online_providers>`, you can authorize and capture payments in two steps instead of one. To enable this feature, go to the :guilabel:`Configuration` tab of the selected payment provider and enable :guilabel:`Capture Amount Manually`."
msgid "When you authorize a payment, the funds are reserved on the customer's payment method but not immediately charged. They are charged when you manually capture the payment later on. You can also void the authorization to cancel it and release the reserved funds. Capturing payments manually is helpful in many situations:"
msgid "To capture the payment after it was authorized, go to the related sales order or invoice and click the :guilabel:`Capture Transaction` button. To release the funds, click the :guilabel:`Void Transaction` button."
msgid "Some payment providers support capturing only part of the authorized amount. The remaining amount can then be either captured or voided. These providers have the value **Full and partial** in the :ref:`table above <payment_providers/online_providers>`. The providers that only support capturing or voiding the total amount have the value **Full only**."
msgid "The funds are likely not reserved forever. After a certain time, they may be automatically released back to the customer's payment method. Refer to your payment provider's documentation for the exact reservation duration."
msgid "If your payment provider supports this feature, you can refund payments directly from Odoo. It does not need to be enabled first. To refund a customer payment, navigate to it and click the :guilabel:`Refund` button."
msgid "Some payment providers support refunding only part of the amount. The remaining amount can then optionally be refunded, too. These providers have the value **Full and partial** in the :ref:`table above <payment_providers/online_providers>`. The providers that only support refunding the total amount have the value **Full only**."
msgid ":ref:`If the payment provider supports this feature <payment_providers/online_providers>`, you can allow customers to use the :guilabel:`Google Pay` and :guilabel:`Apple Pay` buttons and pay their eCommerce orders in one click. When they use one of these buttons, customers go straight from the cart to the confirmation page without filling out the contact form. They just have to validate the payment on Google's or Apple's payment form."
msgid "To enable this feature, go to the :guilabel:`Configuration` tab of the selected payment provider and enable :guilabel:`Allow Express Checkout`."
msgid ":ref:`If the payment provider supports this feature <payment_providers/online_providers>`, you can add extra fees to online transactions. Fees can be configured either as **fixed** amounts and percentages, **variable** amounts and percentages, or both simultaneously. They can also differ based on whether the transaction is **domestic** or **international**."
msgid "To enable this feature, go to the :guilabel:`Fees` tab of the selected payment provider, enable :guilabel:`Add Extra Fees`, and configure the settings to your liking."
msgid "You can adapt the payment provider's availability by specifying the :guilabel:`Maximum Amount` allowed and modifying the :guilabel:`Currencies` and :guilabel:`Countries` in the :guilabel:`Configuration` tab."
msgid "All payment providers have a different list of available currencies and countries. They serve as a first filter during payment operations, i.e., the payment methods linked to the payment provider are not available for selection if the customer's currency or country is not in the supported list. As there might be errors, updates, and unknowns in the lists of available currencies and countries, adding or removing a payment provider's supported currencies or countries is possible."
msgid ":ref:`Payment methods <payment_providers/payment_methods>` also have their own list of available currencies and countries that serves as another filter during payment operations."
msgid "If the list of supported currencies or countries is empty, it means the list is too long to be displayed, or Odoo does not have information on that payment provider. The payment provider remains available, even though it is possible the payment will be refused at a later stage should the country or currency not be supported."
msgid "You can restrict the :guilabel:`Maximum Amount` that can be paid with the selected provider. Leave the field to `0.00` to make the payment provider available regardless of the payment amount."
msgid "This feature is not intended to work on pages that allow the customer to update the payment amount, e.g., the **Donation** snippet and the **Checkout** page when paid :doc:`shipping methods <../websites/ecommerce/checkout_payment_shipping/shipping>` are enabled."
msgid "A :doc:`payment journal <accounting/bank>` must be defined for the payment provider to record the payments on an **outstanding account**. To do so, go to the :guilabel:`Configuration` tab of the selected payment provider and select a :guilabel:`Payment Journal`."
msgid "From an accounting perspective, there are two types of online payment workflows: the payments that are directly deposited into your bank account and follow the usual :doc:`reconciliation <accounting/bank/reconciliation>` workflow, and those coming from third-party :ref:`online payment providers <payment_providers/online_providers>` and require you to follow another accounting workflow. For these payments, you need to consider how you want to record your payments' journal entries. We recommend you ask your accountant for advice."
msgid "By default, the :guilabel:`Bank Account` defined for the :ref:`payment journal <payment_providers/journal>` is used, but you can also specify an :ref:`outstanding account <bank/outstanding-accounts>` for each payment provider to separate the provider's payments from other payments."
msgid "Adyen works only with customers processing **more** than **10 million annually** or invoicing a **minimum** of **1.000** transactions **per month**."
msgid "If you are trying Adyen as a test, with an Adyen *test account*, head to :menuselection:`Accounting --> Configuration --> Payment Providers`. There, click on :guilabel:`Adyen`, enable :guilabel:`Test Mode` and enter your credentials in the :guilabel:`Credentials` tab."
msgid "Go to :menuselection:`Server settings --> Authentification` and copy or generate your **API Key**. Be careful to copy your API key as you'll not be allowed to get it later without generating a new one."
msgid "Now, head to :menuselection:`Client settings --> Authentification` and cody or generate your **Client Key**. This is also the place where you can :ref:`allow payments to be made from your website <adyen/allowed_origins>`."
msgid "In order to retrieve the HMAC Key, you'll need to configure a `Standard Notification` webhook. For this, log into your Adyen account then go to :menuselection:`Developers --> Webhooks --> Add webhook --> Add Standard notification`."
msgid "Then enter :menuselection:`Security --> HMAC Key --> Generate`. Be careful to copy the key as you will not be allowed to do it later without generating a new one."
msgid "In the :guilabel:`Checkout API URL` field, enter the following URL and replace `yourprefix` with the prefix you previously saved: `https://yourprefix-checkout-live.adyenpayments.com/checkout`"
msgid "In the :guilabel:`Recurring API URL` field, enter the following URL and replace `yourprefix` with the prefix you previously saved: `https://yourprefix-pal-live.adyenpayments.com/pal/servlet/Recurring`."
msgid "To allow payment originated from your website, follow the steps in :ref:`adyen/api_and_client_keys` to navigate to your API user and go to :menuselection:`Add allowed origins`, then add the URLs from where payments will be made (the URLs of the servers hosting your Odoo instances)."
msgid "To set it up, enable the **Capture Amount Manually** option on Odoo, as explained in the :ref:`payment providers documentation <payment_providers/manual_capture>`."
msgid "If you configure Odoo to capture amounts manually, make sure to set the **Capture Delay** to **manual** on Adyen. Otherwise, the transaction will be blocked in the authorized state in Odoo."
msgid "Odoo doesn't support the partial capture yet. Be aware that if you make a partial capture from Adyen's interface, Odoo will manage it as if it was a full capture."
msgid "If you are trying Alipay as a test, in the *sandbox*, change the **State** to *Test Mode*. We recommend doing this on a test Odoo database, rather than on your main database."
msgid "`Amazon Payment Services <https://paymentservices.amazon.com/>`_ or APS is an online payment provider established in Dubai offering several online payment options."
msgid "Log into your `Amazon Payment Services Dashboard <https://fort.payfort.com/>`_ and go to :menuselection:`Integration Settings --> Security Settings`. Generate the :guilabel:`Access Code` if none has been generated yet. Copy the values of the :guilabel:`Merchant Identifier`, :guilabel:`Access Code`, :guilabel:`SHA Request Phrase` and :guilabel:`SHA Response Phrase` fields, and save them for later."
msgid "Enter your Odoo database URL in the :guilabel:`Origin URL`, for example: `https://yourcompany.odoo.com/`. Then, click on :guilabel:`Save Changes`."
msgid "Navigate to :menuselection:`Integration Settings --> Technical Settings` and click on :guilabel:`Redirection`. Make sure :guilabel:`Status` is set to `Active` and select your preferred payment methods underneath in :guilabel:`Payment Options`."
msgid "Set :guilabel:`Send Response Parameters` to :guilabel:`Yes` and enter your database URL followed by `/payment/aps/return` in the :guilabel:`Redirection URL`."
msgid "Enter your database URL followed by `/payment/aps/webhook` in the :guilabel:`Direct Transaction Feedback` and :guilabel:`Notification URL` fields."
msgid "Under :menuselection:`Integration Settings --> Payment Page Template` you can customize the look and feel of the Amazon Payment Services payment page (where customers fill out their credit card details during payment)."
msgid ":ref:`Navigate to the payment provider Amazon Payment Services <payment_providers/add_new>`, change its state to :guilabel:`Enabled`, and make sure it is :guilabel:`Published`."
msgid "In the :guilabel:`Credentials` tab, fill the :guilabel:`Merchant Identifier`, :guilabel:`Access Code`, :guilabel:`SHA Request Phrase` and :guilabel:`SHA Response Phrase` with the values you saved at the step :ref:`payment_providers/aps/configure-dashboard`."
msgid "`AsiaPay <https://www.asiapay.com/>`_ is an online payments provider established in Hong Kong and covering several Asian countries and payment methods."
msgid "Log into `AsiaPay Dashboard <https://www.paydollar.com/b2c2/eng/merchant/index.jsp>`_ and go to :menuselection:`Profile --> Account Information`. Copy the values of the :guilabel:`Currency` and :guilabel:`Secure Hash` fields and save them for later."
msgid "In the :guilabel:`Credentials` tab, fill the :guilabel:`Merchant ID`, :guilabel:`Currency`, and :guilabel:`Secure Hash Secret` with the values you saved at the step :ref:`payment_providers/asiapay/configure_dashboard`."
msgid "By default, the payment provider AsiaPay is configured to verify the secret hash with the hash function `SHA1`. If a different function is :ref:`set on your account <payment_providers/asiapay/configure_dashboard>`, activate the :ref:`developer mode <developer-mode>` and set the same value to the field :guilabel:`Secure Hash Function` in Odoo."
msgid "`Authorize.Net <https://www.authorize.net>`_ is a United States-based online payment solution provider, allowing businesses to accept **credit cards**."
msgid "To retrieve them, log into your Authorize.Net account, go to :menuselection:`Account --> Settings --> Security Settings --> API Credentials & Keys`, generate your **Transaction Key** and **Signature Key**, and paste them on the related fields in Odoo. Then, click on **Generate Client Key**."
msgid "To test Authorize.Net with a *sandbox* account, change the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, rather than on your main database."
msgid "If you use the :guilabel:`Test Mode` with a regular account, it results in the following error: *The merchant login ID or password is invalid or the account is inactive*."
msgid "With Authorize.Net, you can enable the :ref:`manual capture <payment_providers/manual_capture>`. If enabled, the funds are reserved for 30 days on the customer's card, but not charged yet."
msgid "To give customers the possibility to pay using ACH, `sign up for Authorize.Net eCheck's service <https://www.authorize.net/payments/echeck.html>`_. Once eCheck is activated, duplicate the previously configured Authorize.Net payment provider on Odoo by going to :menuselection:`Accounting --> Configuration --> Payment Providers --> Authorize.net --> ⛭ Action --> Duplicate`. Then, change the provider's name to differentiate both versions (e.g., `Authorize.net - Banks`)."
msgid "When ready, change the provider's :guilabel:`State` to :guilabel:`Enabled` for a regular account or :guilabel:`Test Mode` for a sandbox account."
msgid "Define an export range using an *opening* and *closing* batch settlement. All transactions within the two batch settlements will be exported to Odoo."
msgid "Select all transactions within the desired range, copy them, and paste them into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import template <authorize-import-template>`."
msgid "In this case, the first batch (01/01/2021) of the year belongs to the settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020."
msgid "Under the :guilabel:`Settlement Date` section, select the previously used range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:` fields and click :guilabel:`Search`."
msgid "In the pop-up window, select :guilabel:`Expanded Fields with CAVV Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and click :guilabel:`Submit`."
msgid "Open the text file, select :guilabel:`All`, copy the data, and paste it into the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template <authorize-import-template>`."
msgid "Transit lines are automatically filled in and updated in the :guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets of the :ref:`Excel import template <authorize-import-template>`. Make sure all entries are present, and **if not**, copy the formula from previously filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` sheets and paste it into the empty lines."
msgid "Copy the data from the :guilabel:`transit for report 2` sheet and use *paste special* to only paste the values in the :guilabel:`Odoo Import to CSV` sheet."
msgid "Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are chargeback entries without any reference number. As they cannot be imported as such, go to :menuselection:`Authorize.Net --> Account --> Statements --> eCheck.Net Settlement Statement`."
msgid "Copy the invoice description, paste it into the :guilabel:`Label` cell of the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the description."
msgid "If there are multiple invoices, add a line into the :ref:`Excel import template <authorize-import-template>` for each invoice and copy/paste the description into each respective :guilabel:`Label` line."
msgid "For **combined chargeback/returns** in the payouts, create a new line in the :ref:`Excel import template <authorize-import-template>` for each invoice."
msgid "Next, delete *zero transaction* and *void transaction* line items, and change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo Import to CSV` sheet to *Number*."
msgid "Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a Transaction` and search again for the previously used batch settlements dates."
msgid "Verify that the batch settlement dates on eCheck.Net match the related payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo Import to CSV`."
msgid "Copy the data - column headings included - from the :guilabel:`Odoo Import to CSV` sheet, paste it into a new Excel file, and save it using the CSV format."
msgid "Open the Accounting app, go to :menuselection:`Configuration --> Journals`, tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites --> Import records --> Load file`. Select the CSV file and upload it into Odoo."
msgid "Log into `Buckaroo Plaza <https://plaza.buckaroo.nl>`_, go to :menuselection:`My Buckaroo --> Websites` and select the :guilabel:`Push settings` tab."
msgid "Enter the URL of your Odoo database, followed by `/payment/buckaroo/webhook` in both the :guilabel:`Push URI Success/Pending` and :guilabel:`Push URI Failure` text fields. For example: `https://yourcompany.odoo.com/payment/buckaroo/webhook`."
msgid "In the :guilabel:`General` tab, copy the website :guilabel:`Key` (i.e., the key used to uniquely identify your website with Buckaroo) and save it for later."
msgid "Go to :menuselection:`Configuration --> Security --> Secret key`, enter or :guilabel:`Generate` a :guilabel:`Secret key` and click :guilabel:`Save`. Save the key for later."
msgid "In the :guilabel:`Credentials` tab, fill the :guilabel:`Website Key` and :guilabel:`Secret Key` fields with the values you saved at the step :ref:`payment_providers/buckaroo/configure_dashboard`."
msgid "Upon checkout or when paying a bill online, you can choose the payment outcome when using the demo payment provider. To do so, click on the :guilabel:`Payment Status` drop-down menu and select the desired outcome."
msgid "If you selected :guilabel:`Pending` as **payment outcome**, you can change the state of the transaction straight from its form view. To access a transaction's form view, activate the :ref:`developer mode <developer-mode>`, and go to :menuselection:`Accounting / Website --> Configuration --> Payment Transactions`. Then, change the status of a transaction by clicking on the state bar (:guilabel:`Draft, Pending, Authorized, Confirmed, Canceled, Error`)."
msgid "`Flutterwave <https://flutterwave.com/>`_ is an online payments provider established in Nigeria and covering several African countries and payment methods."
msgid "Log into `Flutterwave Dashboard <https://dashboard.flutterwave.com/>`_ and go to :menuselection:`Settings --> API`. Copy the values of the :guilabel:`Public Key` and :guilabel:`Secret Key` fields and save them for later."
msgid "Go to :menuselection:`Settings --> Webhooks` and enter your Odoo database URL followed by `/payment/flutterwave/webhook` in the :guilabel:`URL` text field."
msgid "In the :guilabel:`Credentials` tab, fill the :guilabel:`Public Key`, :guilabel:`Secret Key`, and :guilabel:`Webhook Secret` with the values you saved at the step :ref:`payment_providers/flutterwave/configure_dashboard`."
msgid "If you choose to allow saving payment methods, it is recommended to only enable card payments from Flutterwave dashboard, as only cards can be saved as payment tokens. To do so, go to your Flutterwave Dashboard and then to :menuselection:`Settings --> Account Settings`."
msgid "`Mercado Pago <https://www.mercadopago.com/>`_ is an online payment provider covering several countries, currencies and payment methods in Latin America."
msgid "Select :guilabel:`Credenciales de producción` in the left part of the application page, then select the industry, optionally enter your domain, and click :guilabel:`Activar credenciales de producción`."
msgid "If you are trying Mercado Pago as a test, select :guilabel:`Credienciales de prueba` in the left part of the application page, then copy the test :guilabel:`Access token`."
msgid "In the :guilabel:`Credentials` tab, fill in the :guilabel:`Access Token` with the value you saved at the :ref:`payment_providers/mercado_pago/configure_dashboard` step."
msgid "To retrieve your API key, log into your Mollie account, go to :menuselection:`Developers --> API keys`, and copy your Test or Live **API Key**."
msgid "If you are trying Mollie as a test, with the Test API key, change the **State** to *Test Mode*. We recommend doing this on a test Odoo database, rather than on your main database."
msgid "`Ogone <https://www.ingenico.com/>`_, also known as **Ingenico Payment Services** is a France-based company that provides the technology involved in secure electronic transactions."
msgid "You need to create an **API user** to be used in the creation of transactions from Odoo. While you can use your main account to do so, using an **API user** ensures that if the credentials used in Odoo are leaked, no access to your Ogone configuration is possible. Additionally, passwords for **API users** do not need to be updated regularly, unlike normal users."
msgid "To create an **API user**, go to :menuselection:`Configuration --> Users` and click on :guilabel:`New User`. The following fields must be configured:"
msgid "After the creation of the user, you are required to generate a password. Save the password and **UserID**, as they will be required later on during the setup."
msgid "If you already have an user set up, make sure it is activated without any error. If not, simply click the :guilabel:`Activate(Errors)` button to reset the user."
msgid "Ogone must now be configured to accept payments from Odoo. Head to :menuselection:`Configuration --> Technical Information --> Global Security Parameters`, select :guilabel:`SHA-512` as :guilabel:`Hash Algorithm` and :guilabel:`UTF-8` as :guilabel:`character encoding`. Then, go to the :guilabel:`Data and Origin verification` tab of the same page and leave the URL field of the :guilabel:`e-Commerce and Alias Gateway` section blank."
msgid "If you need to use another algorithm, such as `sha-1` or `sha-256`, within Odoo, activate the :ref:`developer mode <developer-mode>` and go to the **Payment Providers** page in :menuselection:`Accounting --> Configuration --> Payment Providers`. Click on :guilabel:`Ogone`, and in the :guilabel:`Credentials` tab, select the algorithm you wish to use in the :guilabel:`Hash function` field."
msgid "You are now required to generate **SHA-IN** passphrases. **SHA-IN** and **SHA-OUT** passphrases are used to digitally sign the transaction requests and responses between Odoo and Ogone. By using these secret passphrases and the `sha-1` algorithm, both systems can ensure that the information they receive from the other was not altered or tampered with."
msgid "Enter the same **SHA-IN** passphrase in both :guilabel:`Checks for e-Commerce & Alias Gateway` and :guilabel:`Checks for DirectLink and Batch (Automatic)`. You can leave the IP address field blank."
msgid "Your **SHA-IN** and **SHA-OUT** passphrases should be different, and between 16 and 32 characters long. Make sure to use the same **SHA-IN** and **SHA-OUT** passphrases throughout the entire Ogone configuration, as Odoo only allows a single **SHA-IN** and single **SHA-OUT** passphrase."
msgid "In order to retrieve the **SHA-OUT** key, log into your Ogone account, go to :menuselection:`Configuration --> Technical Information --> Transaction feedback --> All transaction submission modes`, and get or generate your **API Key** and **Client Key**. Be careful to copy your API key as you’ll not be allowed to get it later without generating a new one."
msgid "The :guilabel:`URL` fields for :guilabel:`HTTP redirection in the browser` can be left empty, as Odoo will specify these URLs for every transaction request."
msgid "Both **URL** fields should contain the same following URL, with `<example>` replaced by your database: `https://<example>/payment/ogone/return`."
msgid ":guilabel:`Dynamic eCommerce Parameters` should contain the following values: `ALIAS`, `AMOUNT`, `CARDNO`, `CN`, `CURRENCY`, `IP`, `NCERROR` `ORDERID`, `PAYID`, `PM`, `STATUS`, `TRXDATE`. Other parameters can be included (if you have another integration with Ogone that requires them), but are not advised."
msgid "To allow your customers to save their credit card credentials for future use, head to :menuselection:`Configuration --> Alias --> My alias information`. From this tab, you can configure how the user can have its card details saved, for how long the information is saved, if a checkbox to save the card information should be displayed, etc."
msgid "To set up Ogone in Odoo, head to :menuselection:`Accounting --> Configuration --> Payment Providers` and open the Ogone provider. In the :guilabel:`Credentials` tab, enter the **PSPID** of your Ogone account, and fill out the other fields as configured in your :ref:`Ogone portal <ogone/ogone>`."
msgid "`Paypal <https://www.paypal.com/>`_ is an American online payment provider available worldwide, and one of the few that does not charge a subscription fee."
msgid "While PayPal is available in `over 200 countries/regions <https://www.paypal.com/webapps/mpp/country-worldwide>`_, only `a selection of currencies are supported <https://developer.paypal.com/docs/reports/reference/paypal-supported-currencies>`_."
msgid "To access your PayPal account settings, log into PayPal, open the :guilabel:`Account Settings`, and open the :guilabel:`Website payments` menu."
msgid "Note that for PayPal to work **in Odoo**, the options :ref:`Auto Return <paypal/auto-return>`, :ref:`PDT <paypal/pdt>`, and :ref:`IPN <paypal/ipn>` **must** all be enabled."
msgid "From :guilabel:`Website payments`, go to :menuselection:`Website preferences --> Update --> Auto return for website payments --> Auto return` and select :guilabel:`On`. Enter the address of your Odoo database (e.g., `https://yourcompany.odoo.com`) in the :guilabel:`Return URL` field, and :guilabel:`Save`."
msgid ":abbr:`PDT (Payment Data Transfer)` allows to receive payment confirmations, displays the payment status to the customers, and verifies the authenticity of the payments. From :menuselection:`Website preferences --> Update`, scroll down to :guilabel:`Payment data transfer` and select :guilabel:`On`."
msgid "PayPal displays your **PDT Identity Token** as soon as :ref:`Auto return <paypal/auto-return>` and :ref:`Payment Data Transfer (PDT) <paypal/pdt>` are enabled. If you need the **PDT Identity Token**, disable and re-enable :guilabel:`Payment data transfer` to display the token again."
msgid ":abbr:`IPN (Instant Payment Notifications)` is similar to **PDT**, but allows for more notifications, such as chargeback notifications. To enable **IPN**, go to :menuselection:`Website payments --> Instant payment notifications --> Update` and click :guilabel:`Choose IPN settings`. Enter a :guilabel:`Notification URL`, select :guilabel:`Receive IPN messages (Enabled)`, and :guilabel:`Save`."
msgid "We advise not to prompt customers to log in with a PayPal account upon payment. It is better and more accessible for customers to pay with a debit/credit card. To disable that prompt, go to :menuselection:`Account Settings --> Website payments --> Update` and select :guilabel:`On` for :guilabel:`PayPal account optional`."
msgid "If you use accented characters (or anything other than primary Latin characters) for customer names or addresses, then you **must** configure the encoding format of the payment request sent by Odoo to PayPal. If you do not, some transactions fail without notice."
msgid "To do so, go to `your production account <https://www.paypal.com/cgi-bin/customerprofileweb ?cmd=_profile-language-encoding>`_. Then, click :guilabel:`More Options` and set the two default encoding formats as :guilabel:`UTF-8`."
msgid "Configure your :ref:`Paypal Sandbox account <paypal/testing>`, then follow this `link <https://sandbox.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`_ to configure the encoding format in a test environment."
msgid "Odoo needs your **API Credentials** to connect with your PayPal account. To do so, go to :menuselection:`Accounting --> Configuration --> Payment Providers` and :guilabel:`Activate` PayPal. Then, enter your PayPal account credentials in the :guilabel:`Credentials` tab:"
msgid "To set the :guilabel:`PDT Identity Token`, switch to :ref:`developer mode <developer-mode>` and retrieve the token by following the configuration steps at :ref:`paypal/pdt`."
msgid "If you are trying PayPal as a test, using a :ref:`PayPal Sandbox account <paypal/testing>`, change the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database rather than on your main database."
msgid "You can charge :ref:`extra fees <payment_providers/extra_fees>` to customers choosing to pay with PayPal in order to cover the transaction fees PayPal charges you."
msgid "`Traders in the EU <https://europa.eu/youreurope/citizens/consumers/shopping/pricing-payments/index_en.htm>`_ are not allowed to charge extra fees for paying with credit cards."
msgid "Log into PayPal sandbox using the merchant account and follow the same configuration instructions. Enter your sandbox credentials in Odoo (:menuselection:`Accounting --> Configuration --> Payment Providers --> PayPal` in the :guilabel:`Credentials` tab, and make sure the status is set on :guilabel:`Test Mode`. We recommend doing this on a test Odoo database rather than your main database."
msgid "Log into `Razorpay Dashboard <https://dashboard.razorpay.com/>`_ and go to :menuselection:`Settings --> API Keys`. Generate the new keys and copy the values of the :guilabel:`Key Id` and :guilabel:`Secret Key` fields and save them for later."
msgid "Go to :menuselection:`Settings --> Webhooks`, click on :guilabel:`Create New Webhook`, and enter your Odoo database URL followed by `/payment/razorpay/webhook` in the :guilabel:`Webhook URL` text field."
msgid "Make sure the :guilabel:`payment.authorized`, :guilabel:`payment.captured`, :guilabel:`payment.failed`, :guilabel:`refund.failed` and :guilabel:`refund.processed` checkboxes are ticked."
msgid "In the :guilabel:`Credentials` tab, fill the :guilabel:`Key Id`, :guilabel:`Key Secret`, and :guilabel:`Webhook Secret` with the values you saved at the step :ref:`payment_providers/razorpay/configure_dashboard`."
msgid "You can copy your credentials from your SIPS environment info documentation, in the section **PROD**, and paste them in the related fields under the **Credentials** tab."
msgid "If you are trying SIPS as a test, with the *TEST* credentials, change the **State** to *Test Mode*. We recommend doing this on a test Odoo database, rather than on your main database."
msgid "`Stripe <https://stripe.com/>`_ is a United States-based online payment solution provider allowing businesses to accept **credit cards** and other payment methods."
msgid "At the end of the process, click :guilabel:`Agree and submit`. If all requested information has been submitted, you are then redirected to Odoo, and your payment provider is enabled."
msgid "To use an existing Stripe account, :ref:`activate the Developer mode <developer-mode>` and :ref:`enable Stripe manually <payment_providers/add_new>`. You can then :ref:`Fill in your credentials <stripe/api_keys>`, :ref:`generate a webhook <stripe/webhook>`, and enable the payment provider."
msgid "You can also test Stripe using the :ref:`payment_providers/test-mode`. To do so, first, `log into your Stripe dashboard <https://dashboard.stripe.com/dashboard>`_ and switch to the **Test mode**. Then, in Odoo, :ref:`activate the Developer mode <developer-mode>`, :ref:`navigate to the payment provider Stripe <payment_providers/supported_providers>`, :ref:`fill in your API credentials <stripe/api_keys>` with the test keys, and set the :guilabel:`State` field to :guilabel:`Test Mode`."
msgid "Go to `the API keys page on Stripe <https://dashboard.stripe.com/account/apikeys>`_, or log into your Stripe dashboard and go to :menuselection:`Developers --> API Keys`."
msgid "In the :guilabel:`Credentials` tab, fill in the :guilabel:`Publishable Key` and :guilabel:`Secret Key` fields with the values you previously saved."
msgid "Go to the `Webhooks page on Stripe <https://dashboard.stripe.com/webhooks>`_, or log into your Stripe dashboard and go to :menuselection:`Developers --> Webhooks`."
msgid "In the :guilabel:`Hosted endpoints` section, click :guilabel:`Add endpoint`. Then, in the :guilabel:`Endpoint URL` field, enter your Odoo database's URL, followed by `/payment/stripe/webhook`, e.g., `https://yourcompany.odoo.com/payment/stripe/webhook`."
msgid "in the :guilabel:`Payment intent` section: :guilabel:`payment_intent.amount_capturable_updated`, :guilabel:`payment_intent.succeeded` and :guilabel:`payment_intent.payment_failed`;"
msgid "To adapt the list of enabled payment methods, go to the :guilabel:`Configuration` tab and edit the list of :guilabel:`Supported Payment Icons`."
msgid "If a payment icon record does not exist in the database and its related local payment method is listed above, it is automatically enabled with Stripe."
msgid "To allow customers to use the Apple Pay button to pay their eCommerce orders, go to the :guilabel:`Configuration` tab, enable :guilabel:`Allow Express Checkout`, and click :guilabel:`Enable Apple Pay`."
msgid "The **Wire transfer** payment method allows you to provide payment instructions to your customers, such as the bank details and communication. They are displayed:"
msgid "at the end of the checkout process, once the customer has selected :guilabel:`Wire transfer` as a payment method and clicked the :guilabel:`Pay now` button:"
msgid "While this method is very accessible and requires minimal setup, it is very inefficient process-wise. We recommend setting up a :doc:`payment provider <../payment_providers>` instead."
msgid "Online orders remain in the :guilabel:`Quotation sent` (i.e., unpaid order) stage until you receive the payment and :guilabel:`Confirm` the order."
msgid "**Wire transfer** can be used as a template for other payment methods that are processed manually, such as checks, by renaming or duplicating it."
msgid "To configure **Wire Transfer**, go to :menuselection:`Accounting / Website --> Configuration --> Payment Providers`, and open the :guilabel:`Wire Transfer` card. Then, in the :guilabel:`Configuration` tab:"
msgid "If you have already defined :doc:`a bank account <../accounting/bank>`, the account number will be automatically added to the default message generated by Odoo."
